MX-3100n Custom Folders over VLAN's

[warren.kemp]

Hi,

We have a networked MX-3100 shared from the server on VLAN 34. Routing is setup so that VLAN 32 can print to this printer, this all works fine. The problem is with the custom folders facility on the printer. The custom folder's can be configured on VLAN 34 fine, but VLAN 32 cant see any custom folders, it cant retrieve the list, even through printing is fine.

Any ideas ?

[Ceechtay]

Re: MX-3100n Custom Folders over VLAN's

Custom Folders are set up on each PC's Printing Preferences and, I believe, therefore the PCs must be able to communicate with the copier directly. The PCs are sending their print jobs to the server, which then sends the print jobs to the copier. You may have communication between the PCs and the server, but not necessarily between the PCs and the copier. Can you ping the copier or access the copier's webpage from the PCs?

If you cannot ping or hit the copier's webpage (do both tests, as ICMP traffic may be blocked, but HTTP may be allowed), then they need to route some traffic from VLAN32 to VLAN34.

I believe (not 100% certain and haven't tested) that the custom folder information is sent via SNMP protocol and it may be blocked for security reasons between VLANs, while still being allowed within the VLAN.

To narrow it down, I would wireshark the communication between a PC/server on VLAN34 and the copier when obtaining the Custom Folder list and then do the same wireshark from a PC on VLAN32. You should be able to see which ports/protocols are used to send the Custom Folder information. It's also possible that the copier's response may be a multi-cast or broadcast, which is why it may be blocked.

[warren.kemp]

Re: MX-3100n Custom Folders over VLAN's

Custom Folders are set up on each PC's Printing Preferences and, I believe, therefore the PCs must be able to communicate with the copier directly. The PCs are sending their print jobs to the server, which then sends the print jobs to the copier. You may have communication between the PCs and the server, but not necessarily between the PCs and the copier. Can you ping the copier or access the copier's webpage from the PCs?

If you cannot ping or hit the copier's webpage (do both tests, as ICMP traffic may be blocked, but HTTP may be allowed), then they need to route some traffic from VLAN32 to VLAN34.

I believe (not 100% certain and haven't tested) that the custom folder information is sent via SNMP protocol and it may be blocked for security reasons between VLANs, while still being allowed within the VLAN.

To narrow it down, I would wireshark the communication between a PC/server on VLAN34 and the copier when obtaining the Custom Folder list and then do the same wireshark from a PC on VLAN32. You should be able to see which ports/protocols are used to send the Custom Folder information. It's also possible that the copier's response may be a multi-cast or broadcast, which is why it may be blocked.

Thanks for your help Ceechtay

It was port 80 that is needed for custom folder listings, opened this port on the firewall for the suspect VLAN from the printers VLAN and everything is now fine

[Ceechtay]

Re: MX-3100n Custom Folders over VLAN's

Glad you got it fixed and thanks for letting us know that it's port 80.