Webmail Port will not bind on port 80

[nuclearsiloman]

I have 2 IPs on my server. My only website is bound to the second IP and AMS is bound to the first (default). When I try to bind AMS to port 80, I get the 'can't bind error'.

According to the help doing this is one of the 3 solutions to get rid of the port 8000. Any ideas?

[BBMB32]

Your computer is already listening on port 80 for your website - regardless if it is on the other IP address. I'm not sure if this would work but you could setup the default website to have a host header for your website (i.e. http://www.mysite.com) and a host header for mail.mysite.com which would redirect with the port 8000 on it. That way, the user doesn't have to type mail.mysite.com:8000

I hope this helps.

Brandon

[m1byo]

If you are using IIS, IIS Will still bind to the IP address regardless of host headers.

The available solutions are:
1. run 2 IP Addresses (IIS will have to be specifically configured not to bind onto the second IP) you can then use 1 IP for IIS and 1 IP for AMS ... not much good if you are running NAT Translation behind a router with only 1 WAN IP.
2. run apache webserver with the reverse proxy installed which then forwards all webmail.xxx.xxx to localhost:8000 ... this requires AMS webmail configured on a different port (in this example port 8000)
3. run an independent reverse proxy on port 80 which forwards IIS host headers to a different port e.g. 81, and AMS host headers to a different port again e.g. 8000.
4. run an iframe or redirect in a webpage hosted on IIS which then lets you bind to port 80

I hope these help.

I have tried most of the above solutions, and IF available, by far the easiest one is running 2 IPs!

Ian

[Code Crafters]

There are several solutions to this.

1) Disable IIS running on port 80.
2) Run IIS or WebMail on another port.
3) Use 2 different computers on different Internet IPs.
4) Bind IIS to port 80 on one IP and AMS to port 80 on another IP. The trouble is that IIS has a bug whereby it wrongly grabs all IPs, binds to the ones it wans then releases the remining IPs for other applications to bind to. In this time AMS will have tried to bind and failed because all are in use: bad IIS tut tut. The soluction is to either set AMS to have a startup delay of about 30 seconds in the general settings next to the NT service option or use the following command to properly bind IIS to the IPs only.

httpcfg set iplisten -i xxx.xxx.xxx.xxx

then restart the computer to rebind everything correctly. Obviously bind AMS to a different IP too.