| Author |
port 80 binding errors
|
|
| Mr. Beck 2005-07-28, 5:59 pm |
| I am having problems with IIS and running another application on trying to
bind to port 80. I have IIS running as a web service that uses all available
IP's on port 80. Obviously when I run my other application I get an error
that the port is already in use (i.e. error 10048: port already in use). But
when I stop all my web services in IIS and try to run my other application, I
get a completely different error. The new error is that I cannot bind to
port 80 (i.e. error 10013: error binding to port). I have even tried to set
IIS to point to one IP address (e.g. 192.168.1.41) and my other application
point to a different one (e.g. 192.168.1.40). I still get the 10013 error
that I cannot bind to port 80 with my other application. In fact no matter
what IP address I point my other application at (even out of range ones like
300.300.300.300) it still gives me a 10013 error that I cannot bind to port
80.
Another thing I tried is completely shutting down IIS and running my
application. And.... this works fine.
It seems that when IIS is running it locks up all communcation to port 80 no
matter what IP address. I was wondering if there is a way to prevent this
from happening so that I can run IIS as a web service and my other
application without having any binding errors to port 80.
Thanks in advance for the help.
| |
| Mr. Beck 2005-07-28, 5:59 pm |
| I think I found a solution to my own problem. For anybody else that runs
into this problem, this is how I found to fix this.
http://support.microsoft.com/defaul...kb;EN-US;813368
"Mr. Beck" wrote:
> I am having problems with IIS and running another application on trying to
> bind to port 80. I have IIS running as a web service that uses all available
> IP's on port 80. Obviously when I run my other application I get an error
> that the port is already in use (i.e. error 10048: port already in use). But
> when I stop all my web services in IIS and try to run my other application, I
> get a completely different error. The new error is that I cannot bind to
> port 80 (i.e. error 10013: error binding to port). I have even tried to set
> IIS to point to one IP address (e.g. 192.168.1.41) and my other application
> point to a different one (e.g. 192.168.1.40). I still get the 10013 error
> that I cannot bind to port 80 with my other application. In fact no matter
> what IP address I point my other application at (even out of range ones like
> 300.300.300.300) it still gives me a 10013 error that I cannot bind to port
> 80.
>
> Another thing I tried is completely shutting down IIS and running my
> application. And.... this works fine.
>
> It seems that when IIS is running it locks up all communcation to port 80 no
> matter what IP address. I was wondering if there is a way to prevent this
> from happening so that I can run IIS as a web service and my other
> application without having any binding errors to port 80.
>
> Thanks in advance for the help.
| |
| Alok Kumar 2005-07-28, 5:59 pm |
| or just disable the socket pooling
cscript adsutil.vbs set w3svc/disablesocketpooling true
Alok
"Mr. Beck" wrote:
[vbcol=seagreen]
> I think I found a solution to my own problem. For anybody else that runs
> into this problem, this is how I found to fix this.
>
> http://support.microsoft.com/defaul...kb;EN-US;813368
>
>
>
> "Mr. Beck" wrote:
>
|
|
|
|