I have two Ricoh printers/copiers setup for IP printing in the office.
Before this week there were no problems printing to them.
Now a handful of them (All running Vista, not sure if it is every Vista computer or not, It seems like I would hear more from users if that was the case), see both printers as being offline. All the PC's running XP have no problems printing. When this first occurred a reboot was able to get the printer to appear online, but that is no longer the case. (and at the time I thought only one computer was having the issue) I have removed the printers, reinstalled the latest drivers and there is no change on the Vista machines. I am currently using the same version of a RPCS driver on both VISTA and XP. As a work around I could setup the printers on a 2003 Server, but I don't see why IP printing should just stop working out of the blue like this. The printer can be reached by IP from all computers and the web interface is accessible and reports no errors.
Does anyone have any ideas?

  • Do the "Standard TCP/IP Ports" on both the Vista and XP machines have the SNMP option enabled and the community set the same way? Jun 11, 2009 at 15:11
  • That is a big 10-4.
    – notandy
    Jun 12, 2009 at 20:39

13 Answers 13


If all else fails, you can disable SNMP monitoring in the printer's TCP port properties. You won't be notified when the printer becomes ACTUALLY offline, but you won't get false positives anymore.

  • 2
    This also happens if the SNMP community string is anything other than "public" Jan 26, 2012 at 17:42


We've seen somewhat similar issues here, but outside of a few high-end plotters that we print directly to IP for, we're hosting the rest of them off of a printserver, and your symptoms are not exactly the same as what we've seen, but close enough. I've got a few ideas for you, in the hopes that they'll help but nothing really conclusive :)

1.) Try restarting the local print spooler service on the workstation in question. (ex: net stop "Print Spooler" && net start "Print Spooler"). See if that has any effect.

2.) Navigate to the driver properties of the printer, on the workstation, select "Advanced", select "Print Processor", try setting "WinPrint" to RAW, or changing to MS_XPS and select RAW.

3.) Check the port on the local workstations that the printer is configured to use, is it valid or did it mysteriously dissapear? (We've seen THAT one before. Man, what a pain!)

4.) It's a long-shot, but see if a local firewall is blocking it. Disable any local firewall/ip filtering and test to see if it works. We've seen this before, but specifically in this situation: We're running Symantec EndPoint on all workstations and in some instances, the local Windows default firewall was showing as enabled and running and doing some funky, funky blocking. :)

Either way, good luck!

  • it is 2018 and this is still an issue. Your net stop start worked for me , many many thanks!
    – rob
    Jun 26, 2018 at 8:22

Restarting Print Spooler service on the client did the job. Restarting the service on the server didn't work.

Our network: Win7Ultimate 64bit + a bunch of Win7Pro 64bit without domain, only workgroup.


Did you change the default snmp community (public) ? Put it back online through the file menu once the printer is opened (or right click on it first.)

  • Nope, no changes to the SNMP. Toggling offline/online makes no difference.
    – notandy
    Jun 12, 2009 at 15:59

I could resolve the issue by starting the SNMP Trap service which I had disabled manually (Windows 7).


This vista forum has two suggestions, one is to try and setup the printer port as 'persistent' using the dos command

net use LPT1 \\[printservername]\P1 /persistent:yes

The other is to apply the hotfix #934455 available from microsoft. This should be included in SP1.

Another site suggests restarting the Print Spooler service, which should reset the offline status. Also in the properties of Print Spooler / Recovery try setting the 'Recovery on Subsequent failures' to Restart. The default is it stops restarting after 2 failed attempts.

  • They are running SP2.
    – notandy
    Jun 12, 2009 at 15:59
  • Did you try the other suggestions? Jun 12, 2009 at 19:35
  • I am not using a print server so that eliminate net use. I tried restarting the print spooler service and it didn't fix the issue.
    – notandy
    Jun 12, 2009 at 20:38
  • But are you still using IP printing, so it still creates a virtual port. Jun 12, 2009 at 21:16

I had the same problem with a 2008 Server machine (basically Vista Light), I had to reboot it before it would print. Talk about aggravation. There is a registry setting hidden deep within the bowels of HKLM

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Hardware Profiles\0001\System\CurrentControlSet\Control\Print\Printers\

Find the offending printer entry, then find the entry named.


Edit it. Changing it to the magical value of


This makes my cry for CUPS ... or even lpr ...

  • Hmm, I'll have to check this out.
    – notandy
    Jun 12, 2009 at 20:41
  • 1
    If you try it, don't use HKLM\System\ControlSet001, but HKLM\System\CurrentControlSet, which is a link to the ControlSet that is actually active on your machine.
    – Massimo
    Jun 15, 2009 at 21:50

In my case printer was seen by windows 7 as offline when someone was trying to print using wireless lan. In wire lan everything was ok and also it worked on Linux even withs wireless lan connection.

I found out that widows 7 use snmp to determine printer state, after unblocking snmp communication (of course only for printer) on our firewall it works perfectly whether client is in wire or wireless network and on with every OS.


Had the exact same issue in W2K3. I unchecked the snmp option and the printer went back online. (Had the regedit as well.)


Had the exact same issue in server W2K8 also. Local network, no routers, no filters, no firewalls, no natting. All on the same broadcast segment. Since last friday (5/24) all network printers stopped printing from the printer queue in the server. Restart print spool service had no effect. Unchecking the snmp option in the server's port settings did the job.


I found i had disabled SNMP in the web interface and had changed the SNMP community name on the printer when i reenabled, as soon as i changed it back to public to match the communication port settings on the printer driver. It came back online.


An update to my laptop's antivirus software which contains a firewall ended up being the culprit. It started blocking the spooler service after the update. I had to allow the spooler service access through the firewall and it started working fine again.


the problem might be that your router is reassigning the ip that the printer has acquired. this might be because you turn off your printer after use and also your router. you only have to reassign an ip to your printer and my advice is that you reserve it by your router.

and never face this problem again.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .