Connecting to printer on diff Subnet.

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 - WAP ( - Gateway addr of - Watchguard x1250e -

I can connect to ALL domain resources on subnet however when I try to connect or even ping the printer ( 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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Is this a network Printer?
Typically if so they need port tcp port 9100 open.
Haze0830Author Commented:
yes it is...and port 9100 is open.
Can you add the printer to the server, and then share the printer from there?
ON-DEMAND: 10 Easy Ways to Lose a Password

Learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees in this on-demand webinar. We cover the importance of multi-factor authentication and how these solutions can better protect your business!

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.

Haze0830Author Commented:
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.
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Haze0830Author Commented:
I'll give it a shot.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.