Vista can't connect to NAS device.

[G0AOZ]

User has several networked XP machines which backup to a NAS device using simple batch files with the XCOPY command. The NAS device has a mapped drive letter on all the these computers.

A Vista machine has just been connected to the network and that sees the NAS device and also has a drive letter mapped. However, going into the Command Prompt window and trying to change to the designated mapped drive letter (S, completely hangs the Vista machine.

I have discovered that by simply adding the mapped drive letter (S:\) to the end of the PATH line in System Variables within System Properties in Control Panel, the batchfile now works and Vista no longer hangs.

Is this the right way to solve this one, or will I run into problems elsewhere?

ROGER - G0AOZ.

 

[smah]

Do you mean that vista hangs when you start the command prompt, or do you mean the vista hangs when you execute the 'net use' command? Are there any clues in event viewer when this happens?

 

[linney]

Any clues in these?

vista - terrastation
thread1583-1362143

http://www.google.com/search?q=NAS+device++vista&rls=com.microsoft:

 

[jdemmi]

I have Vista Business and a Buffalo NAS...I do not experience that problem.

But let me ask you this question.....

When you boot up the PC and login more than likely the drive will be displayed in "My Computer" with a RED X through it because the connection to the networked drive has not been established. In my case double clicking it prompts me foe my user name and password (different than my domain credentials) and then establishes the connection. If you do not have different credentials assigned to the share double clicking the drive would still establish the connection. So....can you let me know if, when you're typing S: at a command prompt if the drive is displayed as "disconnected" (with the RED X)?

(I am wondering if by adding the drive letter to the path it is forcing the connection to be established automatically upon boot)

-- Jason
"It's Just Ones and Zeros

 

[G0AOZ]

No, I can open the Command Prompt window ok, and "normal" commands like ipconfig etc., all work fine. If, however, I try to go to the previously mapped drive by type S: <Enter> it hangs and eventually I see "not responding" at the top of the prompt window. This doesn't appear to happen if I make the addition to the PATH line in System Variables.

Prior to altering the PATH statement, going to D: (DVD) or E: (flash drive) worked fine. Just not to the NAS device...

Thanks for the links Linney - don't see anything that points me towards the problem I have though.

Anyhow, problem appears to be solved by this inclusion in the path, although I am not entirely sure why...

ROGER - G0AOZ.

 

[G0AOZ]

Jdemmi, no this mapped drive was available under My Computer immediately after boot up, and files accessible with Explorer. No red X appeared against the drive at any stage. After doing this check, I went to the Command Prompt, and then it hung. Hasn't done this trick since I added S: to the path...

ROGER - G0AOZ.

 

[SimonDavies]

Are there any 6004 error messages in the event log?

Simon

The real world is not about exam scores, it's about ability.