Inside users would use the inside IP for the printer.
--
Jason Roysdon, CCNP/CCDP, MCSE, CNA, Network+, A+
List email: [EMAIL PROTECTED]
Homepage: http://jason.artoo.net/
Cisco resources: http://r2cisco.artoo.net/
"Brian Hartsfield" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> At 12:28 PM 1/16/2001 -0600, Ole Drews Jensen wrote:
>
> >Now, with all devices at that office connecting to a cheap hub, wouldn't
> >this work okay, or would the best thing be to statically NAT
214.100.200.70
> >to a dedicated address on the 192.168.20.0 network which then is assigned
> >the printer?
>
> You would want to use a static NAT because can't put a device from the
> 214.100.200.* network on the 192.168.20.* network. If a machine on the
> local LAN tries to get to that printer, it will determine that the machine
> is not on its local network and send the packet to its default gateway
> (i.e. the router). The router will then route the packet to the external
> network and nobody will respond to it. A static NAT will solve this
> problem and machine on the local LAN will use the "inside" IP address for
> the printer and users on the internet will use the "external" IP address
of
> the printer and both will work.
>
> Brian
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
