FD in Oudenaarde
New Member
Hi,
I notice a strange problem here since I have a vista machine (everything was just fine while I used XP) and I wonder if somebody can help.
A list of what I experience and some explanation to start with.
- We have a company network here with multiple network drives located on windows 2003 servers.
- When I open "explorer" in vista it shows me my local disk + all network drives when I select "computer". As is the case all network drives are properly activated and therefore are not shown with red crosses to indicate not being connected.
- When I use any other application and use the "open" facility in it to open a file and work on it it rightly always shows an "explorer" like file selection window. Within it I then choose "computer" again.
- This is where things go wrong. The moment I select "computer" it shows me my local disk + the network drives again. The difference though is that always all networks drives are shown as inaccessible (red cross on them).
- In reality that is not the case as I can effortlessly click any network drive and get instant access to it, selecting my file is never a problem.
- Last observation: when I repeat the file selection operation the network drive is no longer crossed out (red cross gone).
Now for the problem: If I have not performed a file selection procedure, as described above, at least once on a network drive I cannot double click a file on that drive in windows explorer to get the application (to which it is associated for automatic opening) to open it automatically. I always get a message that the file does not exist in spite of the fact that windows explorer shows the network drive to be accessible and actually lists/shows the file.
If I have performed a file opening procedure VISTA appears to remember the drive has been accessed and effortlessly performs correctly when you double click a file. it starts the associated application, offers the coordinates of the file to the other application and all works well.
Bottom line: If I do not perform a "file open" procedure first I cannot double click a file on a network drive and get it to open. Not a major problem but a real nuisance if you are in a hurry to open a file.
Oh yeah: the problem does not occur on the local hard disk, there I can always double click any file and it always opens correctly.
Anybody got any suggestions how to solve this one or, at least, what the cause is ?
Any help would be much appreciated.
FD
I notice a strange problem here since I have a vista machine (everything was just fine while I used XP) and I wonder if somebody can help.
A list of what I experience and some explanation to start with.
- We have a company network here with multiple network drives located on windows 2003 servers.
- When I open "explorer" in vista it shows me my local disk + all network drives when I select "computer". As is the case all network drives are properly activated and therefore are not shown with red crosses to indicate not being connected.
- When I use any other application and use the "open" facility in it to open a file and work on it it rightly always shows an "explorer" like file selection window. Within it I then choose "computer" again.
- This is where things go wrong. The moment I select "computer" it shows me my local disk + the network drives again. The difference though is that always all networks drives are shown as inaccessible (red cross on them).
- In reality that is not the case as I can effortlessly click any network drive and get instant access to it, selecting my file is never a problem.
- Last observation: when I repeat the file selection operation the network drive is no longer crossed out (red cross gone).
Now for the problem: If I have not performed a file selection procedure, as described above, at least once on a network drive I cannot double click a file on that drive in windows explorer to get the application (to which it is associated for automatic opening) to open it automatically. I always get a message that the file does not exist in spite of the fact that windows explorer shows the network drive to be accessible and actually lists/shows the file.
If I have performed a file opening procedure VISTA appears to remember the drive has been accessed and effortlessly performs correctly when you double click a file. it starts the associated application, offers the coordinates of the file to the other application and all works well.
Bottom line: If I do not perform a "file open" procedure first I cannot double click a file on a network drive and get it to open. Not a major problem but a real nuisance if you are in a hurry to open a file.
Oh yeah: the problem does not occur on the local hard disk, there I can always double click any file and it always opens correctly.
Anybody got any suggestions how to solve this one or, at least, what the cause is ?
Any help would be much appreciated.
FD
