Solved

Connecting to printer on diff Subnet.

Posted on 2007-04-04
7
329 Views
Last Modified: 2010-03-18
I've got an issue here trying to connect to a printer on a different subnet. I have a WAP that is setup on a different subnet - I have everything configured to allow me to connect to domain resources on our domain subnet. PC's that connect to the WAP are NOT on the domain. Here is the setup -

Laptop 192.168.2.10 - WAP (192.168.2.250 - Gateway addr of 192.168.1.1) - Watchguard x1250e - 192.168.1.0/24

I can connect to ALL domain resources on subnet 192.168.1.0/24 however when I try to connect or even ping the printer (192.168.1.150) it times out. I've gone the route of adding a local printer - new port - standard TCP/IP and then using the printers IP and it tells me it can't locate the printer. I can successfully ping several other domain PC's by name and IP addr - but not this printer.

Any help?
       
0
Comment
Question by:Haze0830
7 Comments
 
LVL 6

Expert Comment

by:kane77573
ID: 18851259
Is this a network Printer?
Typically if so they need port tcp port 9100 open.
0
 
LVL 2

Author Comment

by:Haze0830
ID: 18853610
yes it is...and port 9100 is open.
0
 
LVL 12

Expert Comment

by:RWrigley
ID: 18855152
Can you add the printer to the server, and then share the printer from there?
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 2

Expert Comment

by:IrfanAsim
ID: 18857325
To troubleshoot this connectivity issue I would start from physical layer like testing network cable, network jack and then jetdirect network card. After that I would verify that ip configuration on the printer is correct specially ip address, subnet mask and gateway.

0
 
LVL 2

Author Comment

by:Haze0830
ID: 18859484
I don't see an option anywhere to check the subnet mask or gateway. I know it's not a cable or switch issue and it is currently shared off of a server.
0
 
LVL 12

Accepted Solution

by:
RWrigley earned 500 total points
ID: 18861695
If you can't print to it through the server share, then its likely that the problem has nothing to do with the printer itself.  You may have a firewall issue that is blocking the LDP ports (typically, UDP 161, and occasionally TCP 515 or 9100).  You might have to check with the actual printer to see if there are others.
0
 
LVL 2

Author Comment

by:Haze0830
ID: 18875184
I'll give it a shot.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

David Varnum recently wrote up his impressions of PRTG, based on a presentation by my colleague Christian at Tech Field Day at VMworld in Barcelona. Thanks David, for your detailed and honest evaluation!
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup". After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a  panic as all your work w…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now