Problem With Manually Set Network Connection Getting A 169 Address

D

designersystems

New member
Joined
May 23, 2011
Messages
4
Location
Massachusetts
I am running a 2008 Server as a DC with DNS and manually set the IP address on LAN #1 to 192.168.1.150. After rebooting the server, the network connection is showing connected but when I click on the Details button, it shows a 169 IP address and the Default Gateway is now blank.

I am able to use the LAN #2 temporarily.

Anyone having the same problem?
 
Hi there,

Can you tell me if there are any entry on event viewer? How you can temporary fix this problem until reboot?(if you can do this)
 
ICTCity said:
Hi there,

Can you tell me if there are any entry on event viewer? How you can temporary fix this problem until reboot?(if you can do this)
Click to expand...

There are no errors in the Application or System logs. There are errors in the DNS log. which I expected.
Temporarily I am able to use LAN #2 using a different IP. I haven't tried to use the 150 address on LAN #2 yet. I want to fix the problem.
 
Are you running a physical or virtual server?

Can you uninstall your Nic and reinstall? When you have noticed this problem? Have you done something like bonding before adding DNS role?
 
ICTCity said:
Are you running a physical or virtual server?

Can you uninstall your Nic and reinstall? When you have noticed this problem? Have you done something like bonding before adding DNS role?
Click to expand...

I am running a physical machine. I didn't uninstall and reinstall the nic because this server is being used. It has been an ongoing problem which the customer is getting frustrated about. I am not familiar with "bonding". Added the DNS as part of the AD promotion.
 
If you can use the other Nic, you can uninstall the other. Not?

Bonding is "merge" 2 physical Nic which will appear as one single.

before adding the dns/ad role the problem was the same?
 
ICTCity said:
If you can use the other Nic, you can uninstall the other. Not?

Bonding is "merge" 2 physical Nic which will appear as one single.

before adding the dns/ad role the problem was the same?
Click to expand...

I haven't tried to uninstall the 1st nic yet. A little leary doing that remotely. But I may have to do that.

We do not bond them, we leave them separate for this particular reason. If one fails, we have the other.

Cannot say if the problem existed before the dns/ad role. Didn't check it at that time.

Could possible be a hardware issue. My boss is having me call Dell. There is a service contract on this server.
 
a bond is created for this reason, if one fails, the other still works. With Dell the name may be different, but essentially it will be the same thing. You will have to connect 2 cables and, as said before, in case of a failure of one Nic the other will work.

Uninstall the Nic and reinstall, if this doesn't help, contact the support but I don't think this is a hardware problem...
 
Back
Top