Jump to content
|Topic||Stats||Last action by|
|Should current fake worth company be illegal?||
|I need to find a DLL, please see screen grab.||
|The Big Wrestling Thread!||
|In fight against spammers, Steam now restricts accounts until users show hard cash||
|Have You Heard About Neowin's Deals?||
Posted 10 July 2012 - 23:55
Posted 11 July 2012 - 01:58
Posted 18 July 2012 - 19:16
I would start by checking the following:
- DNS: Can it resolve the domain and all domain controllers? Are the IP addresses correct?
- Run a diagnostic check for active directory. I can't remember how exactly but dcdiag sounds right.
- Check event viewer on the domain controller and clients for any clues on related errors.
- What domain functional level is the forest and domain? May want to raise them to Server 2008 R2 if not already.
- How is the latency and bandwidth between the DC and client site?
Posted 18 July 2012 - 19:36
Posted 24 July 2012 - 10:20
Posted 12 January 2013 - 02:31
Posted 12 January 2013 - 14:38
Posted 12 January 2013 - 15:16
Posted 13 January 2013 - 11:35
Something doesn't sound right withy the network setup. Could be active directory, could be Dns, could be replication..... Any event logs on the servers (system, application, security, Dns, replication).
If there's a firewall between the computers and the DC, I would look at that... Typically dynamic RPC ports allocation. Try to restrict the ports used for RPC by the domain controllers and make sure the now fixed tcp port range is open on the firewall.
Have a look at these KBs
Posted 13 January 2013 - 11:52
Posted 13 January 2013 - 21:24