Re: Sites and Services
- From: "Jeremy" <jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 29 Apr 2007 13:10:31 +1000
Download and use nltest.exe (in the reousrce kit or something) to see what site you workstations think they are in. Also use dfsutil.exe to see what SYSVOL referral your clients have.
nltest.exe /dsgetsite
nltest /dclist
dfsutil.exe /pktinfo
The site link will only come into effect when trying to locate a DC outside the current site. The workstation should always prefer to authenticate to a DC in its site first.
Also, is the field site DC a global catalog? If not the client will contact the global catalog in order to enumerate USG memberships. If you only have one domain then all your GCs should be DCs. In your situation they should also be DNS servers and the local clients should have the local DC/GC/DNS server set as the preferred DNS server via DHCP.
Cheers,
Jeremy.
"Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:9EB92286-002A-4204-95E0-27D7E58174E1@xxxxxxxxxxxxxxxx
Windows 2003 forest. I have multiple field sites and a corporate office. At
one of the field offices, I have a power domain controller onsite. Let's
assume for a minute that it's 10.46.0.0 255.255.0.0 subnet that I have setup
for this site with this domain controller in that site.
Let's assume that the corporate office is 10.10.0.0 255.255.0.0 subnet. Why
would some users authenticate locally to their DC as they should, and some
authenticate all the way across to the corporate office. Note that I have
the link cost set high. Having a very hard time trying to understand why
some machines would go across that WAN link when the DC local to them is not
by any means getting hit hard. Any help would be appreciated.
.
- Prev by Date: Re: Sites and Services
- Next by Date: Re: Cannot Assign Permissions to Domain Local Groups
- Previous by thread: Re: Sites and Services
- Next by thread: Re: Sites and Services
- Index(es):
Relevant Pages
|
