wireless printer not visible on other subnets
-
I have just re-jigged my network,.. and my wireless HP150 printer has moved from its common ( single ) subnet, to a distributed network with several subnets.
Needless to say hosts connected on the same subnet as the printer work fine, and can still see the printer ( and print).
However, hosts on other subnets do not see, and hence cannot print.
I have tried a series/combination of ports 137-139 and 9100.. sharing to 'other' subnets,... but this does not seem to work,..
Do I need to share to the WAN,.. I am thinking yes,.. as the HP print solution uses the cloud,.. but not sure...
Are there any wiki's or previous posts where this question has been answered,.. in my searches so far I have not found what I am looking for..
My firewall rules for my printer attached subnet, is as follows
Any help gratefully received...
-
The rule to pass traffic for the printer will need to be on the interface where the clients are not the where the printer is.
They will not be able to 'discover' the printer in a different subnet so clients wanting to use it will need the IP address setting directly.
Steve
-
I would try the "9100 allow" on the client subnet (pc printing)
As pfSense filter "inbound packages"Btw:
If had a printer that needed for me to open up to the Cloud/Internet ... It would be in the "garbage" the next day -
@bingo600 said in wireless printer not visible on other subnets:
If had a printer that needed for me to open up to the Cloud/Internet ... It would be in the "garbage" the next day
I feel this way about a lot of the "connected" stuff on sale these days. Putting these things on your network is a self inflicted wound.
-
Do you mean you can't see the printer or you can't connect? If the printer is on a different subnet, then browsing won't work, but connecting to it will. Browsing relies on the the printer broadcasting it's existence and broadcasts don't pass through routers.
-
tx guys,..have followed advice.. and changed rules around as follows..
But alas I still cannot see printer on other network subnets..
I am setting my rules correctly,.. they are top of the list?? for LAN1
info,.. I can see printer,.. ie ping it from LAN1 to LAN2,.. So I know it is there from a network POV,.. but guess its a port issue setup,... that eludes me..
Thanks -
What are you using for printing ?
On Win/Linux you can define a "network printer" and point it to the printers ip address.On phones you are prob using an app (sigh) ...
Have you tried avahi , to do (help) w. the discovery.Geezzz i hate printers.
/Bingo
-
@diyhouse said in wireless printer not visible on other subnets:
But alas I still cannot see printer on other network subnets.
Again, you cannot browse past a router. You have to manually configure the link to a printer.
-
You need to proxy the mDNS/Bonjour between the subnets were your clients (things that want to print) and the subnet were your printers are. Use avahi to do that:
Pick the two networks that apply to your setup. In my case they would be Home and Printers.
On the subnet were the printers are needs a rule like this:
Notice the Gear icon. You need to pass ip options, look in advanced options.
I'm assuming you have an any-to-any rule on the subnet were the clients are. If not you will need a rule to allow the clients to see the printers.
-
@stephenw10 said in wireless printer not visible on other subnets:
They will not be able to 'discover' the printer in a different subnet so clients wanting to use it will need the IP address setting directly.
Yup, still that.
I would not bother trying to make the printer discoverable if it was me. I've been that road and there is pain that way!
Just setting the printer IP manually in the client will allow you to print to it.
Steve
-
@stephenw10 Generally speaking I agree with that. It's when the wife and kids want to "airprint" from iPhones and iPads that you need to be able to discover the printers...
The OP didn't give specifics about what his clients are and so on...
-
Indeed. Moving to the same wifi the printer is on is often an option in that case.
Using Avahi is also an option, just not one I would choose given the choice.
Sometimes we are not really given a choice.Steve
-
@stephenw10 tx guys,.. Yes I can feed the ip address into my windows 10 client i've discovered,.. the main Linux (my ) machine is on the same subnet,. (as the same room), its when the wife and kids want to print from their phones and tablets that 'problems' arise,..
-
@diyhouse said in wireless printer not visible on other subnets:
its when the wife and kids want to print from their phones and tablets that 'problems' arise
The simple solution here is to just put the printer on the wifi network/vlan..
Your better OSes can just put in the fqdn or IP of the printer to print to it. (windows/linux/etc) While your tablets and phones want to discovery it. It simpler solution all the way around to just put that printer on the same L2 as those devices.
-
Yeahh...
I have my WiFi printer on the "Phone Vlan" , just to solve that issue.
But i think i tried avahi before i moved the printer to the phone vlan. It worked "almost" every time
My wifes nagging made me move it to the phone vlan, never heard anything after that. Well as long as she doesn's update the Canon Print APP
Ohh...The WiFi coverage in the "printer room" was a bit intermediate , so the "smart cheap wifi printer solution" ended up "costing" a C3502 AP + a PoE injector ... (and 24/7/365 power to the AP)
What one does not do ... In order to "protect your hearing"
/Bingo
-
The simple solution here is to just put the printer on the wifi network/vlan..
Unless you have more than one wireless network running around the house,.. and you monitor the traffic on each.. ( things are never that simple )..
-
Ok, folks,.. This has made for an interesting afternoon,. Really appreciate the input and comments from folks....
I am tending to try and get avahi working... I have watched several videos and combined with the posts here above,.. I am struggling to get my head around the rule specified in jwj's post ,.. and the gear wheel options...
I am running 2.45 Rel. P1,.. the latest,.. afaik....
Things I have tried so far still do not allow my phones to see the connected printer...
I need help to protect my hearing,..
Any hints gratefully received -
@diyhouse said in wireless printer not visible on other subnets:
and you monitor the traffic on each.. ( things are never that simple ).
Huh? I have 4 different wifi networks.. Printer is on the trusted one - if wife wants to print.. Click make sure on correct wifi network.. Which is really the only 1 she uses anyway.. Since she has really zero use for her phone or tablet to be on the other ones, iot stuff, guest and roku..
Yeah it is that simple... Unless you love to do things the hard way..
Really - if your user can not click to connect to wifi network X when they wan to print.. They don't need to print ;) its that freaking simple and easy.
Guests freaking don't need to print.. Roku's sure don't need to print.. I might jump on the iot wifi if setting up a new iot device. Or for some strange reason I want discover a different roku might jump on that. But day to day there is zero reason to not be on the normal trusted wifi network that allows me to print. For wife devices - don't even give them the option to join the other wifi vlans.. Good luck doing it the hard way.. While also breaking your L2 boundary..
-
Hope this helps. Sorry about not showing this earlier. Just tick allow IP options in the advanced options section (you click the blue box to expand the section). Leave everything else in there on the defaults.
-
That's in combination with Avahi I assume?
