Error: Protocol Not Valid for HTTP. Might Be Because Port Number IsOut of Range.

I am getting the following error:

"The protocol binding '192.168.100.110:80:' is not valid for 'http'.
This might be because the port number is out of range."

I have checked network solutions and my router and my server and
everything looks the same.
In my router, I had the TCP protocol selected. I have changed to
"both" to no avail. I have also
tried pointingto 8080.

I have never seen this before. I get the error when I try to point to
a new WCF web service that
is running below a subdomain.

Any ideas?

Thanks.

It could possibly be because you already have an apache web service running
on port 80 on that server,
Anthony,
http://www.airdesk.com


"pbd22" <(E-Mail Removed)> wrote in message
news:8aff48c6-3b56-48a5-9dfc-(E-Mail Removed)...
>
> I am getting the following error:
>
> "The protocol binding '192.168.100.110:80:' is not valid for 'http'.
> This might be because the port number is out of range."
>
> I have checked network solutions and my router and my server and
> everything looks the same.
> In my router, I had the TCP protocol selected. I have changed to
> "both" to no avail. I have also
> tried pointingto 8080.
>
> I have never seen this before. I get the error when I try to point to
> a new WCF web service that
> is running below a subdomain.
>
> Any ideas?
>
> Thanks.

On Apr 23, 5:08*pm, "Anthony [MVP]" <anth...@no-reply.com> wrote:
> It could possibly be because you already have an apache web service running
> on port 80 on that server,
> Anthony,http://www.airdesk.com
>
> "pbd22" <dush...@gmail.com> wrote in message
>
> news:8aff48c6-3b56-48a5-9dfc-(E-Mail Removed)...
>
>
>
> > I am getting the following error:
>
> > "The protocol binding '192.168.100.110:80:' is not valid for 'http'.
> > This might be because the port number is out of range."
>
> > I have checked network solutions and my router and my server and
> > everything looks the same.
> > In my router, I had the TCP protocol selected. I have changed to
> > "both" to no avail. I have also
> > tried pointingto 8080.
>
> > I have never seen this before. I get the error when I try to point to
> > a new WCF web service that
> > is running below a subdomain.
>
> > Any ideas?
>
> > Thanks.

Hi. Thanks.

Thanks is an interesting thought.

I am using IIS 6.0 / Server 2003, not Apache.
Does anybody out there know of a DOS command
to probe port 80 and find out what processes are using it?
Or, for that matter, to find out what ports are being used
by a particular server?

I am still stuck on this one...

"pbd22" <(E-Mail Removed)> wrote in message
news:4b709e86-9ce2-4485-933b-(E-Mail Removed)...
>
> Hi. Thanks.
>
> Thanks is an interesting thought.
>
> I am using IIS 6.0 / Server 2003, not Apache.
> Does anybody out there know of a DOS command
> to probe port 80 and find out what processes are using it?
> Or, for that matter, to find out what ports are being used
> by a particular server?
>
> I am still stuck on this one...

You can use netstat -ano, look at the PID and associate it with the PID in
Task Manager.

There are other tools that can also be used, such as Process Explorer, to
take it a step further, if need be, to look at the actual DLLs under a
process.

Process ExplorerProcess Explorer, also known as procexp.exe, shows you
information about which handles and DLLs processes have opened or loaded.
http://technet.microsoft.com/en-us/s.../bb896653.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

On Apr 23, 11:08*pm, "Ace Fekay [Microsoft Certified Trainer]"
<ace...@mvps.RemoveThisPart.org> wrote:
> "pbd22" <dush...@gmail.com> wrote in message
>
> news:4b709e86-9ce2-4485-933b-(E-Mail Removed)...
>
>
>
> > Hi. Thanks.
>
> > Thanks is an interesting thought.
>
> > I am using IIS 6.0 / Server 2003, not Apache.
> > Does anybody out there know of a DOS command
> > to probe port 80 and find out what processes are using it?
> > Or, for that matter, to find out what ports are being used
> > by a particular server?
>
> > I am still stuck on this one...
>
> You can use netstat -ano, look at the PID and associate it with the PID in
> Task Manager.
>
> There are other tools that can also be used, such as Process Explorer, to
> take it a step further, if need be, to look at the actual DLLs under a
> process.
>
> Process ExplorerProcess Explorer, also known as procexp.exe, shows you
> information about which handles and DLLs processes have opened or loaded.http://technet.microsoft.com/en-us/s.../bb896653.aspx
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> ace...@mvps.RemoveThisPart.org
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> checkhttp://support.microsoft.comfor regional support phone numbers.

OK, thanks for that.
I tried netstat - ano and looked up PID "4" (which pointed to port 80)
and there was no PID "4" in task manager.
PID 4 was the only port 80 process according to netstat so, I am
wondering if an overloaded port isn't the
answer to my original question?

I am still perplexed by this error. Under what conditions might the
network think that a port number which is
obviolusly within bounds might be out of range (assuming a competing
process is not the answer)?

"pbd22" <(E-Mail Removed)> wrote in message
news:893c3a50-392a-437f-9c10-(E-Mail Removed)...

OK, thanks for that.
I tried netstat - ano and looked up PID "4" (which pointed to port 80)
and there was no PID "4" in task manager.
PID 4 was the only port 80 process according to netstat so, I am
wondering if an overloaded port isn't the
answer to my original question?

I am still perplexed by this error. Under what conditions might the
network think that a port number which is
obviolusly within bounds might be out of range (assuming a competing
process is not the answer)?


===
PDB22,

Do you have any apps installed that use web-based administration? I've seen
some apps, such as McAfee ePo, and many others, use their own built-in
Apache installations for them selves, which I;ve found in some cases
conflict.

Kind of unusual that a PID doesn't show up. I assume you have it set to view
processes from all users? Have you looked at Process explorer?

Ace

If you turn the IIS service to manual or disabled and restart, then run
netstat -an, do you see a service on port 80?

I'm afraid I don't follow what you are referring to in the rest of your
problem description. Maybe there is just a problem with the way you have set
up IIS for this web site,
Anthony
http://www.airdesk.com



"pbd22" <(E-Mail Removed)> wrote in message
news:4b709e86-9ce2-4485-933b-(E-Mail Removed)...
> On Apr 23, 5:08 pm, "Anthony [MVP]" <anth...@no-reply.com> wrote:
>> It could possibly be because you already have an apache web service
>> running
>> on port 80 on that server,
>> Anthony,http://www.airdesk.com
>>
>> "pbd22" <dush...@gmail.com> wrote in message
>>
>> news:8aff48c6-3b56-48a5-9dfc-(E-Mail Removed)...
>>
>>
>>
>> > I am getting the following error:
>>
>> > "The protocol binding '192.168.100.110:80:' is not valid for 'http'.
>> > This might be because the port number is out of range."
>>
>> > I have checked network solutions and my router and my server and
>> > everything looks the same.
>> > In my router, I had the TCP protocol selected. I have changed to
>> > "both" to no avail. I have also
>> > tried pointingto 8080.
>>
>> > I have never seen this before. I get the error when I try to point to
>> > a new WCF web service that
>> > is running below a subdomain.
>>
>> > Any ideas?
>>
>> > Thanks.
>
> Hi. Thanks.
>
> Thanks is an interesting thought.
>
> I am using IIS 6.0 / Server 2003, not Apache.
> Does anybody out there know of a DOS command
> to probe port 80 and find out what processes are using it?
> Or, for that matter, to find out what ports are being used
> by a particular server?
>
> I am still stuck on this one...