Hello! Our Windows NT 4 primary domain controller was originally configured with a token ring network card.
We desperately want to remove the token ring network card and hub, to replace it with an Ethernet adapter. We assumed Windows NT would transparently continue its work uninterrupted, but we were apparently wrong.
I'm open to any suggestions. Here's the story:
Our Windows NT 4 Server Primary Domain Controller (named NT_RAS, IP 10.1.32.16) serves DHCP and WINS for the 10.1.32 network on our LAN. Caleb is working to get rid of the token ring network, and NT_RAS is the last bastion.
NT_RAS also handles all out Windows network printers and roaming profiles; for example: \\nt_ras\laser09, \\nt_ras\laser03, \\nt_ras\sales
Last Friday, Caleb enabled the Ethernet adapter in NT_RAS; it has been in there forever, possibly from the time of purchase, but never used as far as we know. We connected it to the Ethernet switch, and disconnected the token ring adapter from its hub. The Ethernet adapter was given the IP address 10.1.77.xx and rebooted. After rebooting, NT_RAS could communicate on the network and do most things--but we could not ping 10.1.32.16 or print any jobs on network printers. (These were the only immediately noticable problems; there may be others we don't know about.) I could ping its IP 10.1.77.xx.
It's all been set back so our users can work.
Any ideas?
We desperately want to remove the token ring network card and hub, to replace it with an Ethernet adapter. We assumed Windows NT would transparently continue its work uninterrupted, but we were apparently wrong.
I'm open to any suggestions. Here's the story:
Our Windows NT 4 Server Primary Domain Controller (named NT_RAS, IP 10.1.32.16) serves DHCP and WINS for the 10.1.32 network on our LAN. Caleb is working to get rid of the token ring network, and NT_RAS is the last bastion.
NT_RAS also handles all out Windows network printers and roaming profiles; for example: \\nt_ras\laser09, \\nt_ras\laser03, \\nt_ras\sales
Last Friday, Caleb enabled the Ethernet adapter in NT_RAS; it has been in there forever, possibly from the time of purchase, but never used as far as we know. We connected it to the Ethernet switch, and disconnected the token ring adapter from its hub. The Ethernet adapter was given the IP address 10.1.77.xx and rebooted. After rebooting, NT_RAS could communicate on the network and do most things--but we could not ping 10.1.32.16 or print any jobs on network printers. (These were the only immediately noticable problems; there may be others we don't know about.) I could ping its IP 10.1.77.xx.
It's all been set back so our users can work.
Any ideas?
