I have a strange problem I was hoping someone could point me in
the right direction. I have apache 1.3 installed on xp, and a
xxx.dyndns.com account which autoupdates from a desktop app.
Everything works fine, I and my friend from another state can both
reach my server from xxx.dyndns.com.

Problem is when I connect my netgear router.

My firewall get's it's ip-address dynamiclly from ISP and has an
internal function to sync with dyndns, that works.

My computer has an internal static IP address, I have the router
forwarding wan port 80 to this internal address.

When I connect it all the computer can surf the web, my dyndns hooks up
though the firewall, and my friend can see my site(not cached) just
fine.

But I can't. I can not reach my own page, If I go to anonomizer.com and
type in my address it pulls it up fine. I can ping it, and trace route
it. I can reach it via loopback, but I can not reach it from
xxx.dyndns.com??? It's the strangest thing, I know it's up becuse other
people can see it, but not from the machine itself???

I have the apache conf file Listen 80, no hardcoded ip, no directory
deny's.

How and why would I be seemingly firewalled from my own site?

gehale@gmail.com said:

> I have a strange problem I was hoping someone could point me in
> the right direction. I have apache 1.3 installed on xp, and a
> xxx.dyndns.com account which autoupdates from a desktop app.
> Everything works fine, I and my friend from another state can both
> reach my server from xxx.dyndns.com.
>
> Problem is when I connect my netgear router.
>
> My firewall get's it's ip-address dynamiclly from ISP and has an
> internal function to sync with dyndns, that works.
>
> My computer has an internal static IP address, I have the router
> forwarding wan port 80 to this internal address.
>
> When I connect it all the computer can surf the web, my dyndns hooks up
> though the firewall, and my friend can see my site(not cached) just
> fine.
>
> But I can't. I can not reach my own page, If I go to anonomizer.com and
> type in my address it pulls it up fine. I can ping it, and trace route
> it. I can reach it via loopback, but I can not reach it from
> xxx.dyndns.com??? It's the strangest thing, I know it's up becuse other
> people can see it, but not from the machine itself???
>
> I have the apache conf file Listen 80, no hardcoded ip, no directory
> deny's.
>
> How and why would I be seemingly firewalled from my own site?

What error page do you get? Can you ping the addy? Does the netgear have
logs that will ?

--
Eggs

-Give a man a fish and you feed him for a day. Teach him to use the Net and
he won't bother you for weeks

I can ping and traceroute the domain name from the server. And my
friends can access the domain name from the outside. I can access
apache from localhost or loopback with no problem.

The problem is for some reason the router get's confused when it try to
address itself via port 80. (port 80 is not blocked, or outside people
would not get to my page)

When I ping the domain or external IP from the inside, or tracert it
takes 1ms and 1 hop, it notices that i'm pinging itself and there is no
need to go further.

But when I try to open the page in IE, via domain name or external IP
(with or without port info :80 or :8080) I get nothing...

On 16 Aug 2005 17:34:29 -0700, gehale@gmail.com wrote:

>I can ping and traceroute the domain name from the server. And my
>friends can access the domain name from the outside. I can access
>apache from localhost or loopback with no problem.
>
>The problem is for some reason the router get's confused when it try to
>address itself via port 80. (port 80 is not blocked, or outside people
>would not get to my page)
>
>When I ping the domain or external IP from the inside, or tracert it
>takes 1ms and 1 hop, it notices that i'm pinging itself and there is no
>need to go further.
>
>But when I try to open the page in IE, via domain name or external IP
>(with or without port info :80 or :8080) I get nothing...

Your router apparently doesn't know about NAT loopback.

-configure it (if possible)

or

-define your dyndns name behind 127.0.0.1 or behind your local
IP address in your host file so your dns client will resolve it
as a local address

or

-configure a http proxy _outside_ your network in your browser.

I posted more detailed info on this subject in this very group
in the recent past (January - June 2005).
--
) Kees Nuyt
(
c[_]