![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I have a Vista PC with some network drives mapped to folders on a network disc and on an XP PC. In Windows Explorer these initially show after bootup as 'disconnected' with a red cross on the icon but become connected when they are first used and the red cross disappears. If the network drives are not used for a while they again show as disconnected until the next use (and a restart of Explorer in order to update it). This 'timeout' seems to me to have no purpose or benefit as the drives are always available. The mappings are also set to reconnect at bootup anyway. This doesn't prevent their use but does anyone know what, why or where to over-ride this misleading indicator ? 'Computer' seems to hang on to the connected state after the first connection and its use can correct the status shown by Explorer. |
|
|||
|
I have the same problems did anybody else reply.
Lee "Tom Allen" wrote: I have a Vista PC with some network drives mapped to folders on a network disc and on an XP PC. In Windows Explorer these initially show after bootup as 'disconnected' with a red cross on the icon but become connected when they are first used and the red cross disappears. If the network drives are not used for a while they again show as disconnected until the next use (and a restart of Explorer in order to update it). This 'timeout' seems to me to have no purpose or benefit as the drives are always available. The mappings are also set to reconnect at bootup anyway. This doesn't prevent their use but does anyone know what, why or where to over-ride this misleading indicator ? 'Computer' seems to hang on to the connected state after the first connection and its use can correct the status shown by Explorer. |
| Thread Tools | |
| Display Modes | |
|
|