Problem accessing website from inside network

I have Belkin 802.11b Wireless Cable/DSL Gateway Router (F5D6231-4) and
I am hosting some websites on my server in the network (FC4 & Apache).
I don't have any problem accessing those websites outside the network,
but when I try to access the same websites inside the network, instead
of the website, I always see the router setup page??!! Has anyone else
face the same problem and/or have solution?

Thanks,
Sachin

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
>I have Belkin 802.11b Wireless Cable/DSL Gateway Router (F5D6231-4) and
> I am hosting some websites on my server in the network (FC4 & Apache).
> I don't have any problem accessing those websites outside the network,
> but when I try to access the same websites inside the network, instead
> of the website, I always see the router setup page??!! Has anyone else
> face the same problem and/or have solution?
>
What are you talking about?

Have you done a hard reset of the router?

Duane

(E-Mail Removed) hath wroth:

>I have Belkin 802.11b Wireless Cable/DSL Gateway Router (F5D6231-4) and
>I am hosting some websites on my server in the network (FC4 & Apache).
>I don't have any problem accessing those websites outside the network,
>but when I try to access the same websites inside the network, instead
>of the website, I always see the router setup page??!! Has anyone else
>face the same problem and/or have solution?

It's rather difficult to decode what you mean by "inside the network".
Also, I can't tell what you mean by "those" websites. Are they YOUR
web servers, or just the usual web servers on the internet?

What exact URL are you feeding the web browser that gives you the
setup page? If it's 192.168.2.1, that's the router. Anything else
will be one of your machines.

Do you have static IP's (192.168.2.xxx) configured for your servers?
Are your Apache servers running on port 80?

Just in case you have inside and outside backwards, if your F5D6231-4
supports remote admin, either move it to a port other than 80, or just
turn off remote admin.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Thanks for your responses.

Let me give you some more details, which might avoid the confusion.
When I said "inside the network" I meant another computer connected to
that Belkin router. So say, one port of router is occupied by my web
server (192.168.2.xx) and I connect my laptop to the wireless network
of the same router (192.168.2.yy), and then I try to connect to my
website from laptop e.g. http://myname.com (which is hosted on the web
server on port 80, and that URL will resolve to Belkin router's WAN
IP), instead of my website, i get the router setup screen. But if I
connect to http://myname.com "ourside the network" (i.e. from the
computer which is not a part of that router network, e.g. my work
machine), it correctly shows the website.

My Remote Management option is disabled, so that's not the issue I
think.

Sachin

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Thanks for your responses.
>
> Let me give you some more details, which might avoid the confusion.
> When I said "inside the network" I meant another computer connected to
> that Belkin router. So say, one port of router is occupied by my web
> server (192.168.2.xx) and I connect my laptop to the wireless network
> of the same router (192.168.2.yy), and then I try to connect to my
> website from laptop e.g. http://myname.com (which is hosted on the web
> server on port 80, and that URL will resolve to Belkin router's WAN
> IP), instead of my website, i get the router setup screen. But if I
> connect to http://myname.com "ourside the network" (i.e. from the
> computer which is not a part of that router network, e.g. my work
> machine), it correctly shows the website.
>
> My Remote Management option is disabled, so that's not the issue I
> think.

Well, you cannot access the Web server from within the LAN/Intranet using
http://myname.com. To access the Web server on the LAN/Intranet from another
machine on the LAN, you would enter http://192.168.2.xx in the browser
address line.

Yes, and you're correct that using Http://myname.com will resolve to the
public WAN/Internet IP issued by the ISP, which allows contact with the Web
server over the Internet, because //myname.com is being equated to the WAN
IP due to the O/S using the URL and looks up the IP to use via the ISP's DNS
servers.

If you want to access the Web server that's running on the local machine,
you would enter http://127.0.0.1 or Http://localhost in the browser address
line, which works that way with IIS and the MS platform.

Duane

(E-Mail Removed) hath wroth:

>Let me give you some more details, which might avoid the confusion.
>When I said "inside the network" I meant another computer connected to
>that Belkin router. So say, one port of router is occupied by my web
>server (192.168.2.xx) and I connect my laptop to the wireless network
>of the same router (192.168.2.yy), and then I try to connect to my
>website from laptop e.g. http://myname.com (which is hosted on the web
>server on port 80, and that URL will resolve to Belkin router's WAN
>IP), instead of my website, i get the router setup screen. But if I
>connect to http://myname.com "ourside the network" (i.e. from the
>computer which is not a part of that router network, e.g. my work
>machine), it correctly shows the website.

Are your client machines Windoze, Linux, or MacIntosh? If a DNS
lookup ends up pointing to the wrong machine, it's just as likely to
be the client as the router. However, I can't tell what it's pointing
to when run from the LAN side. Try running:
ping myname.com
and see what IP address gets resolved. It should be the WAN IP
address of your router which is currently 71.128.193.129. If DNS is
doing it's job, that should work correctly.

However, there's some question as to how your Belkin router handles
connections to your own IP address, from the LAN side, to the WAN IP
address. My guess(tm) is that it will end up doing exactly what you
described previously and end up pointing to the LAN side, which on
port 80 is the internal web page configuration. I'll try it on my
BEFW11S4 and see what happens. Back in a few....

>My Remote Management option is disabled, so that's not the issue I
>think.

No, that's not it. Bad guess on my part.
--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Jeff Liebermann <(E-Mail Removed)> hath wroth:

>However, there's some question as to how your Belkin router handles
>connections to your own IP address, from the LAN side, to the WAN IP
>address. My guess(tm) is that it will end up doing exactly what you
>described previously and end up pointing to the LAN side, which on
>port 80 is the internal web page configuration. I'll try it on my
>BEFW11S4 and see what happens. Back in a few....

Bingo. Mine does the same thing. I redirected port 80 to point to my
workstation IP. That did some really weird things, so I redirected
port 80 to another machine. I'm on home.learnbydestroying.com which
points to my static IP address. When I point my browser to:
http://home.learnbydestroying.com
I get the setup menu login for my BEFW11S4v4 router. That's exactly
what you're getting so I guess(tm) that it's normal or at least
typical. Sorry, I guess you'll have to use the local LAN IP's when
testing your servers from the LAN side of your router.

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

On 15 Apr 2006 22:17:39 -0700, in alt.internet.wireless ,
(E-Mail Removed) wrote:

>Thanks for your responses.
>
>Let me give you some more details, which might avoid the confusion.
>When I said "inside the network" I meant another computer connected to
>that Belkin router. So say, one port of router is occupied by my web
>server (192.168.2.xx) and I connect my laptop to the wireless network
>of the same router (192.168.2.yy), and then I try to connect to my
>website from laptop e.g. http://myname.com

This is your mistake.

Internally, your website is not known by your external URL, so
myname.com will be the incorrect name. Try the IP address directly eg

http://192.168.2.xx

And presumably your PCs have hostnames internal to your network eg
Server1, mypc etc. You can also use that. http://server1

For comparison, I have Apache on one of my PCs, and internally its
known as "http://thepc" whereas externally it is known as
"http://www.myname.dnsalias.net"



Mark McIntyre
--

On Sat, 15 Apr 2006 23:06:33 -0700, in alt.internet.wireless , Jeff
Liebermann <(E-Mail Removed)> wrote:

>(E-Mail Removed) hath wroth:
>
>>Let me give you some more details, which might avoid the confusion.
>>When I said "inside the network" I meant another computer connected to
>>that Belkin router. So say, one port of router is occupied by my web
>>server (192.168.2.xx) and I connect my laptop to the wireless network
>>of the same router (192.168.2.yy), and then I try to connect to my
>>website from laptop e.g. http://myname.com (which is hosted on the web
>>server on port 80, and that URL will resolve to Belkin router's WAN
>>IP), instead of my website, i get the router setup screen. But if I
>>connect to http://myname.com "ourside the network" (i.e. from the
>>computer which is not a part of that router network, e.g. my work
>>machine), it correctly shows the website.
>
>Are your client machines Windoze, Linux, or MacIntosh? If a DNS
>lookup ends up pointing to the wrong machine, it's just as likely to
>be the client as the router.


Jeff, its nothing to do with this - Duane's post answers the problem.
The OP is simply misunderstanding the relationship between internal
and external web addresses. Inside his net, he should use the local
machines' netbios names. Outside, he should use his assigned DNS
entry, which the router will forward to the relevant machine.
Mark McIntyre
--

Mark McIntyre <(E-Mail Removed)> wrote:
>The OP is simply misunderstanding the relationship between internal
>and external web addresses.

Jeff's second answer is the right one, most routers won't allow NAT
machines to loop around and come back into their WAN ports on outbound
connections. Just the way it is... [For instance, Adtran told me to
make sure I put DNS entries in the Netvanta 2054 router's DNS server
to solve the problem, but I just used up another static IP instead.]