asked on

Microsoft, server 2003 new terminal server can't resolve sysvol

I have a new terminal server receiving Event ID 5719 unable to set up secure connection with a domain controller and Event ID 1053 Userenv Windows cannot determine the user or computer name.
The server grinds to a halt and has to be powecycled then it works ok for half a day.

Connectivity is good I can always ping the 2 DC's etc, but intermittantly Machine can not resolve \\domainname.local\sysvol\domainname.local. The box is a Dell poweredge 840 w/ windows server 2003 sp2. The existing network have been working 2 years. I have removed and rejoined the domain a couple of times but the issue always come back. What am I missing?

The DNS looks ok on the DC's and it replicates between them.

lavionline

make sure that dynamic updates are allowed on DNS zone for your domain. Make sure that this machine registers HOST A records when it joins the domain.
make sure that you can resolve domain name, names of DCs fine from this machine using NSlookup
Since there is SP2 for Win2k3 installed on this machine, Check for following registry keys and set them to "0"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnableRSS.
EnableTCPA
EnableTCPChimney
Courtesy http://support.microsoft.com/kb/936594/

rrable

ASKER

Machine registeres the Host records.

The registry keys are set as specified. I applied the hotfix discussed in the MS article 2 days ago and noticed no difference.

NSlookup returns:
cant find server name for address 192.168.51.4: Non existent Domain
Server Unkown
Address 192.168.51.4

Name w2702.clinic.local
address 192.168.51.4

I do not have a reverse zone set up

rrable

ASKER

The domain Controller runs a database application and the vendor set it to restart every morning at 5am for stability? Probably not related but I can't figure out why sometimes the terminial server can resolve the sysvol and sometimes not?

rrable

ASKER

Ok server can resolve sysvol after a restart for a time. Pings to ip and dns are a good. Over the cource of the day I loose the ability to resolve \\domainname\sysvol\domainname. Generating event ID's 1053 and eventually networkconnection is lost. Any Ideas, I'm pulling my hair out.

ASKER CERTIFIED SOLUTION

ChiefIT

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rrable

ASKER

Thanks for the info!