Can't View Website from within LAN

If you can access the page on the server itself by going to localhost, then you should be able to get to it by typing http:\\\\:80 from any other computer on the same network segment (ie, in the same subnet).

Second, I would make sure that whatever port forwarding you setup on the router is still there. Do you have internal vs external IP addressing? (192.168.x.x internal?)

Lastly, do you have a domain name that is pointed correctly?

Thanks for your answer.

Yes, I can actually access the website from within the network using

Yes, the router is set up to use NAT. "ip nat translation" shows me among others this entry, which to me, looks correct:

Pro Inside global Inside Local Outside local Outside global tcp 213.xxx.xxx.xxx:80 192.168.xxx.xxx:80 --- ---

Yes, the domain name points to the right address. As I said, I can access the website from any one machine outside the network using the domain name. It's only on machines hooked up to this network where this doesn't work.

Thanks aga> > > Hi,

canaccessthewebsitefrom any one machine outside the network using the

canaccessthewebsitefrom any one machine outside the network using the

Sounds to me like your router is not allowing traffic out and back in. Are you using an internal DNS server or one from the ISP? If internal, I'd consider putting in a static entry for the web-server to the internal IP address. If externally, something in your router config is preventing traffic from going out and coming back in. You may want to paste your config (just relevant parts of config obviously, and may want to mask IPs)

Do you have a NAT for the entire IP protocol or have just translated the TCP port 80?

Alex.

Is it the alias problem?

OK, below is the part of the config file that, I hope, is relevant. No, there is no internal DNS server, I'm using my ISP's. And yes, I have NAT for the entire protocol (as far as I know). Lastly, I don't know what the alias problem is. Can you please explain?

Thanks for your help,

Stefan

---------------------------------------

ip http server ip http authentication local ip http secure-server ip http timeout-policy idle 5 life 86400 requests 10000 ip nat inside source list 1 interface FastEthernet4 overload ip nat inside source static tcp 192.168.1.123 21 interface FastEthernet4 21 ip nat inside source static tcp 192.168.1.123 50000 interface FastEthernet4 50000 ip nat inside source static tcp 192.168.1.123 80 interface FastEthernet4 80 ip nat inside source static tcp 192.168.1.123 1433 interface FastEthernet4 1433 ip nat inside source static tcp 192.168.1.123 443 interface FastEthernet4 443 ip nat inside source static tcp 192.168.1.123 3389 interface FastEthernet4 3389 ! ip access-list extended Inside_Out permit ip any any ip access-list extended Outside_In permit tcp any host 213.XXX.XXX.XXX eq 22 permit tcp any host 213.XXX.XXX.XXX eq telnet permit tcp host 216.204.141.92 host 213.XXX.XXX.XXX eq 3389 permit tcp host 216.204.141.91 host 213.XXX.XXX.XXX eq 3389 permit tcp host 64.102.253.96 host 213.XXX.XXX.XXX eq 3389 permit tcp host 216.204.141.90 host 213.XXX.XXX.XXX eq 3389 permit tcp any host 213.XXX.XXX.XXX eq 3389 permit esp any any permit ahp any any permit udp any any eq non500-isakmp permit udp any any eq isakmp permit tcp any host 213.XXX.XXX.XXX eq 443 permit tcp host 216.204.141.90 host 213.XXX.XXX.XXX eq 1433 permit tcp host 216.204.141.91 host 213.XXX.XXX.XXX eq 1433 permit tcp host 216.204.141.92 host 213.XXX.XXX.XXX eq 1433 permit tcp host 64.102.253.96 host 213.XXX.XXX.XXX eq 1433 permit tcp any host 213.XXX.XXX.XXX eq www permit tcp any host 213.XXX.XXX.XXX eq ftp permit tcp any host 213.XXX.XXX.XXX eq 50000

Nothing to do with DNS here

You need to add an alias in your box which match the website's REAL address to your lan address. I will do that to my box:

"alias (inside) LAN_ADDRESS WEB_REAL_IP_ADDRESS"

So that "smart" box will not try to route package to the device with the same security level.

You need to read your router manual on how to add alias.

Basically you can not send a request out the same interface you are to receive the request on. I would try the alias command, what this does is rewrites the internal IP for request to that external IP.

So if you had this scenario:

Web: 192.168.0.2 Client: 192.168.0.3 Router Inside: 192.168.0.1 Router Outside: 2.2.2.2

When the client requests you website from the LAN it can not be directed to 2.2.2.2 instead it must use the internal IP of 192.168.0.2, the alias command will rewrite that for you so when the clients request hits the router it rewrites the destination IP as 192.168.0.2.

HTH