<div>
Can you open the netlogon share from the client machine?
</div>


<div>
Do you have more than one windows server? If you have multiple servers setup as domain controllers, then be sure they are replicating the NETLOGON directory. &nbsp;She may be authenticating to a different server, which in case if it is not replicating the login script, it will not have the file to run. &nbsp;<br />
You may also consider to modify the Group Policy for her computer in AD to run login scripts visibly. &nbsp;Also please check the event viewer to list any errors related to logon or netlogon.<br />

</div>


<div>
yes pablovr, I can access and run the login script manually from her workstation. <br />
<br />
evan, I'm betting this is the solution. Looking at that now...
</div>


<div>
wait, dumb question now: I've never checked this before. Where do I go on the server to verify that the server and syncing the netlogon? <br />
<br />
Her PC had no apparent errors related to this problem in her Event Logs. 
</div>


<div>
Just to double check, please run the following command locally on the client machine, as administrator:<br />
net share<br />
There should not be any &quot;Netlogon&quot; entry there. <br />
This would be the case for a local logon script, used in workgroups.
</div>


<div>
If your servers are not replicating with each other, you would see an event in event viewer on the server regarding NTFRS. 
</div>


<div>
You can also open AD sites and services, expand the server that holds the login script, and click on NTDS settings. Then in the right column, right click the server you want to replicate to and click replicate now. &nbsp;If is completes successfully you will get a message box saying just that.
</div>


<div>
Ok, they have:<br />
<br />
SERVER_1 = a Windows 2000 Server as their DC<br />
SERVER_2 = a Windows 2003 Server Standard as a member server<br />
<br />
If they only have one DC than this cannot be a problem with replication, right? Because only DC's can authenticate users, right?
</div>


<div>
That is correct, check the event viewer on the 2000 server and the workstation for any kerberos errors. &nbsp;<br />

</div>


<div>
Thanks gang! I'll let you know what it was after I fix it but I think this is all the input I'll need on this one. &nbsp;
</div>


<div>
<div class="content wysiwyg-content">
This is Windows Server 2003 &amp;&nbsp;a Windows XP Pro workstation. When this user, Veronica, logs in, her login script does not run. I've checked the spelling of the login script file in her AD properties, verified there is only one login script in use on the server, everything I can think of seems ok. What am I missing? Thanks for any help.
</div>
</div>


This is Windows Server 2003 & a Windows XP Pro workstation. When this user, Veronica, logs in, her login script does not run. I've checked the spelling of the login script file in her AD properties, verified there is only one login script in use on the server, everything I can think of seems ok. What am I missing? Thanks for any help.

Login script not running on an XP PRo workstation???

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).