Cannot see internal website fron own network

[SerialCoder]

I had to replace my DSL router with a new on and am having iussues.

I got set up, turned on the NAT, and pointed the web traffic to my server. From the outside, it works just fine.

When I punch in the URL of the Site from within my building I get nothing. When I type in the external IP of that server from the outside world, it works but not in the building.

It is a netopia Cayman router. I dont really want to set up a HOSTS file on 45 workstations. %-(

Thanks for any help,
SerialCoder

 

[bcastner]

Is the server behind the NAT but on a different subnet? You need to add a static route to it in the router.

 

[SerialCoder]

Thanks for the response.

To be clear, I'll fabricate the scenerio:

The Router Ext=200.200.200.200 (Int=10.0.0.1)
Is Translating all requests for200.200.200.199 over to a NT4 box (10.0.0.2) That is working jsut fine from anywhere outside of our LAN. Try to request the server directly using the outside IP

http://200.200.200.199

You get nothing. If you try to open the domain name

http://www.mysite.com

(which is transleted through dns to 200.200.200.199) it fails as well. But this is only from the internal network.

Otherwise it all works fine?

Thanks
SerialCoder

 

[manarth]

some routers do not support backward routing.

if you want to connect to an internal address, you connect using the internal address, you cannot always exploit the port forwarding feature from inside your LAN - only from externally.

if it worked with the old router, i'd go back to that.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[SerialCoder]

I think you are right about the backwards routing. The DSL tech who installed it mentioned that I would not be able to call the router's web GUI with the external IP from within the LAN.

I cannot go back to the other router, it's dead.

So if that Is the case, I have the option of using the HOSTS file. Is there a slick way to have one HOSTS file on the network instead of having to update them on 40+ machines?

Regards,
SerialCoder

 

[manarth]

opt a: have 1 hosts. file on the server, then use a logon script to copy it to the windows dir when someone logs in

opt b: run your own DNS server


To be honest, I'd go for opt a, implement it for a week or so (long enough to be sure every machine had been logged onto at least once, so the new hosts. had propogated to every machine) then remove the logon script.

Either that or, as it's only 40 PCs, simply copy to floppy then copy back to each machine one at a time.

Whatever will be simpler/easier for you.

<marc> i wonder what will happen if i press this...[ul][li]please give feedback on what works / what doesn't[/li][li]need some help? how to get a better answer: faq581-3339[/li][/ul]

 

[SerialCoder]

I thinks I'll give that a shot. (using the login script) Thanks for the input.

SerialCoder