Connect using FTP over VPN to map your network drives.
I had this script setup on a Windows 2003 Small Business Server (SBS) to allow users the option of NOT using Remote Desktop.
I find most of the time people have the apps and software they need on their computers when they are away from the office.
All they really need is the storage folders at the office.
We typically can map the drives over the VPN and be done with it.
But, and believe me when I say this....
I was about ready to replace everyone's computer because of the path resource issues.
It's simple, create a UNC path share while connected with the VPN.
But, now we have a ton of things to look at, XP Home, MAC, Phones, and users.
Not a single person could use the UNC path over the VPN for one reason or another.
Well, the fix was easy and here's what I did.
I shared a common folder in the FTP server.
Start your FTP services on your server. It doesn't matter who's FTP server you're running but you'll need that port 21 connection setup.
Now, setup a "Virtual Folder" and map that to the users home folder which will have the shares in it. If not, create a virtual folder within their home folder of all the network folders they need to access. If it's allot drop down on the root level to save creating ICONS.
You really should only be sharing a few folders but not everyone is like me.
Next up, the script to have them connect to the FTP and setup the local folders as NET USE Mapped drives. (That classic line, I'm missing my T: drive!)
If you have your server setup here's the steps for the client.
- Connect to your VPN.
Open any web browser (Chrome)
From the address line type:
ftp://192.168.x.x/folder/folder3 (Z: drive maybe)
Ok, not very scripty but that's the testing part. Next up you have your BAT files do all the work.