Program when trying to map non-existing network directory

DerChef · 2009-02-07 12:56

Hi there

great little tool but one thing is really annoying: if you choose a setting which tries to map a network drive and for some reason or other there is no access to the mapped directory netsetman freezes and it is very hard to kill it, does not work in the taskmanager with kill process for instance. Last time that happened took me 10 min to get rid of the frozen netsetman.

One suggestion here: there should be a possibility to pre-define some sort of a time out, e.g. if netsetman cannot acces the directory supposed to be mapped to a net drive within pre-defined time it stops here or carries on with the next step.

NetSetMan Support · 2009-02-09 13:49

Sounds odd. Normally the used function should have its own time-out timer. I will have a look at this problem and maybe it is really necessary to add a manual check for the availability of the network resource.

DerChef · 2009-02-13 20:00

don't know whether this is important: problem comes up in our network, no dhcp, fixed ips, fixed gateway etc.

DerChef · 2009-07-18 13:23

trying to push this up:

still an issue does occur with new 2.54 version.

The real trouble is that I cannot kill the netsetman process the only way to get rid of the programm is to log out or sometimes even to shut down the whole system.

If you cannot get the bug out please tell if there is a better way to kill the f...ed up process

NetSetMan Support · 2009-07-20 18:45

I will address that problem very soon. I'm sorry for the long delay, there has been a lot of other important stuff going on. Hopefeully there's an easy solution for this one.

NetSetMan Support · 2009-07-24 16:47

OK, I did a research on that issue.

The function for mapping the network share is a basic Windows API and it uses the global timeout value of Windows. It takes the same time for NetSetMan to find out that the server doesn't exist as it would take typing in "\\server\test" in the address bar of the explorer or any other location.
Notice that the result is kept in some kind of cache. Therefore a second test afterwards will bring the result immediately. For testing purposes the server name should be altered for every new test (server1, server2, ...).

Normally this timeout value is 7,5 seconds. (tested)

If this value has been changed on your system by any program or manually then this might result in such long timeouts.

Have a look at this registry vaule:
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\netbt\Parameters
Key: BCastQueryTimeout

It should be set to 2ee (750). What's your value here?

NetSetMan Support

#1 2009-02-07 12:56

Program when trying to map non-existing network directory

#2 2009-02-09 13:49

Re: Program when trying to map non-existing network directory

#3 2009-02-13 20:00

Re: Program when trying to map non-existing network directory

#4 2009-07-18 13:23

Re: Program when trying to map non-existing network directory

#5 2009-07-20 18:45

Re: Program when trying to map non-existing network directory

#6 2009-07-24 16:47

Re: Program when trying to map non-existing network directory