Running Apache 2.2.10 on port 21 on windows

Page not serving when running apache on port 21

[vinayd]

Hi,

I've installed Apache 2.2.10 on windows box and ran it iniially on port 80. it works fine.

Listen 80

Later I updated httpd.conf file to run it on port 21, it starts properly but does not server any page.

Listen 21

I updated httpd.conf to test apache on other ports and everything works fine.

Please let me know how can I make it running on port 21.

Thanks
Vinay

[coopster]

Welcome to WebmasterWorld, vinayd.

I'm not entirely certain but if you are attempting to access the server on port 21 with a web browser you may find that the browser is attempting to initiate an FTP session and finding no FTP server it fails.

You said it does not serve a page ... to what? Are you indeed attempting to use a web browser? Try to ping the port instead.

[vinayd]

Thanks for reply,

When I ran command 'netstat -na' its showing that server is listening on port 21 but when I try to get content from browser using [mysite.com:21...] , no page is displayed. I'm using IE for getting page, I'm explicitly giving HTTP to browser on port 21. I’ll check it with other browser to check if its browser related issue or apache is not giving content properly. Please provide suggestions to resolve this issue.

[jdMorgan]

Suggestion: Do not use the Web-standard FTP port (21) for an HTTP server (port 80). You are going to have problems both on the server side and on the client side. For example, you won't be able to use a standard FTP server on the same machine as this non-standard HTTP server. If an FTP server comes with the server software "bundle" such as WAMP or XAMPP, you will have to re-configure it or uninstall it; Otherwise the servers will 'fight' for the port, and whichever one grabs the socket first will prevent the other from connecting, and likely cause it to fail on start-up.

If you try to make this site available to the public, you may have massive customer-support issues with browsers, which will require the port number to be typed-in after the domain name. You can use non-standard ports for security or other reasons if you have to. Just don't use any "well-known" ports that are standardized for use with other services.

Generally, avoid any non-standard port below port number 1024.

Jim