Actually, it's much simpler than I thought. The problem was that port 515 was not opened up on the firewall (I thought port 9100 was the only one needed). After that, the firewall keeps track of your print session, and no NAT or other fun stuff is needed. I was now able to print directly to the printer from anywhere. The other problem I had with my AS400 not being able to print to it, was that (this is really so stupid that I overlooked it at first) there was no default gateway setup on the AS400, and therefore no route to the printer either. But, it is all working now, so 'ho ho ho and a bottle of rum'. Thanks for all the replies. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ole -----Original Message----- From: Sudarshan NChari [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 12:33 PM To: 'Ole Drews Jensen'; '[EMAIL PROTECTED]' Subject: RE: TCP/IP print through firewall Hi, I think, you would doing a NAT in this case and your packets to the printer would already be going as a public IP address. So the printer would be knowing where to send the responses back and you wont be needing another NAT. BRgds Sudarshan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ole Drews Jensen Sent: Friday, February 02, 2001 5:10 PM To: '[EMAIL PROTECTED]' Subject: TCP/IP print through firewall All this reading about routed protocols and routing protocols makes you think you know it all, until you are in front of a new funny situation. I am sure that someone out there can explain this to me real quick and easy, so here's my question. We have a LAN with a private network 10.0.0.0, and from a workstation I need to print to a TCP/IP ready printer at another company, which has a public address 100.100.100.100 (this is ofcourse not the real one). My computer should not have any problems getting routed to that printer via it's default gateway (the firewall), via the firewalls default gateway (the router), via the routers default gateway (our isp), and so on. BUT, the computer needs a response from the printer so it knows that it's there and ready, but when the printer tries to reply to my computer 10.1.2.3, it will be dropped by it's default gateway (the other company's router), because the 10.0.0.0 network is not routable through the Internet. I'm I right, and what would be the thing to do here? Would I HAVE to do a NAT on my workstation so the printer can reply back that way? Thanks for any comments on this, 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _________________________________ 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]
