[Misc] OOPS @#$% don't consult

[brotherlarry]

Ok Have been called to a Canon IR7086 that is having network printing issues. It stops printing, the previous tech turned it off then back on and printed the "Q" . That was his fix! Now the customer is hot and they have called me take a look. Any ideas or mystical settings I should look for. Oh yea this is in a school and the company the hired me does not password protect settings.

"Time Is Money Friends"

[LNorris]

Re: OOPS @#$% don't consult

check cable or port on switch.

[JPiek]

Re: OOPS @#$% don't consult

"Network printing issues" includes A LOT !
Could be anything from printqueue on the server (if used) to cabeling errors, faulty routers/switches to defect NIC or wrong settings..

[zoraldinho]

Re: OOPS @#$% don't consult

Cable or ip conflict.

[Canuck]

Re: OOPS @#$% don't consult

Define Network Issues..unplug the cable and ping the machine's IP. If you get a response you have a address conflict. DHCP on?

[kuby]

Re: OOPS @#$% don't consult

Just a suggestion, if you have WiFi in the building and available on your network someone could have taken over the IP address of the copier. Turning Off the copier and back ON and then it prints out the documents is sometimes a sign of this. To check and make sure unplug the network cable on the copier and see if you can still ping that network address. It you can then someone's smart phone or Ipad or something has taken over that IP address and that would explain the problem you are having.

[beaker020]

Re: OOPS @#$% don't consult

one thing people do sometimes, if they are too lazy to assign a proper static ip address to a copier, is to set it to DHCP first, let it find an address and then turn DHCP off. Effectively locking the machine to the DHCP address. That is all well and good except for one thing; Eventually the router will "forget"that the printer is there and it will assign the same address to another device causing an address conflict which will produce symptoms exactly like you described.. When you reboot the device it will grab its address back from the other device, temporarily. What happens next is the 2 devices do battle for the address. The other device wins because it has authority from Mom, ie the dhcp server.

The solution is to move the copiers address outside of your dhcp scope,, I will often let dhcp do its thing, add 100 to whatever address it obtains, ping it first to make sure it is free, and then lock it in .

[JPiek]

Re: OOPS @#$% don't consult

DHCP doesn't authorise, even if it's "Mom" some still don't listen
DHCP just hands out IP adrsses, it doesn't protect them.
Loking an IP a 100 above the asigned Ip might help a bit, but only untill 101 new devices are added. The only right way to do it is to have a networkoperator reserve an IP for the printer....