Archived from groups: microsoft.public.win2000.active_directory (
More info?)
If you have multiple DCs it could be a problem reaching one DC in
particular. Windows clients, when failing to reach a server for whatever
reason, have a series of behaviors to go out and look for a different one,
hence a possible 'seems to work sometimes but other it doesn't' possibility.
I'd suggest doing the command below (you may need to install this tool
first-which is from the resource kit) on a client that is getting the
failure as it is getting that failure:
C:\Tools>nltest /dsgetdc:domaina
DC: \\DC1
Address: \\192.168.0.6
Dom Guid: XXXXXX-XXX-XXX-XXXX-0XXXXXX
Dom Name: domaina
Forest Name: domaina.com
Dc Site Name: WEST
Our Site Name: WEST
Flags: GC DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE
The command completed successfully
Then run it again on the same clients when the problem is not occuring. The
idea is to see if the issue only occurs when clients look to a particular
DC, then run some diagnostics on that DC to see what's going on with it.
Please repost to let us know what you find...
--
Tim Springston [MSFT]
---
This posting is provided "AS IS" with no warranties, and confers no rights.
"Harold Miles" <HaroldMiles@discussions.microsoft.com> wrote in message
news:2C93F88E-3AB5-4D4B-A37B-D63D7C18449F@microsoft.com...
>I have some workstations/users that login and cannot access the sysvol or
>my
> DFS share. The next minute they log in at the same workstation and it all
> works. This is such a random problem. Does anyone have any ideas how to
> troubleshoot such a sporatic problem that I can't replicate. I keep
> thinking
> it is a DNS problem.
>
> Thanks!
Facebook
Twitter
Instagram