Printing problems

[Guest]

We have 600 or so XP Pro machines in a Win2K domain. Today, some of the PC's
lost their ability to print. The printers could be local or network
printers. Some PC's could print to some printers, but not all. When we
tried to print, the error we received was "Some driver files are missing or
incorrect; Reinstall the driver or try using the latest version". I have
tried this with no help.

We have tried rolling XP back to dates last week. This helped with some,
but not all PC's. The PC's that it did not work on, it would work for 10
minutes or so after boot up, but then it would quit.

We have tried removing and adding it back to the domain. This helped a few
of the PC's

HELP!!!!

 

[Trey Scott]

THIS IS A VERY REAL PROBLEM!!!! I have never seen this answered, but this
and many other posts on the internet detail the same problem.

For us, we have a vlan'd out network. Several 172.16.x.0/24 networks. In
our case, building #3, all ip addresses 172.16.6.X/24 hosts are suffering
from this.

No domain PCs can plug in, add the printers as local tcp/ip printers and
work fine. We have another subnet - 172.16.10.X/24 same deal - all users are
domain users. Foriegn, NON-DOMAIN pc's can print to these printers just
fine, but DOMAIN and even removed former-domain pc's cannot. All PCs can
ping and HTTP to the printers, but cannot PRINT to them which is what they're
there for!!!!

This is two days of this - please assist!!!

Along with this, a number of users are reporting that they cannot run a
successful system restore either. We have reloaded drivers so often our
fingers have rashes on them now.

We have tried to run local "gpupdate /force" commands and that seemed to fix
ONE box, which has since broke.

This is a MAJOR, MAJOR problem. I'm a Cisco guy and they want to blame the
network (It's all Nortel equipment) but I'm telling them that if they can
ping/http, the network is good to go - there are no ACL's or firewalls. If
anyone has any idea what this is, please let me in on the big secret.

We get this same message whether trying to print to a TCP_IP port or LPT
port on these PCs. This is KILLING US.

(e-mail address removed)

 

[moogle2002]

Trey:

We found that the unidrv.dll was corrupted on the main print server, which
corrupted it on the workstations. Here is the steps that we did. The Moveon
utility is some freeware we found online that replaces files that are
normally in use upon reboot.

a) Install the utility (MoveOnBoot), then use the utility to delete the
UNIDRV.DLL and UNIDRVUI.DLL files from the
"C:WINDOWS\system32\spool\drivers\w32x86\3" folder.
b) Restart your computer after you have deleted those two files using the
MoveOnBoot utility.
c) copy the clean UNIDRV.DLL and UNIDRVUI.DLL that you copied before from
the Sp2.CAB back into the "C:WINDOWS\system32\spool\drivers\w32x86\3" folder
d) restart your computer again

If this does not work, download new drivers from HP and install them.

If this does not work, try using different drivers that are close the same
model of printer

The Unidrv files we got from extracting them from the SP2 cab, but any will
really work