• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 665
  • Last Modified:

local drives not "connected" with remote desktop

I have a strange problem. I have a 2008R2 server(x) that is scheduld to login via an RDP connection with local drives checked to an other 2008R2 server(y) to make back-ups.
Sometimes when it connects to server y the local tape unit of server x is "connected" and sometimes i see a red cross in front of the tape unit. Via cmd the drive is not availible but when i click in the explorer on the tape drive the red cross disapears and i can access the drive.
But my back-up software crashes when the tape unit is "not connected".
How can i solve this problem.
1 Solution
Are you able to map the redirected 'drive' to a drive letter and then access it?  For example:  net use B: \\tsclient\e   (where e is the letter of the redirected drive)
eliza111197Author Commented:
the drive is already mapped to a drive letter.
Raja Jegan RSQL Server DBA & ArchitectCommented:
Seems like your network connections are lost after the drive is idle/unused for some point of time..
And this fix should help you out..

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Were the drives mapped by the same user that logs in? I try to use UNC paths in these situations - mapped drives are not available until user logs in.
eliza111197Author Commented:
i made a script that creates a mapping each time it logs on
eliza111197Author Commented:
the other solutions didn't work

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now