No, the 10.0.0.0 is private, and wont be found from the router on the remote
network.
Ole
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ole Drews Jensen
Systems Network Manager
CCNA, MCSE, MCP+I
RWR Enterprises, Inc.
[EMAIL PROTECTED]
http://www.CiscoKing.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NEED A JOB ???
http://www.oledrews.com/job
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, February 03, 2001 2:49 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: TCP/IP print through firewall
Hi,
I may be way, way off on this but I'll take a stab. If everybody that
uses the printer sits on the 10.0.0.0 network (ie. 10.0.0.100 and
10.0.0.200)
couldn't you change the printers default gateway to be the 10.0.0.0 network?
That way it would send the replies back to that network and everybody on it
would get their print jobs done. I'm probably wrong but what the hell. =o)
Mark Z.
In a message dated 2/3/01 3:42:21 PM Eastern Standard Time,
[EMAIL PROTECTED] writes:
Let's say that the workstation has IP address 10.0.0.100 and prints to the
remote printer with address 100.100.100.100.
The print reaches the firewall's address 10.0.0.1 and leaves the firewalls
untrusted interface 50.50.50.50. The source IP is still 10.0.0.100 and it
reaches the printer 100.100.100.100 just fine, because it's a public
address.
The printer replies back, but it's default gateway, 100.100.100.1 doesn't
know where to route to network 10.0.0.0 so it gets dropped.
If my firewall translates the address into it's public address 50.50.50.50,
the printer will reply back to it, and I will need to do a "handoff" or NAT
so that port 9100 traffic to 50.50.50.50 gets translated into 10.0.0.100 so
my work station will get the reply.
But, with this solution, the printer reply will end up at 10.0.0.100 if
10.0.0.200 tries to print too.
How does this work?
Thanks,
Ole
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
