Mapped drive dropping

[d4476m]

hi

since Wednesday we have been having a problem where when a user logs on Sims tells us there L:\\ drive is not available when we look at it, the map is correct but will not open to fix it we need to restart the system does anyone know why the mapped drive would behave like this. It is happening to about 10% of our PCs at random times and locations

[mac_shinobi]

how are the drives mapped in the first place ? also when you get this error message are you able to use a unc path to access the same area or shared folder / drive ?

 

you getting any errors in event viewer recently that may be linked to it ?

[contink]

I've found that if a drive letter is used earlier on in a script or another login script is utilising it then the mapping can fail.

 

The best way to avoid this particular problem is one or more of the following:

- run your scripts in series rather than parrallel.

- avoid using a letter in another script and the unmapping, remapping later

- if you must do the above do a loop, test (with timeout) to check for when the mapped drive no longer exists before allowing the next map command to try and use it.

 

Found this has worked for a few scripts of mine which were using M: for temp work, unmapping and the remapped later... M kept getting dropped half the time and not getting remapped.. The above solved it.

[mac_shinobi]

also where you assign the scripts makes a difference as I tried assigning it via startup scripts and it kept giving me error message symbols and then I tried assigning it via a logon script and it worked better.

 

im sure that was the correct way around, might be helpful if you post your script here and let us know how you are assigning the scripts ie via logon script or startup script

[plock]

I've always mapped drives via login scripts, can you do this via startup scripts then?

 

I've never tried!

[Michael]

I would of thought you can't create mapped drives as a startup script, simply because you create shares on a server and add users or security groups to access the share. You cannot add or give computer objects permission to access a share.

 

What you can try is manually navigating to the NETLOGON share, \\servername\NETLOGON from Explorer and run the logon script for that particular user (once logged on). If you still cannot access the drive, I would say it's a permissions issue.

 

Out of curiosity, do have shares across multiple servers? Are the machines with problems using ethernet or wireless? Wireless can create wonderful problems with network drives when connectivity is lost. I'd also check the status of your switches.

[plock]

I would of thought you can't create mapped drives as a startup script, simply because you create shares on a server and add users or security groups to access the share. You cannot add or give computer objects permission to access a share.

 

Indeed - that would make sense!

[strawberry]

have you tried deleting the mapping at the begining of the script before you map it?. If it sees the letter assigned it wont map but will look to the naked eye like it has.

[Lithium]

Our software share is set up with Domain Computers listed with Read Access - and it's worked fine for the whole time as far as I am aware... (the only other permissions are Admins, Domain admins and SYSTEM)

 

The one problem I have with mapped drives is that the mapping stays there no matter how I try to delete it, it just sits there as "Disconnected Network Drive" which then stops any other drives being mapped under that letter... but I work around that...

 

A computer is basically a user which isn't interactive... it changes its password more than users do in a school

[FN-GM]

If it is a .bat script try putting this at the begging of the script.

 

net use * /d /y

[d4476m]

The drive is mapped using a start-up script which has been used for year and works fine until Wednesday the error that seems to come up is a The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server event id: 4 but having looked up the error seems to imply that there machine name has a duplicate on the domain which it does not.

 

if i re boot the pc that is getting the error it will normally start to work till the next day

[d4476m]

Managed to track the error to our Exchange server and its DC replication and have now fixed it

thanks for the help

[ThatBoringBloke]

Managed to track the error to our Exchange server and its DC replication and have now fixed it

thanks for the help

 

Welcome!