Locally connected Printer shows as offline on Windows 7 network after initially working

You really didn't put much thought into that rebuttal. If the manufacturer submitted the driver late, then it would not have been in the Microsoft Update database. If they submitted a driver for test, then Microsoft added a driver that did not pass which would make it Microsoft's fault for adding a faulty driver. HP did not provided the initial Windows 7 driver on their site at all, it was ONLY available via the Microsoft Windows Update database. Which means, that if it was programmed by HP, then they did submit it to Microsoft, and they tested it, and put it on their database. If the driver was not finish, then why did Microsoft put it in their database? That makes no sense! See you keep digging yourself a hole.

Hp didn't finish the drive for testing and that is why it is faulty, but it was not on HP's website until two year later and many customer complaints about the drive in the Microsoft Windows Update database? Again, if HP is the sole faulty party for making a bad driver, then HOW did it get in the Microsoft database? Hmmm? I guess that would mean Microsoft FAILED to test it properly before adding it to their database then wouldn't it? Well since HP has NO control over Microsoft's database, that is NOT HP's fault now is it!?! Now wait just a minute, it's all HP's fault...Did HP screw up Lexmark's drivers? What about Canon and Epson? How did HP cause those companies to have faulty drivers that have to exact same problem? Wait I got it! Their must be a common thread somewhere?

Actually I do get who makes what. You clearly are not aware that Microsoft programs drivers for hardware that is not theirs. I have that direct from Microsoft tech support. (Or at least once upon a time they did...and I assume they still do.)  I have run into several specific cases where Microsoft and a manufacturer got into a pee contest over who could legally and correctly write the drivers. Canon is among the most frequent offended parties. I have had several Canon printers who's drivers got lost in litigation, which was part of why I stopped buying Canon printers

Further more You clearly missed the fact that it was not just HP. The HP 2600n was just one personal example. When it is one manufacturer or one computer, maybe it has nothing to do with the OS. Maybe you could blame the user if it was ever computer that user owns or runs. When you have five or more printer manufacturer, over 30 or more separate users/owners, in different locations with the same problem and the only common thing they have in common is the person they called to find out why the printer they have had for several years is now having problems.

I blame Microsoft because they had no answer either on support forums or when I called an paid the per instance fee for a fix. After they refunded the money because they could not fix the problem I knew where the blame laid. I contacted Microsoft by phone assuming I was missing something. I went in the support forum assuming they also missed something. Since sometimes determined users find fixes that the OS provider missed and the manufacturer also missed. I did not come to the conclusion that it was OS fault anywhere as lightly as you came to the one about HP. I assumed you don't like HP because you keep choosing to ignore the fact that I have mentioned other brands that this same problem occurs with.Since you do not like HP and think they are just bad, it has to be them, or the tech and not your precious Microsoft who is at fault.

If you read my post from the beginning, you will see that at first HP was choosing to not support that printer beyond Windows XP. Something they have done before with other mid to high end home/business equipment. Then after much clatter from customers they back down and finally offer support. That is why it took them 2 years.

I'm not a blame Microsoft first person, but I know they do screwy things. I have even called them with Windows generated error codes and had them tell my they were going to refund the pay per call fee because they knew that specific error coded existed but were not able to reproduce it in their labs and thus had no fix. Seems damn funny to me. As someone with experience coding, I know that error codes basically have an if this happens then do this setup. Programs don't generate error codes randomly.

I am not a Microsoft hater like the idiot Mac fanboys, or the Linux people. Windows may not be the OS that I liked the best, but it is what I use 95% of the time, and what my customers use. I am also not and idiot that assumes that the maker of my favorite things is perfect and never makes mistakes. I have had lemons from my favorite manufactures too. I like HP, but thought poorly of them when they bought out Compost (Compaq). I've not seen much from Compost that was work owning. So don't think I'm some HP fanboy, because I'm not.

Next time don't just read that very last post someone wrote and assume you know why they are making the claims they are. Look as see if they have most that one post and then read the other post, maybe there is a history there that will give you better insight on why they are blaming who they are blaming.

it makes sense if the driver is provided by the manufacturer and they are late in submitting it to Microsoft to be tested.

why blame Microsoft?

you say they put the new driver on their web site and it took 2 year to get it submitted to Microsoft.

why did it take that long?

could it be that the driver they provided on their web site was not finish so that they could submit it to Microsoft?

or that it did not pass the test?

and that it took them 2 year to make it pass the test?

what you don't get is that it is not Microsoft that make the device driver for the manufacturer it is the manufacturer that take care of that part or they pay a third entity to make it for them.

the only thing Microsoft provide is a basic driver to make your device basic fonction work when the device manufacturer did not make any driver for their device. that is made so that the device can work when you connect it and the driver for the device does not exist yet.

look I have often talk with support people and when they have no fix for their device they put the blame on Microsoft driver not being good. that is a lie since the driver for their device (company that make the device)they are the one that submit it to Microsoft.

I would say that something is blocking you. is the computer set to share file with other pc on the network? check the setting.

1: this could be find in the file sharing option of the shared network.

2:also another place to look is in the setting of the pc security setting if it is set to allow other pc to connect to this computer.

3: another thing that could block you is firewall you will have to find in the firewall setting what you are trying to do and where it is block and set to allow.

something more easy for you then transfer file over the network would be to copy your file to a usb memory stick or hard drive. then plug it on the other computer and send those file where you need them.