Server 2000 and 2003 logon issues

SaigaShooter · 02-21-2007, 01:07 PM

I have a domain with a Server 2000 primary domain controller, and a 2003 server at a remote site, acting as a secondary domain controller.

All my logons are being routed accross the t-1 line to the remote site, does a 2003 server automatically handle all logons?

What can I do to fix this?

SafeFromSites · 02-21-2007, 01:16 PM

are the client computers set to view the remote server first in DNS, and does it have a copy of the global catelog?

Mystery · 02-21-2007, 01:41 PM

If you're using static addresses, check the properties of the TCP/IP on the Active NIC in Network and Dial-up connections. and Check if the Primary DNS is set to the remote server.

If you're using dynamic addressing, go to DHCP and check the scope options to ensure that the DNS servers section lists the W2K server at the top of the list.

02-21-2007, 01:07 PM	#1 (permalink)
SaigaShooter Registered User Join Date: Jul 2005 Posts: 18 OS: Windows Xp	Server 2000 and 2003 logon issues I have a domain with a Server 2000 primary domain controller, and a 2003 server at a remote site, acting as a secondary domain controller. All my logons are being routed accross the t-1 line to the remote site, does a 2003 server automatically handle all logons? What can I do to fix this?

02-21-2007, 01:16 PM	#2 (permalink)
SafeFromSites Registered User Join Date: Feb 2007 Posts: 142 OS: XP	are the client computers set to view the remote server first in DNS, and does it have a copy of the global catelog?

02-21-2007, 01:41 PM	#3 (permalink)
Mystery Registered User Join Date: Dec 2006 Posts: 23 OS: Windows 2000 My System	If you're using static addresses, check the properties of the TCP/IP on the Active NIC in Network and Dial-up connections. and Check if the Primary DNS is set to the remote server. If you're using dynamic addressing, go to DHCP and check the scope options to ensure that the DNS servers section lists the W2K server at the top of the list.