Hello,

Afraid (but also hoping) a solution will be painfully obvious, but here goes...
Have a Win 2003 Server where motherboard fried. Replaced with identical
Motherboard... has onboard WLAN connections (2) only one used. Connected
Network cable and fired up. Problem is... cannot connect to network/domain.
Can ping self (localhost) but cannot ping any other computer on network, it
Times out. When pinging IP address of another computer on network, it
Recognizes qualified name of other computer but still times out.
Have tried deleting computer account in Active Directory on Server and recreating.
Tried leaving domain, joining "workgroup" and cannot come back to domain. "Cannot connect to a domain controller". Any push in the right direction will be greatly appreciated.

Hattie

Your IP configuration is incorrect. Make sure that the IP address of the server is the same as it used to be and that your internal DNS information is also correct. Without DNS, your server can not see the Domain entries required to know who the domain controller is. The AD Infrastructure information is also saved into the AD integrated DNS information.

Chuck,

Thanks for answering. Funny thing is, absolutely nothing has been touched in IP settings on client computer or server, nor have any settings been touched in AD or DNS on server. The only thing that was touched was the motherboard on the client computer was swapped for identical.

Chuck,

Thanks for answering. Funny thing is, absolutely nothing has been touched in IP settings on client computer or server, nor have any settings been touched in AD or DNS on server. The only thing that was touched was the motherboard on the client computer was swapped for identical.

Hi,

I did not diagnosed the actual problem yet but still try the following :

1. Is there any firewall? Turn it off.
2. Is your computer has Wlan card and wired lan card? If so, disable your WLAN and try to connect it with wire. Connecting with both can create routing problem.


Also please provide the output of the following commands :

1. ipconfig /ALL
2. route PRINT
3. arp -a
4. tracert <Your domain controller>

Did u re-install the windows?
Can u provide the network diagram? How your server 2003 and AD servers are connected to? Switches, routers etc...

Thanks.

Aley,

Thank you for your answer. Problem has been solved this weekend. We still cannot figure out why, unless the onboard WLAN of the new motherboard was faulty. What we did was to disable the onboard WLAN and install a basic ethernet PCI adapter. Problem solved! The trickiest part was finding an x64 driver for the adapter as we are running Win 2003 Server x64.

Thanks to all who wrote and viewed.