remote machine needs to map a drive over VPN.
I'm using windows RRAS.....only have the VPN function on.
Maybe I can have a login script run when a user VPNs in over RRAS?
Here is my trouble:
I have a server "A" that is scheduled to VPN into another server "B" every night. Then, server "A" is supposed to backup one of its folders to a shared drive (U:\) on server B.
The scheduled VPN-in works fine. I just use the AT command.
The sticky point is the drive mapping. One possible solution would be to have a login script. If my VPN server "A" had a login script to map the drive it needs, then I'd be fine. But, as we know, login scripts run at domain login NOT vpn sign-on.
I also tried to just map the drive beforehand, manually, choosing persistent connection. I figured as soon as VPN connects, the mapped drive will just *be there*. But no, NT backup reports it as unavailable.
So, how can I get a remote machine to map a drive after it calls in via VPN?
To sum up:
1. Machine A VPNs into Machine B (THIS WORKS)
2. Machine A maps a shared drive (say, U:\) from machine B (\\machineB\files)
3. Machine A uses NT backup to copy some files to machine B
Maybe I can have a login script run when a user VPNs in over RRAS?
Here is my trouble:
I have a server "A" that is scheduled to VPN into another server "B" every night. Then, server "A" is supposed to backup one of its folders to a shared drive (U:\) on server B.
The scheduled VPN-in works fine. I just use the AT command.
The sticky point is the drive mapping. One possible solution would be to have a login script. If my VPN server "A" had a login script to map the drive it needs, then I'd be fine. But, as we know, login scripts run at domain login NOT vpn sign-on.
I also tried to just map the drive beforehand, manually, choosing persistent connection. I figured as soon as VPN connects, the mapped drive will just *be there*. But no, NT backup reports it as unavailable.
So, how can I get a remote machine to map a drive after it calls in via VPN?
To sum up:
1. Machine A VPNs into Machine B (THIS WORKS)
2. Machine A maps a shared drive (say, U:\) from machine B (\\machineB\files)
3. Machine A uses NT backup to copy some files to machine B
Have you tried a 3rd Party backup utility such as SmartSync (www.smartsync.com)? I know this has a event scheduler feature that will allow you run a vpn connection and other scripts prior to running your backup or sync. I haven't use the function myself - just know it is there. They give you a free 30 day trial, so check it out.
ASKER
I answered this myself.
A good way to authenticate with another machine, without explicitly mapping a drive is:
net use \\machinename\IPC$ /user:username password
Then for NTBackup, don't use a mapped drive. Back up files to a path such as "\\machinename\share".
So, instead of mapping a U:\ drive to \\machinename\share then backing up to it, I authorize myself using the IPC$ then back up to the share name - no drive letters required.
It works!
A good way to authenticate with another machine, without explicitly mapping a drive is:
net use \\machinename\IPC$ /user:username password
Then for NTBackup, don't use a mapped drive. Back up files to a path such as "\\machinename\share".
So, instead of mapping a U:\ drive to \\machinename\share then backing up to it, I authorize myself using the IPC$ then back up to the share name - no drive letters required.
It works!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.