Wierd Issue

Here's a good one at a customer site:

Mapped network drives W and X provided by logon script.



If you open My Computer and go into W: then open the subfolder ‘sys’ then attempt to open the subfolder ‘word docs’, explorer hangs for 20-30 seconds.



Eventually it comes back to life and opens the folder and everything operates fine.



Each time 3 more copies of the company drive (W : get mapped on additional drive letters. This happens every time you replicate this situation, such that you will eventually end up with drive letters F: through Z: mapped to the same place as W: if you keep doing it.


Happens of a few machines of mixed OS - Vista, XP, 7.



A fresh built PC (XP) has been built and it happens to this - i.ie - delay of 20seconds and 3 + additional drives mapped to the same share.



Does not happen on the server.


No AV - it's been removed for testing. Windows Updates installed.



Ideas welcome!

[DocDutch]

okay try to get to the drive via this way \\"ip address"\W$
see if you get any delays that way.

Originally Posted by DocDutch

okay try to get to the drive via this way \\"ip address"\W$
see if you get any delays that way.

Good shout - tested - same thing.

---------- Post added at 16:25 ---------- Previous post was at 15:59 ----------

Update: I've now moved the test computer into it's own OU with no domain policys enforced or linked - same issue.

---------- Post added at 16:33 ---------- Previous post was at 16:25 ----------

Update: Tested a PC that's not joined to the domain - works ok so I think it's something domain related but not policy related.

Update: Been informed that it only happens on XP - Vista and 7 are fine.

[Lord Nikon]

Try viewing hidden and system files in the folder in question, check for an autorun file or a folder permission policy which is initiating the drive mapping, something with content along the lines of net use * //machine/drive

Originally Posted by Lord Nikon

Try viewing hidden and system files in the folder in question, check for an autorun file or a folder permission policy which is initiating the drive mapping, something with content along the lines of net use * //machine/drive

Been there, done that. No autorun file in the folder - not checked all the subfolders but I don't think it'll be able to run from there.

The odd thing is as well - even if you single rightclick on the folder it produces the same 3 drive mappings and the 10 ish second delay before giving you the context menu.

Even one left click will do the same but obviously won't open the folder until a double click.

There is something very odd with the folder...

[idi banashapan]

is the login script just a Net Use line? if you can provide the script (minus sensative details), that might help.

Originally Posted by idi banashapan

is the login script just a Net Use line? if you can provide the script (minus sensative details), that might help.

Yep - like this:

net use w: \\servername\Company

Simple stuff that's been used millions of times over...

[idi banashapan]

are you sure there are no other scripts set to map a drive? the profile tab in AD against the user object doesn't have a home drive location specified to use the same letter or location?

second to that, what is the behaviour if you clear all mappings, then manually map the drive with a reconnect a logon, then log out and back in?

Originally Posted by idi banashapan

are you sure there are no other scripts set to map a drive? the profile tab in AD against the user object doesn't have a home drive location specified to use the same letter or location?

second to that, what is the behaviour if you clear all mappings, then manually map the drive with a reconnect a logon, then log out and back in?

Nope. It's just a simple install. Drives are mapped by the logon script.

Same thing happens when the drive is disconnected and re-mapped manually.

[idi banashapan]

certainly is strange, i'll give it that! and you say this happens under multiple AD profiles? does it still do it if you make the mapping persistent via the batch?

Originally Posted by idi banashapan

certainly is strange, i'll give it that! and you say this happens under multiple AD profiles? does it still do it if you make the mapping persistent via the batch?

Yep - multiple user accounts - administrator / normal user - still happens.

An yep to persistent mappings.

It really is odd. Thought about renaming the folder or trashing it and restoreing from backup to another name.

[idi banashapan]

I wonder if it's something stupid where XP is timing out for some reason on the mapping. try running;

net config server /autodisconnect:time

and make the time quite long, see if the behaviour persists. I'm not 100% sure it will fix it, but it's worth a go!!

other than that, i take it the logon batch is held under the domain login script folder and not being pulled from somewhere else?

Originally Posted by idi banashapan

I wonder if it's something stupid where XP is timing out for some reason on the mapping. try running;

net config server /autodisconnect:time

and make the time quite long, see if the behaviour persists. I'm not 100% sure it will fix it, but it's worth a go!!

But that would affect ALL users not just specific on Windows XP - I'll give it a shot but doubt it'll fix it.

Originally Posted by idi banashapan

other than that, i take it the logon batch is held under the domain login script folder and not being pulled from somewhere else?

Yep - in sysvol /scripts folder.

Update: PC works perfect in Safe Mode /w Networking - tracked it down to a service - but not sure what yet. Reinstalled the NIC and networking - same persistant issue.