This hotfix is also available at Microsoft Update Catalog. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article.
This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article.
If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix.
For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows 7 or Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:. The global version of this hotfix installs files that have the attributes that are listed in the following tables.
The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Important Windows 7 hotfixes and Windows Server R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. Being "Apple crazy," my son asked me to get an Apple Airport Extreme wireless router. And my lively wife, basically trying to keep our son happy how weak!
She also claimed, unconvincingly I might add, that routine web access was too slow. This from a woman who just learned how to use e-mail a year or so ago and when asked why she never responds to text messages says "I don't know how. And - key to this story - it has a USB port for a printer to make the printer available to all who are on the network.
So Apple claims, and so Apple's instruction and installation booklet claims. I went to Best Buy, after learning that Apple products apparently never go "on sale," bought the thing, followed all the instructions, installed it, and everyone has access to the internet wirelessly and his games seem to be working fine - faster he claims.
But the wireless USB printer function did not work. It works very well with Macs. I tried some of the "solutions" on those forums, to no avail including solutions from "experts" who proposed solutions that users later said did not work - sound familiar? One thing I learned was that you have to find information that is relevant to the operating system on the computer you are having trouble with.
A "fix" that works with Windows XP might not work on a system running Windows Vista, and the same thing might well be true for systems like my office laptop using Windows 7 Enterprise. I often do not see this bit of information on message boards like this, but I do think it is important to make sure the "solutions" you are reading about are geared to the operating system you are using.
This is a long, rambling post, but I hope this little piece of advice makes this post acceptable here. My "fix" was just to skip the router at least I thought that would be my "fix". My printer worked on all computers before. My home "users" and I am the one who uses the printer the most just connected the printer to their computer with the USB cable and everything worked fine.
So, I thought, I should be able to get a new "wireless" printer, which I hoped would act just like a printer actually connected to the computers. I bought an HP wirless printer.
Remember the IT wizard who said the solution was to buy an HP printer? This has worked for two of the computers in our house so far. I used the CD that came with the printer to install the software and printer. There are no "offline" problems with those two computers.
Both of those computers have Windows Vista. Then I tried to do the same thing with my office laptop, which has Windows 7 Enterprise. Unfortuantely, I cannot use the CD installation method.
It seems I do not have "administrator" privileges to do this, and based on past experience, I know better than to call the company help desk for assistance.
I will get a responses like "We do not allow installation of unapproved software" and "that software has not been tested to make sure it does not cause problems with the rest of our system," or a more likely IT solution, "go to the office and print your document. They simply cannot be bothered with individual problems like this. The company actually encourages us to work from home a couple days a week, and everyone knows we need to print something once in a while.
It seems as if the IT guys do not trust us amateurs. But, I was able to "add a printer" through the Windows system. I hope my company's IT people are not reading this, or otherwise they will block my ability to "add a printer," because, after all, I might screw up the computer. I "added the printer," printed a test page as instructed, printed out a couple other sample documents, and everything was working fine at first.
This was puzzling. I went to my other computer mine - where I do have administrator privileges and where I was able to use the installation CD , and was able to print a document wirelessly while the office computer said the printer was "offline. I did notice that at one point, the printer itself apparently "went to sleep. Does my office laptop think my printer is all of a sudden "offline" when it "goes to sleep"? Although my own PC can "wake the printer up" and print something, maybe the office computer is unable to do this.
And so that resulted in the Google search that lead me to this forum. I checked my printer properties, and sure enough, this box is checked. That seemed to work for a few folks, and it sure sounds like the easiest solution if it works. If that does not work, I will try one of the other simpler "fixes. And I am not going to follow the IT wizard's proposal to go buy another HP computer based on his word that this is a good "fix.
This worked well for a long time, and it will work well again. Next step? Or next problem, I should say? That will be my wife's office laptop. Her company likewise does not trust anyone enough to give out "administrator" privilege passwords. We will see if we can get the printer to work from her computer. The printer itself had been "asleep" since Sunday the only light on was the wireless indicator. I started up the computer, opened the printer control screen, and it looked like the computer was "alive" again.
I opened a Word document, and was able to print it. The printer was no longer "offline. I had dismissed any suggestions to use a "reboot" as a fix, because I had tried that on Sunday a couple of times, to no avail.
I waited a couple hours, opened Word again, and was able to print another document. Then I left the machine on all night, and was able to print a document again this morning. We'll see how this works in the future, but for the time being there is no need to uncheck the SNMP box.
This goes to show you that solutions that work for some do not work for all, and that an originally tried solution might work if tried again. Go figure. John has moved to a different team, and I am one of the engineers that has been working on this offline printer issue for many months now. If all of the previous troubleshooting has not provided relief, then there is a good chance you are hitting the issue this hotfix addresses.
We found that this issue occurs because a restricted client thread detects an offline print server. When a client thread detects that a print server is offline, Windows registers a polling loop to check the status of the print server. After the polling loop is registered, Windows queries the print server periodically to check whether it is back online.
In rare cases, a client thread that has a restricted token detects that a print server is offline. In this situation, Windows registers the polling loop in the context of this thread.
However, the thread does not have sufficient rights to query the print server. Therefore, the polling request fails. Restarting the spooler or the client machine will obviously kill this thread running under the restricted context and will query the server with the correct security. I am having the same problem. My scenario is fairly straightforward: 2 Windows 7 64bit machines.
This has been OK for months and months. However, something recently has caused a problem, and both printers now appear as offline on Machine B. I can only assume a Windows update has caused the issue as nothing else is installed on these machines they are office computers in a garage.
So I have tried most of the suggestions on this thread apart from the registry tinkering! Also I can't turn off SNMP for the printers as suggested by many, I get the "cannot configure port" option if I select the printer port and press the "configure" button.
I checked the "turn windows features on or off" and SNMP isn't even enabled. A question more for cmarcho really Or just the one you posted July 11th ? I'm able to connect to the administration interface of the printer via a browser, but can not get this printer 'online'. This is the only solution that has worked for me. While it may be a workaround, it is not difficult to implement. Ultimately, the problem is with Windows 7, and as of this writing Windows 8 is due soon, so I doubt if Microsoft will ever issue a fix.
In fairness, I've used Windows 7 for several years and did not have this issue until recently, so I assume there must be some update or software combination causing the problem and not an inherent bug in Win7. This post is a complete waste of time. Most of us here are professionals and understand how to properly add a printer to a network, which you obviously dont. We don't need you to tell us about how you did it wrong and tried to print to an IP address which has since been used by another device.
This is not amature hour. There is a real problem with the spooler in Windows 7 which apparently now has a hotfix to address the issue. Hi, I suggest you install both. The is a hotfix rollup that includes many updates to the print components.
This may show the printer back online again. If restarting the spooler does not work for you, then you have a different issue than what most are discussing, from what I can tell.
Wow - to say that this post is not an interesting read would be an understatement. Almost like watching an episode of Dallas or something. And to figure that it lasted from Oct 5 to current is pretty amazing and there still for me anyway is not a solution to the issue at hand. I too am in the same boat. We are slow to the show though - we held off on W7 till the last minute. My Domain is split across physically distant facilities - the Primary AD controller is in the main facility - and I have a secondary one at the remote facility.
All working via VPN tunnels between the facilities. We started adding W7 Pro to main facility about 2 years ago, and have no issues like this at all. Added four to the remote location a couple of months ago - and this issue has raised its ugly head.
And even though I am late to the game, my issue seems to be a bit different than yours with some similarities - I believe it is an Administration issue along with some networking issue solely on the Win7 computer. Here is what started happening at my locations:. Users cannot print to a statically assigned network printer from their W7 computers it calles them Offline. The users cannot print from W7 - however - if they remote to their RDP session hosted at the Main facility - it is printing back this network with out issue.
So too are the WXp pro computers in this facility. So naturally I try to Ping the printer - cannot. Even Try Pinging the printer with an Admin run console using the ping -4 to get rid of the IP6 crap and it intermittently works, but eventually fails. It will work for a spell, then fail after trying the different things here have not gotten to the updates yet, but that will be next on my list.
Personally never learned to use SNMP - so it is useless to me anyway. But I think this issue goes deeper. Still does not address the issue. If running your printer in DHCP mode works for you albeit it temporary rock on - but you may have issues down the road. It is interesting that the original Poster ED never replied again after his original post. Wonder if he found a fix? At the same time it is also shunning the AD controller in this facility - not the main one, just its own - so now all authentication requests are going to main facility across the VPN and this printer is shunned.
Any way still fighting the good fight. Since these folks at the remote facility are all remote anyway and use RDP to access the main production environment, should just wipe all their PC's and put Ubuntu on them. That would certainly fix things faster than this running around in circles chasing my tail approach that has been going on so far. Since most of the printers I was replacing were year old Lexmark crap I didn't really have a difficult time getting funding for that. Secondly, this is a prime example of why I won't let my clients buy anything other than HP.
In all my years of doing this I have to say that every time I've allowed a client to buy something other than an HP printer, it's come back to bite us in the ass. It's just not worth it. HP works all the time every time. At least that my experience. In addition we found that on certain devices, giving the user local admin rights and assigning those rights to the printer, that the problem was also corrected.
I don't have issues with RDP printers, again, if you use HP printers most of them are natively supported so there are no issues. For the majority of the time as long as you are not buying their low end based home models - they work very well and last forever if taken care of. Which is why I would like to keep this HP LJ Color printer that has worked flawlessly through the years and is being shunned by these Windows 7 computers for what ever reason Windows 7 thinks they should be shunned.
But when every other computer that is not W7 in the network continues to print fine to this printer, I find it hard to justify replacing it with another 1K printer. If I do find one, an answer that is I will surely post it here. I would LOVE to lease my gear and roll it every three or five years trying to stay on top of the MS upgrade path, but it is just not financially feasible nor do I want to keep relearning or becoming re-certified every time MS decides to change something that was working perfectly fine before as they decided to improve it - hey just like this hosed up windows 7 networking stack that cannot even reliably ping another host in the same subnet without disabling everything, making all users admins and editing the registry times.
Well so much for that - now Ill just grovel and plead and see if any one has experienced something similar to what I am seeing and what it might be. It was working for a little bit, just like it does each time. Till the user needs it, then it gone doing the same thing again. Here is what I am looking at now 4 Command Prompts on three computers. This may be different from what you guys were experiencing, maybe I got a wacky switch or some thing but all are stupid unmanaged switches from Netgear.
Before, I was only seeing the W7's Request time out. Now I am seeing even the XP's intermittently time out. I am experiencing a similar problem, but our printers are connected to a 2k8 Print server, the windows 7 clients which connect to them continue to show the print queues as going offline.
We have tried disabling SNMP, restarting the printers and the print service, and the computers Yup tried that too - and I think just like the disabeling of SNMP on the Client, it only keeps the printers from reporting anything like that its offline - it is still offline, and cannot communicate to the printer, but without SNMP the printer and the client cannot tell each other that.
So in my situation it only made every other client in the network unable to tell if the toner was low while still leaving the W7 computers offline. Today gonna take a look at hardware - yesterday when I would reset my unmanaged switch the XP computer would ping for a spell - made me think something might be getting wacked in the routing. Not sure its picking on this printer, or main from W7 clients, but something is afoot.
Could not agree more, glad I don't have such a setup. These folks were originally set up by an IT consultant. We are talking about maybe 7 PC's and two printers total. They never should have been set up with a Domain in the first place considering they are a remote office and really do not need that level.
They are easily managed with manual process - well - they were anyway until I started adding these W7 PC's. I need to verify that I am not chasing hardware that is causing the W7 clients to drop the networking sooner than the XP's before I totally bash the OS.
Ping statistics for Interface: Request timed out. Reply from OK so hows this for whack a doo - My printer is connected to a small netgear 5 port switch as is one of the W7 PC that is experiencing this issue. As a means to eliminate hardware I started switching things around today suspecting a goofy cheap switch and on this W7 computer hooked to the little 5port switch as I said earlier, I tried a second netgear 5 port and a little Cisco ASA on these connections and was getting the same results - the mac address of the broken printers are getting set to the GW mac address.
When I tried remove the arp entry I could not - each time I delete it popped back up - guessing the Print Spooler was recreating these entries, I did the following:. Wouldnt relesh having to do this on more than one PC let alone numerous -then again, if this is the problem, and its occuring on a print server - I suppose you would only have to statically create it once.
One final note - using the typical arp -s does not hang around after a reboot and I was right back where I was before. So I ended up doing:. When the computer boots, I have the printers that we un-pingable and therefore unreachable and Offline comming right up with the computer.
Not sure what the heck is doing this, again if some one sees something in my noob networking please let me know, as I would like to find out what the heck made this happen and I dont think I should have to be adding static arp entries in Windows 7. Started to suspect it was the Universal print driver. When we started using 64 bit computers, there were not a lot of 64 bit drivers and we ended up using the HP Universal PLC5 6 was always causing problems 5 seemed more stable.
Guess just for simplicities sake, it was easier to just use it rather than anything else. Found out there is a Windows Update for the 64 drivers and this printer is in the update.
Tried that updateing the drivers - same thing when the printer checks to see if the printer is still there, it ends up setting the GW mac address to the ip address rather than its own. It must be the nic card on the printer. Think I just do not want to succumb to the cost of new one for an application specific one. Could try and swap out the jet direct card, but why on a discontinued model - would have to go with Codewize on this one.
Sorry to have been blathering on this post today, but I figured I could use it later to document my findings later. Ok folks, thanks for allowing me to blather on in this post.
Seems my issue was probably not the same as what you guys were experiencing, but in the end this is what I learned - so I will post this final bit and stop pestering you good people! My issue was routing. This was causing intermittently mind you the printer [and even once or twice the AD controller in this facility] to set the mac addresses on a client PC as the router mac address rather than the mac address of the device it was supposed to be - which made w7 flag the printer as Offline - even though I could ping from other devices that had the correct addressing - with connectivity issues always check the arp table first - was one of the last things I did, haven't messed with arp since configuring printers the old fashion way many moons ago.
Since doing this i have not seen the issue again, and my ping requests have also started responding much faster.
I also learned to always assimilate - use the windows drivers when you can - i was ready to chuck a very expensive HPLJ N printer - yes this is a dinosaur, but after replacing the 64bit HP Universal drivers with the windows 7 64 drivers - it is running like a new printer. This was accomplished by using windows update while adding the printer to check for new available drivers every time I add a printer.
Now that process leaves a bit to be desired, but I think you can also get the drivers at this address: catalog. Restarting the print spooler worked for me as well on Windows 7 Pro SP1 bit. To restart the print spooler:. The solution I found to the printer is offline when its not is bypasses all of the Microsoft BS and is a simple solution. First, make sure the printer is connected to the network. Second, configure the settings on the printer to a static IP address. Next, add the printer to devices manually.
Last, Print a test page to verify the solution. This solution bypasses all of the printer drivers and software crap and sends the document straight to the printer. It is also possible that the print spoler needs to be rest. The best way to resolve this problem is to go to you control panel, then select devices and printers. I have one printer, Win 7 64 bit, Canon MP I hate to update I can tell that this issue can occur for multiple reasons so it's not easy to come up with a single solution.
One of the things that works almost every time is to reinstall or update the driver in case there is new version. Another thing that might help sometimes is to restart the printer spooler service. I think this last issue mostly occurs when changes are made to the printer's SNMP settings. I tried pinging from the server - did not work either strange - I was pinging the port instead of the actual printer ip!!
I connected to the server on the client computer via the search button on windows lower left button. Got into the server, clicked on the network printer. Printer said connecting to host, after a couple of seconds the printer queue opened up.
Clicked on file and printer was on-line. I suspect a DNS issue of some kind but unclear, hope this helps. This was a basic ping and search kind if way instead of messing with settings. I hope you can assist me, as I have a similar problem to this and hopefully the following will make sense.
Our PC is running 64 bit windows 7 whereas the pharmacy PC's are running 32 bit, not sure if this is relevant? We have various installations that are running in pharmacies, our installation is behind a Cisco firewall and consists of various PC's, the main one is now running under Windows 7.
It talks to the pharmacy computers via the firewall, with the PC's having a label printer connected via USB. Obviously as I am dealing with remote sites and I do not have access to the client PC's only ours, so it is difficult to make changes to the Pharmacy PC. I have tried a few things from this site but nothing has worked, so does anyone have any ideas, as I can definitely make changes on our PC?
I would suggest going to the printer properties and selecting the 'ports' tab, then click the 'configure port' button and from their remove the 'check' from the button that states 'SNMP Status Enabled' to disable SNMP.
This will take a matter of seconds and your print jobs will start printing as the printer will go from 'offline' to 'online' as soon as you apply this change. One share deployed as default for the site has colour printing disabled. One showing 'Ready', one 'Offline'. I'd tried several slightly different reinstallations of the printer, but every single time the printer would initially appear as 'Ready' but go offline after seconds and remain in that state no matter what.
Anyway, I changed the community name to the one we use for printers and therefore the one that was in the settings on the actual printer and it instantly came back to 'Ready'. I am having this same printer offline issue on a windows 7 32bit machine.
I am using an IP port. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question. Quick access.
Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Networking. Sign in to vote. We are having an unsuaual problem all of a sudden printing to networked printers from Windows 7 clients.
XP and Vista clients print as usual. Windows 7 clients say the printers are offline. I'm sure I was able to print from Windows 7 clients last week. Monday, October 5, PM. Hi, First, I would like to confirm how the printer is connected and what the model of the printer is.
If it persists, try removing and reinstalling this printer: 1. Wednesday, October 7, AM. I'm having a similar problem in Windows 7 Ultimate.
I have a shared network printer that's an HP LJ - this thing has been around since the stone age and works fine - the driver has been bundled with every version of Windows since 95 I think. Everybody in my workgroup can print to the printer just fine, but if I RDP to my main workstation running Windows 7, then next time I log in through the console, the HP LJ which is my default printer shows up as offline even though all the other workstations and server can print fine, so the printer isn't offline at all.
I can connect to the server fine and I can delete the printer, but I can't reinstall it until the workstation reboots. Alternately, a reboot is required to show the printer back online again. I used to have a similar problem in Vista Ultimate when I would login remotely via RDP but then it would only clear the default printer flag, so I'll I had to do was re-select it as the default printer.
This is very annoying. Jeff Balcerzak. Tuesday, February 2, PM. I was having the same issue with Windows 7 bit Ultimate. For some reason the port changes. Had to go in any manually reset the IP address from Sunday, February 7, PM. Monday, March 22, AM. I am having this same problem with windows Vista and two different computers, one a Dell Laser the other an HP office Pro. Wednesday, July 21, PM. I am having this problem as well. I have been able to get the printers to show online again by restarting the print spooler.
Does anyone have a fix? I have Windows 7 Ultimate bit. Saturday, December 11, AM. Dear Vivian, I don't think you are solving any problem. Sunday, December 19, PM. Thanks again! Sunday, February 13, PM. Bottom line is this issue needs to be fixed before I commit my entire network computers to Windows 7 Pro - - Or tell me how to get them to online status so I can print and not have to use my Big Chief tablet and 2 pencil - - - Howard.
Tuesday, February 22, PM. Friday, February 25, PM. Problem seems to be fixed with Win7 SP1 update I installed this morning. Let's see if this update fixes the problem for others who have posted here. Seth Thomas. Proposed as answer by wags Tuesday, May 24, PM. Monday, March 7, PM. Windows 7 Miscellaneous. Use this forum to discuss miscellaneous issues that cannot be covered in any other Windows 7 forum.
Sign in to vote. The problem is that Windows never puts the printer back into an online state after the printer becomes reachable again. First of all, if this is a limitation of Windows, it should be addressed.
Any reply in regards to this issue will be greatly appreciated, however, I do not need an answer that does not really answer the question or gives a convoluted response to what should be a simple fix, thanks. Thursday, June 25, PM. Hi IT Did the issue occur with other printers except the HP printer? Best regards Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
Friday, June 26, AM. Monday, June 29, AM. Hey MeipoXu, Thanks for your response, I have tested the hotfix listed in the Microsoft Support article for Windows 7 and it does seem to fix this issue. Friday, June 26, PM.
0コメント