remember we had a discussion about w2k auto-disconnecting mapped drives. I forgot totally about that until we just implemented new policy of persistent mappings.
I remember I altered the server's side to not disconnect but there was something on the client too.
do you boys remember what those were? lanmanworkstation or something similar comes to mind. and that MS said it does not relate to w2k as it has not this problem whereas w2k was the first one to have it.
The information in this article applies to:
Microsoft Windows Server 2003, Standard Edition
Microsoft Windows Server 2003, Enterprise Edition
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Microsoft Windows Small Business Server 2003, Premium Edition
Microsoft Windows Small Business Server 2003, Standard Edition
MartMart KiX Supporter
Registered: 2002-03-27
Posts: 4673
Loc: The Netherlands
Maybe stupid remark but the way I understand it it also has to be set on the client. Cause client disconnects it.
At the command line part of the document is speaks about changing the config of the server service which is running on normal w2k pro box.
wizard, just like said before, it affects only the SERVER service. that has nothing to do with mappings where the computer is the CLIENT (workstation)
it only affects on shares mapped by other systems. but as this problem started when w2k came to normal networks, it seems the problem ain't on the server side, but on client.
NT client seems to better handle the timed-out network connection than any newer windows version.
