I believe I have a dns issue in a small w2k3 environment. The following is my setup:
Router: Default gateway. No dhcp or port forwarding. Generally no ip magic. Static public ip info from sprint /verified accurate.
Switch: Linksys 24 port gig switch. standard setup.
Server: W2K3 std. managing dns, dhcp, no WINS, no exhange, sqlserver or any other special apps. Its an authentication and file server. Gig nic with static ip.
Workstations: 8 Windows XP pro running office and some other financial apps.
Situation: Server is about 4 months old and has been running as a standalone server acting as a file server outside a W2k domain on the same ip range/subnet. Workstations joined to domain 1 using new server with no problems. When i brought DC 1 down and joined workstations to DC2 (W2k3 server) things came to a standstill. Logins now take 2-25 minutes to process and the same for applications and network drives or UNC paths. Dis-joining and rejoining the domain seemed to help a little but nowhere close enough. Pressing ctrl>alt>del to change the network password fails and tells me that the domain isn’t available or couldn’t be contacted. I tried this right after rejoining the domain, rebooting and logging in. “Password could not be changed at this time because fbc domain is not available”
So to summarize, my logins are terribly slow and some other network functions like mapped drives and unc paths. Also it seems that if I let the PC boot get logged in and all startup programs load the apps do seem to come up faster. Netbios has explicitly been turned on on all cards, dns entries have been manually assigned as well as the server handling dhcp. I have not done any special AD configurations.
Any ideas?
