Brother HL-5450DN IP Address subnet incorrect

fsx_wizard

Reputable
Jan 26, 2015
3
0
4,510
Per subject line - I have a new Brother printer. For some reason it's ip address is 192.168.0.2 gateway 192.168.0.1. My LAN is setup for 192.168.1.XXX. If I reset the printer to factory defaults it's ip/gateway goes to 0.0.0.0. And then sometime later (I don't know why) it reverts back to the 192.168.0.2.

Obviously I cannot reach the printer from a browser because the printer thinks it's on a different subnet. Any suggestions on what to do? I do have a Ubuntu Linux server, but since the printer is network capable I just have it hooked up to an 8 hub switcher. I have windows 7, Ubuntu Linux and MAC OS all on the lan as well.

<edit>. Ok, this is weird. When I rebooted one of the Ubuntu Linux machines, suddenly the printer printed the Ubuntu test page. CUPS reports it's connection as dnssd://Brother%20HL-5450DN%20series._ipp._tcp.local/ The printer itself now says it's ip address is 169.254.202.67 (Via APIPA) with a gateway of 192.168.0.1 - mind that it is actually on my lan of 192,168.1.XXX. What's really weird is that I do not have a DHCP server running, so where is it getting this 169 address from?
 
The above helps explain the 169 IP address, but doesn't explain the 0.x address. Although you don't think you have two DHCP servers on your network, this sure seems like you do. Are you using a router as and access point and forgot to disable the DHCP server?
 
mmm - I do not have any DHCP servers running. I only use fixed addresses. Thanks for that link. It explains the IP address. Now with any luck Windows will be able to see the 169 IP address and I can change it to an address on my LAN.
 
I was able to connect to the brother via the BRAdmin using the 169 address. Changed it to my local LAN and can print from KUbuntu 14.04 and Windows 7. Cannot print (yet) from the older Ubuntu/Kubuntu machines. I think I may have to reboot them in order for the printer changes to take affect. Yeah, I know they shouldn't need to be rebooted, but that's the only way I got the 14.04 distro to recognize it... and that was simply because I did a system upgrade and had to reboot.

I sincerely thank you for your help. I've been going nuts for 2 days trying to make the printer work. Huzzah! Have a virtual beer on me!