Login Scripts and Windows Server 2003

The first thing I would do is check the permissions on the sysvol share on that particular DC.

Run:

dcdiag /fix

(Download Windows 2003 Support Tools to access this - http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en)

and

netdiag /fix

(Download Windows 2003 Resource Kit - http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&DisplayLang=en)

on the affected DC.

Make sure all tests are passed.

Have you checked your event logs for errors?

Permissions are ok on the sysvol.

dcdiag /fix results in following errors:
 Starting test: Advertising
    Warning: TVAE-AD1 is not advertising as a time server.
    ......................... TVAE-AD1 failed test Advertising
 Starting test: Services
       w32time Service is stopped on [TVAE-AD1]
    ......................... TVAE-AD1 failed test Services
Starting test: systemlog
   An Error Event occured.  EventID: 0x00000457
      Time Generated: 04/02/2007   08:36:20
      (Event String could not be retrieved)
   ......................... TVAE-AD1 failed test systemlog

netdiag /fix results in all tests passed.

In my event logs I am seeing DNS Server errors with event id's 4004 and 4015. I am also seeing warnings under the directory service for NTDS Replication with an id of 2089. Under Application in my event log I am seeing a userenv error with an event id 1030, there are also a couple groveler and ESENT errors. I'm lost on this.

There does seem to be a definite time issue on this DC - which could explain the lack of mapped drives.

Can you make sure that the W32time service is set to Automatic - and is Started.

Also - check that "Allow this service to interact with the desktop" is not checked.

Can you also set this DC an authoritative time server:
http://support.microsoft.com/kb/816042

The problem ended up being a DNS issue, thanks for all the help.

What was the final resolution?

(so in future people using the site can find a solution - or at least point them in the correct direction)

The Domain Controllers are all running DNS. But none of them had their own ip listed as the first DNS server when running an ipconfig /all. They all refered to another DNS server on the network. I was refered to this article.

http://support.microsoft.com/kb/814591/en-us 
I hope this helps.

Okay - please ask a new, 0-point question in Community Support\General TA (https://www.experts-exchange.com/Community_Support/General/) containing a link to the original question with a request to close and PAQ or delete it (as you answered the question yourself - a refund is applicable).

After 4 days, allowing for comments from participating experts, the question will be closed.