Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
FTP default port 80 without adding 80 in URL
- Thread starter sirlance
- Start date
yes,
you can configure port 80 to be ftp on the server, but you will not be able to get around the ftp://x.y.z:80 limitation.
Reason is, port 80 is defined as a http port by most commercial browser clients, and may have difficulty recognizing ftp. May work though, worth a shot.
If that doesn't work you could just let them use 80 over http and in IIS allow directory browsing. If you disable script and execute privlages for all files, remove all appication mappings, hack your matabase to disable the ASP engine to not start on that website, remove all ISAPI functionality, and use other security mechanisms, unless they are hitting an html page it should function exactly like an ftp server with both netscape and IE.
Not saying I would do that, but hey you asked for an option.
Good Luck,
Galrahn
galrahn@galrahn.com
you can configure port 80 to be ftp on the server, but you will not be able to get around the ftp://x.y.z:80 limitation.
Reason is, port 80 is defined as a http port by most commercial browser clients, and may have difficulty recognizing ftp. May work though, worth a shot.
If that doesn't work you could just let them use 80 over http and in IIS allow directory browsing. If you disable script and execute privlages for all files, remove all appication mappings, hack your matabase to disable the ASP engine to not start on that website, remove all ISAPI functionality, and use other security mechanisms, unless they are hitting an html page it should function exactly like an ftp server with both netscape and IE.
Not saying I would do that, but hey you asked for an option.
Good Luck,
Galrahn
galrahn@galrahn.com
- Thread starter
- #3
Thanks for the information.
I was also told I can edit the "service" file to achieve this. I found the file, changed the default ports for FTP from 20/21 to 80/81. I made sure it was changed in ISM. I then rebooted (just in case), and verfiied IIS had started. I then tried to access the site, but this time I got a message:
"The folder 'ftp://systemname' is read-only because the proxy server is not set up to allow full access. To move, paste, rename, or delete files, you must use a different proxy. For information on changing your proxy, contact your administrator".
The dir is set for full access for everyone. Read/write is set in ISM. On the normal ports, I was able to browse and post. No proxy server in house, and even if I do, bith systems are internal to the network not needing to use a proxy.
Has anyone seen this message? If so, how do I get around it.
I was also told I can edit the "service" file to achieve this. I found the file, changed the default ports for FTP from 20/21 to 80/81. I made sure it was changed in ISM. I then rebooted (just in case), and verfiied IIS had started. I then tried to access the site, but this time I got a message:
"The folder 'ftp://systemname' is read-only because the proxy server is not set up to allow full access. To move, paste, rename, or delete files, you must use a different proxy. For information on changing your proxy, contact your administrator".
The dir is set for full access for everyone. Read/write is set in ISM. On the normal ports, I was able to browse and post. No proxy server in house, and even if I do, bith systems are internal to the network not needing to use a proxy.
Has anyone seen this message? If so, how do I get around it.
- Status
Similar threads
- Locked
- Question
- Locked
- Question