Shared printer not printing
I have a Windows 2003 domain with 2 clients: A Vista SP1 machine and a Windows 7 machine. I share a printer attached to the Windows 7 machine. The windows Vista machine can see and connect to it without error. I can print fine from the Windows 7 machine. I cannot print from the Vista machine. The print job shows in the statuswindow on the W7 machine as it should (spooling->printing->deleting), but nothing goes outto the printer... Nothing in the event viewer on either machine. I've also tried changing the setting to produce the print jobs on the client vs. not... Ideas?
January 23rd, 2009 9:47pm

Wow... No one? Really? Is there an "official" bug reporting mechanism for Windows 7, or do we just wait and hope that someone at Microsoft is actually reading and checking this stuff? There seem to be quite a few "issues" with this beta. I listen to a few tech podcasts and many people rave about the stability and "rediness" of Windows 7. They must not be actually USING it. Examples of serious issues: --Installer functionality can be crippled. Yes there is a fix in this forum, but the fact that it CAN and HAS happened is alarming! --Windows Media player corruption when Upgrading Vista to Windows 7 (cannot end the wmplayer32.exe process). I seemed to be the only person in 2.5 million users that experienced this one, though... --Windows Media Player's inability to play any DVD except bootleg or pirated ones... That's a funny one, and yes, I had to instll the VLC player to play DVD movies... --Other random problems installing some software. Symantec's Endpoint requires two manual installs and doesn't support all features. iTunes took two installs, also. I assume the first installed Quicktime, then failed the rest, then the second run skipped Quicktime (already installed) and went right into successful iTunes install. Anyway... RANT RANT RANT... Just a bit frustrated that there is so little "Official" feedback and support in these forums. Heck! Even a simple "We are aware of this problem, and are working on a solution..." post would be good. I understand what BETA means, but normally, whenever I've been in a Beta program, there is some sort of feedback system with the developers... This is sort of a Throw us in the water and see if we swim sort of thing...
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2009 6:03pm

Has anyone found a solution for this problem yet?
January 25th, 2009 8:41pm

I'll try it on my setup..brbJohnWL
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2009 8:43pm

I just tried sharing a printer from Win7beta to XP and Vista, I did not get dropped a dropped job(s). If the printer drops the job(s), then the way I would go about it is reset the printing system on Vista and Win7beta. 1) Go to control panel-> admin. tools->services. 2) scroll down to Print spooler and restart the service. 3) Make sure you are using the correct driver. If not download the lastest driver from the manf. Note: Flush the memory on the printer also. let me know if that helps. John JohnWL
January 25th, 2009 9:00pm

Wish I could help as well. I have the same setup, HP printer on the w7 comp and vista on the network. No problems though. If your print jobs on the W7 machine go through the spooler no prob, then it sounds like a driver issue on the Vista computer. Somehow something is getting messed up when the document goes to the spooler from the Vista machine.What kind of printer is it?
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2009 11:24pm

I've tried resetting print spoolers on both machines. When I send the print job from the Vista machine to the 7 machine, the PRINTER folder receives the customary two files (.SHD and .SPL), but the are zero bytes! After a few minutes they are gone... I will try to manually install the drivers, locally,to the Vista machine and direct it to the share on the 7 machine. This sort of defeats the purpose of sharing a printer and making it easy, eh? Another possible reason for this is that the 7 machine is 64bit and the Vista machine is 32 bit. I checked theAditional Drivers and only the x64 Type 3 - User Mode driver is checked. I cannot install the x86 as it asks for the ntprint.inf file from the Windows media and the media I have is apparently only 64bit, or the Windows 7 DVD structure is not in the standard format (there is no i386 folder on it). It won't accept the ntprint.inf file from the Windows\inf folder, either... This would be one of those pesky little bugs, maybe, that I was talking about. When I shared this printer from my Vista 64bit install, it was fine with the 32 Vista machine, so perhaps the print system is not complete, or someone forgot that there may actually be mixed 32/64 bit systems out there... I'll let everyone know if the manual install works. Thanks for the feedback!
January 26th, 2009 1:17am

That was it... The Vista drivers... I set up a local port to the Windows 7 share and used the Vista drivers from HP's website (latest) and it is now printing. I actually ran the full install of the drivers, skipping all the extra junk and the printer detection steps, then manually added the printer, with the local port to the share. When asked for the driver, I pointed it to the %TEMP% folder where the installer extracted it's files to (HP doesn't clean up after themselves, so it's still there). When asked, I told it to use the existing driver (Recommended) choice. Thought I'd give the full accounting of the steps in case someone else has trouble sharing from a 64bit 7 to a 32bit Vista... Thanks again for the help everyone!
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2009 1:38am

i am having kind of the same issue i have a wireless hp printer and have been able to install the software from hp on my windows 7 machine i can print on the machine for 1 day athen it goes into an offline mode and the only way to get it back is to un install it under devices and re install it this issue is also apparrent when i just use the windows 7 drivers for it as well.
July 4th, 2009 10:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics