Oh well. Backup and Punt on both fronts I guess.
NetSetMan looks good in description and maybe it is just me but it hit all around the problem without actually giving me what I need. I have seen such a program somewhere that is like a pumped up version of netsetman. I remember it allowing you to set up such a way that even included what printer would be the default for a given profile. I guess i can write s imple script with net use to kill the one mapping path and use the other. But Hope Springs Eternal. Maybe... It's outr there somewhere. Because its a little more complicated than that.
While in office it has to use an actual mapped network drive to get to R: , if NOT in the office, it has to run NETDRIVE2 to create the FTP mapping for the exact same drive letter but get there with FTP. I have already played enough with netdrive to know that it isn't happy if there are any leftover maps that USED to be connected to that same setup with normal networking
I am tempted to try amputating "mountpoints2" from the registry before letting netdrive even run. It just gets recreated anyway.
These are people who I guarantee will shut the lid on their laptop putting it to sleep and while it "dreams" about the old "\\10.0\x.x.x\sharedfolder" connection being mapped to R: and wakes up in a Radison Inne somewhere, connects to a 192.168.1.x dhcp and cant find the way to get to the files on R:. In their case, NetDrive2 won't even run automatically since they never turned the sytem off., ANd if they RUN it, it will try to do a real FTP connect to the Server's Working FTP connecton but fail because the internal Windows config still shows the user connected via another method (The old 10.x.x.x\sharedfolder).
So it gives an error report which no one will understand. EASY to fix. IF! they Reboot. But they won't.
A scripted app to close the old drive setup and /Disconnect and remove it completely is probably the only sure way. Then continue run Netdrive2 which will have no problem making the FTP connection to the public IP. Either way, it is the SAME files on the SAME Server. I just have to get them in through a different type of door. FTP has checked out so far to work every time at any location so it beats out trying VPN's that connect every time but wont allow a mapped drive letter much of the time, giving only a "network Place". This used to be so simple to map drive letters over IP across the net. Those were the days. I can also add in the removal of the primary printer so they can grab whatever is where they are because most of them don't know that the default printer STAYS as the defrault printer until they change it. That is a feature you would think MS would have already added. Maybe by Windows 14. ?
Sometimes I feel like I work for a 3rd World (no make that 4th or 5th world) company where technology has yet to arrive and most are better off with pencils and REAL "Paper Notepads" not "Notebooks". If I told them i could get cheap paper "notepads" that had an unlimited Battery Run time they would jump all over that before anyone ever figured it out..