|
Question : Windows Server 2003 DHCP Problems
|
|
We recently were hit by a virus that symantec removed from the server. To make sure it was off of the server I unplugged the network cable to the server. After hooking it up all seemed well, until yesterday I recieved a phone call stating that randomly computers were unable to login to the domain. I connected to the server and saw that all the fsmo roles were no longer on the server and had the word ERROR, and when I tried to transfer I was told it was not possible because the computer that held them was offline. So I seized all the roles, and thought this would cure the problem.
To my suprise nothing happened, so I reset DHCP and unplugged all switches and routers. When I did this a computer that previously wouldnt logon, went in fine, ran the script and all. Then I logged out, to try it again it worked fine. After five minutes I retried and it would not go in. This computer was a Windows 98 computer.
Well I have found some interesting things that may help find the problem, but my brain is trying to figure it out and right now is unable to.
The server has a static ip, however when I open up command prompt on the server and try to ping it using its name I get the 169.254.x.x which tells me it is having problems finding the dhcp server...(It is the DHCP server)
If I ping it by name from a computer that is windows xp and logging in ok, It pings the proper address. From the server if I ping it, using its IP Address it pings fine.
Also, I am unable to access network drives on the server. I can from time to time but periodically only. When I try to double click them to establish connection I get the error "The local device name is already in use"
I checked the event log, and it is in there for NetBT. It says a duplicate name has been detected on the TCP Network. The ip address of the machine that sent the message is there. I check the nbtstat -n and it basically is tell me the 169.254 is there as well as the correct ip address. Here is the output:
Node IpAddress: [169.254.20.133] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
WGJH_SERVER <00> UNIQUE Conflict
WGJH_SERVER <20> UNIQUE Conflict
WGJH <00> GROUP Registered
WGJH <1C> GROUP Registered
WGJH <1B> UNIQUE Registered
WGJH <1E> GROUP Registered
WGJH_SERVER <03> UNIQUE Conflict
WGJH <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
ADMINISTRATOR <03> UNIQUE Registered
Local Area Connection:
Node IpAddress: [10.93.96.7] Scope Id: []
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
WGJH_SERVER <00> UNIQUE Conflict
WGJH_SERVER <20> UNIQUE Conflict
WGJH <00> GROUP Registered
WGJH <1C> GROUP Registered
WGJH <1B> UNIQUE Registered
WGJH <1E> GROUP Registered
WGJH_SERVER <03> UNIQUE Conflict
WGJH <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered
ADMINISTRATOR <03> UNIQUE Registered
If anyone has any idea at all of where to look I would really appreciate it. I think the problem lies somewhere with that ip address conflict, but I can not figure out why it is using that 169.254 default for no dhcp server address, as well as the normal address.
Thanks,
Chad
If I could offer 2000 points i would!
|
Answer : Windows Server 2003 DHCP Problems
|
|
Is this server Multi-homed? - If so, have you tried disabling one of the NIC's?
Have you looked in WINS or DHCP Admin tools for your servers name / IP? If you find it, have you tried removing them.
|
|
|
|
|
