-
December 20th, 2002, 08:52 AM
#1
W2K losing mapped drives
This has been happening for a while now, but is becoming more and more annoying each day.
When a user logs in, the logon script runs mapping all networked drives, varying between 3 and 8 drives at a time. After a few hours, if you go into My Computer and view the drives, some (if not ALL) have a little red X through the icon. But, if you go to click it, you can get in (most of the time) and the icon returns to normal.
Has anyone else seen this? I have not been able to locate any information on the KB at M$ regarding this. Any help is appreciated.
Thanks in advance and have a good holiday!
-
December 20th, 2002, 08:58 AM
#2
Driver Terrier
Have you got persistent:yes in the script?
2k also closes unused maps and refreshes them on demand, its a "feature"
read all about it here
Never, ever approach a computer saying or even thinking "I will just do this quickly."
-
December 20th, 2002, 03:06 PM
#3
Registered User
this is indicative of a win2k machine on an nt4 domain. if this is the case there are two courses of action, live with it or go to active directory.
"no eternal reward will forgive us now for wasting the dawn"
-
December 21st, 2002, 02:09 PM
#4
Registered User
Originally posted by NooNoo
H
2k also closes unused maps and refreshes them on demand, its a "feature"
Wise man said...
It's not a BUG, it's an UNDOCUMENTED FEATURE...
Cheers,
Gabriel
and One other thing I saw it also in WIN2K Domain.
Real stupidity beats Artifical Intelligence
Avatar courtesy of A D E P T
-
December 28th, 2002, 11:17 PM
#5
Registered User
its a plus though for networks with slow links.
SMB is a bandwidth hog
-
September 22nd, 2003, 06:06 PM
#6
Found this info on the Microsoft Website:
This behavior occurs because Windows NT Server 4.0, Windows 2000 Server, and Windows Server 2003 can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. The connection can be re-established very quickly, if required.
To resolve this behavior, change the default time-out period on the shared network computer. To do this, use one of the following methods.
NOTE: You cannot change the default time-out period for Microsoft Windows 95-based computers and Microsoft Windows 98-based computers that have shared resources.
Registry Editor
NOTE: You cannot use this method to turn off the autodisconnect feature of the Server service. You can only use this method to change the default time-out period for the autodisconnect feature. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to increase the default time-out period. To do this, follow these steps, and then quit Registry Editor:
Click Start, click Run, type regedit (Windows 2000 or Windows Server 2003) or type regedt32 (Windows NT 4.0), and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters
In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:
On the Edit menu, point to New, and then click REG_DWORD.
Type autodisconnect, and then press ENTER.
Click Hexadecimal.
In the Value data box, type ffffffff, and then click OK.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks