Hi
I have an issue i need your help with. I believe i may know what the cause is but perhaps i have missed something.
I have an SBS2003 Domain. The SBS server sits in an office 40km away from my problem server. I also have an additional DC in the same office as the SBS server with AD and DNS.
I have a Terminal Server in my office that is spitting out event ID 1054 each day "Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted." (I have GP running on the SBS server with the required domain settings)
I ran a netdiag on the Terminal (results attached) that is telling me the DNS test passed but also says it couldn't find a primary authoritive DNS Server for the Terminal Server (error_timeout). The link between the 2 offices is 1.5mb/256K and i have a suspicion the reason could be the slow link back to the DC.
I have 3 nics on the Terminal. The NIC that has the gateway settings is pointing to the SBS server first for DNS and then the second DNS server. I also have a reverse lookup zone for the subnet of the Terminal Server. (The other 2 Nics are for access to the Terminal from the the clients)
We sit behind a Cisco router for Internet access that is managed by another company (we are a Financial Institution) so i cannot access the router.
When i browse to the SBS server name, \\sbsservername,i can see all the shares such as sysvol etc. I have also set a persistent route to the subnet of the SBS server on the Terminal Server. The route has been set to use the Cisco router. I have flushed DNS, re-registered DNS etc, but appears to have had no affect.
It's funny though, it appears some of the settings from GP are being applied, such as Proxy settings, but others like security zones, are not. I have to set them on the Local policy on the Terminal Server.
Am i on the right lines with my thinking regarding speed as the issue or is there something else i can do?
Cheers
Start Free Trial
