General discussion

Locked

Mapped Drive issues

By richardd ·
The company I work for uses mapped drives to access info through a program used for titles for houses. A few of the client machines while working in this program will stop working and give a error message can not locate directory (network drive path) of the selected system. Even after I close out of the program and open the mapped drive directly same error. This happens every day and the only way to get them to log back into the program is to either restart the machine or remap the drive.Plenty of licenses of server and software. Cant figuire this one out. Any Help would be most excellent.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

UNC Path

by zenobyt In reply to Mapped Drive issues

Are you able to modify the program to use the UNC path instead of the mapped drive letter?

Collapse -

OS's

by jbaker In reply to Mapped Drive issues

What are the client and server OS's There are some issues with XP dropping the connection to a 2000 Server after what the XP perceives to be a period of inactivity, sometimes while a file is opne on that mapped drive.

Collapse -

Drive Mapping May Time Out on a Windows 2000-Based Computer

by Schema In reply to Mapped Drive issues

Microsoft Knowledge Base Article - Q297684
Drive Mapping May Time Out on a Windows 2000-Based Computer
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional

SYMPTOMS
When you perform drive mapping from a Windows 2000-based client computer to either a Microsoft Windows NT or Windows 2000 network share, the drive mapping may be disconnected after 15 minutes of inactivity and Windows Explorer may display a red "X" on the icon of the mapped drive. However, if you attempt to access or browse the mapped drive, it reconnects quickly.
CAUSE
This behavior can occur because both Windows NT Server version 4.0 and Windows 2000 Server can drop idle connections after a specified time-outperiod, which by default is 15 minutes, so that server resources are not wasted on unused sessions. The connection can be re-established very quickly at a later time, if required.
RESOLUTION
To resolve this behavior, use a command to change the default time-out period on the Windows NT Server 4.0 or Windows 2000 Server: At a command prompt, type: net config server /autodisconnect:30.

The valid value range to configure this setting from a command line is from -1 through 65,535 minutes. To disable Autodisconnect, set it to -1.

NOTE: This step must not be confused with the remote access Autodisconnect parameter that is turned off if you set it to a value of zero (0).

If you set Autodisconnect to zero (0), this setting is not turned off and after a few seconds of idle time very fast disconnections can occur.

Collapse -

by solonow In reply to Drive Mapping May Time Ou ...

You should also check the application vendors FAQ support section or call tech support. They may already have an answer for you....

Sol

Back to IT Employment Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums