External IP works, internet IP doesnt

Hi, im running apache webserver and, when i type in the IP i dont get the webpage, but when someone external to my network does, the webpage comes up

Im behind a alcatel router, with port forwarding. I believe it may be the hosts file i need to edit, in XP, i added a line

<IP ADDRESS> Hostname

still wont work

why can everyone else view my webpage but me on the internal network.

Thanks.

use your internal IP address when adding to the hosts file.

my hosts has this line

10.0.0.1 heaven

how do i read the hosts file

i tried nbtstat -R

is that right, when does win xp read the hosts. i did restart once.

nbtstat has nothing to do with the hosts file.

Does this link work:
http://10.0.0.1

when i try and type the static IP nothing views..

remember i have port forwarding on for port 80 on the alcatel 4 port router.

everyone else can view my website by typing static ip

i want to type in

http://static ip and view it, it times out

everyone ELSE can view it

thanks

With some routers you will never be able to enter the external IP and view the website from within the network. You must use the internal IP. So you must do one of 2 things. You must use the internal IP to point to your website domain in your hosts file like so:

10.0.0.1 www.mysite.com

Or setup BIND using "views" so that it returns the external IP when resolving external requests, and returns the internal IP when resolving internal requests.

ill try adding that line 10.0.0.1 <IP address)

i must use ip address, as i dont yet own a domain name onthe outside

when does the host file get read? i edited it just then?

do i need to restart or can i do it without that, and also BIND

im looking up how i can use bind now

its really annoying not being able to view my webpage like everyone else...

thanks

XP reloads the hosts file when it detects that it has changed. It doesn't take long for it to take effect. I've also tried adding a line to the hosts file something like this:

192.168.1.1 router

So that I can access my router via the name rather than IP, but for some reason that didn't work. Perhaps I mistook something, dunno. But for sure whenever I use a proper domain (with a period and extension) it works fine.

So just make up a domain and use it to access your site.

Ok that worked

www.domainname.com worked pointing to IP 10.0.0.1

and

10.0.0.138 router

WORKED

now i type in router and it connects


as for allowing the ip to work, i cant get that working yet, ive played around with the hosts file a bit

thanks for your help you got something right!!

I don't have BIND views implemented yet, so I had to set up DNS on my workstation with the private IPs in the zone file for the domain rather than the public IPs. It's a real PITA to do it that way, especially if you have multiple domains hosted and have to make changes occasionally, but it works.

I am going to implement "views" since it is so much easier and probably more secure than having DNS running all over the place.

you can not go out a NAT firewall and come back in!

It depends on the router's routing table. On my linksys router for instance I can connect to my public IP. It's just a matter of me sending a packet to the router's public interface, and the router routing the packet back to my computer on the private interface.

*cough* if its not in your routers routing table to get back to your PC or the server thats on the same network you got bigger problems. let me refraze though this is a firewall not a routing issue that will keep this from working PIX, Bordermanager, sonicwall, ISA, etc it will not work.

I'm not quite sure what you're saying. All I know is that you said "you can not go out a NAT firewall and come back in!". By this statement I'm guessing you are saying that you CANNOT connect to your router's public IP and expect to connect to a server on the private network.

And yet, on my linksys router this is what happens.

123.45.67.89 = internet client
192.168.1.100 = network client
192.168.1.2 = network web server
192.168.1.1 = router private IP
68.51.39.58 = router public IP

1) 123.45.67.89 connects to 68.51.39.58 port 80
2) router forwards request to 192.168.1.2 port 80

1) 192.168.1.100 connects to 68.51.39.58 port 80
2) router forwards request to 192.168.1.2 port 80

1) 192.168.1.100 connects to 192.168.1.1 port 80
2) router accepts the request and asks for a password