Will
Guest
|
 Posted:
Mon Nov 07, 2005 9:50 am Post subject:
SYSVOL Not Reachable By Fully Qualified Domain |
|
|
I have two W2K Domain Controllers for a forest with a single domain. These
are:
dc1.x.corp.com: 10.1.1.1
dc2.x.corp.com 10.1.1.2
When I go to the command line, either of the following works fine:
dir \\dc1.x.corp.com\sysvol /s
dir \\dc2.x.corp.com\sysvol /s
But if I try to access sysvol through the domain only, I get "0 files found"
on a line by itself. The location I am trying to reach would be:
dir \\x.corp.com\sysvol /s
x.corp.com resolves to the two IPs: 10.1.1.1 and 10.1.1.2
Windows 2003 is attempting to do group policy updates using the domain name
only rather than a specific domain controller, and currently my W2K server
is loaded with GPO update errors that all say group policy cannot be located
at \\x.corp.com\sysvol. This appears to be correct relative to the
command lines shown above.
What would cause the domain-only listing of sysvol above to fail, where the
domain controller versions work? Is the issue just one of having two IPs
assigned to the domain?
What's the correct workaround / fix?
--
Will |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in