Can"t see my own port 8080

Folks can see my webserver on port 8080 from the internet. I cannot
see it myself. Is that weird or am I missing something? Thx in
advance for any advice!

Re: Can"t see my own port 8080

you are missing something

"Darksong" wrote in message
news:1182595218.547517.317550@k79g2000hse.googlegroups.com.. .
> Folks can see my webserver on port 8080 from the internet. I cannot
> see it myself. Is that weird or am I missing something? Thx in
> advance for any advice!
>

Re: Can"t see my own port 8080

How is everything set up? Is IIS running on port 8080, or do you have port
forwarding from 8080 to 80, and IIS is running on port 80?

Does your router (if any) have loop back capabilities?

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Darksong wrote:

>Folks can see my webserver on port 8080 from the internet. I cannot
>see it myself. Is that weird or am I missing something? Thx in
>advance for any advice!

Re: Can"t see my own port 8080

Hi -
Port 8080 is the port being used by the webserver and the router port
forwards to the machine's internal IP address at that port.

I'm not sure if loopback is a capability of the router. I don't see
anything that mentions it unless Netgear calls it something else.
(Netgear WGR614v6). Do you think that's an issue?



On Jun 24, 4:39 am, "Kristofer Gafvert"
wrote:
> How is everything set up? Is IIS running on port 8080, or do you have port
> forwarding from 8080 to 80, and IIS is running on port 80?
>
> Does your router (if any) have loop back capabilities?
>
> --
> Regards,
> Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>
>
>
> Darksong wrote:
> >Folks can see my webserver on port 8080 from the internet. I cannot
> >see it myself. Is that weird or am I missing something? Thx in
> >advance for any advice!- Hide quoted text -
>
> - Show quoted text -

Re: Can"t see my own port 8080

If you can use http://localhost:8080/ to access the website from the
server itself, but you cannot use an external name or IP address from
within your internal network, then i do think it is a networking problem
and likely the router does not support loop back.


--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Darksong wrote:

>Hi -
>Port 8080 is the port being used by the webserver and the router port
>forwards to the machine's internal IP address at that port.
>
>I'm not sure if loopback is a capability of the router. I don't see
>anything that mentions it unless Netgear calls it something else.
>(Netgear WGR614v6). Do you think that's an issue?
>
>
>
>On Jun 24, 4:39 am, "Kristofer Gafvert"
>wrote:
>>How is everything set up? Is IIS running on port 8080, or do you have port
>>forwarding from 8080 to 80, and IIS is running on port 80?
>>
>>Does your router (if any) have loop back capabilities?
>>
>>--
>>Regards,
>>Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>>
>>
>>
>>Darksong wrote:
>>>Folks can see my webserver on port 8080 from the internet. I cannot
>>>see it myself. Is that weird or am I missing something? Thx in
>>>advance for any advice!- Hide quoted text -
>>
>>- Show quoted text -

Re: Can"t see my own port 8080

This may be unrelated but I thought it would be worth mentioning:

Over the course of the last week folks (including myself) started
noticing that we were not able to hit my site from an external source
(in addition to the originally posted issue of not being able to
connect to the external address from inside the network).

I'm in Northern Virginia with Cox as the ISP. Possibly port 8080 is
now being blocked as well as 80? I changed the port number and all is
well again.


On Jun 26, 1:22 am, "Kristofer Gafvert"
wrote:
> If you can usehttp://localhost:8080/to access the website from the
> server itself, but you cannot use an external name or IP address from
> within your internal network, then i do think it is a networking problem
> and likely the router does not support loop back.
>
> --
> Regards,
> Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>
>
>
> Darksong wrote:
> >Hi -
> >Port 8080 is the port being used by the webserver and the router port
> >forwards to the machine's internal IP address at that port.
>
> >I'm not sure if loopback is a capability of the router. I don't see
> >anything that mentions it unless Netgear calls it something else.
> >(Netgear WGR614v6). Do you think that's an issue?
>
> >On Jun 24, 4:39 am, "Kristofer Gafvert"
> >wrote:
> >>How is everything set up? Is IIS running on port 8080, or do you have port
> >>forwarding from 8080 to 80, and IIS is running on port 80?
>
> >>Does your router (if any) have loop back capabilities?
>
> >>--
> >>Regards,
> >>Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> >>Darksong wrote:
> >>>Folks can see my webserver on port 8080 from the internet. I cannot
> >>>see it myself. Is that weird or am I missing something? Thx in
> >>>advance for any advice!- Hide quoted text -
>
> >>- Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Re: Can"t see my own port 8080

That is possible, but it should not affect how it works internally (well,
that depends on how the network is set up). So it could be.


--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


Darksong wrote:

>This may be unrelated but I thought it would be worth mentioning:
>
>Over the course of the last week folks (including myself) started
>noticing that we were not able to hit my site from an external source
>(in addition to the originally posted issue of not being able to
>connect to the external address from inside the network).
>
>I'm in Northern Virginia with Cox as the ISP. Possibly port 8080 is
>now being blocked as well as 80? I changed the port number and all is
>well again.
>
>
>On Jun 26, 1:22 am, "Kristofer Gafvert"
>wrote:
>>If you can usehttp://localhost:8080/to access the website from the
>>server itself, but you cannot use an external name or IP address from
>>within your internal network, then i do think it is a networking problem
>>and likely the router does not support loop back.
>>
>>--
>>Regards,
>>Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>>
>>
>>
>>Darksong wrote:
>>>Hi -
>>>Port 8080 is the port being used by the webserver and the router port
>>>forwards to the machine's internal IP address at that port.
>>
>>>I'm not sure if loopback is a capability of the router. I don't see
>>>anything that mentions it unless Netgear calls it something else.
>>>(Netgear WGR614v6). Do you think that's an issue?
>>
>>>On Jun 24, 4:39 am, "Kristofer Gafvert"
>>>wrote:
>>>>How is everything set up? Is IIS running on port 8080, or do you have
>>>>port
>>>>forwarding from 8080 to 80, and IIS is running on port 80?
>>
>>>>Does your router (if any) have loop back capabilities?
>>
>>>>--
>>>>Regards,
>>>>Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>>
>>>>Darksong wrote:
>>>>>Folks can see my webserver on port 8080 from the internet. I cannot
>>>>>see it myself. Is that weird or am I missing something? Thx in
>>>>>advance for any advice!- Hide quoted text -
>>
>>>>- Show quoted text -- Hide quoted text -
>>
>>- Show quoted text -

Re: Can"t see my own port 8080

SOLUTION
Just to get some closure on this thread in case anyone else has this
problem, the solution for the original post was as simple as upgrading
the firmware for the router.


On Jun 27, 11:52 am, "Kristofer Gafvert"
wrote:
> That is possible, but it should not affect how it works internally (well,
> that depends on how the network is set up). So it could be.
>
> --
> Regards,
> Kristofer Gafverthttp://www.gafvert.info/iis/- IIS Related Info
>
>
>
> Darksong wrote:
> >This may be unrelated but I thought it would be worth mentioning:
>
> >Over the course of the last week folks (including myself) started
> >noticing that we were not able to hit my site from an external source
> >(in addition to the originally posted issue of not being able to
> >connect to the external address from inside the network).
>
> >I'm in Northern Virginia with Cox as the ISP. Possibly port 8080 is
> >now being blocked as well as 80? I changed the port number and all is
> >well again.
>
> >On Jun 26, 1:22 am, "Kristofer Gafvert"
> >wrote:
> >>If you can usehttp://localhost:8080/toaccess the website from the
> >>server itself, but you cannot use an external name or IP address from
> >>within your internal network, then i do think it is a networking problem
> >>and likely the router does not support loop back.
>
> >>--
> >>Regards,
> >>Kristofer Gafverthttp://www.gafvert.info/iis/-IIS Related Info
>
> >>Darksong wrote:
> >>>Hi -
> >>>Port 8080 is the port being used by the webserver and the router port
> >>>forwards to the machine's internal IP address at that port.
>
> >>>I'm not sure if loopback is a capability of the router. I don't see
> >>>anything that mentions it unless Netgear calls it something else.
> >>>(Netgear WGR614v6). Do you think that's an issue?
>
> >>>On Jun 24, 4:39 am, "Kristofer Gafvert"
> >>>wrote:
> >>>>How is everything set up? Is IIS running on port 8080, or do you have
> >>>>port
> >>>>forwarding from 8080 to 80, and IIS is running on port 80?
>
> >>>>Does your router (if any) have loop back capabilities?
>
> >>>>--
> >>>>Regards,
> >>>>Kristofer Gafverthttp://www.gafvert.info/iis/-IISRelated Info
>
> >>>>Darksong wrote:
> >>>>>Folks can see my webserver on port 8080 from the internet. I cannot
> >>>>>see it myself. Is that weird or am I missing something? Thx in
> >>>>>advance for any advice!- Hide quoted text -
>
> >>>>- Show quoted text -- Hide quoted text -
>
> >>- Show quoted text -- Hide quoted text -
>
> - Show quoted text -