Discussion Locked

Mapped drives

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
How is it possible for a work station to have a valid mapped drive to a server (peer to peer) and at the same time show broken mapped drives to the same server?

8 replies

by gigelul

Hi,
Maybe these broken mapped drives don't exist (are old shares), was mapped by other user/password or you don't have permissions to access that shares.
What OS is on your server?

by ramjet1

They are current working mappings. I can understand all of them being in one state or the other but they should all be of the same status. It's a simple win'98 peer to peer. Each w.s. has the same 3 mapped drives to the same workstation/server. One oddball shows 2 broken and 1 unbroken.

by gigelul

How many users/workstations are in your network?
In a pear to pear network a share allow maximum 10 connections at the same time!

by ramjet1

Less then 10. This configuration has worked for solidly for a few years.

They are current working mappings. I can understand all of them being in one state or the other but they should all be of the same status. It's a simple win'98 peer to peer.Each w.s. has the same 3 mapped drives to the same workstation/server. One oddball shows 2 broken and 1 unbroken.

by nikki96

It's probably just windows autodisconnect. Windows will disconnect the connection after a set amount of time. Just click on the icon and it re-opens the connection.
You can turn that off, but it is OS dependent (Windows98 or NT or 2000 all have different methods).

HTH
Nikki

by saihib

Nope, don't work that way, sport. Autodisconnet kicks in by default in Win2K after 15 minutes of inactivity on a mapped drive. If your "server" is a different OS, let us know, we may be able to help. In order to keep connections persistent you can do one of two things: Edit the Registry or change policy in Active Directory. Let us know which path you want to take.

by vh_s

Nope, it is not a question of whether you have peer-to-peer and therefore 10 wks max.

This lies in how Windows handles the mapped drive when it start-up.

The setting lies in the Network Applet of Control Panel. Click the Client for MicrosoftNetwork -> Properties, and there you should find a radio button Quick Links.

This means that during startup, Windows would assume that the connection is available and that Windows wouldn't test for its availability. Therefore Windows would show this connection / mapped drive as broken map. But...., whenever you click on the broken map, Windows would directly test this connection and (sometimes, yes I know!) would repaint the figure and the red-X would disappear.

The setting of Quick Linksis a matter of speedying the startup only.

One case,
You connect to the internet, and mapped a website into a drive using its ip address directly. So you could type in the Map Network Drive:

F: \\xxx.xxx.xxx.xxx\shares

This connection would not be always available. So, you use that quick links so that Windows wouldn't test its availability. Only when you are sure that you are connected to the internet, you click on that drive.

vh_s

by ramjet1

Problem disappeared on its on. Still don't know what caused it to show up or go away.

This discussion is closed to new replies.