E
edward
My apologies for the cross posting, but dind't know if
this topic belong here.
I've done a search and wasn't able to find the
appropriate answer to my question/issue.
Recently I added a DC (Win 2003) to one of my remote
locations; however, users at this location are still
being authenticated by the DC at the corporate LAN. I
noticed that they're caching their LOGONSERVER even
though I've manually set LOGONSERVER=\\NEWDC. At a
restart this variable seems to get a new value, a cached
value.
1.) How can I tell these computers (XP Pro SP1) to look
for a DC (Win 2003) on their LAN rather than go across
the WAN link? FYI, all my DC are Windows 2003.
2.) To minimize traffic on the WAN link should I setup
the remote DC as a DNS and DHCP server? I have many
remote locations and just want to make sure I deploy
these servers in the proper way.
Thanks for your time.
this topic belong here.
I've done a search and wasn't able to find the
appropriate answer to my question/issue.
Recently I added a DC (Win 2003) to one of my remote
locations; however, users at this location are still
being authenticated by the DC at the corporate LAN. I
noticed that they're caching their LOGONSERVER even
though I've manually set LOGONSERVER=\\NEWDC. At a
restart this variable seems to get a new value, a cached
value.
1.) How can I tell these computers (XP Pro SP1) to look
for a DC (Win 2003) on their LAN rather than go across
the WAN link? FYI, all my DC are Windows 2003.
2.) To minimize traffic on the WAN link should I setup
the remote DC as a DNS and DHCP server? I have many
remote locations and just want to make sure I deploy
these servers in the proper way.
Thanks for your time.