I recently implemented a small 15 node 1 server Windows 2K network for a new client of mine. Here's the rundown:
15 Win2K SP3 Dell workstations
1 Win2K Dell Server SP3 (DHCP, DNS, AD Domain controller)
Initially all computers were configured and added to the AD domain without a hitch. Once all PCs were deployed I was successfully able to login to the domain as the domain user of the PC. I receieved a phone call the day after the rollout from the fellow who supports the customers DB, MAS90, stating that transfering converted MAS90 data from a test workstation to the server was dog slow. After looking into the problem I noticed that I mistakingly configured the PC NICS to talk at 100MB full duplex in an environment with a Intel EtherExpress 10/100 MB hub (I know...DUH!) I changed the NIC settings to 100/half which fixed the slow network connection and then...I was unable to login to the domain (domain controlloer not found/the network name is no longer available - all workstations). Knowing that all was fine until I changed the NIC card settings, I set the server and a workstation back to 100 full just to see what would happen. Still can't login to the domain. Removed computer account from domain, reconfigured workstation for workgroup, recreated computer account in AD and tried to join the domain...same problem.
No DNS related errors in the event logs. I'm able to ping the server using the FQDN and can ping the FQDN of the workstation from the server. I'm able to browse to the server and all workstations through Network Neighborhood and I'm able to map server network drives and network printers when logged in locally to the PC. After chasing my tail for a while, I went so far as to reinstall AD and DNS. No luck. To eliminate a potential DNS quirk, I installed WINS on the server and configured the workstation for WINS... no luck. Also, to eliminate any potential DHCP problem, I statically configured a workstation with IP, DNS, etc...no luck.
Just today I tried adding a PC to the domain using the Network Identification Wizard which provided something quite interesting. After taking forever to find the domain specefied, I recieved a message stating that a computer account for the PC already exists in the domain for the PC I was attempting to join to the domain and was asked if I wanted to use this computer account. I said yes, and after another loooong wait I recieved the network name no longer exists message I'd recieved so many times in the past. As illogical as it seems, since this all began when fooling with the NIC card settings, I'm hoping that the LinkSys switch I've been waiting to deploy may resolve my problem, but I can't see this being the problem considering I can access the server fine and I'm getting the network name not available error.
I'm normally not one to ask for help, but I'm just about out of options and was hoping that one of my fellow network admins may have run into this CRAZY problem. Has anyone seen this before? I'd appreciate whatever input any of you can offer.
Thanks to all
HRS11
15 Win2K SP3 Dell workstations
1 Win2K Dell Server SP3 (DHCP, DNS, AD Domain controller)
Initially all computers were configured and added to the AD domain without a hitch. Once all PCs were deployed I was successfully able to login to the domain as the domain user of the PC. I receieved a phone call the day after the rollout from the fellow who supports the customers DB, MAS90, stating that transfering converted MAS90 data from a test workstation to the server was dog slow. After looking into the problem I noticed that I mistakingly configured the PC NICS to talk at 100MB full duplex in an environment with a Intel EtherExpress 10/100 MB hub (I know...DUH!) I changed the NIC settings to 100/half which fixed the slow network connection and then...I was unable to login to the domain (domain controlloer not found/the network name is no longer available - all workstations). Knowing that all was fine until I changed the NIC card settings, I set the server and a workstation back to 100 full just to see what would happen. Still can't login to the domain. Removed computer account from domain, reconfigured workstation for workgroup, recreated computer account in AD and tried to join the domain...same problem.
No DNS related errors in the event logs. I'm able to ping the server using the FQDN and can ping the FQDN of the workstation from the server. I'm able to browse to the server and all workstations through Network Neighborhood and I'm able to map server network drives and network printers when logged in locally to the PC. After chasing my tail for a while, I went so far as to reinstall AD and DNS. No luck. To eliminate a potential DNS quirk, I installed WINS on the server and configured the workstation for WINS... no luck. Also, to eliminate any potential DHCP problem, I statically configured a workstation with IP, DNS, etc...no luck.
Just today I tried adding a PC to the domain using the Network Identification Wizard which provided something quite interesting. After taking forever to find the domain specefied, I recieved a message stating that a computer account for the PC already exists in the domain for the PC I was attempting to join to the domain and was asked if I wanted to use this computer account. I said yes, and after another loooong wait I recieved the network name no longer exists message I'd recieved so many times in the past. As illogical as it seems, since this all began when fooling with the NIC card settings, I'm hoping that the LinkSys switch I've been waiting to deploy may resolve my problem, but I can't see this being the problem considering I can access the server fine and I'm getting the network name not available error.
I'm normally not one to ask for help, but I'm just about out of options and was hoping that one of my fellow network admins may have run into this CRAZY problem. Has anyone seen this before? I'd appreciate whatever input any of you can offer.
Thanks to all
HRS11
