Windows Script Host when logging into machines

Lately more and more issues have been occuring on various clients involving the Windows Script host. Users are issued a script that applies when they first login. This script handles the mapping of 6 or so mapped drives. Unfortunately, lately more and more computers have been having issues applying this script, when someone logs off and then at some point someone logs in (Doesn't matter how long they wait).

This issue doesn't occur on the first boot / first login of the machine... but will always occur thereafter. It doesn't seem to occur quite on every machine, but it happens on more and more now.

Being for a police department, this issue is becomming more critical, due to the amount of users logging in and out of the machines... and if the drives don't get mapped, they lose crucial access to their reports and other files.

are you using the fully qulified domain name in the \\***\<Sharename> section? meaning.. are you just putting in \\<computername>\<sharename> or are you putting in \\<somedomain.domainname.com>\<sharename>?

Are you able to ping the computer name and/or fully qualified domain name?

Also.. Are these occuring on windows 2000 or windows XP? Service Pack levels?

Windows 2000 domain or windows 2003 domain?

Do any of the drives get mapped correctly?

Do you have access to the group policies on the domain? (in particular, look in the settings:
Computer Configuration/Windows Settings/Security Settings/Local Policies/Security Options/LAN Manager Authentication Level... may also want to check the login script group policy settings , run login scripts asynchronously or something like that)

Unfortunately the only drives that get mapped are when the user logs in. If I login as the administrator, there are absolutely no drives that are mapped.

Click to expand...

Logging in as a local administrator account will not run the login.vbs script as it is a domain login policy.. and thus not have any of the drives mapped (assuming you have it setup as a login script on the domain user account properties..)

are you using the fully qulified domain name in the \\***\<Sharename> section? meaning.. are you just putting in \\<computername>\<sharename> or are you putting in \\<somedomain.domainname.com>\<sharename>?

Click to expand...

We are only putting in \\<servername>\<sharename>, not <servername>.<domainname>.com.

Are you able to ping the computer name and/or fully qualified domain name?

Click to expand...

Yes, when this error occurs, I'm able to ping the server by either IP Address or FQDN.

Also.. Are these occuring on windows 2000 or windows XP? Service Pack levels?

Click to expand...

Windows XP SP2 Machines... Also, this only really beginning happening more frequently, recently... This leads myself and a few others to believe that this is due to perhaps a recent windows update.

Windows 2000 domain or windows 2003 domain?

Click to expand...

Windows 2003

Do any of the drives get mapped correctly?

Click to expand...

Negative Ghostrider, my belief is that as soon as the script fails, especially at the first mapping, it doesn't process the rest.

Do you have access to the group policies on the domain? (in particular, look in the settings:
Computer Configuration/Windows Settings/Security Settings/Local Policies/Security Options/LAN Manager Authentication Level... may also want to check the login script group policy settings , run login scripts asynchronously or something like that)

Click to expand...

Yes! I do have access to the scripts, the policies, everything... I'm an administrator, hehe. Unfortunately though I know very LITTLE about "LAN Manager Authentication Level". I also know nothing about running login scripts asynchronously.

Logging in as a local administrator account will not run the login.vbs script as it is a domain login policy.. and thus not have any of the drives mapped (assuming you have it setup as a login script on the domain user account properties..)

Click to expand...

Yeah, I'm aware of that, I was just stating that we don't have logon script associated with the administrator account. I'll read over that KB, although I highly doubt this has anything to do with mup.sys... I mean why would it work on the first login?

When I try to map the drives manually, I get the same error message, "No Network Provider can accept the given network path". Also, I noticed that when the script fails, I am entirely unable to change the computer's name, description, and domain status either. Peculiar.

Also, another update:

As this request was cross posted on message boards, someone else responded to me to a script that they use. The script is completely different on the way it operates, though I still have it mapping the drives. Another difference is that this script hands out the mapped drives by running from a GPO, instead of running as a script from the user's profile... and I still get the same error messages.

Oddly enough, I contacted Microsoft in regards to this issue, and they wanted to go over some things. While we were having some other strange issues with the primary culprit from this issue, they wanted me to remove and re-join the machine to the domain. Upon doing so, I wasn't able to re-create the script host error... I definitely need to try this some more tomorrow when I am back at that client.