Accessing Webmail without using port No. extension
Accessing Webmail without using port No. extension
am 07.08.2007 00:04:37 von Nirvana
Hi All,
I've web server and mail server running on same Windows 2k3 + IIS 6
box.
Mail server is Code Crafters Ability Mail Server.
I can access mail server by using http://www.mydomain.com:1234
But I want to access mail server by just typing URL of domain without
port extension
E.g. http://webmail.mydomain.com
I tried 2 solutions
1) Host header solution: I configured webmail.mydomain.com hos header
and pointed port to 1234
- This obviously fails as I'm trying to use port 1234 which is being
used by mail server
2) I configured webmail.mydomain.com as a separate website
While configuring I pointed the home directory to a dummy empty folder
and then I redirected the URL to http://www.mydomain.com:1234
Selected "redirection to another URL"
Selected "exact URL" and "permanent redirection"
- I ended up at same place where I started from. This solution
redirects http://webmail.mydomain.com to http://www.mydomain.com:1234
Now I'm lost how do I make this work?
My requirement is I don't want the port number, I want it to access on
Port 80. Reason is I want to access webmail behind a proxy which
blocks almost all ports except 80.
I can't run mail server on port 80 as I run web server.
Any help would be appreciated. I can offer pure British Beer ;)
Cheers
Re: Accessing Webmail without using port No. extension
am 07.08.2007 00:10:32 von Nirvana
On Aug 6, 11:04 pm, Nirvana wrote:
> Hi All,
> I've web server and mail server running on same Windows 2k3 + IIS 6
> box.
>
> Mail server is Code Crafters Ability Mail Server.
>
> I can access mail server by usinghttp://www.mydomain.com:1234
>
> But I want to access mail server by just typing URL of domain without
> port extension
> E.g.http://webmail.mydomain.com
>
> I tried 2 solutions
> 1) Host header solution: I configured webmail.mydomain.com hos header
> and pointed port to 1234
> - This obviously fails as I'm trying to use port 1234 which is being
> used by mail server
>
> 2) I configured webmail.mydomain.com as a separate website
> While configuring I pointed the home directory to a dummy empty folder
> and then I redirected the URL tohttp://www.mydomain.com:1234
>
> Selected "redirection to another URL"
> Selected "exact URL" and "permanent redirection"
>
> - I ended up at same place where I started from. This solution
> redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> Now I'm lost how do I make this work?
>
> My requirement is I don't want the port number, I want it to access on
> Port 80. Reason is I want to access webmail behind a proxy which
> blocks almost all ports except 80.
>
> I can't run mail server on port 80 as I run web server.
>
> Any help would be appreciated. I can offer pure British Beer ;)
>
> Cheers
I also tried to run webmail.mydomain.com on port 1234 but obviously it
throws conflict.
Re: Accessing Webmail without using port No. extension
am 07.08.2007 05:19:31 von Ken Schaefer
"Nirvana" wrote in message
news:1186437877.676396.205730@l70g2000hse.googlegroups.com.. .
> Hi All,
> I've web server and mail server running on same Windows 2k3 + IIS 6
> box.
>
> Mail server is Code Crafters Ability Mail Server.
>
> I can access mail server by using http://www.mydomain.com:1234
>
> But I want to access mail server by just typing URL of domain without
> port extension
> E.g. http://webmail.mydomain.com
>
> I tried 2 solutions
> 1) Host header solution: I configured webmail.mydomain.com hos header
> and pointed port to 1234
> - This obviously fails as I'm trying to use port 1234 which is being
> used by mail server
What you should be doing is:
a) configuring a Host header of "webmail.mydomain.com" on the current
website listening on port 1234.
b) Change the port from 1234 to port 80
c) Configure a DNS entry to point webmail.mydomain.com -> IP address of your
server
> 2) I configured webmail.mydomain.com as a separate website
> While configuring I pointed the home directory to a dummy empty folder
> and then I redirected the URL to http://www.mydomain.com:1234
>
> Selected "redirection to another URL"
> Selected "exact URL" and "permanent redirection"
>
> - I ended up at same place where I started from. This solution
> redirects http://webmail.mydomain.com to http://www.mydomain.com:1234
>
> Now I'm lost how do I make this work?
You need to read up a bit on how HTTP works. The Host header is a HTTP
header that the client sends to the server to indicate what website it wants
to access. IIS uses this to route the request to the correct website. This
is the way that you can have multiple websites all listening on the same IP
+ port (port 80), and IIS still knows which website the client wants to
access.
Cheers
Ken
> My requirement is I don't want the port number, I want it to access on
> Port 80. Reason is I want to access webmail behind a proxy which
> blocks almost all ports except 80.
>
> I can't run mail server on port 80 as I run web server.
>
> Any help would be appreciated. I can offer pure British Beer ;)
>
>
> Cheers
>
Re: Accessing Webmail without using port No. extension
am 07.08.2007 08:31:52 von Kristofer Gafvert
I don't understand this. You say that you are now using port 1234 to
access webmail. You also say that this port is used by your email server.
This doesn't work. You cannot have the email server and IIS listening on
the same port (because they are two different processes). If you are using
port 1234 to access the webmail at this moment, perhaps you are not using
IIS at all?
Anyway, if you are indeed using IIS, we should be able to make this working.
What you need to do is:
1. Make sure that DNS is working and webmail.mydomain.com is pointing to
the IP address of the webserver. (should already be working since you
managed to set up a redirection)
2. Modify the existing website to use port 80 and the webmail.mydomain.com
host header.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Nirvana wrote:
>Hi All,
>I've web server and mail server running on same Windows 2k3 + IIS 6
>box.
>
>Mail server is Code Crafters Ability Mail Server.
>
>I can access mail server by using http://www.mydomain.com:1234
>
>But I want to access mail server by just typing URL of domain without
>port extension
>E.g. http://webmail.mydomain.com
>
>I tried 2 solutions
>1) Host header solution: I configured webmail.mydomain.com hos header
>and pointed port to 1234
>- This obviously fails as I'm trying to use port 1234 which is being
>used by mail server
>
>2) I configured webmail.mydomain.com as a separate website
>While configuring I pointed the home directory to a dummy empty folder
>and then I redirected the URL to http://www.mydomain.com:1234
>
>Selected "redirection to another URL"
>Selected "exact URL" and "permanent redirection"
>
>- I ended up at same place where I started from. This solution
>redirects http://webmail.mydomain.com to http://www.mydomain.com:1234
>
>Now I'm lost how do I make this work?
>
>My requirement is I don't want the port number, I want it to access on
>Port 80. Reason is I want to access webmail behind a proxy which
>blocks almost all ports except 80.
>
>I can't run mail server on port 80 as I run web server.
>
>Any help would be appreciated. I can offer pure British Beer ;)
>
>
>Cheers
Re: Accessing Webmail without using port No. extension
am 07.08.2007 08:57:16 von Nirvana
On Aug 7, 4:19 am, "Ken Schaefer"
wrote:
> "Nirvana" wrote in message
>
> news:1186437877.676396.205730@l70g2000hse.googlegroups.com.. .
>
>
>
> > Hi All,
> > I've web server and mail server running on same Windows 2k3 + IIS 6
> > box.
>
> > Mail server is Code Crafters Ability Mail Server.
>
> > I can access mail server by usinghttp://www.mydomain.com:1234
>
> > But I want to access mail server by just typing URL of domain without
> > port extension
> > E.g.http://webmail.mydomain.com
>
> > I tried 2 solutions
> > 1) Host header solution: I configured webmail.mydomain.com hos header
> > and pointed port to 1234
> > - This obviously fails as I'm trying to use port 1234 which is being
> > used by mail server
>
> What you should be doing is:
> a) configuring a Host header of "webmail.mydomain.com" on the current
> website listening on port 1234.
> b) Change the port from 1234 to port 80
> c) Configure a DNS entry to point webmail.mydomain.com -> IP address of your
> server
>
> > 2) I configured webmail.mydomain.com as a separate website
> > While configuring I pointed the home directory to a dummy empty folder
> > and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > Selected "redirection to another URL"
> > Selected "exact URL" and "permanent redirection"
>
> > - I ended up at same place where I started from. This solution
> > redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> > Now I'm lost how do I make this work?
>
> You need to read up a bit on how HTTP works. The Host header is a HTTP
> header that the client sends to the server to indicate what website it wants
> to access. IIS uses this to route the request to the correct website. This
> is the way that you can have multiple websites all listening on the same IP
> + port (port 80), and IIS still knows which website the client wants to
> access.
>
> Cheers
> Ken
>
> > My requirement is I don't want the port number, I want it to access on
> > Port 80. Reason is I want to access webmail behind a proxy which
> > blocks almost all ports except 80.
>
> > I can't run mail server on port 80 as I run web server.
>
> > Any help would be appreciated. I can offer pure British Beer ;)
>
> > Cheers
Hi Ken,
All is setup as you described here.
"b) Change the port from 1234 to port 80 "
Do you mean to change the port 1234 to 80 in e-mail server?
Its not clear.
I can't change e-mail server's web service to use port 80 as it says
conflict.
Re: Accessing Webmail without using port No. extension
am 07.08.2007 11:04:50 von Nirvana
On Aug 7, 7:31 am, "Kristofer Gafvert"
wrote:
> I don't understand this. You say that you are now using port 1234 to
> access webmail. You also say that this port is used by your email server.
>
> This doesn't work. You cannot have the email server and IIS listening on
> the same port (because they are two different processes). If you are using
> port 1234 to access the webmail at this moment, perhaps you are not using
> IIS at all?
>
> Anyway, if you are indeed using IIS, we should be able to make this working.
>
> What you need to do is:
> 1. Make sure that DNS is working and webmail.mydomain.com is pointing to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection)
> 2. Modify the existing website to use port 80 and the webmail.mydomain.com
> host header.
>
> --
> Regards,
> Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>
> Nirvana wrote:
> >Hi All,
> >I've web server and mail server running on same Windows 2k3 + IIS 6
> >box.
>
> >Mail server is Code Crafters Ability Mail Server.
>
> >I can access mail server by usinghttp://www.mydomain.com:1234
>
> >But I want to access mail server by just typing URL of domain without
> >port extension
> >E.g.http://webmail.mydomain.com
>
> >I tried 2 solutions
> >1) Host header solution: I configured webmail.mydomain.com hos header
> >and pointed port to 1234
> >- This obviously fails as I'm trying to use port 1234 which is being
> >used by mail server
>
> >2) I configured webmail.mydomain.com as a separate website
> >While configuring I pointed the home directory to a dummy empty folder
> >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> >Selected "redirection to another URL"
> >Selected "exact URL" and "permanent redirection"
>
> >- I ended up at same place where I started from. This solution
> >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> >Now I'm lost how do I make this work?
>
> >My requirement is I don't want the port number, I want it to access on
> >Port 80. Reason is I want to access webmail behind a proxy which
> >blocks almost all ports except 80.
>
> >I can't run mail server on port 80 as I run web server.
>
> >Any help would be appreciated. I can offer pure British Beer ;)
>
> >Cheers
HI Kris
1) I use http://xx.xxx.xx.xxx:1234 to access my webmail. My e-mail
server is a 3rd party server (Ability Mail Server -
http://www.code-crafters.com/abilitymailserver/) which includes SMTP,
Webmail, IMAP, POP etc..
I use IIS as web server only.
2) In this 3rd party server there is an option (obviously) to select
the port for Webmail. And this is the port 1234 which I set here. So
my webmail is listening on port 1234. It works fine and I can access
my webmail from http://xx.xxx.xx.xxx:1234
3) DNS is pointing correctly. I've set the DNS for
webmail.mydomain.com to point to my server IP Address.
Till this point all is clear and all is working fine.
Now the problem is how do I make webmail.mydomain.com working?
If I change the webmail.mydomain.com host header in IIS to use port
1234 then it gives conflict as the mail server is already running
Webmail on port 1234.
And this is trouble. you can't have 2 services running on same port?
And that is where I'm stuck.
It is sunny today see if I can get it working ;)
Re: Accessing Webmail without using port No. extension
am 07.08.2007 11:11:38 von Nirvana
On Aug 7, 7:31 am, "Kristofer Gafvert"
wrote:
> I don't understand this. You say that you are now using port 1234 to
> access webmail. You also say that this port is used by your email server.
>
> This doesn't work. You cannot have the email server and IIS listening on
> the same port (because they are two different processes). If you are using
> port 1234 to access the webmail at this moment, perhaps you are not using
> IIS at all?
>
> Anyway, if you are indeed using IIS, we should be able to make this working.
>
> What you need to do is:
> 1. Make sure that DNS is working and webmail.mydomain.com is pointing to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection)
> 2. Modify the existing website to use port 80 and the webmail.mydomain.com
> host header.
>
> --
> Regards,
> Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>
> Nirvana wrote:
> >Hi All,
> >I've web server and mail server running on same Windows 2k3 + IIS 6
> >box.
>
> >Mail server is Code Crafters Ability Mail Server.
>
> >I can access mail server by usinghttp://www.mydomain.com:1234
>
> >But I want to access mail server by just typing URL of domain without
> >port extension
> >E.g.http://webmail.mydomain.com
>
> >I tried 2 solutions
> >1) Host header solution: I configured webmail.mydomain.com hos header
> >and pointed port to 1234
> >- This obviously fails as I'm trying to use port 1234 which is being
> >used by mail server
>
> >2) I configured webmail.mydomain.com as a separate website
> >While configuring I pointed the home directory to a dummy empty folder
> >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> >Selected "redirection to another URL"
> >Selected "exact URL" and "permanent redirection"
>
> >- I ended up at same place where I started from. This solution
> >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> >Now I'm lost how do I make this work?
>
> >My requirement is I don't want the port number, I want it to access on
> >Port 80. Reason is I want to access webmail behind a proxy which
> >blocks almost all ports except 80.
>
> >I can't run mail server on port 80 as I run web server.
>
> >Any help would be appreciated. I can offer pure British Beer ;)
>
> >Cheers
Hi Kris,
"I don't understand this. You say that you are now using port 1234 to
access webmail. You also say that this port is used by your email
server. "
Yes as I explained in my earlier post above, my webmail server is
listening on port 1234
"This doesn't work. You cannot have the email server and IIS listening
on
the same port (because they are two different processes). If you are
using
port 1234 to access the webmail at this moment, perhaps you are not
using
IIS at all? "
Yes right, I can't do that I can understand that.
"What you need to do is:
1. Make sure that DNS is working and webmail.mydomain.com is pointing
to
the IP address of the webserver. (should already be working since you
managed to set up a redirection) "
Always works nor problem no trouble.
"2. Modify the existing website to use port 80 and the
webmail.mydomain.com
host header. "
?????
Didn't get it.
Re: Accessing Webmail without using port No. extension
am 08.08.2007 01:17:40 von Nirvana
On Aug 7, 10:11 am, Nirvana wrote:
> On Aug 7, 7:31 am, "Kristofer Gafvert"
> wrote:
>
>
>
> > I don't understand this. You say that you are now using port 1234 to
> > accesswebmail. You also say that this port is used by your email server.
>
> > This doesn't work. You cannot have the email server and IIS listening on
> > the same port (because they are two different processes). If you are using
> > port 1234 to access thewebmailat this moment, perhaps you are not using
> > IIS at all?
>
> > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > What you need to do is:
> > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > the IP address of the webserver. (should already be working since you
> > managed to set up a redirection)
> > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > host header.
>
> > --
> > Regards,
> > Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> > Nirvana wrote:
> > >Hi All,
> > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > >box.
>
> > >Mail server is Code Crafters Ability Mail Server.
>
> > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > >But I want to access mail server by just typing URL of domain without
> > >port extension
> > >E.g.http://webmail.mydomain.com
>
> > >I tried 2 solutions
> > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > >and pointed port to 1234
> > >- This obviously fails as I'm trying to use port 1234 which is being
> > >used by mail server
>
> > >2) I configuredwebmail.mydomain.com as a separate website
> > >While configuring I pointed the home directory to a dummy empty folder
> > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > >Selected "redirection to another URL"
> > >Selected "exact URL" and "permanent redirection"
>
> > >- I ended up at same place where I started from. This solution
> > >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> > >Now I'm lost how do I make this work?
>
> > >My requirement is I don't want the port number, I want it to access on
> > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > >blocks almost all ports except 80.
>
> > >I can't run mail server on port 80 as I run web server.
>
> > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > >Cheers
>
> Hi Kris,
> "I don't understand this. You say that you are now using port 1234 to
> accesswebmail. You also say that this port is used by your email
> server. "
> Yes as I explained in my earlier post above, mywebmailserver is
> listening on port 1234
>
> "This doesn't work. You cannot have the email server and IIS listening
> on
> the same port (because they are two different processes). If you are
> using
> port 1234 to access thewebmailat this moment, perhaps you are not
> using
> IIS at all? "
> Yes right, I can't do that I can understand that.
>
> "What you need to do is:
> 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection) "
>
> Always works nor problem no trouble.
>
> "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> host header. "
> ?????
> Didn't get it.
One of my reply was lost....
Here is the update.
I found http://support.microsoft.com/kb/813368/EN-US/
So I though I got the magic power but still i'm stuck.
1) I disabled the socket pooling so that I can run mailserver on
10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
2) I configured all my websites in IIS to use 10.0.0.1:80 so that
there is no conflict between 2 IP Addresses for port 80
3) Now I can't configure mail server to use 10.0.0.2:80 it gives
conflict. Throws "Unable to open WebMail port"
It seems socket pooling disabling doesn't work?
Re: Accessing Webmail without using port No. extension
am 08.08.2007 01:17:55 von Nirvana
On Aug 7, 10:11 am, Nirvana wrote:
> On Aug 7, 7:31 am, "Kristofer Gafvert"
> wrote:
>
>
>
> > I don't understand this. You say that you are now using port 1234 to
> > accesswebmail. You also say that this port is used by your email server.
>
> > This doesn't work. You cannot have the email server and IIS listening on
> > the same port (because they are two different processes). If you are using
> > port 1234 to access thewebmailat this moment, perhaps you are not using
> > IIS at all?
>
> > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > What you need to do is:
> > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > the IP address of the webserver. (should already be working since you
> > managed to set up a redirection)
> > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > host header.
>
> > --
> > Regards,
> > Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> > Nirvana wrote:
> > >Hi All,
> > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > >box.
>
> > >Mail server is Code Crafters Ability Mail Server.
>
> > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > >But I want to access mail server by just typing URL of domain without
> > >port extension
> > >E.g.http://webmail.mydomain.com
>
> > >I tried 2 solutions
> > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > >and pointed port to 1234
> > >- This obviously fails as I'm trying to use port 1234 which is being
> > >used by mail server
>
> > >2) I configuredwebmail.mydomain.com as a separate website
> > >While configuring I pointed the home directory to a dummy empty folder
> > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > >Selected "redirection to another URL"
> > >Selected "exact URL" and "permanent redirection"
>
> > >- I ended up at same place where I started from. This solution
> > >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> > >Now I'm lost how do I make this work?
>
> > >My requirement is I don't want the port number, I want it to access on
> > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > >blocks almost all ports except 80.
>
> > >I can't run mail server on port 80 as I run web server.
>
> > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > >Cheers
>
> Hi Kris,
> "I don't understand this. You say that you are now using port 1234 to
> accesswebmail. You also say that this port is used by your email
> server. "
> Yes as I explained in my earlier post above, mywebmailserver is
> listening on port 1234
>
> "This doesn't work. You cannot have the email server and IIS listening
> on
> the same port (because they are two different processes). If you are
> using
> port 1234 to access thewebmailat this moment, perhaps you are not
> using
> IIS at all? "
> Yes right, I can't do that I can understand that.
>
> "What you need to do is:
> 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection) "
>
> Always works nor problem no trouble.
>
> "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> host header. "
> ?????
> Didn't get it.
One of my reply was lost....
Here is the update.
I found http://support.microsoft.com/kb/813368/EN-US/
So I though I got the magic power but still i'm stuck.
1) I disabled the socket pooling so that I can run mailserver on
10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
2) I configured all my websites in IIS to use 10.0.0.1:80 so that
there is no conflict between 2 IP Addresses for port 80
3) Now I can't configure mail server to use 10.0.0.2:80 it gives
conflict. Throws "Unable to open WebMail port"
It seems socket pooling disabling doesn't work?
Re: Accessing Webmail without using port No. extension
am 08.08.2007 01:18:08 von Nirvana
On Aug 7, 10:11 am, Nirvana wrote:
> On Aug 7, 7:31 am, "Kristofer Gafvert"
> wrote:
>
>
>
> > I don't understand this. You say that you are now using port 1234 to
> > accesswebmail. You also say that this port is used by your email server.
>
> > This doesn't work. You cannot have the email server and IIS listening on
> > the same port (because they are two different processes). If you are using
> > port 1234 to access thewebmailat this moment, perhaps you are not using
> > IIS at all?
>
> > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > What you need to do is:
> > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > the IP address of the webserver. (should already be working since you
> > managed to set up a redirection)
> > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > host header.
>
> > --
> > Regards,
> > Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> > Nirvana wrote:
> > >Hi All,
> > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > >box.
>
> > >Mail server is Code Crafters Ability Mail Server.
>
> > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > >But I want to access mail server by just typing URL of domain without
> > >port extension
> > >E.g.http://webmail.mydomain.com
>
> > >I tried 2 solutions
> > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > >and pointed port to 1234
> > >- This obviously fails as I'm trying to use port 1234 which is being
> > >used by mail server
>
> > >2) I configuredwebmail.mydomain.com as a separate website
> > >While configuring I pointed the home directory to a dummy empty folder
> > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > >Selected "redirection to another URL"
> > >Selected "exact URL" and "permanent redirection"
>
> > >- I ended up at same place where I started from. This solution
> > >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> > >Now I'm lost how do I make this work?
>
> > >My requirement is I don't want the port number, I want it to access on
> > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > >blocks almost all ports except 80.
>
> > >I can't run mail server on port 80 as I run web server.
>
> > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > >Cheers
>
> Hi Kris,
> "I don't understand this. You say that you are now using port 1234 to
> accesswebmail. You also say that this port is used by your email
> server. "
> Yes as I explained in my earlier post above, mywebmailserver is
> listening on port 1234
>
> "This doesn't work. You cannot have the email server and IIS listening
> on
> the same port (because they are two different processes). If you are
> using
> port 1234 to access thewebmailat this moment, perhaps you are not
> using
> IIS at all? "
> Yes right, I can't do that I can understand that.
>
> "What you need to do is:
> 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection) "
>
> Always works nor problem no trouble.
>
> "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> host header. "
> ?????
> Didn't get it.
One of my reply was lost....
Here is the update.
I found http://support.microsoft.com/kb/813368/EN-US/
So I though I got the magic power but still i'm stuck.
1) I disabled the socket pooling so that I can run mailserver on
10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
2) I configured all my websites in IIS to use 10.0.0.1:80 so that
there is no conflict between 2 IP Addresses for port 80
3) Now I can't configure mail server to use 10.0.0.2:80 it gives
conflict. Throws "Unable to open WebMail port"
It seems socket pooling disabling doesn't work?
Re: Accessing Webmail without using port No. extension
am 08.08.2007 01:44:42 von Nirvana
On Aug 7, 10:11 am, Nirvana wrote:
> On Aug 7, 7:31 am, "Kristofer Gafvert"
> wrote:
>
>
>
> > I don't understand this. You say that you are now using port 1234 to
> > accesswebmail. You also say that this port is used by your email server.
>
> > This doesn't work. You cannot have the email server and IIS listening on
> > the same port (because they are two different processes). If you are using
> > port 1234 to access thewebmailat this moment, perhaps you are not using
> > IIS at all?
>
> > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > What you need to do is:
> > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > the IP address of the webserver. (should already be working since you
> > managed to set up a redirection)
> > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > host header.
>
> > --
> > Regards,
> > Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> > Nirvana wrote:
> > >Hi All,
> > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > >box.
>
> > >Mail server is Code Crafters Ability Mail Server.
>
> > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > >But I want to access mail server by just typing URL of domain without
> > >port extension
> > >E.g.http://webmail.mydomain.com
>
> > >I tried 2 solutions
> > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > >and pointed port to 1234
> > >- This obviously fails as I'm trying to use port 1234 which is being
> > >used by mail server
>
> > >2) I configuredwebmail.mydomain.com as a separate website
> > >While configuring I pointed the home directory to a dummy empty folder
> > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > >Selected "redirection to another URL"
> > >Selected "exact URL" and "permanent redirection"
>
> > >- I ended up at same place where I started from. This solution
> > >redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>
> > >Now I'm lost how do I make this work?
>
> > >My requirement is I don't want the port number, I want it to access on
> > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > >blocks almost all ports except 80.
>
> > >I can't run mail server on port 80 as I run web server.
>
> > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > >Cheers
>
> Hi Kris,
> "I don't understand this. You say that you are now using port 1234 to
> accesswebmail. You also say that this port is used by your email
> server. "
> Yes as I explained in my earlier post above, mywebmailserver is
> listening on port 1234
>
> "This doesn't work. You cannot have the email server and IIS listening
> on
> the same port (because they are two different processes). If you are
> using
> port 1234 to access thewebmailat this moment, perhaps you are not
> using
> IIS at all? "
> Yes right, I can't do that I can understand that.
>
> "What you need to do is:
> 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> to
> the IP address of the webserver. (should already be working since you
> managed to set up a redirection) "
>
> Always works nor problem no trouble.
>
> "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> host header. "
> ?????
> Didn't get it.
One of my reply was lost....
Here is the update.
I found http://support.microsoft.com/kb/813368/EN-US/
So I though I got the magic power but still i'm stuck.
1) I disabled the socket pooling so that I can run mailserver on
10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
2) I configured all my websites in IIS to use 10.0.0.1:80 so that
there is no conflict between 2 IP Addresses for port 80
3) Now I can't configure mail server to use 10.0.0.2:80 it gives
conflict. Throws "Unable to open WebMail port"
It seems socket pooling disabling doesn't work?
Re: Accessing Webmail without using port No. extension
am 08.08.2007 03:14:44 von David Wang
On Aug 7, 4:17 pm, Nirvana wrote:
> On Aug 7, 10:11 am, Nirvana wrote:
>
>
>
>
>
> > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > wrote:
>
> > > I don't understand this. You say that you are now using port 1234 to
> > > accesswebmail. You also say that this port is used by your email server.
>
> > > This doesn't work. You cannot have the email server and IIS listening on
> > > the same port (because they are two different processes). If you are using
> > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > IIS at all?
>
> > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > What you need to do is:
> > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > the IP address of the webserver. (should already be working since you
> > > managed to set up a redirection)
> > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > host header.
>
> > > --
> > > Regards,
> > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelated Info
>
> > > Nirvana wrote:
> > > >Hi All,
> > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > >box.
>
> > > >Mail server is Code Crafters Ability Mail Server.
>
> > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > >But I want to access mail server by just typing URL of domain without
> > > >port extension
> > > >E.g.http://webmail.mydomain.com
>
> > > >I tried 2 solutions
> > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > >and pointed port to 1234
> > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > >used by mail server
>
> > > >2) I configuredwebmail.mydomain.com as a separate website
> > > >While configuring I pointed the home directory to a dummy empty folder
> > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > >Selected "redirection to another URL"
> > > >Selected "exact URL" and "permanent redirection"
>
> > > >- I ended up at same place where I started from. This solution
> > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > >Now I'm lost how do I make this work?
>
> > > >My requirement is I don't want the port number, I want it to access on
> > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > >blocks almost all ports except 80.
>
> > > >I can't run mail server on port 80 as I run web server.
>
> > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > >Cheers
>
> > Hi Kris,
> > "I don't understand this. You say that you are now using port 1234 to
> > accesswebmail. You also say that this port is used by your email
> > server. "
> > Yes as I explained in my earlier post above, mywebmailserver is
> > listening on port 1234
>
> > "This doesn't work. You cannot have the email server and IIS listening
> > on
> > the same port (because they are two different processes). If you are
> > using
> > port 1234 to access thewebmailat this moment, perhaps you are not
> > using
> > IIS at all? "
> > Yes right, I can't do that I can understand that.
>
> > "What you need to do is:
> > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > to
> > the IP address of the webserver. (should already be working since you
> > managed to set up a redirection) "
>
> > Always works nor problem no trouble.
>
> > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > host header. "
> > ?????
> > Didn't get it.
>
> One of my reply was lost....
>
> Here is the update.
>
> I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> So I though I got the magic power but still i'm stuck.
>
> 1) I disabled the socket pooling so that I can run mailserver on
> 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> there is no conflict between 2 IP Addresses for port 80
> 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> conflict. Throws "Unable to open WebMail port"
>
> It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> - Show quoted text -
Please verify by running the following on the commandline:
NETSTAT.EXE -ano
It will show you how IIS and WebMail are binding to their IP:Port. You
should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
no socket pooling)
Maybe WebMail uses socket pooling of its own, so it will fail even if
you successfully disable IIS's socket pooling. Maybe WebMail does not
want to allow access on port 80.
Maybe you can configure the proxy to forward http://webmail.domain.com
to http://webmail:1234 .
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: Accessing Webmail without using port No. extension
am 08.08.2007 11:01:47 von Nirvana
On Aug 8, 2:14 am, David Wang wrote:
> On Aug 7, 4:17 pm, Nirvana wrote:
>
>
>
> > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > wrote:
>
> > > > I don't understand this. You say that you are now using port 1234 to
> > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > the same port (because they are two different processes). If you are using
> > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > IIS at all?
>
> > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > What you need to do is:
> > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > the IP address of the webserver. (should already be working since you
> > > > managed to set up a redirection)
> > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > host header.
>
> > > > --
> > > > Regards,
> > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > Nirvana wrote:
> > > > >Hi All,
> > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > >box.
>
> > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > >But I want to access mail server by just typing URL of domain without
> > > > >port extension
> > > > >E.g.http://webmail.mydomain.com
>
> > > > >I tried 2 solutions
> > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > >and pointed port to 1234
> > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > >used by mail server
>
> > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > >Selected "redirection to another URL"
> > > > >Selected "exact URL" and "permanent redirection"
>
> > > > >- I ended up at same place where I started from. This solution
> > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > >Now I'm lost how do I make this work?
>
> > > > >My requirement is I don't want the port number, I want it to access on
> > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > >blocks almost all ports except 80.
>
> > > > >I can't run mail server on port 80 as I run web server.
>
> > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > >Cheers
>
> > > Hi Kris,
> > > "I don't understand this. You say that you are now using port 1234 to
> > > accesswebmail. You also say that this port is used by your email
> > > server. "
> > > Yes as I explained in my earlier post above, mywebmailserver is
> > > listening on port 1234
>
> > > "This doesn't work. You cannot have the email server and IIS listening
> > > on
> > > the same port (because they are two different processes). If you are
> > > using
> > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > using
> > > IIS at all? "
> > > Yes right, I can't do that I can understand that.
>
> > > "What you need to do is:
> > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > to
> > > the IP address of the webserver. (should already be working since you
> > > managed to set up a redirection) "
>
> > > Always works nor problem no trouble.
>
> > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > host header. "
> > > ?????
> > > Didn't get it.
>
> > One of my reply was lost....
>
> > Here is the update.
>
> > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > So I though I got the magic power but still i'm stuck.
>
> > 1) I disabled the socket pooling so that I can run mailserver on
> > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > there is no conflict between 2 IP Addresses for port 80
> > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > conflict. Throws "Unable to open WebMail port"
>
> > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > - Show quoted text -
>
> Please verify by running the following on the commandline:
> NETSTAT.EXE -ano
>
> It will show you how IIS and WebMail are binding to their IP:Port. You
> should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> no socket pooling)
>
> Maybe WebMail uses socket pooling of its own, so it will fail even if
> you successfully disable IIS's socket pooling. Maybe WebMail does not
> want to allow access on port 80.
>
> Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> tohttp://webmail:1234.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
Thanks David
I'll try later and will update.
" Maybe you can configure the proxy to forward http://webmail.domain.com
to http://webmail:1234 . "
The proxy is on client side (Read from my work lol ;) ). Client side
has blocked almost all ports and the only port open is 80 and that is
why the whole story begins to configure Webmail on port 80.
Cheers
Re: Accessing Webmail without using port No. extension
am 10.08.2007 08:39:51 von Kristofer Gafvert
Hello,
The problem seems to be that you have IIS listening on port 80, and you
have some other kind of software you also want to listen on port 80. You
cannot have multiple applications listening on the same IP address and
port. So you either need a second IP address, use a second port (which you
are already doing) or need a third application that can listen on port 80
and forward all requests to either of the other two applications based on
the host header (OctaGate Switch can do this, do a search on google to
find, i am sure there are other programs as well).
Host headers in IIS only works if all websites are on IIS. In your
situation, this does not seem to be the case.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Nirvana wrote:
>On Aug 7, 7:31 am, "Kristofer Gafvert"
>wrote:
>>I don't understand this. You say that you are now using port 1234 to
>>access webmail. You also say that this port is used by your email server.
>>
>>This doesn't work. You cannot have the email server and IIS listening on
>>the same port (because they are two different processes). If you are using
>>port 1234 to access the webmail at this moment, perhaps you are not using
>>IIS at all?
>>
>>Anyway, if you are indeed using IIS, we should be able to make this
>>working.
>>
>>What you need to do is:
>>1. Make sure that DNS is working and webmail.mydomain.com is pointing to
>>the IP address of the webserver. (should already be working since you
>>managed to set up a redirection)
>>2. Modify the existing website to use port 80 and the webmail.mydomain.com
>>host header.
>>
>>--
>>Regards,
>>Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>>
>>Nirvana wrote:
>>>Hi All,
>>>I've web server and mail server running on same Windows 2k3 + IIS 6
>>>box.
>>
>>>Mail server is Code Crafters Ability Mail Server.
>>
>>>I can access mail server by usinghttp://www.mydomain.com:1234
>>
>>>But I want to access mail server by just typing URL of domain without
>>>port extension
>>>E.g.http://webmail.mydomain.com
>>
>>>I tried 2 solutions
>>>1) Host header solution: I configured webmail.mydomain.com hos header
>>>and pointed port to 1234
>>>- This obviously fails as I'm trying to use port 1234 which is being
>>>used by mail server
>>
>>>2) I configured webmail.mydomain.com as a separate website
>>>While configuring I pointed the home directory to a dummy empty folder
>>>and then I redirected the URL tohttp://www.mydomain.com:1234
>>
>>>Selected "redirection to another URL"
>>>Selected "exact URL" and "permanent redirection"
>>
>>>- I ended up at same place where I started from. This solution
>>>redirectshttp://webmail.mydomain.comto http://www.mydomain.com:1234
>>
>>>Now I'm lost how do I make this work?
>>
>>>My requirement is I don't want the port number, I want it to access on
>>>Port 80. Reason is I want to access webmail behind a proxy which
>>>blocks almost all ports except 80.
>>
>>>I can't run mail server on port 80 as I run web server.
>>
>>>Any help would be appreciated. I can offer pure British Beer ;)
>>
>>>Cheers
>
>Hi Kris,
>"I don't understand this. You say that you are now using port 1234 to
>access webmail. You also say that this port is used by your email
>server. "
>Yes as I explained in my earlier post above, my webmail server is
>listening on port 1234
>
>"This doesn't work. You cannot have the email server and IIS listening
>on
>the same port (because they are two different processes). If you are
>using
>port 1234 to access the webmail at this moment, perhaps you are not
>using
>IIS at all? "
>Yes right, I can't do that I can understand that.
>
>"What you need to do is:
>1. Make sure that DNS is working and webmail.mydomain.com is pointing
>to
>the IP address of the webserver. (should already be working since you
>managed to set up a redirection) "
>
>Always works nor problem no trouble.
>
>"2. Modify the existing website to use port 80 and the
>webmail.mydomain.com
>host header. "
>?????
>Didn't get it.
Re: Accessing Webmail without using port No. extension
am 12.08.2007 16:45:37 von Nirvana
On Aug 8, 10:01 am, Nirvana wrote:
> On Aug 8, 2:14 am, David Wang wrote:
>
>
>
> > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > wrote:
>
> > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > the same port (because they are two different processes). If you are using
> > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > IIS at all?
>
> > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > What you need to do is:
> > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > the IP address of the webserver. (should already be working since you
> > > > > managed to set up a redirection)
> > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > host header.
>
> > > > > --
> > > > > Regards,
> > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > Nirvana wrote:
> > > > > >Hi All,
> > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > >box.
>
> > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > >But I want to access mail server by just typing URL of domain without
> > > > > >port extension
> > > > > >E.g.http://webmail.mydomain.com
>
> > > > > >I tried 2 solutions
> > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > >and pointed port to 1234
> > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > >used by mail server
>
> > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > >Selected "redirection to another URL"
> > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > >- I ended up at same place where I started from. This solution
> > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > >Now I'm lost how do I make this work?
>
> > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > >blocks almost all ports except 80.
>
> > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > >Cheers
>
> > > > Hi Kris,
> > > > "I don't understand this. You say that you are now using port 1234 to
> > > > accesswebmail. You also say that this port is used by your email
> > > > server. "
> > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > listening on port 1234
>
> > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > on
> > > > the same port (because they are two different processes). If you are
> > > > using
> > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > using
> > > > IIS at all? "
> > > > Yes right, I can't do that I can understand that.
>
> > > > "What you need to do is:
> > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > to
> > > > the IP address of the webserver. (should already be working since you
> > > > managed to set up a redirection) "
>
> > > > Always works nor problem no trouble.
>
> > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > host header. "
> > > > ?????
> > > > Didn't get it.
>
> > > One of my reply was lost....
>
> > > Here is the update.
>
> > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > So I though I got the magic power but still i'm stuck.
>
> > > 1) I disabled the socket pooling so that I can run mailserver on
> > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > there is no conflict between 2 IP Addresses for port 80
> > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > conflict. Throws "Unable to open WebMail port"
>
> > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > - Show quoted text -
>
> > Please verify by running the following on the commandline:
> > NETSTAT.EXE -ano
>
> > It will show you how IIS and WebMail are binding to their IP:Port. You
> > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > no socket pooling)
>
> > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > want to allow access on port 80.
>
> > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > tohttp://webmail:1234.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> Thanks David
> I'll try later and will update.
>
> " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> tohttp://webmail:1234. "
> The proxy is on client side (Read from my work lol ;) ). Client side
> has blocked almost all ports and the only port open is 80 and that is
> why the whole story begins to configure Webmail on port 80.
>
> Cheers
Hi All,
I've checked by running NETSTAT.EXE -ano command and I can see
0.0.0.0:80 which means I've got a service still listening on port 80.
I've checked carefully and none of my websites are listening on
default port, all of them are listening on 10.0.0.1:80
So the conclusion is I've still got some server/services listening on
port 80.
I run IIS, mySQL and Ability mail server and I can't think of any
other services which might be listening on port 80.
Router firewall is disabled.
How do I find out which service/server is still listening on
0.0.0.0:80 ?
Thanks
Nirvana
Re: Accessing Webmail without using port No. extension
am 12.08.2007 17:39:59 von Nirvana
On Aug 12, 3:45 pm, Nirvana wrote:
> On Aug 8, 10:01 am, Nirvana wrote:
>
>
>
> > On Aug 8, 2:14 am, David Wang wrote:
>
> > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > wrote:
>
> > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > the same port (because they are two different processes). If you are using
> > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > IIS at all?
>
> > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > What you need to do is:
> > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > the IP address of the webserver. (should already be working since you
> > > > > > managed to set up a redirection)
> > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > host header.
>
> > > > > > --
> > > > > > Regards,
> > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > Nirvana wrote:
> > > > > > >Hi All,
> > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > >box.
>
> > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > >port extension
> > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > >I tried 2 solutions
> > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > >and pointed port to 1234
> > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > >used by mail server
>
> > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > >Selected "redirection to another URL"
> > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > >- I ended up at same place where I started from. This solution
> > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > >Now I'm lost how do I make this work?
>
> > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > >blocks almost all ports except 80.
>
> > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > >Cheers
>
> > > > > Hi Kris,
> > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > accesswebmail. You also say that this port is used by your email
> > > > > server. "
> > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > listening on port 1234
>
> > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > on
> > > > > the same port (because they are two different processes). If you are
> > > > > using
> > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > using
> > > > > IIS at all? "
> > > > > Yes right, I can't do that I can understand that.
>
> > > > > "What you need to do is:
> > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > to
> > > > > the IP address of the webserver. (should already be working since you
> > > > > managed to set up a redirection) "
>
> > > > > Always works nor problem no trouble.
>
> > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > host header. "
> > > > > ?????
> > > > > Didn't get it.
>
> > > > One of my reply was lost....
>
> > > > Here is the update.
>
> > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > So I though I got the magic power but still i'm stuck.
>
> > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > there is no conflict between 2 IP Addresses for port 80
> > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > conflict. Throws "Unable to open WebMail port"
>
> > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > Please verify by running the following on the commandline:
> > > NETSTAT.EXE -ano
>
> > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > no socket pooling)
>
> > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > want to allow access on port 80.
>
> > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > tohttp://webmail:1234.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > Thanks David
> > I'll try later and will update.
>
> > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > tohttp://webmail:1234. "
> > The proxy is on client side (Read from my work lol ;) ). Client side
> > has blocked almost all ports and the only port open is 80 and that is
> > why the whole story begins to configure Webmail on port 80.
>
> > Cheers
>
> Hi All,
> I've checked by running NETSTAT.EXE -ano command and I can see
> 0.0.0.0:80 which means I've got a service still listening on port 80.
> I've checked carefully and none of my websites are listening on
> default port, all of them are listening on 10.0.0.1:80
>
> So the conclusion is I've still got some server/services listening on
> port 80.
>
> I run IIS, mySQL and Ability mail server and I can't think of any
> other services which might be listening on port 80.
> Router firewall is disabled.
>
> How do I find out which service/server is still listening on
> 0.0.0.0:80 ?
>
> Thanks
> Nirvana
Here is the current situation
Socket pooling disabled.
2 IP addresses 10.0.0.1 and 10.0.0.2 configured in TCP/IP
I can see that there is a service/server running on 10.0.0.2:80, this
is the IP:port where I want to run my Webmail.
How do I find which server/service is running on 10.0.0.2:80
Re: Accessing Webmail without using port No. extension
am 12.08.2007 18:11:03 von Nirvana
On Aug 12, 4:39 pm, Nirvana wrote:
> On Aug 12, 3:45 pm, Nirvana wrote:
>
>
>
> > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > wrote:
>
> > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > IIS at all?
>
> > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > What you need to do is:
> > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > managed to set up a redirection)
> > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > host header.
>
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > Nirvana wrote:
> > > > > > > >Hi All,
> > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > >box.
>
> > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > >port extension
> > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > >I tried 2 solutions
> > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > >and pointed port to 1234
> > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > >used by mail server
>
> > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > >Selected "redirection to another URL"
> > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > >blocks almost all ports except 80.
>
> > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > >Cheers
>
> > > > > > Hi Kris,
> > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > server. "
> > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > listening on port 1234
>
> > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > on
> > > > > > the same port (because they are two different processes). If you are
> > > > > > using
> > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > using
> > > > > > IIS at all? "
> > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > "What you need to do is:
> > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > to
> > > > > > the IP address of the webserver. (should already be working since you
> > > > > > managed to set up a redirection) "
>
> > > > > > Always works nor problem no trouble.
>
> > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > host header. "
> > > > > > ?????
> > > > > > Didn't get it.
>
> > > > > One of my reply was lost....
>
> > > > > Here is the update.
>
> > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > Please verify by running the following on the commandline:
> > > > NETSTAT.EXE -ano
>
> > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > no socket pooling)
>
> > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > want to allow access on port 80.
>
> > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > tohttp://webmail:1234.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //
>
> > > Thanks David
> > > I'll try later and will update.
>
> > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > tohttp://webmail:1234. "
> > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > has blocked almost all ports and the only port open is 80 and that is
> > > why the whole story begins to configure Webmail on port 80.
>
> > > Cheers
>
> > Hi All,
> > I've checked by running NETSTAT.EXE -ano command and I can see
> > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > I've checked carefully and none of my websites are listening on
> > default port, all of them are listening on 10.0.0.1:80
>
> > So the conclusion is I've still got some server/services listening on
> > port 80.
>
> > I run IIS, mySQL and Ability mail server and I can't think of any
> > other services which might be listening on port 80.
> > Router firewall is disabled.
>
> > How do I find out which service/server is still listening on
> > 0.0.0.0:80 ?
>
> > Thanks
> > Nirvana
>
> Here is the current situation
> Socket pooling disabled.
> 2 IP addresses 10.0.0.1 and 10.0.0.2 configured in TCP/IP
> I can see that there is a service/server running on 10.0.0.2:80, this
> is the IP:port where I want to run my Webmail.
>
> How do I find which server/service is running on 10.0.0.2:80
I did little experiment, by stopping World Wide Publishing Service and
10.0.0.2:80 disappeared?
World Wide Publishing Service is using 10.0.0.2:80?
What does it mean?
Re: Accessing Webmail without using port No. extension
am 13.08.2007 10:22:04 von David Wang
On Aug 12, 7:45 am, Nirvana wrote:
> On Aug 8, 10:01 am, Nirvana wrote:
>
>
>
>
>
> > On Aug 8, 2:14 am, David Wang wrote:
>
> > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > wrote:
>
> > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > the same port (because they are two different processes). If you are using
> > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > IIS at all?
>
> > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > What you need to do is:
> > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > the IP address of the webserver. (should already be working since you
> > > > > > managed to set up a redirection)
> > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > host header.
>
> > > > > > --
> > > > > > Regards,
> > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > Nirvana wrote:
> > > > > > >Hi All,
> > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > >box.
>
> > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > >port extension
> > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > >I tried 2 solutions
> > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > >and pointed port to 1234
> > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > >used by mail server
>
> > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > >Selected "redirection to another URL"
> > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > >- I ended up at same place where I started from. This solution
> > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > >Now I'm lost how do I make this work?
>
> > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > >blocks almost all ports except 80.
>
> > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > >Cheers
>
> > > > > Hi Kris,
> > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > accesswebmail. You also say that this port is used by your email
> > > > > server. "
> > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > listening on port 1234
>
> > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > on
> > > > > the same port (because they are two different processes). If you are
> > > > > using
> > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > using
> > > > > IIS at all? "
> > > > > Yes right, I can't do that I can understand that.
>
> > > > > "What you need to do is:
> > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > to
> > > > > the IP address of the webserver. (should already be working since you
> > > > > managed to set up a redirection) "
>
> > > > > Always works nor problem no trouble.
>
> > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > host header. "
> > > > > ?????
> > > > > Didn't get it.
>
> > > > One of my reply was lost....
>
> > > > Here is the update.
>
> > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > So I though I got the magic power but still i'm stuck.
>
> > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > there is no conflict between 2 IP Addresses for port 80
> > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > conflict. Throws "Unable to open WebMail port"
>
> > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > Please verify by running the following on the commandline:
> > > NETSTAT.EXE -ano
>
> > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > no socket pooling)
>
> > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > want to allow access on port 80.
>
> > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > tohttp://webmail:1234.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > Thanks David
> > I'll try later and will update.
>
> > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > tohttp://webmail:1234. "
> > The proxy is on client side (Read from my work lol ;) ). Client side
> > has blocked almost all ports and the only port open is 80 and that is
> > why the whole story begins to configure Webmail on port 80.
>
> > Cheers
>
> Hi All,
> I've checked by running NETSTAT.EXE -ano command and I can see
> 0.0.0.0:80 which means I've got a service still listening on port 80.
> I've checked carefully and none of my websites are listening on
> default port, all of them are listening on 10.0.0.1:80
>
> So the conclusion is I've still got some server/services listening on
> port 80.
>
> I run IIS, mySQL and Ability mail server and I can't think of any
> other services which might be listening on port 80.
> Router firewall is disabled.
>
> How do I find out which service/server is still listening on
> 0.0.0.0:80 ?
>
> Thanks
> Nirvana- Hide quoted text -
>
> - Show quoted text -
NETSTAT.EXE -ano also tells you the PID that is holding that socket.
Look up the PID in the Task Manager to figure out what process is
holding onto 0.0.0.0:80.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: Accessing Webmail without using port No. extension
am 14.08.2007 02:01:35 von Nirvana
On Aug 13, 9:22 am, David Wang wrote:
> On Aug 12, 7:45 am, Nirvana wrote:
>
>
>
> > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > wrote:
>
> > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > IIS at all?
>
> > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > What you need to do is:
> > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > managed to set up a redirection)
> > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > host header.
>
> > > > > > > --
> > > > > > > Regards,
> > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > Nirvana wrote:
> > > > > > > >Hi All,
> > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > >box.
>
> > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > >port extension
> > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > >I tried 2 solutions
> > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > >and pointed port to 1234
> > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > >used by mail server
>
> > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > >Selected "redirection to another URL"
> > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > >blocks almost all ports except 80.
>
> > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > >Cheers
>
> > > > > > Hi Kris,
> > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > server. "
> > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > listening on port 1234
>
> > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > on
> > > > > > the same port (because they are two different processes). If you are
> > > > > > using
> > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > using
> > > > > > IIS at all? "
> > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > "What you need to do is:
> > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > to
> > > > > > the IP address of the webserver. (should already be working since you
> > > > > > managed to set up a redirection) "
>
> > > > > > Always works nor problem no trouble.
>
> > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > host header. "
> > > > > > ?????
> > > > > > Didn't get it.
>
> > > > > One of my reply was lost....
>
> > > > > Here is the update.
>
> > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > Please verify by running the following on the commandline:
> > > > NETSTAT.EXE -ano
>
> > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > no socket pooling)
>
> > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > want to allow access on port 80.
>
> > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > tohttp://webmail:1234.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //
>
> > > Thanks David
> > > I'll try later and will update.
>
> > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > tohttp://webmail:1234. "
> > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > has blocked almost all ports and the only port open is 80 and that is
> > > why the whole story begins to configure Webmail on port 80.
>
> > > Cheers
>
> > Hi All,
> > I've checked by running NETSTAT.EXE -ano command and I can see
> > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > I've checked carefully and none of my websites are listening on
> > default port, all of them are listening on 10.0.0.1:80
>
> > So the conclusion is I've still got some server/services listening on
> > port 80.
>
> > I run IIS, mySQL and Ability mail server and I can't think of any
> > other services which might be listening on port 80.
> > Router firewall is disabled.
>
> > How do I find out which service/server is still listening on
> > 0.0.0.0:80 ?
>
> > Thanks
> > Nirvana- Hide quoted text -
>
> > - Show quoted text -
>
> NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> Look up the PID in the Task Manager to figure out what process is
> holding onto 0.0.0.0:80.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
I checked in Task Manager for that PID and it is svchost.exe
Where to go from here now?
Cheers
Nirvana
Re: Accessing Webmail without using port No. extension
am 14.08.2007 02:32:13 von David Wang
On Aug 13, 5:01 pm, Nirvana wrote:
> On Aug 13, 9:22 am, David Wang wrote:
>
>
>
>
>
> > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > wrote:
>
> > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > IIS at all?
>
> > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > What you need to do is:
> > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > managed to set up a redirection)
> > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > host header.
>
> > > > > > > > --
> > > > > > > > Regards,
> > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > Nirvana wrote:
> > > > > > > > >Hi All,
> > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > >box.
>
> > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > >port extension
> > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > >I tried 2 solutions
> > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > >and pointed port to 1234
> > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > >used by mail server
>
> > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > >Selected "redirection to another URL"
> > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > >Cheers
>
> > > > > > > Hi Kris,
> > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > server. "
> > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > listening on port 1234
>
> > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > on
> > > > > > > the same port (because they are two different processes). If you are
> > > > > > > using
> > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > using
> > > > > > > IIS at all? "
> > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > "What you need to do is:
> > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > to
> > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > managed to set up a redirection) "
>
> > > > > > > Always works nor problem no trouble.
>
> > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > host header. "
> > > > > > > ?????
> > > > > > > Didn't get it.
>
> > > > > > One of my reply was lost....
>
> > > > > > Here is the update.
>
> > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > Please verify by running the following on the commandline:
> > > > > NETSTAT.EXE -ano
>
> > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > no socket pooling)
>
> > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > want to allow access on port 80.
>
> > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > tohttp://webmail:1234.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > //
>
> > > > Thanks David
> > > > I'll try later and will update.
>
> > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > tohttp://webmail:1234. "
> > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > has blocked almost all ports and the only port open is 80 and that is
> > > > why the whole story begins to configure Webmail on port 80.
>
> > > > Cheers
>
> > > Hi All,
> > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > I've checked carefully and none of my websites are listening on
> > > default port, all of them are listening on 10.0.0.1:80
>
> > > So the conclusion is I've still got some server/services listening on
> > > port 80.
>
> > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > other services which might be listening on port 80.
> > > Router firewall is disabled.
>
> > > How do I find out which service/server is still listening on
> > > 0.0.0.0:80 ?
>
> > > Thanks
> > > Nirvana- Hide quoted text -
>
> > > - Show quoted text -
>
> > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > Look up the PID in the Task Manager to figure out what process is
> > holding onto 0.0.0.0:80.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> I checked in Task Manager for that PID and it is svchost.exe
>
> Where to go from here now?
>
> Cheers
> Nirvana- Hide quoted text -
>
> - Show quoted text -
svchost.exe is a generic process that can run many Windows Services.
What specific service(s) is running in that process?
Please use:
TASKLIST.EXE /svc
to tell me which service runs in which process name and PID.
I suspect it is still WAS's svchost.exe, in which case it means you
did not disable Socket Pooling as described in the KB article you
listed earlier.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: Accessing Webmail without using port No. extension
am 14.08.2007 11:22:54 von cw1972
On Aug 14, 1:01 am, Nirvana wrote:
> On Aug 13, 9:22 am, David Wang wrote:
>
>
>
>
>
> > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > wrote:
>
> > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > IIS at all?
>
> > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > What you need to do is:
> > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > managed to set up a redirection)
> > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > host header.
>
> > > > > > > > --
> > > > > > > > Regards,
> > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > Nirvana wrote:
> > > > > > > > >Hi All,
> > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > >box.
>
> > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > >port extension
> > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > >I tried 2 solutions
> > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > >and pointed port to 1234
> > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > >used by mail server
>
> > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > >Selected "redirection to another URL"
> > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > >Cheers
>
> > > > > > > Hi Kris,
> > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > server. "
> > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > listening on port 1234
>
> > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > on
> > > > > > > the same port (because they are two different processes). If you are
> > > > > > > using
> > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > using
> > > > > > > IIS at all? "
> > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > "What you need to do is:
> > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > to
> > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > managed to set up a redirection) "
>
> > > > > > > Always works nor problem no trouble.
>
> > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > host header. "
> > > > > > > ?????
> > > > > > > Didn't get it.
>
> > > > > > One of my reply was lost....
>
> > > > > > Here is the update.
>
> > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > Please verify by running the following on the commandline:
> > > > > NETSTAT.EXE -ano
>
> > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > no socket pooling)
>
> > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > want to allow access on port 80.
>
> > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > tohttp://webmail:1234.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > //
>
> > > > Thanks David
> > > > I'll try later and will update.
>
> > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > tohttp://webmail:1234. "
> > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > has blocked almost all ports and the only port open is 80 and that is
> > > > why the whole story begins to configure Webmail on port 80.
>
> > > > Cheers
>
> > > Hi All,
> > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > I've checked carefully and none of my websites are listening on
> > > default port, all of them are listening on 10.0.0.1:80
>
> > > So the conclusion is I've still got some server/services listening on
> > > port 80.
>
> > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > other services which might be listening on port 80.
> > > Router firewall is disabled.
>
> > > How do I find out which service/server is still listening on
> > > 0.0.0.0:80 ?
>
> > > Thanks
> > > Nirvana- Hide quoted text -
>
> > > - Show quoted text -
>
> > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > Look up the PID in the Task Manager to figure out what process is
> > holding onto 0.0.0.0:80.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> I checked in Task Manager for that PID and it is svchost.exe
>
> Where to go from here now?
>
Process Explorer (http://www.microsoft.com/technet/sysinternals/
ProcessesAndThreads/ProcessExplorer.mspx) from SysInternals will tell
you what process is running within svchost.exe
Re: Accessing Webmail without using port No. extension
am 14.08.2007 20:49:17 von Nirvana
On Aug 14, 1:32 am, David Wang wrote:
> On Aug 13, 5:01 pm, Nirvana wrote:
>
>
>
> > On Aug 13, 9:22 am, David Wang wrote:
>
> > > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > > wrote:
>
> > > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > > IIS at all?
>
> > > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > > What you need to do is:
> > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > managed to set up a redirection)
> > > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > host header.
>
> > > > > > > > > --
> > > > > > > > > Regards,
> > > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > > Nirvana wrote:
> > > > > > > > > >Hi All,
> > > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > > >box.
>
> > > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > > >port extension
> > > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > > >I tried 2 solutions
> > > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > > >and pointed port to 1234
> > > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > > >used by mail server
>
> > > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > > >Selected "redirection to another URL"
> > > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > > >Cheers
>
> > > > > > > > Hi Kris,
> > > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > > server. "
> > > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > > listening on port 1234
>
> > > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > > on
> > > > > > > > the same port (because they are two different processes). If you are
> > > > > > > > using
> > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > > using
> > > > > > > > IIS at all? "
> > > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > > "What you need to do is:
> > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > > to
> > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > managed to set up a redirection) "
>
> > > > > > > > Always works nor problem no trouble.
>
> > > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > host header. "
> > > > > > > > ?????
> > > > > > > > Didn't get it.
>
> > > > > > > One of my reply was lost....
>
> > > > > > > Here is the update.
>
> > > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > > - Show quoted text -
>
> > > > > > Please verify by running the following on the commandline:
> > > > > > NETSTAT.EXE -ano
>
> > > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > > no socket pooling)
>
> > > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > > want to allow access on port 80.
>
> > > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > tohttp://webmail:1234.
>
> > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > //
>
> > > > > Thanks David
> > > > > I'll try later and will update.
>
> > > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > tohttp://webmail:1234. "
> > > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > > has blocked almost all ports and the only port open is 80 and that is
> > > > > why the whole story begins to configure Webmail on port 80.
>
> > > > > Cheers
>
> > > > Hi All,
> > > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > > I've checked carefully and none of my websites are listening on
> > > > default port, all of them are listening on 10.0.0.1:80
>
> > > > So the conclusion is I've still got some server/services listening on
> > > > port 80.
>
> > > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > > other services which might be listening on port 80.
> > > > Router firewall is disabled.
>
> > > > How do I find out which service/server is still listening on
> > > > 0.0.0.0:80 ?
>
> > > > Thanks
> > > > Nirvana- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > > Look up the PID in the Task Manager to figure out what process is
> > > holding onto 0.0.0.0:80.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > I checked in Task Manager for that PID and it is svchost.exe
>
> > Where to go from here now?
>
> > Cheers
> > Nirvana- Hide quoted text -
>
> > - Show quoted text -
>
> svchost.exe is a generic process that can run many Windows Services.
> What specific service(s) is running in that process?
>
> Please use:
> TASKLIST.EXE /svc
>
> to tell me which service runs in which process name and PID.
>
> I suspect it is still WAS's svchost.exe, in which case it means you
> did not disable Socket Pooling as described in the KB article you
> listed earlier.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
Interesting stuff
I can see following processes running with process ID 668 including
the 10.0.0.2:80
TCP 10.0.0.1:4546 0.0.0.0:0 LISTENING
668
TCP 10.0.0.2:80 0.0.0.0:0 LISTENING
668
TCP 10.0.0.2:4546 0.0.0.0:0 LISTENING
668
I checked the output of TASKLIST.EXE /svc and for PID 668 and found
following processes
svchost.exe 668 W3SVC
Any help?
Thanks
Nirvana
Re: Accessing Webmail without using port No. extension
am 14.08.2007 21:02:25 von Nirvana
On Aug 14, 10:22 am, cw1972 wrote:
> On Aug 14, 1:01 am, Nirvana wrote:
>
> > On Aug 13, 9:22 am, David Wang wrote:
>
> > > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > > wrote:
>
> > > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > > IIS at all?
>
> > > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > > What you need to do is:
> > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > managed to set up a redirection)
> > > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > host header.
>
> > > > > > > > > --
> > > > > > > > > Regards,
> > > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > > Nirvana wrote:
> > > > > > > > > >Hi All,
> > > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > > >box.
>
> > > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > > >port extension
> > > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > > >I tried 2 solutions
> > > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > > >and pointed port to 1234
> > > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > > >used by mail server
>
> > > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > > >Selected "redirection to another URL"
> > > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > > >Cheers
>
> > > > > > > > Hi Kris,
> > > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > > server. "
> > > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > > listening on port 1234
>
> > > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > > on
> > > > > > > > the same port (because they are two different processes). If you are
> > > > > > > > using
> > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > > using
> > > > > > > > IIS at all? "
> > > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > > "What you need to do is:
> > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > > to
> > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > managed to set up a redirection) "
>
> > > > > > > > Always works nor problem no trouble.
>
> > > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > host header. "
> > > > > > > > ?????
> > > > > > > > Didn't get it.
>
> > > > > > > One of my reply was lost....
>
> > > > > > > Here is the update.
>
> > > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > > - Show quoted text -
>
> > > > > > Please verify by running the following on the commandline:
> > > > > > NETSTAT.EXE -ano
>
> > > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > > no socket pooling)
>
> > > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > > want to allow access on port 80.
>
> > > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > tohttp://webmail:1234.
>
> > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > //
>
> > > > > Thanks David
> > > > > I'll try later and will update.
>
> > > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > tohttp://webmail:1234. "
> > > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > > has blocked almost all ports and the only port open is 80 and that is
> > > > > why the whole story begins to configure Webmail on port 80.
>
> > > > > Cheers
>
> > > > Hi All,
> > > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > > I've checked carefully and none of my websites are listening on
> > > > default port, all of them are listening on 10.0.0.1:80
>
> > > > So the conclusion is I've still got some server/services listening on
> > > > port 80.
>
> > > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > > other services which might be listening on port 80.
> > > > Router firewall is disabled.
>
> > > > How do I find out which service/server is still listening on
> > > > 0.0.0.0:80 ?
>
> > > > Thanks
> > > > Nirvana- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > > Look up the PID in the Task Manager to figure out what process is
> > > holding onto 0.0.0.0:80.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > I checked in Task Manager for that PID and it is svchost.exe
>
> > Where to go from here now?
>
> Process Explorer (http://www.microsoft.com/technet/sysinternals/
> ProcessesAndThreads/ProcessExplorer.mspx) from SysInternals will tell
> you what process is running within svchost.exe
I run process explorer and can see that it is
svchost.exe -k iisvcs with process ID 668
Any help?
Re: Accessing Webmail without using port No. extension
am 14.08.2007 22:40:44 von David Wang
On Aug 14, 11:49 am, Nirvana wrote:
> On Aug 14, 1:32 am, David Wang wrote:
>
>
>
>
>
> > On Aug 13, 5:01 pm, Nirvana wrote:
>
> > > On Aug 13, 9:22 am, David Wang wrote:
>
> > > > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > > > wrote:
>
> > > > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > > > IIS at all?
>
> > > > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > > > What you need to do is:
> > > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > > managed to set up a redirection)
> > > > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > > host header.
>
> > > > > > > > > > --
> > > > > > > > > > Regards,
> > > > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > > > Nirvana wrote:
> > > > > > > > > > >Hi All,
> > > > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > > > >box.
>
> > > > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > > > >port extension
> > > > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > > > >I tried 2 solutions
> > > > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > > > >and pointed port to 1234
> > > > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > > > >used by mail server
>
> > > > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > > > >Selected "redirection to another URL"
> > > > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > > > >Cheers
>
> > > > > > > > > Hi Kris,
> > > > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > > > server. "
> > > > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > > > listening on port 1234
>
> > > > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > > > on
> > > > > > > > > the same port (because they are two different processes). If you are
> > > > > > > > > using
> > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > > > using
> > > > > > > > > IIS at all? "
> > > > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > > > "What you need to do is:
> > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > > > to
> > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > managed to set up a redirection) "
>
> > > > > > > > > Always works nor problem no trouble.
>
> > > > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > host header. "
> > > > > > > > > ?????
> > > > > > > > > Didn't get it.
>
> > > > > > > > One of my reply was lost....
>
> > > > > > > > Here is the update.
>
> > > > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > > > - Show quoted text -
>
> > > > > > > Please verify by running the following on the commandline:
> > > > > > > NETSTAT.EXE -ano
>
> > > > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > > > no socket pooling)
>
> > > > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > > > want to allow access on port 80.
>
> > > > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > > tohttp://webmail:1234.
>
> > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > > //
>
> > > > > > Thanks David
> > > > > > I'll try later and will update.
>
> > > > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > tohttp://webmail:1234. "
> > > > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > > > has blocked almost all ports and the only port open is 80 and that is
> > > > > > why the whole story begins to configure Webmail on port 80.
>
> > > > > > Cheers
>
> > > > > Hi All,
> > > > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > > > I've checked carefully and none of my websites are listening on
> > > > > default port, all of them are listening on 10.0.0.1:80
>
> > > > > So the conclusion is I've still got some server/services listening on
> > > > > port 80.
>
> > > > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > > > other services which might be listening on port 80.
> > > > > Router firewall is disabled.
>
> > > > > How do I find out which service/server is still listening on
> > > > > 0.0.0.0:80 ?
>
> > > > > Thanks
> > > > > Nirvana- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > > > Look up the PID in the Task Manager to figure out what process is
> > > > holding onto 0.0.0.0:80.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //
>
> > > I checked in Task Manager for that PID and it is svchost.exe
>
> > > Where to go from here now?
>
> > > Cheers
> > > Nirvana- Hide quoted text -
>
> > > - Show quoted text -
>
> > svchost.exe is a generic process that can run many Windows Services.
> > What specific service(s) is running in that process?
>
> > Please use:
> > TASKLIST.EXE /svc
>
> > to tell me which service runs in which process name and PID.
>
> > I suspect it is still WAS's svchost.exe, in which case it means you
> > did not disable Socket Pooling as described in the KB article you
> > listed earlier.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> Interesting stuff
> I can see following processes running with process ID 668 including
> the 10.0.0.2:80
>
> TCP 10.0.0.1:4546 0.0.0.0:0 LISTENING
> 668
> TCP 10.0.0.2:80 0.0.0.0:0 LISTENING
> 668
> TCP 10.0.0.2:4546 0.0.0.0:0 LISTENING
> 668
>
> I checked the output of TASKLIST.EXE /svc and for PID 668 and found
> following processes
> svchost.exe 668 W3SVC
>
> Any help?
>
> Thanks
> Nirvana- Hide quoted text -
>
> - Show quoted text -
Please clarify if you still see a svchost holding 0.0.0.0:80
>From your output, there is no socket pooling because the binding is to
specific IP:Port
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: Accessing Webmail without using port No. extension
am 15.08.2007 01:47:31 von Nirvana
On Aug 14, 9:40 pm, David Wang wrote:
> On Aug 14, 11:49 am, Nirvana wrote:
>
>
>
> > On Aug 14, 1:32 am, David Wang wrote:
>
> > > On Aug 13, 5:01 pm, Nirvana wrote:
>
> > > > On Aug 13, 9:22 am, David Wang wrote:
>
> > > > > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > > > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > > > > wrote:
>
> > > > > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > > > > IIS at all?
>
> > > > > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > > > > What you need to do is:
> > > > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > > > managed to set up a redirection)
> > > > > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > > > host header.
>
> > > > > > > > > > > --
> > > > > > > > > > > Regards,
> > > > > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > > > > Nirvana wrote:
> > > > > > > > > > > >Hi All,
> > > > > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > > > > >box.
>
> > > > > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > > > > >port extension
> > > > > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > > > > >I tried 2 solutions
> > > > > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > > > > >and pointed port to 1234
> > > > > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > > > > >used by mail server
>
> > > > > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > > > > >Selected "redirection to another URL"
> > > > > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > > > > >Cheers
>
> > > > > > > > > > Hi Kris,
> > > > > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > > > > server. "
> > > > > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > > > > listening on port 1234
>
> > > > > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > > > > on
> > > > > > > > > > the same port (because they are two different processes). If you are
> > > > > > > > > > using
> > > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > > > > using
> > > > > > > > > > IIS at all? "
> > > > > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > > > > "What you need to do is:
> > > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > > > > to
> > > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > > managed to set up a redirection) "
>
> > > > > > > > > > Always works nor problem no trouble.
>
> > > > > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > > host header. "
> > > > > > > > > > ?????
> > > > > > > > > > Didn't get it.
>
> > > > > > > > > One of my reply was lost....
>
> > > > > > > > > Here is the update.
>
> > > > > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > > > > - Show quoted text -
>
> > > > > > > > Please verify by running the following on the commandline:
> > > > > > > > NETSTAT.EXE -ano
>
> > > > > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > > > > no socket pooling)
>
> > > > > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > > > > want to allow access on port 80.
>
> > > > > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > > > tohttp://webmail:1234.
>
> > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > > > //
>
> > > > > > > Thanks David
> > > > > > > I'll try later and will update.
>
> > > > > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > > tohttp://webmail:1234. "
> > > > > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > > > > has blocked almost all ports and the only port open is 80 and that is
> > > > > > > why the whole story begins to configure Webmail on port 80.
>
> > > > > > > Cheers
>
> > > > > > Hi All,
> > > > > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > > > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > > > > I've checked carefully and none of my websites are listening on
> > > > > > default port, all of them are listening on 10.0.0.1:80
>
> > > > > > So the conclusion is I've still got some server/services listening on
> > > > > > port 80.
>
> > > > > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > > > > other services which might be listening on port 80.
> > > > > > Router firewall is disabled.
>
> > > > > > How do I find out which service/server is still listening on
> > > > > > 0.0.0.0:80 ?
>
> > > > > > Thanks
> > > > > > Nirvana- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > > > > Look up the PID in the Task Manager to figure out what process is
> > > > > holding onto 0.0.0.0:80.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > //
>
> > > > I checked in Task Manager for that PID and it is svchost.exe
>
> > > > Where to go from here now?
>
> > > > Cheers
> > > > Nirvana- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > svchost.exe is a generic process that can run many Windows Services.
> > > What specific service(s) is running in that process?
>
> > > Please use:
> > > TASKLIST.EXE /svc
>
> > > to tell me which service runs in which process name and PID.
>
> > > I suspect it is still WAS's svchost.exe, in which case it means you
> > > did not disable Socket Pooling as described in the KB article you
> > > listed earlier.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > Interesting stuff
> > I can see following processes running with process ID 668 including
> > the 10.0.0.2:80
>
> > TCP 10.0.0.1:4546 0.0.0.0:0 LISTENING
> > 668
> > TCP 10.0.0.2:80 0.0.0.0:0 LISTENING
> > 668
> > TCP 10.0.0.2:4546 0.0.0.0:0 LISTENING
> > 668
>
> > I checked the output of TASKLIST.EXE /svc and for PID 668 and found
> > following processes
> > svchost.exe 668 W3SVC
>
> > Any help?
>
> > Thanks
> > Nirvana- Hide quoted text -
>
> > - Show quoted text -
>
> Please clarify if you still see a svchost holding 0.0.0.0:80
>
> >From your output, there is no socket pooling because the binding is to
>
> specific IP:Port
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
Now the socket pooling is disabled (Since Aug 12, I'm posting all data
based on socket polling disabled)
There is no binding on 0.0.0.0:80
All of my websites are now listening on 1.0.0.0:80
I want to make 1.0.0.02:80 to be used by Webmail
But 1.0.0.02:80 is already used by svchost:
TCP 10.0.0.2:80 0.0.0.0:0 LISTENING 668
So the problem I'm facing is
"who is using 1.0.0.02:80"
Re: Accessing Webmail without using port No. extension
am 15.08.2007 06:18:46 von David Wang
On Aug 14, 4:47 pm, Nirvana wrote:
> On Aug 14, 9:40 pm, David Wang wrote:
>
> > On Aug 14, 11:49 am, Nirvana wrote:
>
> > > On Aug 14, 1:32 am, David Wang wrote:
>
> > > > On Aug 13, 5:01 pm, Nirvana wrote:
>
> > > > > On Aug 13, 9:22 am, David Wang wrote:
>
> > > > > > On Aug 12, 7:45 am, Nirvana wrote:
>
> > > > > > > On Aug 8, 10:01 am, Nirvana wrote:
>
> > > > > > > > On Aug 8, 2:14 am, David Wang wrote:
>
> > > > > > > > > On Aug 7, 4:17 pm, Nirvana wrote:
>
> > > > > > > > > > On Aug 7, 10:11 am, Nirvana wrote:
>
> > > > > > > > > > > On Aug 7, 7:31 am, "Kristofer Gafvert"
> > > > > > > > > > > wrote:
>
> > > > > > > > > > > > I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > > > > accesswebmail. You also say that this port is used by your email server.
>
> > > > > > > > > > > > This doesn't work. You cannot have the email server and IIS listening on
> > > > > > > > > > > > the same port (because they are two different processes). If you are using
> > > > > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not using
> > > > > > > > > > > > IIS at all?
>
> > > > > > > > > > > > Anyway, if you are indeed using IIS, we should be able to make this working.
>
> > > > > > > > > > > > What you need to do is:
> > > > > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing to
> > > > > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > > > > managed to set up a redirection)
> > > > > > > > > > > > 2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > > > > host header.
>
> > > > > > > > > > > > --
> > > > > > > > > > > > Regards,
> > > > > > > > > > > > Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelatedInfo
>
> > > > > > > > > > > > Nirvana wrote:
> > > > > > > > > > > > >Hi All,
> > > > > > > > > > > > >I've web server and mail server running on same Windows 2k3 + IIS 6
> > > > > > > > > > > > >box.
>
> > > > > > > > > > > > >Mail server is Code Crafters Ability Mail Server.
>
> > > > > > > > > > > > >I can access mail server by usinghttp://www.mydomain.com:1234
>
> > > > > > > > > > > > >But I want to access mail server by just typing URL of domain without
> > > > > > > > > > > > >port extension
> > > > > > > > > > > > >E.g.http://webmail.mydomain.com
>
> > > > > > > > > > > > >I tried 2 solutions
> > > > > > > > > > > > >1) Host header solution: I configuredwebmail.mydomain.com hos header
> > > > > > > > > > > > >and pointed port to 1234
> > > > > > > > > > > > >- This obviously fails as I'm trying to use port 1234 which is being
> > > > > > > > > > > > >used by mail server
>
> > > > > > > > > > > > >2) I configuredwebmail.mydomain.com as a separate website
> > > > > > > > > > > > >While configuring I pointed the home directory to a dummy empty folder
> > > > > > > > > > > > >and then I redirected the URL tohttp://www.mydomain.com:1234
>
> > > > > > > > > > > > >Selected "redirection to another URL"
> > > > > > > > > > > > >Selected "exact URL" and "permanent redirection"
>
> > > > > > > > > > > > >- I ended up at same place where I started from. This solution
> > > > > > > > > > > > >redirectshttp://webmail.mydomain.comtohttp://www.mydomain.c om:1234
>
> > > > > > > > > > > > >Now I'm lost how do I make this work?
>
> > > > > > > > > > > > >My requirement is I don't want the port number, I want it to access on
> > > > > > > > > > > > >Port 80. Reason is I want to accesswebmailbehind a proxy which
> > > > > > > > > > > > >blocks almost all ports except 80.
>
> > > > > > > > > > > > >I can't run mail server on port 80 as I run web server.
>
> > > > > > > > > > > > >Any help would be appreciated. I can offer pure British Beer ;)
>
> > > > > > > > > > > > >Cheers
>
> > > > > > > > > > > Hi Kris,
> > > > > > > > > > > "I don't understand this. You say that you are now using port 1234 to
> > > > > > > > > > > accesswebmail. You also say that this port is used by your email
> > > > > > > > > > > server. "
> > > > > > > > > > > Yes as I explained in my earlier post above, mywebmailserver is
> > > > > > > > > > > listening on port 1234
>
> > > > > > > > > > > "This doesn't work. You cannot have the email server and IIS listening
> > > > > > > > > > > on
> > > > > > > > > > > the same port (because they are two different processes). If you are
> > > > > > > > > > > using
> > > > > > > > > > > port 1234 to access thewebmailat this moment, perhaps you are not
> > > > > > > > > > > using
> > > > > > > > > > > IIS at all? "
> > > > > > > > > > > Yes right, I can't do that I can understand that.
>
> > > > > > > > > > > "What you need to do is:
> > > > > > > > > > > 1. Make sure that DNS is working andwebmail.mydomain.com is pointing
> > > > > > > > > > > to
> > > > > > > > > > > the IP address of the webserver. (should already be working since you
> > > > > > > > > > > managed to set up a redirection) "
>
> > > > > > > > > > > Always works nor problem no trouble.
>
> > > > > > > > > > > "2. Modify the existing website to use port 80 and thewebmail.mydomain.com
> > > > > > > > > > > host header. "
> > > > > > > > > > > ?????
> > > > > > > > > > > Didn't get it.
>
> > > > > > > > > > One of my reply was lost....
>
> > > > > > > > > > Here is the update.
>
> > > > > > > > > > I foundhttp://support.microsoft.com/kb/813368/EN-US/
>
> > > > > > > > > > So I though I got the magic power but still i'm stuck.
>
> > > > > > > > > > 1) I disabled the socket pooling so that I can run mailserver on
> > > > > > > > > > 10.0.0.2:80 (utilizing same port on 2 IP addresses on same Server)
> > > > > > > > > > 2) I configured all my websites in IIS to use 10.0.0.1:80 so that
> > > > > > > > > > there is no conflict between 2 IP Addresses for port 80
> > > > > > > > > > 3) Now I can't configure mail server to use 10.0.0.2:80 it gives
> > > > > > > > > > conflict. Throws "Unable to open WebMail port"
>
> > > > > > > > > > It seems socket pooling disabling doesn't work?- Hide quoted text -
>
> > > > > > > > > > - Show quoted text -
>
> > > > > > > > > Please verify by running the following on the commandline:
> > > > > > > > > NETSTAT.EXE -ano
>
> > > > > > > > > It will show you how IIS and WebMail are binding to their IP:Port. You
> > > > > > > > > should not see 0.0.0.0:80 (this means port 80 of any IP -- which is
> > > > > > > > > socket pooling) but rather 10.0.0.1:80 (only port 80 on IP 10.0.0.1 --
> > > > > > > > > no socket pooling)
>
> > > > > > > > > Maybe WebMail uses socket pooling of its own, so it will fail even if
> > > > > > > > > you successfully disable IIS's socket pooling. Maybe WebMail does not
> > > > > > > > > want to allow access on port 80.
>
> > > > > > > > > Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > > > > tohttp://webmail:1234.
>
> > > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > > > > //
>
> > > > > > > > Thanks David
> > > > > > > > I'll try later and will update.
>
> > > > > > > > " Maybe you can configure the proxy to forwardhttp://webmail.domain.com
> > > > > > > > tohttp://webmail:1234. "
> > > > > > > > The proxy is on client side (Read from my work lol ;) ). Client side
> > > > > > > > has blocked almost all ports and the only port open is 80 and that is
> > > > > > > > why the whole story begins to configure Webmail on port 80.
>
> > > > > > > > Cheers
>
> > > > > > > Hi All,
> > > > > > > I've checked by running NETSTAT.EXE -ano command and I can see
> > > > > > > 0.0.0.0:80 which means I've got a service still listening on port 80.
> > > > > > > I've checked carefully and none of my websites are listening on
> > > > > > > default port, all of them are listening on 10.0.0.1:80
>
> > > > > > > So the conclusion is I've still got some server/services listening on
> > > > > > > port 80.
>
> > > > > > > I run IIS, mySQL and Ability mail server and I can't think of any
> > > > > > > other services which might be listening on port 80.
> > > > > > > Router firewall is disabled.
>
> > > > > > > How do I find out which service/server is still listening on
> > > > > > > 0.0.0.0:80 ?
>
> > > > > > > Thanks
> > > > > > > Nirvana- Hide quoted text -
>
> > > > > > > - Show quoted text -
>
> > > > > > NETSTAT.EXE -ano also tells you the PID that is holding that socket.
> > > > > > Look up the PID in the Task Manager to figure out what process is
> > > > > > holding onto 0.0.0.0:80.
>
> > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > //
>
> > > > > I checked in Task Manager for that PID and it is svchost.exe
>
> > > > > Where to go from here now?
>
> > > > > Cheers
> > > > > Nirvana- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > svchost.exe is a generic process that can run many Windows Services.
> > > > What specific service(s) is running in that process?
>
> > > > Please use:
> > > > TASKLIST.EXE /svc
>
> > > > to tell me which service runs in which process name and PID.
>
> > > > I suspect it is still WAS's svchost.exe, in which case it means you
> > > > did not disable Socket Pooling as described in the KB article you
> > > > listed earlier.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //
>
> > > Interesting stuff
> > > I can see following processes running with process ID 668 including
> > > the 10.0.0.2:80
>
> > > TCP 10.0.0.1:4546 0.0.0.0:0 LISTENING
> > > 668
> > > TCP 10.0.0.2:80 0.0.0.0:0 LISTENING
> > > 668
> > > TCP 10.0.0.2:4546 0.0.0.0:0 LISTENING
> > > 668
>
> > > I checked the output of TASKLIST.EXE /svc and for PID 668 and found
> > > following processes
> > > svchost.exe 668 W3SVC
>
> > > Any help?
>
> > > Thanks
> > > Nirvana- Hide quoted text -
>
> > > - Show quoted text -
>
> > Please clarify if you still see a svchost holding 0.0.0.0:80
>
> > >From your output, there is no socket pooling because the binding is to
>
> > specific IP:Port
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> Now the socket pooling is disabled (Since Aug 12, I'm posting all data
> based on socket polling disabled)
> There is no binding on 0.0.0.0:80
>
> All of my websites are now listening on 1.0.0.0:80
>
> I want to make 1.0.0.02:80 to be used by Webmail
>
> But 1.0.0.02:80 is already used by svchost:
> TCP 10.0.0.2:80 0.0.0.0:0 LISTENING 668
>
> So the problem I'm facing is
>
> "who is using 1.0.0.02:80"
I presume you have websites listening on 10.0.0.1:80 and
10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
IIS.
You will have to turn off the website listening on 10.0.0.2:4546 to
make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
List works.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: Accessing Webmail without using port No. extension
am 15.08.2007 14:18:49 von Nirvana
>
> I presume you have websites listening on 10.0.0.1:80 and
> 10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
> IIS.
>
> You will have to turn off the website listening on 10.0.0.2:4546 to
> make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
> List works.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
This is very strange I run no websites/server on 2nd IP 10.0.0.2
exclusively.
All of my websites are on 10.0.0.1
10.0.0.2:4546 might be used by any other servers?
Some server might be taking 10.0.0.2 ports by default.
If I remove 10.0.0.2 IP Address from TCP/IP i doesn't affect any of my
server/websites.
Re: Accessing Webmail without using port No. extension
am 17.08.2007 01:47:56 von Nirvana
> I presume you have websites listening on 10.0.0.1:80 and
> 10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
> IIS.
>
> You will have to turn off the website listening on 10.0.0.2:4546 to
> make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
> List works.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //
I tried to kill task 10.0.0.2:4546 from task manager but the
10.0.0.2:80 is not killed.
I killed even 10.0.0.2:80 associated process in task manager but it
starts again on different port.
Any idea what this service could be?
Re: Accessing Webmail without using port No. extension
am 17.08.2007 02:09:31 von Nirvana
On Aug 17, 12:47 am, Nirvana wrote:
> > I presume you have websites listening on 10.0.0.1:80 and
> > 10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
> > IIS.
>
> > You will have to turn off the website listening on 10.0.0.2:4546 to
> > make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
> > List works.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> I tried to kill task 10.0.0.2:4546 from task manager but the
> 10.0.0.2:80 is not killed.
> I killed even 10.0.0.2:80 associated process in task manager but it
> starts again on different port.
>
> Any idea what this service could be?
It is World wide publishing process which is running on both
10.0.0.1:80 and 10.0.0.2:80
how to make this not using 10.0.0.2:80?
Re: Accessing Webmail without using port No. extension
am 17.08.2007 03:21:28 von Nirvana
On Aug 17, 12:47 am, Nirvana wrote:
> > I presume you have websites listening on 10.0.0.1:80 and
> > 10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
> > IIS.
>
> > You will have to turn off the website listening on 10.0.0.2:4546 to
> > make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
> > List works.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //
>
> I tried to kill task 10.0.0.2:4546 from task manager but the
> 10.0.0.2:80 is not killed.
> I killed even 10.0.0.2:80 associated process in task manager but it
> starts again on different port.
>
> Any idea what this service could be?
okie finally I manage to setup the webmail on 10.0.0.2:80 it works
fine.
When I type http://10.0.0.2:80 on my W2k3 server webmail shows up.
Now I'm back to the point from where I started.
How do i setup my domain webmail.mydomain.com to be redirected to
webmail?
I can't configure webmail.mydomain.com on 10.0.0.2:80 as webmail is
runnign on this port
I can't redirect webmail.mydomain.com to http://10.0.0.2:80 as it it
local IP and not visible on internet
Humm!!! after so long discussion and crossing so many hurdles I'm back
to Square one ;)
Re: Accessing Webmail without using port No. extension
am 18.08.2007 10:12:08 von David Wang
On Aug 16, 6:21 pm, Nirvana wrote:
> On Aug 17, 12:47 am, Nirvana wrote:
>
>
>
>
>
> > > I presume you have websites listening on 10.0.0.1:80 and
> > > 10.0.0.2:4546, and no websites explicitly listening on 10.0.0.2:80 in
> > > IIS.
>
> > > You will have to turn off the website listening on 10.0.0.2:4546 to
> > > make 10.0.0.2:80 available. It's a quirk with how HTTP.SYS IP Listen
> > > List works.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //
>
> > I tried to kill task 10.0.0.2:4546 from task manager but the
> > 10.0.0.2:80 is not killed.
> > I killed even 10.0.0.2:80 associated process in task manager but it
> > starts again on different port.
>
> > Any idea what this service could be?
>
> okie finally I manage to setup the webmail on 10.0.0.2:80 it works
> fine.
> When I typehttp://10.0.0.2:80on my W2k3 server webmail shows up.
>
> Now I'm back to the point from where I started.
>
> How do i setup my domain webmail.mydomain.com to be redirected to
> webmail?
>
> I can't configure webmail.mydomain.com on 10.0.0.2:80 as webmail is
> runnign on this port
> I can't redirect webmail.mydomain.com tohttp://10.0.0.2:80as it it
> local IP and not visible on internet
>
> Humm!!! after so long discussion and crossing so many hurdles I'm back
> to Square one ;)- Hide quoted text -
>
> - Show quoted text -
Actually, you are back at everyone's original suggestion to run a
proxy server in front of the whole thing to forward/reverse-proxy
requests appropriately to each web/mail server.
The entire socket pooling exercise happened because you decided that
moving Web Mail's port was somehow going to solve the web proxying
issue...
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//