mediaogre
asked on
Post domain user account pw change getting network drive map error
Hi folks,
A little information:
Environment: I am running Windows Server 2003 SP1 AD enabled. I have GPO based logon map drive scripts associated with OUs. XP SP2 client workstations. The script is located on our FSMO DC and the UNC path for the mapping points to FileServer1 (for example).
Issue: I just changed my domain account password (from a complex 9 character to a complex 12 character pw) and now when I log in to the domain, Windows Script Host throws the following error:
************************** ********** ********** ********** ********** ********** ********** ********** ********** ********
Script: \\mydomain.com\SysVol\mydo main.com\P olicies\{E AAA5FB0-DD B2-496C-A8 0E-7590AF2 FDC9C}\Use r\Scripts\ Logon\TS-M ap-T.vbs
Line: 16
Char: 1
Error: Logon failure: unknown user name or bad password.
Code: 8007052E
Source: WSHNetwork.MapNetworkDrive
************************** ********** ********** ********** ********** ********** ********** ********** ********** ********
It doesn't seem to matter which mechanism I use to change the password. Be it the Options page from the OWA interface, ADUC or Ctrl+Alt+Delete (or even a "force pw change" script) the failed result persists.
I *can* successfully map to the same UNC (from the logon script) using the Windows Map Network Drive function with my new credentials. However, if I run the script locally, I receive the same error minus the DC's script location directory path.
The script does not contain any user/credential information. I'm not sure where to begin.
Thanks in advance,
Greg
A little information:
Environment: I am running Windows Server 2003 SP1 AD enabled. I have GPO based logon map drive scripts associated with OUs. XP SP2 client workstations. The script is located on our FSMO DC and the UNC path for the mapping points to FileServer1 (for example).
Issue: I just changed my domain account password (from a complex 9 character to a complex 12 character pw) and now when I log in to the domain, Windows Script Host throws the following error:
**************************
Script: \\mydomain.com\SysVol\mydo
Line: 16
Char: 1
Error: Logon failure: unknown user name or bad password.
Code: 8007052E
Source: WSHNetwork.MapNetworkDrive
**************************
It doesn't seem to matter which mechanism I use to change the password. Be it the Options page from the OWA interface, ADUC or Ctrl+Alt+Delete (or even a "force pw change" script) the failed result persists.
I *can* successfully map to the same UNC (from the logon script) using the Windows Map Network Drive function with my new credentials. However, if I run the script locally, I receive the same error minus the DC's script location directory path.
The script does not contain any user/credential information. I'm not sure where to begin.
Thanks in advance,
Greg
What does line 16, char 1 say? If you can post the script that would be great...or at least portions that would let us know. Are you setting something in the .vbs script that uses a username/pwd to authenticate?
I'd be thinking that the Domain Controller with the PDC Emulator role is offline... and that the credentials changes haven't had time to replicate.
I'd be curious to know if the problem "goes away by itself" with a few hours.
I'd be curious to know if the problem "goes away by itself" with a few hours.
ASKER
TheCleaner- following is the scipt I'm using (note the lack of domain/acount credentials):
***SNIP***
' TS-Map-T.vbs
' VBScript to map the T: drive for the TST.
' -------------------------- ---------- ---------- ---------- ---------'
Option Explicit
Dim objNetwork
Dim strDriveLetter, strRemotePath
strDriveLetter = "T:"
strRemotePath = "\\FS1\IST"
' Purpose of the script to create a network object. (objNetwork)
' Then to apply the MapNetworkDrive method. Result X: drive
Set objNetwork = WScript.CreateObject("WScr ipt.Networ k")
objNetwork.MapNetworkDrive strDriveLetter, strRemotePath
WScript.Quit
***SNIP***
graye- *Sheesh* that's a good and scary thought. I have verified that the FSMO and subsequently the PDC emulator is online. Also, I forced a manual password change from ADUC on said emulator. :-{ I too was hoping that the issue would go the way of the X-file and "correct* itself as things trimmed out. However, I changed my passwork yesterday at around 10:00 AM.
***SNIP***
' TS-Map-T.vbs
' VBScript to map the T: drive for the TST.
' --------------------------
Option Explicit
Dim objNetwork
Dim strDriveLetter, strRemotePath
strDriveLetter = "T:"
strRemotePath = "\\FS1\IST"
' Purpose of the script to create a network object. (objNetwork)
' Then to apply the MapNetworkDrive method. Result X: drive
Set objNetwork = WScript.CreateObject("WScr
objNetwork.MapNetworkDrive
WScript.Quit
***SNIP***
graye- *Sheesh* that's a good and scary thought. I have verified that the FSMO and subsequently the PDC emulator is online. Also, I forced a manual password change from ADUC on said emulator. :-{ I too was hoping that the issue would go the way of the X-file and "correct* itself as things trimmed out. However, I changed my passwork yesterday at around 10:00 AM.
script looks fine.
what about this...try doing a net use command (cmd prompt)
is T listed already?
What about trying something like net use T: /del
then run the script again. It could just be that the old drive mapping was caching old credentials.
what about this...try doing a net use command (cmd prompt)
is T listed already?
What about trying something like net use T: /del
then run the script again. It could just be that the old drive mapping was caching old credentials.
ASKER
Hmm. net use yields only my Home Folder. The delete usage outputs, "The network connection could not be found". You got me thinking though...(Thanks!- That's what we're doing here right?) I UNCd to the share associated with drive mapping and received a login dialog for that file server. However, when I UNC to other shares (on the same file server) to which I *don't* map drives, I do *not* receive a login dialog. Thoughts?
check the share permissions on the share you are mapping and the NTFS perms. Make sure you didn't get removed from it somehow.
If you go to \\servername and then just try to open the share does it prompt you for username/pwd?
If you go to \\servername and then just try to open the share does it prompt you for username/pwd?
ASKER
TheCleaner- Perms are Ok. I do receive a login prompt.
but other shares on the same server work just fine? That's strange.
Is your home folder that's mapped going to the same file server too?
If so I would try this:
net use driveletter: /del
for all drives mapped
also net use path /del
for anything showing in a net use that isn't associated to a drive letter.
Then do a gpupdate /force on your PC and restart.
I'd also try going to a different computer and testing.
Is your home folder that's mapped going to the same file server too?
If so I would try this:
net use driveletter: /del
for all drives mapped
also net use path /del
for anything showing in a net use that isn't associated to a drive letter.
Then do a gpupdate /force on your PC and restart.
I'd also try going to a different computer and testing.
ASKER
I thought the different-shares-on-same-s erver inconsistent behavior was weird too.
Home Folder lives on a different file server. However, I have that configured through AD account properties and not via logon script in a GPO.
I'll try your net use and force policy update suggestions and post the results.
Home Folder lives on a different file server. However, I have that configured through AD account properties and not via logon script in a GPO.
I'll try your net use and force policy update suggestions and post the results.
ASKER
Ding-ding-ding. I logged in from another machine and... no error. (BTW- I tried your other suggestions to no avail) Logging in via console or TS/RDP doesn't make a difference; it works either way. FWIW- I tried with success on three separate machines.
So, getting closer. Any idea why my personal machine would be the culprit?
So, getting closer. Any idea why my personal machine would be the culprit?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.