Windows 7 64-bit printing to HP2035N printer - printer won't stop
I've got a new machine running 64-bit Windows 7 Home Premium, and I'm trying to print to a network-connected HP LaserJet 2035. The printer is connected to the machine via a TCP/IP port. When I print something, it keeps printing it over and over and over and won't stop. The printer status screen just keeps resetting. I've gotten the latest drivers from HP and done all the Windows updates. No help. This machine replaced a Win XP Pro machine that worked fine in the same configuration. Two other Windows XP machines work fine on it. It installs fine, Windows 7 finds the printer on the network, I get no error messages that anything is wrong, ever. I'm stumped. I'd appreciate any advice. Thanks in advance for your help. Kevin Semi-geek
September 18th, 2010 2:56pm

Hi kwg58, Appears like a driver problem. The only available drivers that I located were these: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=18972&prodSeriesId=3662025&swItem=lj-76599-1&prodNameId=3662049&swEnvOID=4063&swLang=8&taskId=135&mode=4&idx=3 They are usb drivers, where you install them first, cancel when it asks you to connect the usb cable, then run the add printer, networked printer wizard. I would attempt the installation again. Uninstall the printer, then any software in the programs list, and try the above steps. Install the driver package and cancel out. Use the wizard from Start>Devices and Printers>add a printer. Have the IP address available for the wizard if it doesn't auto-detect. Sure it will work on XP fine, it's an XP era printer with specific drivers and software.
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2010 8:31am

Nano, Those are the drivers I was using. I deleted everything and reinstalled them, and now things work fine. Thanks for your help. Now let me vent, just to get some things off my chest. I'm not some kid... I installed my first Windows printer in Windows Release 2. I installed my first networked printer in Windows for Workgroups 3.11. I've worked with Novell, Win NT, Win 2K/2K3/2K8, and a couple of versions of Unix/Linux. It drives me nuts how the vendor drivers change how things work so often, sometimes with the drivers for different printers from the same vendor installed differently in the same operating system. I've downloaded a driver file, expanded its contents to a folder, and pointed to that folder to find the driver when installing the printer. I've downloaded driver files as .exe files that added the drivers to the Windows registry so that they were available as printers in the Windows dialog used to select printer drivers doing the "Add a Printer" wizard (the one with the vendor in the left pane and the specific devices in the right pane). Now all of a sudden the driver files run a program that installs the drivers, but they don't show up on any of the "add printer" dialogs in Windows, so you don't know if these programs have actually worked. It's extremely annoying, and I wonder what people who don't have my experience and/or don't know how to navigate TechNet or forums like these handle these situations. You mention that these are "USB" drivers, and you're right. But the device has a USB port AND an RJ45 network connection, but the driver installation doesn't seem to be able to handle connecting the driver to a network-attached printer. That's just inexcusable on the vendor's part. I'm not looking to let Microsoft off the hook here, either. I ran the "find a network printer" wizard in Windows 7 six times as part of this process; it only found this printer three times, and it NEVER found another printer attached to an XP machine on this network. That's inexcusable. I know I complained about how the driver installation procedures change without warning or notification, but it also annoys me that another thing hasn't changed. When I learned to connect to a network printer by installing a Local TCP/IP port in Windows NT or 2000, I figured it was just a workaround for something new and somewhat exotic, and would be fixed. Ten+ years down the line, we're still doing it that way because Microsoft still hasn't fixed a really stupid interface design problem to make it possible to easily install a type of devicee that is no longer new and no longer exotic. It makes no sense at all. Aaargh. OK, I've vented and feel better now. Thanks for your help. Kevin Semi-geek
September 21st, 2010 11:13am

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

Other recent topics Other recent topics