NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DNS and Printer problems RAX80
Client OS: Windows 10 64 bit Router: Nighthawk RAX80 Router firmware: V1.0.3.106_1.0.50 Purchase Date: 12/20/2020 Printer: Brother HL-L2380DW I am ready to take a bat to this router and live ...
temmet wrote:
Now I have a printer that the router can detect but to which no client can connect. I’ve reconnected the printer to the network to ensure a fresh connection, reinstalled the printer software and drivers on the clients, but have had no success so far. While investigating this today, I noticed that none of the clients can ping each other but they can ping the router. Is there a setting in the router I’m missing?
Is this a wifi connection from the printer to the router?
The usual way to fix wifi printers is to find the printer maker's utility, the software that runs on your operating system. Then use that to connect the printer to the wifi.
The router just broadcasts wifi. It is then down to the printer to play ball. There isn't much that you can do on a router, beyond fixing it to a particular IP address, that affects what the printer gets up to.
Where possible, using the WPS feature can simplify things.
temmet wrote:
I have a DNS problem that has existed since day one.
Given the symptoms you describe, it might also help if you told people what the modem is in front of this router, if there is one. The model number could be useful. Is it, by any chance, also a router, with a set of LAN ports on the back?
The reason for asking is that a lot of people turn up here trying to put a router behind a modem that is also a router. That can complicate troubleshooting.
michaelkenward wrote:Is this a wifi connection from the printer to the router?
The usual way to fix wifi printers is to find the printer maker's utility, the software that runs on your operating system. Then use that to connect the printer to the wifi.
The router just broadcasts wifi. It is then down to the printer to play ball. There isn't much that you can do on a router, beyond fixing it to a particular IP address, that affects what the printer gets up to.
Where possible, using the WPS feature can simplify things.
The printer software didn't detect the printer, but I was able to manually configure the IP address and it worked. I didn't use the Brother software with the last router so I assumed the same was true this time. Thank you very much.
michaelkenward wrote:Given the symptoms you describe, it might also help if you told people what the modem is in front of this router, if there is one. The model number could be useful. Is it, by any chance, also a router, with a set of LAN ports on the back?
The reason for asking is that a lot of people turn up here trying to put a router behind a modem that is also a router. That can complicate troubleshooting.
The modem is a Netgear CM600.
temmet wrote:
The printer software didn't detect the printer, but I was able to manually configure the IP address and it worked. I didn't use the Brother software with the last router so I assumed the same was true this time.
Smells like a printer/PC issue. But I am not familiar with Brother printers.
However, it make sense to me to at least trying to follow the maker's instructions before moving on to esoteric DNS tweaks.
temmet wrote:The modem is a Netgear CM600.
Nothing complicated to get in the way there.
michaelkenward wrote:
temmet wrote:The modem is a Netgear CM600.
Nothing complicated to get in the way there.
I apologize for the break between my posts. I'm back, with the same DNS problem. My printer issue has been resolved but I'm still getting strange DNS problems. If it isn't my modem, what should I be checking next?
temmet wrote:
michaelkenward wrote:
temmet wrote:The modem is a Netgear CM600.
Nothing complicated to get in the way there.
I apologize for the break between my posts. I'm back, with the same DNS problem. My printer issue has been resolved but I'm still getting strange DNS problems. If it isn't my modem, what should I be checking next?
It remains unclear to me what these "strange DNS problems" are.