chinatti
MIS
- Feb 15, 2007
- 1
Hi,
I'm having problems with a new Win2003 Server Standard R2 that I'm adding to an existing Win2000 Server domain. I configured the new server, brought it on as a member server to the 2000 domain without any problems. Since I'm planning on migrating the domain from 2000->2003, I ran:
adprep /forestprep
adprep /domainprep
And then I ran the Active Directory Wizard to promote the new Win2003 Server to a DC. That ran successfully, and everything seemed fine. However, as soon as I rebooted, networking was completely broken. I can't get in or out of the machine. The machine responds to ARPs, but not pings, and I can't ping anything else. If I look under ControlPanel->NetworkConnections, all I see is (empty). BUT, if I run "ipconfig" from the command prompt, I see the network adapter listed, with its correct IP address and settings. If I look under "Services", the "Network Connections" service is stopped, and I can't manually start it.
The odd part is that if I start up a ping to the box, and reboot it, it starts responding to pings almost immediately, and then at some point, while it's in the "Preparing network connections..." screen, it stops responding and never comes back. Also, if I sniff the network, I see some traffic back & forth between the box and the Win2000 Domain controller before things "break".
I'm suspicious that some sort of "policy" was being downloaded from the Win2000 Server, but I'm not sure where to look for that...
I also tried running:
adprep /domainprep /gpprep
... I wasn't too sure exactly what that would be needed for, but it didn't help.
Lastly, I tried several of the steps outlined in:
... but no luck there either. Also tried uninstalling the driver for the network adapter in "Device Drivers", rebooted, and no luck (still reports "device is functioning properly"). I wish it were!!!
This new server is running as a Guest O/S in VMWare Server 1.0.1, but I can't believe that would cause a problem. Just for kicks I created a new VM, re-installed Win2003, and had the same exact bahavior (only *after* I added the server to the domain and rebooted).
I'm at a loss ... any help would be greatly appreciated!
Thanks in advance.....
I'm having problems with a new Win2003 Server Standard R2 that I'm adding to an existing Win2000 Server domain. I configured the new server, brought it on as a member server to the 2000 domain without any problems. Since I'm planning on migrating the domain from 2000->2003, I ran:
adprep /forestprep
adprep /domainprep
And then I ran the Active Directory Wizard to promote the new Win2003 Server to a DC. That ran successfully, and everything seemed fine. However, as soon as I rebooted, networking was completely broken. I can't get in or out of the machine. The machine responds to ARPs, but not pings, and I can't ping anything else. If I look under ControlPanel->NetworkConnections, all I see is (empty). BUT, if I run "ipconfig" from the command prompt, I see the network adapter listed, with its correct IP address and settings. If I look under "Services", the "Network Connections" service is stopped, and I can't manually start it.
The odd part is that if I start up a ping to the box, and reboot it, it starts responding to pings almost immediately, and then at some point, while it's in the "Preparing network connections..." screen, it stops responding and never comes back. Also, if I sniff the network, I see some traffic back & forth between the box and the Win2000 Domain controller before things "break".
I'm suspicious that some sort of "policy" was being downloaded from the Win2000 Server, but I'm not sure where to look for that...
I also tried running:
adprep /domainprep /gpprep
... I wasn't too sure exactly what that would be needed for, but it didn't help.
Lastly, I tried several of the steps outlined in:
... but no luck there either. Also tried uninstalling the driver for the network adapter in "Device Drivers", rebooted, and no luck (still reports "device is functioning properly"). I wish it were!!!
This new server is running as a Guest O/S in VMWare Server 1.0.1, but I can't believe that would cause a problem. Just for kicks I created a new VM, re-installed Win2003, and had the same exact bahavior (only *after* I added the server to the domain and rebooted).
I'm at a loss ... any help would be greatly appreciated!
Thanks in advance.....
