«

Maybe it has something to do with the NATing happening on those
devices. Does it maybe see the return from web server has a new
connection? See if they can allow established or something on those
boxes. This is a shot in the dark...

Aaron

"Kevin Modlin" <> wrote in message news:<awieb.37924$ thlink.net>...
> Disclaimer: I am a newbie (big time).
>
> I have a Cisco 1700 configured to allow external access to an internal
> webserver using a command like:
>
> ip nat inside source static tcp 192.168.1.5 80 68.x.x.x 80 extendable
>
> This works like a champ as long as the person trying to access the site is
> inside a Cisco router. Anyone behind a Linksys, DLink, or any other brand
> gets a page cannot be displayed error. Where should I start to look?

Aaron Woody wrote:

> Maybe it has something to do with the NATing happening on those
> devices. Does it maybe see the return from web server has a new
> connection? See if they can allow established or something on those
> boxes. This is a shot in the dark...
>
> Aaron
>
> "Kevin Modlin" <> wrote in message news:<awieb.37924$ thlink.net>...
>
>>Disclaimer: I am a newbie (big time).
>>
>>I have a Cisco 1700 configured to allow external access to an internal
>>webserver using a command like:
>>
>>ip nat inside source static tcp 192.168.1.5 80 68.x.x.x 80 extendable
>>
>>This works like a champ as long as the person trying to access the site is
>>inside a Cisco router. Anyone behind a Linksys, DLink, or any other brand
>>gets a page cannot be displayed error. Where should I start to look?
Try adding no-alias at the end of the nat statement.