NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk R7000: WI-FI Pring sharing
Hi, On my R7000 I have enabled smart connect to let the system intelligently select the best WiFi band 2.4 GHz or 5 GHz. But my HP WI-FI printer is on 2.4 GHz band. The devices (laptops, smartpho...
Thanks for the reply. As you have indicated they were not on the same network. After modifying the setup, everthing works fine.
An assigned address is not really required for a printer. Most devices can find the printer just fine by other means (e.g. Windows name).
TheEther wrote:
An assigned address is not really required for a printer. Most devices can find the printer just fine by other means (e.g. Windows name).
'not really required' is the operative word. Under Windows 7 my HP 310A although found would not stay connected. Contacted HP and they said make it 192.168.1.10 *specifically*. Did that and had no problems after that. Funny part is under W8 and W10 it can use any DHCP IP Address it gets.
I'll assume some printers could use fixed IP Addresses then?
Your situation could be unique to your HP310A. I doubt HP would be so dumb as to require all of their network-enabled printers to use a static IP address, especially 192.168.1.10. My Brother printer has no problems working with a DHCP address.
Giving assigned address to important devices are benefitial. You can id. the device by ip address or won't get into trouble like ip address confilict. Assigned address is arbitrary within the LAN ip addess range defined in the router set up. In my case I assigned address for
NAS, wirelss ip cameras, wireless printers for that reason. I don't believe HP printer works only with assigned address 192.168.1.10.
VE6CGX wrote:I don't believe HP printer works only with assigned address 192.168.1.10.
True, but that was HP's 'work-around' for that printer under W7 for me. Had to start the router DHCP at 192.168.1.20 to be safe. All I can say it worked. W8 and above, no need to do that. I think the real problem was the driver, especially after the PC went to hybernation. It sort of got 'lost' I guess, but direct addressing I guess worked.
I only mentioned that as maybe there are some printers that do either need or work better with assigned IP Addresses.
Right now I only assign set IP Addresses to the PC's so I can tell which one it is in the LOG. NG doesn't provide device names in the log, and on bringing up systems without assigned IP Addresses they will move around.
Of course so. If you want to quick look at currently connected devices, run ipscan. Some devices will id. itself like Brother printer, other's will give MAC address.
