Then the issue is very easily solved and is routinely posted in this forum as well as every other print forum.
If the fact the Webui crashes is misinformation (Like the Phaser and Mac Sierra information seems to be). The ping command will surely still be running along and hitting the other device using the same IP address, so when you run arp/a again, it will identify the hardware (physical address) of the other device, you can then find that device on the LAN and figure out the DHCP issue to stop it re-occurring. Then go ahead and unplug the printer in question from the LAN entirely. So if the webui and print stops working at the same time, and you can ping it when that occurs, do a ping with the -t command to keep it running, also run an arp/a from the command line to find that hardware ID of the device (lets pretend this yellow one is a printer) You can downgrade the firmware only with an Altboot and all data will be lost, but it won't fix anything, the firmware cannot be causing the issue, and if it couold, it sure wouldn't do it to 2 different printers at the same time. The only time the 2 things would occur at the same time is if you have 2 machines on the LAN with the same IP address, and if a reboot was fixing it, you would have to assume you are statically assigning IP addresses that exist in your DHCP pool too. Then you state "web interface stops responding", that doesn't seem likely, it doesn't at all fit the printer is offline error that occurs in Windows (never on a Mac).
Xerox printer drivers for mac os sierra mac osx#
You list the Workcenter 58XX and Win10 圆4 in the post.Īnd list Mac OSX Sierra and a Phaser (2 massively different things) in the subject line.
0 kommentar(er)
