Thank you for your ongoing participation.
Having let the printer sit unplugged for a long while, I now finf that the GFI (not fuse, as I said above) will test again. Now that I know this, it appears that my problem is something other than my first guess. The printer powers on, but the loud blowy cycle doesn't occur, and the display panel remains blank. I had thought the problem was some sort of reduced power issue possibly involving the GFI test; in any case, it appears that the problem is more serious, and I'll have to decide whether to have the thing repaired or just buy a new printer.
Now I wish it had been a router issue. The solution would have been a lot less expensive.
It is vastly simpler to tell someone to use DHCP than it is to teach them how to get the IP scheme from the LAN themselves, especially when the user may not have any technical ability at all, and you would need to document for every single OS (Win 200-7, Win 8, Win 10, OSX etc) and every way the Windows Control panel can be laid out (Classic View/Small Icons). So instead they just say "Set it to DHCP, take the info it obtains and set that as static"
This does have its own set of failings of course, turn the printer off, add a new device to the LAN, that device takes the printers IP (remember, it is using a static IP, but it came from the DHCP pool) and print jobs now go to a device that may or may not even be a printer, then the printer comes on and you have a duplicate IP scenario on your hands.
But that is a "network problem, not a Xerox problem", and the directions is then 5 pages shorter.
I'm far from a technical writer mind you, and speaking in an entirely un-official capacity, but I'm pretty sure that is the gist of it.
Thanks for your reply. I'm going to have to hold off on this for a while, as it appears that my printer's fuse has blown and I need to take care of that issue before I can continue with this.
Oh, it might not be the fuse, though the test button no longer does anything and the fuse button won't lock down. The printer comes on, the blank information screen lights up along with the power light and the alert light. From that point, the motor might or might not cycle on briefly (maybe 2 or 3 seconds), but in either case, the info screen remains blank.
"Odd, I would understand it not being able to do it while set to DHCP, but not if set to manual. (Don't even try DHCP/AutoIP)"
That makes sense, but why does the owner's manual say to set to DHCP and then change the IP address manually? This has been the case since 2011, according to the issue I linked to earlier.
I'll be back. I hope.
Odd, I would understand it not being able to do it while set to DHCP, but not if set to manual. (Don't even try DHCP/AutoIP)
If you are comfortable with using a laptop via crossover cable connection, change it in CWIS via Properties > Protociols > TCP/IP
The following is a quick runthrough of a crossover connection, but it assumes you can change the MFP settings, in your case, make the laptop match the IP scheme currently on the device and make the laptop one number higher in the last octet.
From the Windows 7 client Workstation do the following;
IP Address: 192.168.1.10
Subnet mask: 255.255.255.0
Gateway: [leave-it-blank]
DNS Servers: [leave-it-blank]
From the Printer
IP Address: 192.168.1.100
Subnet mask: 255.255.255.0
Gateway: [leave-it-blank]
DNS Servers: [leave-it-blank]
Then in CWIS you can set it however it needs to be on your new LAN setup, then swap the crossover going to your laptop to the printer with the LAN cable going to the wall.
Thank you for your prompt reply. I thought the claim that this is a compatibility issue was either spurious or grossly oversimplified, but oh, well.
I found DCHP under the IPv4 option in the TCP/IP submenu, and selecting it doesn't work.
Unfortunately, I am unable to manually reset the IP Address (or the Subnet or Gateway, for that matter) using the arrows, as the user manual instructs. There seems to be no such function. In fact, upon digging into this by searching for "change ip address", I've found that this issue has been brought up in these forums:
http://forum.support.xerox.com/t5/Printing/Phaser-6280n-connecting-to-router-using-TCP-IP/td-p/1828
Thank you.
DF
Routers use standardized connectivity protocols, the problem can't be of compatibility unless you are using WiFi connections.
If wired, set it (the printer) to DHCP, it seems more like the printer is using a statically assigned IP address outside the subnet of the new router.(You do want static IP's in the end, because DHCP lets the IP change, which breaks the ability to print)
For example, old router was on 192.168.1.1 and the new one is on 192.168.0.1. If the subnet is 255.255.255.0 (normally this is true) then the new router won't see the printer.
So, to test the theory, on the MFP go to Menu > Admin Menu > OK > Network Setup > TCP/IP > OK and set it to DHCP, or to a new IP/Subnet/Gateway in line with the new setup.
I have a Xerox Phaser 6280 printer, which worked just fine with my old router. My new router (Netgear AC1200 R6200) cannot recognize that the printer is connected with a LAN cable. Netgear and Best Buy tell me that this is a compatibility issue. Before I take the router back and get another one, I need a list of wireless/LAN routers that are compatible with this printer.
Thank you.
DF