HP Printer Not Connecting Via Satelite

[pug306d]

Hello,

I have an HP printer which needs to connect to the wifi in 2.4ghz. When it is connected to the router, no problem is detected, on the other hand when I put it near the satellite it switches to ip address 169 ...... and is therefore not found on the network.

If I turn off the sattelite, the printer reconnects to the router and starts working again.

Do you have any idea what is causing this problem?

I have RBR750 + 1 Satelite, all other devices work fine via the satelite its only the HP printer that connects to the wifi but never gets a IP address from DHCP.  If I turn off the satelite the printer connects to the router and gets a LAN IP from DHCP.  If I set a static IP on the printer it still cannot be reached when connected to the satelite.

The WiFi connection itself is fine its the IP connectivity that is broken when the printer connects via the satelite.

The printer model is HP 8500A.

Thanks

[Mikey94025 · Accepted solution]

Your problem is interesting because it sounds like your HP printer is able work with the Orbi network, just only when talking to the router and not your satellite.  The 169.* address means that your printer is unable to request a DHCP address and your static IP address test (good idea) means that it cannot communicate with the Orbi network either.  Do you have any other wireless devices working through the satellite?

One thing to try is to improve your 2.4Ghz wireless device compatibility.  This is unlikely to work because your printer works with your router, but still cheap to try as an experiment.  

Try setting your CTS/RTS Threshold to 2347:

1. Go to the web admin portal at http://orbilogin.com/
2. Click to the Advanced tab, Advanced left menu, Wireless Settings
3. Set CTS/RTS Threshold to 2347 for both 2.4hz and 5Ghz networks
4. Press Apply

See if that helps.  If problems still persist, next try disabling AX mode for the 2.4Ghz band:

1. Go to http://orbilogin.com/
2. Click to hte Advanced tab, Setup left menu, Wireless Setup
3. Uncheck "Enable 2.4G" under the top Enable AX section
4. Press Apply

[Mikey94025 · Accepted solution]

Your problem is interesting because it sounds like your HP printer is able work with the Orbi network, just only when talking to the router and not your satellite.  The 169.* address means that your printer is unable to request a DHCP address and your static IP address test (good idea) means that it cannot communicate with the Orbi network either.  Do you have any other wireless devices working through the satellite?

One thing to try is to improve your 2.4Ghz wireless device compatibility.  This is unlikely to work because your printer works with your router, but still cheap to try as an experiment.  

Try setting your CTS/RTS Threshold to 2347:

1. Go to the web admin portal at http://orbilogin.com/
2. Click to the Advanced tab, Advanced left menu, Wireless Settings
3. Set CTS/RTS Threshold to 2347 for both 2.4hz and 5Ghz networks
4. Press Apply

See if that helps.  If problems still persist, next try disabling AX mode for the 2.4Ghz band:

1. Go to http://orbilogin.com/
2. Click to hte Advanced tab, Setup left menu, Wireless Setup
3. Uncheck "Enable 2.4G" under the top Enable AX section
4. Press Apply

[CrimpOn]

---

@pug306d wrote:

only the HP printer that connects to the wifi but never gets a IP address from DHCP.  If I turn off the satelite the printer connects to the router and gets a LAN IP from DHCP.  If I set a static IP on the printer it still cannot be reached when connected to the satelite.

---

What is the evidence that the printer has connected to the satellite?

• It is not the Orbi 'app' Connected Devices or the Orbi web interface Attached Devices, because it does not show up on them.
• Does the printer control panel somehow indicate a successful connection?
  (On my printer, I can print out the network parameters from the printer itself.  The HP8500A manual (page 221) talks about printing out the network status: http://h10032.www1.hp.com/ctg/Manual/c02668142.pdf 

[pug306d]

Disabling AX on the 2.4Ghz fixed the issue, not sure why it worked fine with the router and not the satelite as AX was enabled on both?