Keith,
this is a pretty standard thing (I have seen it on many networks - normally
the Webserver is in a DMZ so it resolves/is resolveable from both internal
and external networks and maybe a different DNS is used outside with another
one inside (that forwards on if the address is not resolvable)).
Why not just use a host file on your internal machines that will resolve to
the internal address? Its got to be cheaper and easier than trying to find a
solution to a problem that you are likely to encounter again and again?
Sid.
"Keith Elkin" <(E-Mail Removed)> wrote in message
news:d223b4557710f21158d8ade5951f20d0@TeraNews...
> I have had major connectivity problems (frequent signal loss, router
> hanging, etc..) with the Linksys BEFR11SW, trying V1, V2, and V3. Their
V4
> unit fixed those issues, but introduced a major problem of TCP/IP
> connections dropping within minutes... I gave up and purchased a NetGear
> 814. Now here's the problem...
>
> I have keithelkin.com pointing to 24.189.196.100:81. From outside of the
> private network, I can either use the domain name, or the IP address, and
> access the website. From inside the network, I am unable to access the
> website using the public IP or domain name, I am only able to access it
> using the private 192.168.0.x IP. Netgear says this is intended, although
> for the life of me I can't understand why. Linksys resolved external IP's
> and routed properly from within the private network. So now I'm going to
> return the Netgear and purchase a different wireless access point/router.
> Can anyone reccomend a brand that isn't prone to problems like the
Linksys,
> and will resolve and route internal traffic from within the private
network
> properly when using the public IP address?
>
> Thanks,
> -Keith
>
>
|