Cannot print between VLANs

Question

M4100 switch, Port VLANs with routing enabled.

Each VLAN has its own router attached because each VLAN services a different organization with their own External IP. These organizations share a single central printer. Each router has a static route to the other routers on the other VLANs.

-The printer is on VLAN 101.

- I can print from any node on VLAN 101.

- From all VLANs I can ping the printer.

- From other VLANs I can login to the web interface of the printer,

- From other VLANs when I send a print job the printer sees the print job but refuses it with a very generic (i.e. meaningless) error

- If I route the printing to the external IP address of VLAN 101 or replace the M4100 with another (dumb) switch, printing works fine.

WTF??!! What is the printer expecting that is not being properly routed through the M4100 switch? Anyone else had this or similar problems?

DaneA · Answer

Hi&nbsp;KBXR,

&nbsp;

Kindly try to configure Protected Port(s). &nbsp;

&nbsp;

a. On the web-GUI of the M4110-26G, go to Security &gt; Traffic Control &gt; Protected Ports.

b. In the Group ID, select 0. &nbsp;

c. On the Group Name field, you may enter any group name you want.
 d. Click the orange bar to display the available ports.

e. Select the check box below on the appropriate port where the printer is connected.

f. Click Apply.

g. Check if you will be able to print from other VLANs other than VLAN 101.

&nbsp;

As reference guide, read pages 319-320 of the M4100 user manual&nbsp;here. &nbsp;Let me know if it helps. &nbsp;

&nbsp;

Regards,

&nbsp;

DaneA
 NETGEAR Community Team

KBXR · Answer

No change, unfortunately. Print jobs from vlan 101 work just fine, print jobs from the other vlans fail. The printer logs the print jobs from other vlans as "Cancelled" Not a terribly helpful log entry but it is clear that the print job gets to the printer. The printer logs show the name of the file being printed as well as the name of the user who sent the job, but the job is "Cancelled" almost immediately and never enters the print cue.

I was hopful. :-) Any other thoughts?

DaneA · Answer

Hi&nbsp;KBXR,
&nbsp;
Your existing network is kinda intricate. &nbsp;Can you post an image or screenshot of your detailed network setup?&nbsp;
&nbsp;
You might want to consider configuring Asymmetric VLANs. &nbsp;However, as per your initial post, each VLAN has its own router. &nbsp;So having Asymmetric VLANs is not advisable. &nbsp;
&nbsp;
&nbsp;
Regards,
&nbsp;
DaneA
NETGEAR Community Team

KBXR · Answer

Yeah, intricate might be a word for it.I've been thinking that I might want to redesign to a singlerouter with multiple WAN ports, create the VLANs at the router, get rid ofall IP routing on the switch and use port defined VLANs on the switchsimply to keep the Microsoft Small Business Servers from seeing eachother's DHCP service.After a quick look, it seems that the document you sent may hold the answer. Thanks! &nbsp;If I still havequestions after I study the document and implement some changes to test, I'll post a picture of the current network.Thanks Dane.

KBXR · Answer

OK, so the article helps A LOT!! &nbsp;Seems I was creating an asymetrical vlans already but didn't (don't) understand the rules of the game yet.&nbsp;&nbsp;I have, however, run into an issue with the rule that says for the asymetrical vlans to flow traffice between them that all the vlans must belong to the same subnet. Mine do not. &nbsp;I have 192.168.10.0/24 192.168.20.0/24 and so on.&nbsp;&nbsp;(Funny thing is, though, that currently traffic routes between the /24 subnets just fine using the IP address. The printers actually see the job comming at them. I still want to know what bit of information is left out, wrong, or what protocal is blocked that does not allow the print job to complet. &nbsp;But let's ignore that for the moment.)&nbsp;I am stuck with keeping the three /24 subnets because:- Each Microsoft Small Business Server demands that it be on a /24 network. Period. No getting around it.&nbsp;- Each Mictosoft Small Business Server demands that it be the only DHCP server on the subnet. Period. No getting around it. (that even makes sense)- I have too many devices to put on a single /24 network&nbsp;So I was thinking ....- Define each of the routers as being on a 192.168.0.0/16 network.- Each of the routers keeps its current PVID&nbsp;- mark the physical switch ports of the routers as Untagged on all of the vlans so that the routers can freely talk directly to each other but not directly to any other devices not on their vlan.&nbsp;- The only switch ports marked as Untagged on multiple vlans would be the for&nbsp;the routers&nbsp;- I shouldn't have to create any static routes at the routers since they all belong to the same /16 subnet&nbsp;&nbsp;Think that would work? Thoughts?

Forum Discussion

Cannot print between VLANs

7 Replies

Related Content

Wireless Printing

Random Printing

Wireless Printing Using WiFi Range Extender and Ethernet Print Server

Wireless Printing

Set up AC1750 Smart WiFi Router as print server

NETGEAR Academy

ProSupport for Business