Wondows 7 32 bit Print Issues

[mojorolla]

I have got a bit of a pickle here.
Typical office, 9 PCs (Windows 7 32 and 64 bit) , print drivers installed and shared from the server (2008 r2). Install was flawless, all drivers were found at the workstations without issue. As I moved onto the scan to email setup, a woman pulled me aside and said her job did not print. I went to her PC, and sure enough, default was set to the old machine. So, I click to set default, and it gives me an error 0X00000709, odd. So I open the queue and attempt it from there, same thing.
Now here is where it gets interesting.
It will print from Word and from the internet, but I have to select it from the drop down menu. In Excel, it says "printer not installed, select another", at which point I cannot select any printers listed. From Outlook, it codes to "no printer installed, please install a printer" I have uninstalled and tried installing it locally, stopping the print spooler on the PC and the server, pinged and used the copier web page, changed ports from RAW to LPR, checked the cables, and a few reboots. It is only the one PC, all others work fine.
I did find a few posts concerning tweaking the Windows registry but being a customers PC, I am not at liberty to do that.
Any one seen anything like this before????

[mojorolla]

Re: Wondows 7 32 bit Print Issues

Great....I spelled Wondows in the title....

[sandmanmac]

Re: Wondows 7 32 bit Print Issues

I'd try installing the printer locally on the problem PC, but beyond that, it's obviously a PC issue, and not your problem, in my opinion

[ZOOTECH]

Re: Wondows 7 32 bit Print Issues

Great....I spelled Wondows in the title....

HA HA

[nmfaxman]

Re: Wondows 7 32 bit Print Issues

Did you load the 32 bit driver in the 64 bit share under additional drivers in the share?

Wondows (snicker). You finger f*#ed yourself.
Almost as funny as frimware.

[MFPTech]

Re: Wondows 7 32 bit Print Issues

[I went to her PC, and sure enough, default was set to the old machine]

First, I will not give the new machine the same IP as the old one
Second, I will uninstall (properly) the driver of the old machine before installing the driver of the new one.

Cheers,

[mrwho]

Re: Wondows 7 32 bit Print Issues

As Sandmanmac clearly (and rightly so, IMHO) pointed out, it's not your problem, you should hand it over to TI.

Anyway, if you want to try out something that shouldn't hurt, try to eliminate all the printers from Wondows (*snicker!*), remove the drivers from the server properties and then, after a reboot, try to reinstall the old thing.

[MFPTech]

Re: Wondows 7 32 bit Print Issues

[I went to her PC, and sure enough, default was set to the old machine]

First, I will not give the new machine the same IP as the old one
Second, I will uninstall (properly) the driver of the old machine before installing the driver of the new one.

Cheers,

Third, I will not touch servers. Copier techs do not get paid enough to work on servers, and, normally, customers that have servers and no IT are cheap and have a crappy network.

[mojorolla]

Re: Wondows 7 32 bit Print Issues

I sent their IT guy your ideas and a few links I found. It's their PC, their problem.

Thank you all for your replies.

The old machine drivers were all installed locally. I prefer a server because everything is set once and it takes 2 minutes at each machine. In an office with 50-100 PCs, it saves a huge chunk of time; sometimes days.

As to money, I do very well. The reason being all those years as a technician doing things I wasn't paid for.

[dickierock]

Re: Wondows 7 32 bit Print Issues

I have had something similar,printers drivers dropping from network on windows 7 machines.Seemed to happen when for instance the paper ran out or some other issue,then the driver just greyed out(offline) and not come back to ready. There seems to be a bit of advice out there to for these types of issues to "untick" SNMP in the port configuration of the driver.Work for me so far.

[mramlawi]

Re: Wondows 7 32 bit Print Issues

its a pc problem ,looks like some virus man , it happened with me lots ,this is an virus

[NatSass]

Re: Wondows 7 32 bit Print Issues

As you mentioned here it definitely should be your PC issue. So better check your PC again and see weather problem solved.

[rthonpm]

Re: Wondows 7 32 bit Print Issues

I have had something similar,printers drivers dropping from network on windows 7 machines.Seemed to happen when for instance the paper ran out or some other issue,then the driver just greyed out(offline) and not come back to ready. There seems to be a bit of advice out there to for these types of issues to "untick" SNMP in the port configuration of the driver.Work for me so far.

Some network administrators will disable SNMP traffic as a security precaution. It can also cause trouble with drivers with built-in status reporting sending prompts for low toner, jams, etc to all users. I generally always uncheck SNMP on all installs unless it's absolutely needed.

[TheOwl]

Re: Wondows 7 32 bit Print Issues

I know this thread is getting a bit stale, but I thought I better input my 2 cents worth:

The problem is from corruption in copying the driver from the server and seems to happen from more 2008 Servers than anything else. As the client PC copies the driver from the server, either there is packet loss or packet corruption. To fix this issue, you must remove the print driver correctly:

1. Devices and Printers
2. Remove the print queue associated to your problem machine
3. Click on another printer
4. Click on Print Server Properties
5. Click on Drivers
6. Select the driver in question
8. Remove
9. Remove Driver and Driver Package

Once you have done that, you can now start fresh as though the printer and driver were never installed. If you find that it happens again, then do the above again and then do the following:

1. Devices and Printers
2. Add Printer
3. Local Printer
4. Use the LPT1 port
5. Have Disk
6. Point to the driver you used on the server (ie, driver files saved on USB drive or network share)
7. Finish
8. Now add the print queue that is on the server.

The above method gets around the possible cause of driver corruption on installation from the server's print share. As the driver has already been installed on the PC, then there is no need for the PC to request the drivers from the server.

I know alot you say "Not our problem" when it comes to things like this, but I have recently given my techs a stir up about this as it does quite often make you look bad, especially when you get asshole IT people who find out that they fucked up, but decide to blame it on the copier because they won't know any better. Half of my role where I work is purely solving issues like this where IT people blame us, so I go in and make sure that the IT people end up looking like dicks!!!

The easiest thing to do is to relay information to the IT people and make sure that you have a decent crack at resolving the issues yourself. After all, the more time you spend on the issue the first time, the more likely you are to resolve really quickly the next time without IT's help.

[MFPTech]

Re: Wondows 7 32 bit Print Issues

I know this thread is getting a bit stale, but I thought I better input my 2 cents worth:

The problem is from corruption in copying the driver from the server and seems to happen from more 2008 Servers than anything else. As the client PC copies the driver from the server, either there is packet loss or packet corruption. To fix this issue, you must remove the print driver correctly:

1. Devices and Printers
2. Remove the print queue associated to your problem machine
3. Click on another printer
4. Click on Print Server Properties
5. Click on Drivers
6. Select the driver in question
8. Remove
9. Remove Driver and Driver Package

Once you have done that, you can now start fresh as though the printer and driver were never installed. If you find that it happens again, then do the above again and then do the following:

1. Devices and Printers
2. Add Printer
3. Local Printer
4. Use the LPT1 port
5. Have Disk
6. Point to the driver you used on the server (ie, driver files saved on USB drive or network share)
7. Finish
8. Now add the print queue that is on the server.

The above method gets around the possible cause of driver corruption on installation from the server's print share. As the driver has already been installed on the PC, then there is no need for the PC to request the drivers from the server.

I know alot you say "Not our problem" when it comes to things like this, but I have recently given my techs a stir up about this as it does quite often make you look bad, especially when you get asshole IT people who find out that they fucked up, but decide to blame it on the copier because they won't know any better. Half of my role where I work is purely solving issues like this where IT people blame us, so I go in and make sure that the IT people end up looking like dicks!!!

The easiest thing to do is to relay information to the IT people and make sure that you have a decent crack at resolving the issues yourself. After all, the more time you spend on the issue the first time, the more likely you are to resolve really quickly the next time without IT's help.

To ask your techs for server installations I hope you give them a server in the demo room, time to practice and pay them extra for IT calls because you must charge the customer extra for server installation. Then you have to take the liability for any server-related issues that customer will complain because "all happened after the tech touched the server".

My approach is to hand over to the customer's IT the driver CD/DVD that comes with the machine and offer to work together if they need help, not to argue or compete with them. If the IT insists that it does not work and it's a deal breaker then I will use my virtual server to demonstrate in the presence of my manager. If there is no IT, I won't touch the server because, as I have said it before, the networks with a server and no IT are most likely screwed up. In this case I will do peer to peer installation and I will show/guide an end user how to install the driver.

Cheers,