|
|
|
re: Networking in a Windows 2000 Domain
Saturday, April 26, 2003 at 8:26 pm
Windows 2000 Annoyances Discussion Forum
Posted by Johnny Ryall
(4 messages posted)
What Curt wrote is correct. If your Domain Controller is in the same location physically
then make sure your clients have the DC's IP in their DNS settings. Then they won't
take forever to log in. (in fact if you check your logs they're probably not connecting
to the DC at all)
Now that the DNS settings are correct your folder redirect/roaming profiles should
work.
On Friday, February 7, 2003 at 5:18 am, Curt R wrote:
>I'm not sure I quite understand. You said. "my domain controller is set up on a
>different internet connection than that of the clients". What I'm wondering about
>after reading this is the following: Are the clients and server in the same location
>(building) and if so, why aren't they connected via a LAN connection?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.
>
|
All messages in this thread [show all]
 | |  | re: Networking in a Windows 2000 Domain (Johnny Ryall: Sat, Apr 26, 2003, 8:26 pm) |
| |
| |
Return to the Windows 2000 Discussion Forum
|
|
|
|
