Mapped drive

[Becky]

Hello,
We have a small network in our organization and everybody
maps a drive from Windows 2000 Advanced Server and run an
application from there. From time to time we see red x on
the mapped drive in the file explorer in the local
computer as if they are disconnected, however when we
click the drive we see the files and red x disappears.
What might be the reason of red x in the map drive? Our
problem is we are facing a few problems when we run an
executable in the map driver and we are wondering if red x
might be a reason.
Thanks,
Becky

 

[Dave Patrick]

The default timeout is 15 minutes. From a command prompt on the server side
net config server /autodisconnect:-1
for no disconnect.

Setting this from the command line may turn off auto tuning for the server
service. So a better solution is to navigate to
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

and set the Reg_DWord hex value of
"autodisconnect"=ffffffff

If "autodisconnect" doesn't exist, Add it.

(note; ffffffff = aprox. 8171 years)



You'll probably also want to ask the application developer if they support
running the app in that fashion.


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


:
| Hello,
| We have a small network in our organization and everybody
| maps a drive from Windows 2000 Advanced Server and run an
| application from there. From time to time we see red x on
| the mapped drive in the file explorer in the local
| computer as if they are disconnected, however when we
| click the drive we see the files and red x disappears.
| What might be the reason of red x in the map drive? Our
| problem is we are facing a few problems when we run an
| executable in the map driver and we are wondering if red x
| might be a reason.
| Thanks,
| Becky

 

[Colon Terminus]

Nah, the red X probably isn't related to your problem at all. You'll get a
lot of advice as to how to make the red X go away. It may, or may not, work.
I have some workstations that see the red X from time to time on various
shares and nothing seems to fix it. I have one workstation that has a
constant red X on one share from 30 seconds after boot for the rest of the
day. None of the other workstations have the red X on this share. None of
the red Xes get in the way of sharing though, they're just an annoyance.

This is but one of many problems that Microsoft deems unworthy of fixing. My
biggest pet peeve with Windows is it's inability to estimate time to
completion for progress bars in the GUI. This'n has been there since Win95
and exists in all versions of Windows up to XP. I don't know if it still
exists in 2003, but I suspect it does. I guess MS just doesn't figure it is
worth fixing, but I grow weary of seeing a progress bar that counts down to
zero then claims there's 247819462 miniutes remaining.