We're currently in the process of moving our PDC as well as removing some of the burdens the old server holds (SQL, DNS, DHCP, WINS, etc). The old server will eventually become soley an Exchange server. There is also a secondary domain/active directory server on our network. Both of the current domain controllers are Win2k. The new server is Win2003.
I've already successfully moved DNS, DHCP, and WINS to the new server. However, when I go to setup Active Directory on the new 2003 server, it appears as though the network card's drivers aren't loading properly. The system boots up with several errors related network connectivity. DHCP also fails to start for some reason. You cannot ping out of the server, however you can ping the 2003 machine from any other computer on the network. You can also ping loopback and the interfaces own address from the 2003 server.
One very odd thing that I have noted is that if you plug the network cable into the second, unused interface everything works fine...that is, until you restart the server. Then we get the same problems. As a note, you cannot remove the active directory role from the server until you switch network interfaces again as the server cannot connect to the pdc. I've checked all of the network settings for each interface and even reinstalled the drivers to no avail.
The only signifigant message in Event Viewer relates directly to connectivity issues with the PDC. There is nothing about a failed driver load or anything else usefull. It's already obvious that if the network card is having issues that the server won't be able to connect to any other domain controllers.
Has anyone seen anything like this before?
I've already successfully moved DNS, DHCP, and WINS to the new server. However, when I go to setup Active Directory on the new 2003 server, it appears as though the network card's drivers aren't loading properly. The system boots up with several errors related network connectivity. DHCP also fails to start for some reason. You cannot ping out of the server, however you can ping the 2003 machine from any other computer on the network. You can also ping loopback and the interfaces own address from the 2003 server.
One very odd thing that I have noted is that if you plug the network cable into the second, unused interface everything works fine...that is, until you restart the server. Then we get the same problems. As a note, you cannot remove the active directory role from the server until you switch network interfaces again as the server cannot connect to the pdc. I've checked all of the network settings for each interface and even reinstalled the drivers to no avail.
The only signifigant message in Event Viewer relates directly to connectivity issues with the PDC. There is nothing about a failed driver load or anything else usefull. It's already obvious that if the network card is having issues that the server won't be able to connect to any other domain controllers.
Has anyone seen anything like this before?