the world can see my WS, but inside my LAN, I can't with 2614 router

[bob smith_6]

I was running a gateway machine (2 nics) with cable modem with REAL IP on one side, and hub connected to the otherside, a 10.0.0.x LAN. Also, I have a web server at 10.0.0.2 serving up pages via NAT and the real IP as (let's say) www.xyz.com at port 80. I've replaced the gateway machine with a router, configured the router to NAT port 80 traffic to the webserver and all is well. HOWEVER... from INSIDE the lan, when I browse to http://www.xyz.com it can't find it! I can, of course, surf to http://10.0.0.2 directly where the ws is running. All other surfing works (yahoo.com etc).

The gateway was running win95 sygate, and the router is a speed stream 2614 (http://www.speedstream.com/datasheet_2614.html). I explained this to their tech support but I don't think the rep. really understood the problem.

Any ideas? (just to be clear, the world can hit my 'www.xyz.com' page, but inside the router, I can't. But all other DNS lookups work. Also, other services behave the same way... outside, I can FTP to www.xyz.com, but inside, I can't unless I use 10.0.0.2)

thanks!
Bob

[Karl McMurdo]

What do you get as an address if you try pinging www.xyz.com from inside the nat, I've seen one router dns implimentation that wouldn't pass results pointing to itself back to the client properly, but passed back the local address, 10.0.0.1 which may have been technically accurate, but it wouldn't accept redirects from internal addresses (ie: 10.0.0.5 tries to get to 10.0.0.1:80 which in fact points to 10.0.0.2:80) we bypassed the problem by adding the outside address to the local hosts files. (Not ideal but it worked, couldn't add the local address as different services went to different internal servers)

If you use the IP address instead of the host name ie: if www.xyz.com resolves to 123.aaa.bbb.ccc does http://123.aaa.bbb.ccc/ work where http://www.xyz.com/ didn't, if so the above solution would work in the interim.

[Karl McMurdo]

One other minor point, one client had all kinds of weird issues with their router till in frustration I experimented with valid private addresses rather than .0.0. addresses (they were using 90.0.0.* and it seemd to freak out the router, once we set them to 192.168.90.* things started working)

Just something to try.

[bob smith_6]

Thanks so much for your reply... here's some more info:

Inside the NAT/LAN, ping www.xyz.com actually works, and the IP address is resolved to 123.aaa.bbb.ccc (well, my REAL one : )

bash-2.04$ ping xyz.com
PING xyz.com (123.aaa.bbb.ccc) from 10.0.0.2 : 56(84) bytes of data.
64 bytes from dhcp123-aaa-bbb-ccc.myservice.com (123.aaa.bbb.ccc): icmp_seq=0 ttl=64 time=1.181 msec

bash-2.04$ ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) from 10.0.0.2 : 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=64 usec

Notice the big difference in ping time too, so I think the first one must be going out to the WAN side? Actually, I just pinged 10.0.0.1 and it has the same time as pinging xyz.com. (traceroute works too, but it's only one step : )

Also, when I surf to http://123.aaa.bbb.ccc from any machine on the nat (linux and windows) it also does not find the webserver. I should have mentioned this before.

As far as trying 192.x.y.z (which was the default), I never have. I changed the defaults to 10.0.0.x right away. I will try this as soon as I get home from work today : )

Anymore ideas?
Thanks again,
Bob

[bob smith_6]

I reset the router back to the factory setting... 192.168.254.*. I reconfigured the network and it still doesn't not allow me to surf to my own web site :o(

Any other ideas??
Kevin

[Jane Doe_1 · Accepted solution]

It's the way the router is made.To fix the issue you could setup a pc outside the network.(bypass the router,connect all pcs but one to the router to a hub to the modem then add the other pc to the hub going to the modem that will allow you to see internaly,because actually you'll be outside the network.You will have to purchase another IP address from you ISP though.

[Jane Doe_1]

It is the way the router is made.you cannot see your network internally.You can setup a pc outside the network in the same area to fix the issue.to do this connect all pcs except one to the router then with a straight cable connect the router to the hub and then the modem into the uplink on the hub.the last pc should be added to the hub(bypassing the router) going into the modem.this pc will be outside the network and you will have what you want.But you will have to purchace another IP address from your ISP.

[D. Jackson_1]

What do your /etc/nsswitch.conf files look like.
Do they have DNS listed first?
It sounds like one box is hitting the DNS first and the other is hitting the FILES.

HTH

[Dean_17]

This is an old post and not sure if you still need help or not, but you could be encountering a few different things from the sound of it. Behing that you have moved the www server inside, you need to verify a few things. Being that many of the more "inexpensive routers" are configured via web as it appears that your router is, even though you have port forwarding enabled the router will still respond to request from any inside IP address. Fastest way to circumvent this would be to add entries in your HOST file on your client machine. FTP has no problems because your router does not have anything listening for FTP requests.

Hope this helps out.
- dak -