The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Setting up a network printer on a different DHCP

    Discussion in 'Networking and Wireless' started by saturnotaku, Nov 16, 2020.

  1. saturnotaku

    saturnotaku Notebook Nobel Laureate

    Reputations:
    4,879
    Messages:
    8,926
    Likes Received:
    4,705
    Trophy Points:
    431
    On my home network, I have a combo modem/router where I have my desktop PC and a couple other devices connected. That area uses the DHCP range of 192.168.0.X. One of those devices is a Linksys Velop mesh network, which has its own DHCP range of 192.168.1.X. Since most of my devices are wireless, I have my Canon TR8520 AIO printer connected to one of the Ethernet ports on the Velop. That works fine for printing from my laptops, smartphones, and tablets. However, if I try to use the AIO from my desktop, I can't see it on the network. I tried adding the printer manually by IP address, but the computer doesn't see it. Googling doesn't produce any leads so I'm hoping I can find some help here.
     
    Last edited: Nov 16, 2020
  2. Aivxtla

    Aivxtla Notebook Evangelist

    Reputations:
    709
    Messages:
    650
    Likes Received:
    890
    Trophy Points:
    106
    Common cascading routers issue. Devices from the Velop should be able to connect to clients on the combo router since the Velop is essentially a LAN device for the first router but not in reverse due to NAT/Firewall on the WAN port side of the Velop. You could just set the Velop to AP mode and let the combo unit be the DHCP server for all clients or if you want to keep the current setup set the printer to the combo unit and the clients on the Velop should see it if you manually enter the IP on the Velop side clients.
     
    Last edited: Nov 16, 2020
    saturnotaku likes this.
  3. saturnotaku

    saturnotaku Notebook Nobel Laureate

    Reputations:
    4,879
    Messages:
    8,926
    Likes Received:
    4,705
    Trophy Points:
    431
    I ended up working around it by plugging my switch into the other Ethernet port on the main Velop node, which put all devices that might need to use the printer within the same DHCP range. Appreciate the suggestion all the same.
     
    Aivxtla likes this.
  4. hacktrix2006

    hacktrix2006 Hold My Vodka, I going to kill my GPU

    Reputations:
    677
    Messages:
    2,183
    Likes Received:
    1,421
    Trophy Points:
    181
    Normally if I am running something on a different IP range I run a static route to that IP on a different subnet.

    So say I have Main Router on 192.168.0.1 and a printer on 192.168.1.4

    What I would do is make a static rout from 192.168.1.4 to 192.168.0.1 infact it's what I do for my modem to my router as I have them separated IP wise but need access to the Management GUI and stats GUI.

    Sent from my SNE-LX1 using Tapatalk