Mapping a drive to a server in the DMZ

[TheFanatic]

I think I have been looking at this one too long and am just missing something obvious. I have a web designer that RDP's into a 2000 server every day. That server has a drive mapped to a system in the DMZ. Since the machine in the DMZ is not part of the domain we use the credentials from a local account on the DMZ machine to map the drive.

The drive is mapped by using another user name and password (that of the local account created on the DMZ machine), yet every time the user RDP's into the 2000 server in our domain, he has to retype the password for the local account on the DMZ machine the first time he accesses the mapped drive. The drive was set to reconnect at logon.

Why does the user have to reauthenticate every time? What am I missing here?

 

[wallst32]

The RDP login is not the same as console. If you have a drive mapped on the console it does not port over to RDP sessions. So once the RDP session is closed the drive mapping is closed and must be re-established.

What you do is have the user "disconnect" from RDP instead of logging out. This would preserve the user's environment (including the drive mapping).