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.
Who is Participating?
eliza111197Author Commented:
i made a script that creates a mapping each time it logs on
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.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
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..

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:
the other solutions didn't work
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.