[driven]

I've upgraded my router from a MacSense (three years old) to a Netgear wireless MR814.

Queston:
I can set up "Port Forwarding" to allow incoming traffic to get to my web-server. If I am *outside* my LAN it works great!

BUT: Inside my LAN if I attempt to access my web-server I find that it's blocked. (But if I type in the internal address it works.)

From what I'm reading this appears to be normal. Is there a way around this so that I can use the same URL to access from inside and outside my LAN?

Thanks in advance.

[Landos Mustache]

I am also having a hell of a time trying to figure out how to use the Port Forwarding to open the quicktime ports.

[Camelot]

Originally posted by driven:
Queston:
I can set up "Port Forwarding" to allow incoming traffic to get to my web-server. If I am *outside* my LAN it works great!

BUT: Inside my LAN if I attempt to access my web-server I find that it's blocked. (But if I type in the internal address it works.)

From what I'm reading this appears to be normal. Is there a way around this so that I can use the same URL to access from inside and outside my LAN?

NAT bounce-back like this is a common problem.

About the only way I can think of fixing this is to add a static entry in your hosts table (using NetInfo Manager).

Add an entry for the FQDN of your site that points to the internal address on your network. That way when you try to access http://www.yoursite.com/ you'll get the internal server.

This won't work, of course if you don't have a hostname for the site and are only accessing it via IP address. The only thing that *might* work there is IP Aliasing where you use your external network addresses on the inside, too, but this can confuse your router, so should be used with caution.

[driven]

Originally posted by Camelot:


NAT bounce-back like this is a common problem.

About the only way I can think of fixing this is to add a static entry in your hosts table (using NetInfo Manager).

Add an entry for the FQDN of your site that points to the internal address on your network. That way when you try to access http://www.yoursite.com/ you'll get the internal server.

This won't work, of course if you don't have a hostname for the site and are only accessing it via IP address. The only thing that *might* work there is IP Aliasing where you use your external network addresses on the inside, too, but this can confuse your router, so should be used with caution.

Thanks. This might work. At least I know that it isn't something unique to me. DOH!

The only real problem is with my laptop where I'll have to maintain two separate sets of bookmarks.
1) For when I'm on the LAN and
2) For when I'm away from the LAN.

(Side note: I do have a hostname for this URL.)

Thanks again.

Any other advise is welcome as well.

[Landos Mustache]

Post your problem here, you will get a better response:

http://www.broadbandreports.com/forum/equip,9

[ghporter]

Originally posted by Landos Mustache:
Post your problem here, you will get a better response:

http://www.broadbandreports.com/forum/equip,9

Please note that the reason you will get a "better" response is that the forum this link goes to is specific to Netgear equipment, not because we don't like helping you!

Also note that Broadband Reports has forums on a lot of different kinds of networking equipment-it's worth the time to check it out.

P.S. Don't be put off by the "PC centric" nature of the forums-they can't help it, and you'll still get plenty of great help there.