just to confirm. What you got was a normal drive letter thn could be accessed just any other.
If you go to a dos cmd prompt, you can type in x: and it open to yout ftp folder.
once there, you can create folders, copy files into them and have no issues doing so. They upload when sent & download back if pulled.?
For all intents, a Normal Shared Network folder accessed with a drive letter. If so, i m doing something very wrong.
Please send me the link to dl the copy you got maybe mine was corrupted?
You did not have to setup anything odd?, you are using port 21? On the FTP server, was it remote from your home.
If I still cannot get in to work I will IM your with credentials to access the FTP server at the office here and give you a login to see if you can get into it.
if you can, then Christmas came early!
This is a normal windows 2008R2 Box with IIS setup for FTP. I can access the shared folder with no problem while on the same local network
That is essential for this to work. This means people IN the office have the full 1GB data throuput for all access to those files as a normally mapped network drive to letter R:.
when they leave the office to travel or go home as soon as they try to connect to R: the NetSet program i found will switch their mspping to FTP-USE. Same drive-letter , same files. Just slower. When they come back to office, the NetSet program switches them back to the local High Speed drive mapping. I would be a Real Hero for a change.
I still don't know why WINDOWS wont work when it plainly says it will.
Looking forward to the PROOF of the Pudding (Hope it is 180Proof