Mapped Network drive goes Disconnected

[Cstorms]

So recently we started using vbscript to map a couple of drives and it works well, or so it seems. After a while when a user clicks on the drive it takes anywhere from 8-15 seconds for it to bring up the contents. After that it works fine for a while again. Anyone know what could be causing this, dns is correct both the A record and PTR are accurate the rest of the drives that are mapped in Novell work fine but these Windows Servers are crapping out..

Thanks for lookin!

Cory

 

[TNGPicard]

Random shot in the dark, I ran into this at a client site a few weeks ago. The mapped drive target was/is a directory FULL of a few thousand images, sub folders, etc. The server and the client were not using a corporate managed AV solution and the client AV system was set to scan network files before access; what seemed to be going on was the AV was checking every file for bad stuff before letting the OS complete the operation to open the folder for the user. When I changed the desktop machine to use the corporate managed product which is set to trust machines also using the same managed product the problem resolved.



Have you checked the server to see if the client is still connected to the share?

Is this on multiple machines or just one machine?

Mark L.

 

[Cstorms]

Thanks for the reply, it looks like the client actually loses connection when I check via netstat, however after uninstalling and reinstalling the Client for Microsoft Networks it seems to be just fine from that point on... Whats a bummer here is currently run a mixed Windows AD/Novell eDir environment so troubleshooting the direct cause is very cumbersome.

I am probably going to try and use snetcfg in a scripted solution to automate as much as possible, however I really want to know WHY that fixes it since the client for ms networks is already installed in the first place... Thanks again. (I will check a/v stuff as well since its typically a weird problem maker)

Cory

 

[TNGPicard]

Cory -

Good find on that, its such a atypical thing I never think to check that from the start (the client for ms networks). I don't know how to do it in VB script off teh top of my head with the drive maps but maybe try running

net use /persistent:yes

It should save the setting between boots/logins and maybe that will also help keep your drive maps in place.

Mark / TNG

 

[Cstorms]

I think I am going to try and map it differently yes, I found "snetcfg" still floating around so I downloaded it and it looks like that is capable of uninstalling/installing from the cmd line, hopefully this can be a possible solution to a mass deployment.

Thanks for the replies.

Cory

 

[Cstorms]

For those of you who were following along heres what we found and changed to fix it..

When we reinstalled the MS client it rearranged our provider order so that the LanmanWorkstation was on top, this made connections to these mapped drives go alot faster since it didnt try and use a bunch of other provider services.. In order to get this out to all of our user computers we made a reg hack and deployed it so that the key under..

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

.. would have the lanmanworkstation first in the list

Have a good day

Cory