Putting your main DC (in this case, your only DC) in a separate physical location makes no sense whatsoever. If it is located physically in a separate location, you could create a new DC in the same location as the clients and fix it so the clients authenticate to the DC that's physically located in the same place as them. Otherwise you'll have to live with the delays.

If however, your DC is located in the same place and you have it on a separate internet connection from the client PC's you should really connect all the clients and the DC on the same LAN so the clients can authenticate via the LAN instead of the internet.


On Friday, February 7, 2003 at 2:36 am, farklem wrote:
>Ok, so I got my domain controller working running Windows 2000 Advanced Server.
>With 4 client machines running Windows 2000 Professional. The only problem is that
>my domain controller is set up on a different internet connection than that of the
>clients. I have roaming profiles set up on my network but when I try to login on
>the client machines it does ereything over the internet so it takes forever to logon
>and transfere files between the clients and the domain controller. Is there any
>way to fix this problem? Is there a way to force it to use NetBIOS or something
>so that it doesn't use TCP/IP to communicate with the server?

Written in response to: Networking in a Windows 2000 Domain (farklem: Friday, February 7, 2003 at 2:36 am) Responses to this message: re: Networking in a Windows 2000 Domain (Johnny Ryall: Saturday, April 26, 2003 at 8:26 pm)

• Reply or follow-up to this message

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum