Printers falling offline

gferrin2012

Honorable
Jun 3, 2013
237
0
10,710
We have a corporate office network it is available hardwired or wifi.
In the office upstairs, we have 8 workstations, all connected to the network. Connected to the network is a Brother 8910DW (recently added to replace a Brother8810DW).
So, the 8 workstations need to be able to print AND scan to and from the 8891DW.
Here is the problem...
I have three stations that disconnect from the printer and show offline almost everyday. THE OTHER 5 HAVE NO ISSUES.
---they are running windows 7
---there seems to be no way to get the printer back online
---if you "add printer" it finds it, sets up a new printer with a new name and finds the correct driver on the computer.
Now the steps I have taken are:
---I have deleted all Brother drivers and software and re-installed from supplied disk.
---I have made sure all computers were using hardwired connection ONLY. (some were plugged in, some using wifi).
---I had them NOT turn off their computers overnight (This seemed to work for a while, but inevitably it lost the connection to the printer)
---I assigned a static ip address to printer.
Now, when doing all of the above, none of the working 5 ever had an issue.
Just wondering if anyone had some advice, or needed any more info to venture a starting point?

Thank you
 
Solution


The other users are good so, the printer is not falling offline.
Maybe a suspicious network hub? I had a user last month complaining of something similar.... swapping an old 10/100 network dumb hub that was connecting her to the network seemed to do the trick. She kept losing connection to a networked printer that everyone else seemed fine with.
 

gferrin2012

Honorable
Jun 3, 2013
237
0
10,710

I thank you for the response, I have fired off an email to see if the person indeed, had hubs instead of switches!. One way or the other I will post what I find tomorrow!
 

yayo3p

Honorable
Mar 24, 2015
104
0
10,710
You dont have a print server do you? But anyways, first thing to check is to see if there are some print jobs corrupted or stuck under their windows profile. If so, delete them. Second open up the printer properties and go to the Ports tab. Uncheck SNMP. Sometimes this protocol causes printers to be offline.
 


The other users are good so, the printer is not falling offline.
 
Solution

gferrin2012

Honorable
Jun 3, 2013
237
0
10,710

Thank you so much for your input. I went there this morning and this is what I found. The printer will actually print from the three offending offices, but scan function does not. It buffers then just times out. As the customer did, I uninstalled, reinstalled to verify software. All good. I assigned static ip to both printer and (one) of the work stations (just to be on safe side). This is a switched network no server with the basic router, modem hookup to the 'ol standard tp-link 24 port switch. Old I.T guy kind of vanished so I may try to check config of ports if owner can supply password (He had a scared look when passwords were brought up, it was very clearly the look of "not a clue").
My question is, the config looks odd. here they are. The station had a static 192.168.0.8 255.255.255.0 mask. gateway 192.168.1.1 dns 62.74.x.x Printer had a static 192.168.1.12 255.255.255.0 mask. Gateway 192.168.1.1 dns 62.74. x.x
They all print, but the three offices cannot scan, times out. Perhaps a firewall setting on stations? Or perhaps a port configuration (filtering)? Please excuse my ignorance of tp-link switches,
Thanks for any input!
I noted it prompted for a node. I did not think this necessary because of the switched network.

 

yayo3p

Honorable
Mar 24, 2015
104
0
10,710


You would now have to log into the router and check the settings. Check the DHCP scope. Your DHCP scope should be 192.168.1.x, so with that being said, make sure you assign a 192.168.1.X ( X = 1 - 254) ip address to those printers. Choose an IP address that falls outside the DHCP scope.
 

gferrin2012

Honorable
Jun 3, 2013
237
0
10,710

My bad, yes I see the typo, it actually had 192.168.1..8....not a 192.168.0.8 as I typed earlier! Sorry about that!