![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Network shares kept getting disconnected on the company LAN. This caused my VFP app to hang when it accessed those shares. I did some searching and found net config server /idledisconnect:<bignum could help. Per my testing, it appears to keep the shares open just fine, but lettered, network drives based on such shares still disconnect. The drive letter is still usable, but there is a delay before data starts flowing. Is there a way to prevent lettered, network drive disconnection, too? Sincerely, Gene Wirchenko |
#3
| |||
| |||
|
|
There's an AutoDisconnect setting you need to change. From a cmd prompt: net config server /autodisconnect:-1 |
#4
| |||
| |||
|
|
On Wed, 14 Sep 2005 19:30:27 -0700, "Fred Taylor" ftaylor (AT) mvps (DOT) org!REMOVE> wrote: There's an AutoDisconnect setting you need to change. From a cmd prompt: net config server /autodisconnect:-1 Windows XP does not recognise "/autodisconnect". What is the difference between it and "/idledisconnect"? [snip] Sincerely, Gene Wirchenko |
#5
| |||
| |||
|
|
On Wed, 14 Sep 2005 19:30:27 -0700, "Fred Taylor" ftaylor (AT) mvps (DOT) org!REMOVE> wrote: There's an AutoDisconnect setting you need to change. From a cmd prompt: net config server /autodisconnect:-1 Windows XP does not recognise "/autodisconnect". What is the difference between it and "/idledisconnect"? [snip] Sincerely, Gene Wirchenko |
![]() |
| Thread Tools | |
| Display Modes | |
| |