Accessing my printer from another VLAN

I have a UnRaid server that is also hosting my Windows VM, which is using VLAN ID 10. My VM can freely access all other devices on the network, however, I am having trouble connecting to the printer.

If I want my VM to access the printer, should I configure Port5 of GS1200-8 as tagged or untagged for VLAN 10? Since the printer is not VLAN aware, it seems logical to leave it as untagged. However, I remember reading about a rule stating each port can only have one untagged VLAN ID. I cannot isolate the printer for the VM only, since other PCs on the network need it as well.


Accepted Solution

  • PeterUK
    PeterUK Posts: 2,702  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    edited September 2022 Answer ✓

    What printer is it? I had the same problem this what you need to do my printer is HP the pain is HP only give you drivers if you setup with their app with the printer on the same subnet first.

    Once done you can put the printer back to 192.168.1.30

    Then what you need to do is make virtual interface on VLAN10 192.168.10.254/24

    Make the following NAT rule

    incoming interface VLAN10

    external IP 192.168.10.254

    internal IP 192.168.1.30

    Service-Group with TCP 80, 9100 and UDP 161

    routing rule

    incoming interface

    member VLAN10

    destination 192.168.1.30

    Service-Group with TCP 80, 9100 and UDP 161

    next hop

    type interface

    interface LAN1

    SNAT outgoing-interface


    Then on the PC on VLAN10 go to:

    Control Panel\All Control Panel Items\Devices and Printers

    click add a printer then “The printer that I want isn't listed”

    select “add a printer using an IP address or hostname” click next

    device type TCP/IP device and enter 192.168.10.254

    This will get you to print but not use the scanner

    You might be able to get way with doing NAT and routing if PC on VLAN10 has a gateway set where I do not and just setup the printer by IP in windows.

    On a side note I fixed being able to use the scanner just add the route rule in windows like this.

    route /p add 192.168.1.0 mask 255.255.255.0 192.168.10.254


All Replies

  • mMontana
    mMontana Posts: 1,300  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    192.168.10.0/24 and 192.168.1.0/24 in which zone are for USG40?
  • 192.168.1.0/24 is in zone LAN1 192.168.10.0/24 is in a zone I created VLAN10
  • PeterUK
    PeterUK Posts: 2,702  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    edited September 2022 Answer ✓

    What printer is it? I had the same problem this what you need to do my printer is HP the pain is HP only give you drivers if you setup with their app with the printer on the same subnet first.

    Once done you can put the printer back to 192.168.1.30

    Then what you need to do is make virtual interface on VLAN10 192.168.10.254/24

    Make the following NAT rule

    incoming interface VLAN10

    external IP 192.168.10.254

    internal IP 192.168.1.30

    Service-Group with TCP 80, 9100 and UDP 161

    routing rule

    incoming interface

    member VLAN10

    destination 192.168.1.30

    Service-Group with TCP 80, 9100 and UDP 161

    next hop

    type interface

    interface LAN1

    SNAT outgoing-interface


    Then on the PC on VLAN10 go to:

    Control Panel\All Control Panel Items\Devices and Printers

    click add a printer then “The printer that I want isn't listed”

    select “add a printer using an IP address or hostname” click next

    device type TCP/IP device and enter 192.168.10.254

    This will get you to print but not use the scanner

    You might be able to get way with doing NAT and routing if PC on VLAN10 has a gateway set where I do not and just setup the printer by IP in windows.

    On a side note I fixed being able to use the scanner just add the route rule in windows like this.

    route /p add 192.168.1.0 mask 255.255.255.0 192.168.10.254



  • Thanks for the detailed reply. I am not a network guru, but I managed to digest it enough to put in the proper rules. I can now ping and access the printer's web portal from the VM now.

    After some searching and reading, it seems like this yet to be implemented feature will greatly reduce the amount of work needed for problems like this. Hopefully Zyxel will get this ready soon.