Printer driver not installed

> I've seen this once before. The "rebuilt" machine.
>
> When you rebuilt the machine, was the OS installed into the same directory
> structure? The Win2k default directory is \WINNT. The Server 2003 default
> is \WINDOWS. If you took all the files and file shares from a backup, it's
> possible that the restored PRINT$ share in the mmc snapin for Shared Folders
> is pointing to the wrong location.
>
> PRINT$ share should be pointing to %windir%\system32\spool\drivers. The
> spooler will be installing new driver files at this location. If the PRINT$
> share points to c:\winnt\system32\spool\drivers only the files available in
> this old directory will be available to the clients. Point to the proper
> location or stop the spooler, delete the print$ entry and restart the
> spooler. The spooler service will tell the server service to add the
> correct print$ share during initialization.
>
> If this fixes your issue, get your boss to buy you an adult beverage.
>
>
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...

> > We recently rebuilt a server that was servicing shared networked printers
> > (Windows 2003 server).
> >
> > We recreated the shares with the same name and used the same printer
> > drivers
> > that we had before.
> >
> > We have quite a few XP and Win2K computers using these printers. A couple
> > of
> > our XP computers are having problems printing to one of these printers. A
> > HP
> > laserjet 4350.
> >
> > If you try to go to the properties of the printer on one of these XP
> > machines, a message comes up saying that the printer drivers are not
> > installed, do you want to install them.
> >
> > If you say NO, the properties page comes up without the General Tab and
> > you
> > can't print.
> >
> > If you say yes, you have to install printers drivers, but it doesn't help.
> > You still can't print and it again says that no printer drivers are
> > installed.
> >
> > We delete the printer, go into server properties of the XP computer
> > printers
> > and delete the printer driver, then re-install the printer through the Add
> > Printer wizard, and the same thing happens. It still says that no printer
> > drivers are installed and you can't print.
> >
> > At this time, under any user profile, you cannot get these computers to
> > print to this printer.
> >
> > We can install another printer on these computers and it works fine, and,
> > other computers, both XP and Win2k, can print to this printer (HP 4350)
> > with
> > no problems, so the printer is just fine and the drivers, which are the
> > latest, are ok.
> >
> > Any ideas on how to get these computers to be able to print to this
> > printer
> > would be appreciated. Thanks...
> >
> > Mike

>
>
>

> It was a Windows 2003 server that was re-built and it was installed into
> the
> default Windows directory. The directory structure for PRINT$ is correct
> and
> the same as it was before the re-build. All drivers and printer shares (23
> of
> them) were recreated.
>
> We have hundreds of computers using these printers but only a couple of
> Windows XP machines that have this problem. I'm pretty convinced that it's
> something with the XP machines, not the server. With these problem XP
> computers, there seems to be no way to completely delete the printer and
> re-install it. Delete it all you want, anyway that you want and they still
> say drivers not installed. Where as a computer that doesn't have this
> problem, you can delete and re-install and it works fine. I figure
> something
> in the registry is not being fully deleted on the problem computer, but I
> don't know what it is. Any thoughts?? Thanks for any help.
>
> Mike
>
>
> "Alan Morris [MSFT]" wrote:
>

>> I've seen this once before. The "rebuilt" machine.
>>
>> When you rebuilt the machine, was the OS installed into the same
>> directory
>> structure? The Win2k default directory is \WINNT. The Server 2003
>> default
>> is \WINDOWS. If you took all the files and file shares from a backup,
>> it's
>> possible that the restored PRINT$ share in the mmc snapin for Shared
>> Folders
>> is pointing to the wrong location.
>>
>> PRINT$ share should be pointing to %windir%\system32\spool\drivers. The
>> spooler will be installing new driver files at this location. If the
>> PRINT$
>> share points to c:\winnt\system32\spool\drivers only the files available
>> in
>> this old directory will be available to the clients. Point to the proper
>> location or stop the spooler, delete the print$ entry and restart the
>> spooler. The spooler service will tell the server service to add the
>> correct print$ share during initialization.
>>
>> If this fixes your issue, get your boss to buy you an adult beverage.
>>
>>
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
>> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...

>> > We recently rebuilt a server that was servicing shared networked
>> > printers
>> > (Windows 2003 server).
>> >
>> > We recreated the shares with the same name and used the same printer
>> > drivers
>> > that we had before.
>> >
>> > We have quite a few XP and Win2K computers using these printers. A
>> > couple
>> > of
>> > our XP computers are having problems printing to one of these printers.
>> > A
>> > HP
>> > laserjet 4350.
>> >
>> > If you try to go to the properties of the printer on one of these XP
>> > machines, a message comes up saying that the printer drivers are not
>> > installed, do you want to install them.
>> >
>> > If you say NO, the properties page comes up without the General Tab and
>> > you
>> > can't print.
>> >
>> > If you say yes, you have to install printers drivers, but it doesn't
>> > help.
>> > You still can't print and it again says that no printer drivers are
>> > installed.
>> >
>> > We delete the printer, go into server properties of the XP computer
>> > printers
>> > and delete the printer driver, then re-install the printer through the
>> > Add
>> > Printer wizard, and the same thing happens. It still says that no
>> > printer
>> > drivers are installed and you can't print.
>> >
>> > At this time, under any user profile, you cannot get these computers to
>> > print to this printer.
>> >
>> > We can install another printer on these computers and it works fine,
>> > and,
>> > other computers, both XP and Win2k, can print to this printer (HP 4350)
>> > with
>> > no problems, so the printer is just fine and the drivers, which are the
>> > latest, are ok.
>> >
>> > Any ideas on how to get these computers to be able to print to this
>> > printer
>> > would be appreciated. Thanks...
>> >
>> > Mike

>>
>>
>>

> When you delete the printer connection from the client, are you deleting the
> driver that the connection was using? I am assuming all the machines are
> 32bit.
>
> Bruce has some pointers on removing the print drivers
>
> http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
>
>
> Also from the client machine, open the remote print$ of the print server
>
> \\printservername\print$
>
> 10/11/2007 08:45 PM <DIR> color
> 10/10/2007 02:14 AM <DIR> IA64
> 10/22/2007 12:55 PM <DIR> w32x86
> 10/16/2007 11:42 AM <DIR> x64
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> news:01C6E3CA-DFFE-477E-BCCE-680A38F011E8@microsoft.com...

> > It was a Windows 2003 server that was re-built and it was installed into
> > the
> > default Windows directory. The directory structure for PRINT$ is correct
> > and
> > the same as it was before the re-build. All drivers and printer shares (23
> > of
> > them) were recreated.
> >
> > We have hundreds of computers using these printers but only a couple of
> > Windows XP machines that have this problem. I'm pretty convinced that it's
> > something with the XP machines, not the server. With these problem XP
> > computers, there seems to be no way to completely delete the printer and
> > re-install it. Delete it all you want, anyway that you want and they still
> > say drivers not installed. Where as a computer that doesn't have this
> > problem, you can delete and re-install and it works fine. I figure
> > something
> > in the registry is not being fully deleted on the problem computer, but I
> > don't know what it is. Any thoughts?? Thanks for any help.
> >
> > Mike
> >
> >
> > "Alan Morris [MSFT]" wrote:
> >

> >> I've seen this once before. The "rebuilt" machine.
> >>
> >> When you rebuilt the machine, was the OS installed into the same
> >> directory
> >> structure? The Win2k default directory is \WINNT. The Server 2003
> >> default
> >> is \WINDOWS. If you took all the files and file shares from a backup,
> >> it's
> >> possible that the restored PRINT$ share in the mmc snapin for Shared
> >> Folders
> >> is pointing to the wrong location.
> >>
> >> PRINT$ share should be pointing to %windir%\system32\spool\drivers. The
> >> spooler will be installing new driver files at this location. If the
> >> PRINT$
> >> share points to c:\winnt\system32\spool\drivers only the files available
> >> in
> >> this old directory will be available to the clients. Point to the proper
> >> location or stop the spooler, delete the print$ entry and restart the
> >> spooler. The spooler service will tell the server service to add the
> >> correct print$ share during initialization.
> >>
> >> If this fixes your issue, get your boss to buy you an adult beverage.
> >>
> >>
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> >> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...
> >> > We recently rebuilt a server that was servicing shared networked
> >> > printers
> >> > (Windows 2003 server).
> >> >
> >> > We recreated the shares with the same name and used the same printer
> >> > drivers
> >> > that we had before.
> >> >
> >> > We have quite a few XP and Win2K computers using these printers. A
> >> > couple
> >> > of
> >> > our XP computers are having problems printing to one of these printers.
> >> > A
> >> > HP
> >> > laserjet 4350.
> >> >
> >> > If you try to go to the properties of the printer on one of these XP
> >> > machines, a message comes up saying that the printer drivers are not
> >> > installed, do you want to install them.
> >> >
> >> > If you say NO, the properties page comes up without the General Tab and
> >> > you
> >> > can't print.
> >> >
> >> > If you say yes, you have to install printers drivers, but it doesn't
> >> > help.
> >> > You still can't print and it again says that no printer drivers are
> >> > installed.
> >> >
> >> > We delete the printer, go into server properties of the XP computer
> >> > printers
> >> > and delete the printer driver, then re-install the printer through the
> >> > Add
> >> > Printer wizard, and the same thing happens. It still says that no
> >> > printer
> >> > drivers are installed and you can't print.
> >> >
> >> > At this time, under any user profile, you cannot get these computers to
> >> > print to this printer.
> >> >
> >> > We can install another printer on these computers and it works fine,
> >> > and,
> >> > other computers, both XP and Win2k, can print to this printer (HP 4350)
> >> > with
> >> > no problems, so the printer is just fine and the drivers, which are the
> >> > latest, are ok.
> >> >
> >> > Any ideas on how to get these computers to be able to print to this
> >> > printer
> >> > would be appreciated. Thanks...
> >> >
> >> > Mike
> >>
> >>
> >>

>
>
>

> When you delete the printer connection from the client, are you deleting the
> driver that the connection was using? I am assuming all the machines are
> 32bit.
>
> Bruce has some pointers on removing the print drivers
>
> http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
>
>
> Also from the client machine, open the remote print$ of the print server
>
> \\printservername\print$
>
> 10/11/2007 08:45 PM <DIR> color
> 10/10/2007 02:14 AM <DIR> IA64
> 10/22/2007 12:55 PM <DIR> w32x86
> 10/16/2007 11:42 AM <DIR> x64
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> news:01C6E3CA-DFFE-477E-BCCE-680A38F011E8@microsoft.com...

> > It was a Windows 2003 server that was re-built and it was installed into
> > the
> > default Windows directory. The directory structure for PRINT$ is correct
> > and
> > the same as it was before the re-build. All drivers and printer shares (23
> > of
> > them) were recreated.
> >
> > We have hundreds of computers using these printers but only a couple of
> > Windows XP machines that have this problem. I'm pretty convinced that it's
> > something with the XP machines, not the server. With these problem XP
> > computers, there seems to be no way to completely delete the printer and
> > re-install it. Delete it all you want, anyway that you want and they still
> > say drivers not installed. Where as a computer that doesn't have this
> > problem, you can delete and re-install and it works fine. I figure
> > something
> > in the registry is not being fully deleted on the problem computer, but I
> > don't know what it is. Any thoughts?? Thanks for any help.
> >
> > Mike
> >
> >
> > "Alan Morris [MSFT]" wrote:
> >

> >> I've seen this once before. The "rebuilt" machine.
> >>
> >> When you rebuilt the machine, was the OS installed into the same
> >> directory
> >> structure? The Win2k default directory is \WINNT. The Server 2003
> >> default
> >> is \WINDOWS. If you took all the files and file shares from a backup,
> >> it's
> >> possible that the restored PRINT$ share in the mmc snapin for Shared
> >> Folders
> >> is pointing to the wrong location.
> >>
> >> PRINT$ share should be pointing to %windir%\system32\spool\drivers. The
> >> spooler will be installing new driver files at this location. If the
> >> PRINT$
> >> share points to c:\winnt\system32\spool\drivers only the files available
> >> in
> >> this old directory will be available to the clients. Point to the proper
> >> location or stop the spooler, delete the print$ entry and restart the
> >> spooler. The spooler service will tell the server service to add the
> >> correct print$ share during initialization.
> >>
> >> If this fixes your issue, get your boss to buy you an adult beverage.
> >>
> >>
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> >> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...
> >> > We recently rebuilt a server that was servicing shared networked
> >> > printers
> >> > (Windows 2003 server).
> >> >
> >> > We recreated the shares with the same name and used the same printer
> >> > drivers
> >> > that we had before.
> >> >
> >> > We have quite a few XP and Win2K computers using these printers. A
> >> > couple
> >> > of
> >> > our XP computers are having problems printing to one of these printers.
> >> > A
> >> > HP
> >> > laserjet 4350.
> >> >
> >> > If you try to go to the properties of the printer on one of these XP
> >> > machines, a message comes up saying that the printer drivers are not
> >> > installed, do you want to install them.
> >> >
> >> > If you say NO, the properties page comes up without the General Tab and
> >> > you
> >> > can't print.
> >> >
> >> > If you say yes, you have to install printers drivers, but it doesn't
> >> > help.
> >> > You still can't print and it again says that no printer drivers are
> >> > installed.
> >> >
> >> > We delete the printer, go into server properties of the XP computer
> >> > printers
> >> > and delete the printer driver, then re-install the printer through the
> >> > Add
> >> > Printer wizard, and the same thing happens. It still says that no
> >> > printer
> >> > drivers are installed and you can't print.
> >> >
> >> > At this time, under any user profile, you cannot get these computers to
> >> > print to this printer.
> >> >
> >> > We can install another printer on these computers and it works fine,
> >> > and,
> >> > other computers, both XP and Win2k, can print to this printer (HP 4350)
> >> > with
> >> > no problems, so the printer is just fine and the drivers, which are the
> >> > latest, are ok.
> >> >
> >> > Any ideas on how to get these computers to be able to print to this
> >> > printer
> >> > would be appreciated. Thanks...
> >> >
> >> > Mike
> >>
> >>
> >>

>
>
>

> Well.... I've been through Bruce's document and tried the cleanspl.exe to
> no
> effect. Cleanspl.exe cleared out all printers, then install this printer
> and
> the same thing happens. You try to use the printer and it says, "printer
> driver not installed, do you want to install one", and around and around
> we
> go. All other printers setup on this computer work fine, just this one is
> a
> problem. Any other suggestions? Thanks for your help.
>
> Mike
>
> "Alan Morris [MSFT]" wrote:
>

>> When you delete the printer connection from the client, are you deleting
>> the
>> driver that the connection was using? I am assuming all the machines are
>> 32bit.
>>
>> Bruce has some pointers on removing the print drivers
>>
>> http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
>>
>>
>> Also from the client machine, open the remote print$ of the print server
>>
>> \\printservername\print$
>>
>> 10/11/2007 08:45 PM <DIR> color
>> 10/10/2007 02:14 AM <DIR> IA64
>> 10/22/2007 12:55 PM <DIR> w32x86
>> 10/16/2007 11:42 AM <DIR> x64
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
>> news:01C6E3CA-DFFE-477E-BCCE-680A38F011E8@microsoft.com...

>> > It was a Windows 2003 server that was re-built and it was installed
>> > into
>> > the
>> > default Windows directory. The directory structure for PRINT$ is
>> > correct
>> > and
>> > the same as it was before the re-build. All drivers and printer shares
>> > (23
>> > of
>> > them) were recreated.
>> >
>> > We have hundreds of computers using these printers but only a couple of
>> > Windows XP machines that have this problem. I'm pretty convinced that
>> > it's
>> > something with the XP machines, not the server. With these problem XP
>> > computers, there seems to be no way to completely delete the printer
>> > and
>> > re-install it. Delete it all you want, anyway that you want and they
>> > still
>> > say drivers not installed. Where as a computer that doesn't have this
>> > problem, you can delete and re-install and it works fine. I figure
>> > something
>> > in the registry is not being fully deleted on the problem computer, but
>> > I
>> > don't know what it is. Any thoughts?? Thanks for any help.
>> >
>> > Mike
>> >
>> >
>> > "Alan Morris [MSFT]" wrote:
>> >
>> >> I've seen this once before. The "rebuilt" machine.
>> >>
>> >> When you rebuilt the machine, was the OS installed into the same
>> >> directory
>> >> structure? The Win2k default directory is \WINNT. The Server 2003
>> >> default
>> >> is \WINDOWS. If you took all the files and file shares from a backup,
>> >> it's
>> >> possible that the restored PRINT$ share in the mmc snapin for Shared
>> >> Folders
>> >> is pointing to the wrong location.
>> >>
>> >> PRINT$ share should be pointing to %windir%\system32\spool\drivers.
>> >> The
>> >> spooler will be installing new driver files at this location. If the
>> >> PRINT$
>> >> share points to c:\winnt\system32\spool\drivers only the files
>> >> available
>> >> in
>> >> this old directory will be available to the clients. Point to the
>> >> proper
>> >> location or stop the spooler, delete the print$ entry and restart the
>> >> spooler. The spooler service will tell the server service to add the
>> >> correct print$ share during initialization.
>> >>
>> >> If this fixes your issue, get your boss to buy you an adult beverage.
>> >>
>> >>
>> >>
>> >> --
>> >> Alan Morris
>> >> Windows Printing Team
>> >> Search the Microsoft Knowledge Base here:
>> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
>> >> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...
>> >> > We recently rebuilt a server that was servicing shared networked
>> >> > printers
>> >> > (Windows 2003 server).
>> >> >
>> >> > We recreated the shares with the same name and used the same printer
>> >> > drivers
>> >> > that we had before.
>> >> >
>> >> > We have quite a few XP and Win2K computers using these printers. A
>> >> > couple
>> >> > of
>> >> > our XP computers are having problems printing to one of these
>> >> > printers.
>> >> > A
>> >> > HP
>> >> > laserjet 4350.
>> >> >
>> >> > If you try to go to the properties of the printer on one of these XP
>> >> > machines, a message comes up saying that the printer drivers are not
>> >> > installed, do you want to install them.
>> >> >
>> >> > If you say NO, the properties page comes up without the General Tab
>> >> > and
>> >> > you
>> >> > can't print.
>> >> >
>> >> > If you say yes, you have to install printers drivers, but it doesn't
>> >> > help.
>> >> > You still can't print and it again says that no printer drivers are
>> >> > installed.
>> >> >
>> >> > We delete the printer, go into server properties of the XP computer
>> >> > printers
>> >> > and delete the printer driver, then re-install the printer through
>> >> > the
>> >> > Add
>> >> > Printer wizard, and the same thing happens. It still says that no
>> >> > printer
>> >> > drivers are installed and you can't print.
>> >> >
>> >> > At this time, under any user profile, you cannot get these computers
>> >> > to
>> >> > print to this printer.
>> >> >
>> >> > We can install another printer on these computers and it works fine,
>> >> > and,
>> >> > other computers, both XP and Win2k, can print to this printer (HP
>> >> > 4350)
>> >> > with
>> >> > no problems, so the printer is just fine and the drivers, which are
>> >> > the
>> >> > latest, are ok.
>> >> >
>> >> > Any ideas on how to get these computers to be able to print to this
>> >> > printer
>> >> > would be appreciated. Thanks...
>> >> >
>> >> > Mike
>> >>
>> >>
>> >>

>>
>>
>>

> So the driver installs when you make the connection, but when you actually
> try to print to the device, there is an error stating that the driver is not
> installed.
>
> I've seen this for some HP drivers when updating them but the issue was
> resolved when one first deleted the print driver then installed the new one
> as the old driver registry value where not compatible with the new driver.
>
> I assume you are using the HP Laserjet 4350 PCL 6 driver. What is the
> driver version? Find the installation inf file from where you installed the
> driver on the server, then look for DriverVer=
> HP format is like this
> 60.043.41.00
>
> --
> Alan Morris
> Windows Printing Team
> Search the Microsoft Knowledge Base here:
> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> news:CD351C11-A6B0-4F7A-83DB-737078688152@microsoft.com...

> > Well.... I've been through Bruce's document and tried the cleanspl.exe to
> > no
> > effect. Cleanspl.exe cleared out all printers, then install this printer
> > and
> > the same thing happens. You try to use the printer and it says, "printer
> > driver not installed, do you want to install one", and around and around
> > we
> > go. All other printers setup on this computer work fine, just this one is
> > a
> > problem. Any other suggestions? Thanks for your help.
> >
> > Mike
> >
> > "Alan Morris [MSFT]" wrote:
> >

> >> When you delete the printer connection from the client, are you deleting
> >> the
> >> driver that the connection was using? I am assuming all the machines are
> >> 32bit.
> >>
> >> Bruce has some pointers on removing the print drivers
> >>
> >> http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm
> >>
> >>
> >> Also from the client machine, open the remote print$ of the print server
> >>
> >> \\printservername\print$
> >>
> >> 10/11/2007 08:45 PM <DIR> color
> >> 10/10/2007 02:14 AM <DIR> IA64
> >> 10/22/2007 12:55 PM <DIR> w32x86
> >> 10/16/2007 11:42 AM <DIR> x64
> >>
> >> --
> >> Alan Morris
> >> Windows Printing Team
> >> Search the Microsoft Knowledge Base here:
> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> >> news:01C6E3CA-DFFE-477E-BCCE-680A38F011E8@microsoft.com...
> >> > It was a Windows 2003 server that was re-built and it was installed
> >> > into
> >> > the
> >> > default Windows directory. The directory structure for PRINT$ is
> >> > correct
> >> > and
> >> > the same as it was before the re-build. All drivers and printer shares
> >> > (23
> >> > of
> >> > them) were recreated.
> >> >
> >> > We have hundreds of computers using these printers but only a couple of
> >> > Windows XP machines that have this problem. I'm pretty convinced that
> >> > it's
> >> > something with the XP machines, not the server. With these problem XP
> >> > computers, there seems to be no way to completely delete the printer
> >> > and
> >> > re-install it. Delete it all you want, anyway that you want and they
> >> > still
> >> > say drivers not installed. Where as a computer that doesn't have this
> >> > problem, you can delete and re-install and it works fine. I figure
> >> > something
> >> > in the registry is not being fully deleted on the problem computer, but
> >> > I
> >> > don't know what it is. Any thoughts?? Thanks for any help.
> >> >
> >> > Mike
> >> >
> >> >
> >> > "Alan Morris [MSFT]" wrote:
> >> >
> >> >> I've seen this once before. The "rebuilt" machine.
> >> >>
> >> >> When you rebuilt the machine, was the OS installed into the same
> >> >> directory
> >> >> structure? The Win2k default directory is \WINNT. The Server 2003
> >> >> default
> >> >> is \WINDOWS. If you took all the files and file shares from a backup,
> >> >> it's
> >> >> possible that the restored PRINT$ share in the mmc snapin for Shared
> >> >> Folders
> >> >> is pointing to the wrong location.
> >> >>
> >> >> PRINT$ share should be pointing to %windir%\system32\spool\drivers.
> >> >> The
> >> >> spooler will be installing new driver files at this location. If the
> >> >> PRINT$
> >> >> share points to c:\winnt\system32\spool\drivers only the files
> >> >> available
> >> >> in
> >> >> this old directory will be available to the clients. Point to the
> >> >> proper
> >> >> location or stop the spooler, delete the print$ entry and restart the
> >> >> spooler. The spooler service will tell the server service to add the
> >> >> correct print$ share during initialization.
> >> >>
> >> >> If this fixes your issue, get your boss to buy you an adult beverage.
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Alan Morris
> >> >> Windows Printing Team
> >> >> Search the Microsoft Knowledge Base here:
> >> >> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >> "MLWDFW" <MLWDFW@discussions.microsoft.com> wrote in message
> >> >> news:8A60A900-BF74-4EFF-916E-3575ACEFD439@microsoft.com...
> >> >> > We recently rebuilt a server that was servicing shared networked
> >> >> > printers
> >> >> > (Windows 2003 server).
> >> >> >
> >> >> > We recreated the shares with the same name and used the same printer
> >> >> > drivers
> >> >> > that we had before.
> >> >> >
> >> >> > We have quite a few XP and Win2K computers using these printers. A
> >> >> > couple
> >> >> > of
> >> >> > our XP computers are having problems printing to one of these
> >> >> > printers.
> >> >> > A
> >> >> > HP
> >> >> > laserjet 4350.
> >> >> >
> >> >> > If you try to go to the properties of the printer on one of these XP
> >> >> > machines, a message comes up saying that the printer drivers are not
> >> >> > installed, do you want to install them.
> >> >> >
> >> >> > If you say NO, the properties page comes up without the General Tab
> >> >> > and
> >> >> > you
> >> >> > can't print.
> >> >> >
> >> >> > If you say yes, you have to install printers drivers, but it doesn't
> >> >> > help.
> >> >> > You still can't print and it again says that no printer drivers are
> >> >> > installed.
> >> >> >
> >> >> > We delete the printer, go into server properties of the XP computer
> >> >> > printers
> >> >> > and delete the printer driver, then re-install the printer through
> >> >> > the
> >> >> > Add
> >> >> > Printer wizard, and the same thing happens. It still says that no
> >> >> > printer
> >> >> > drivers are installed and you can't print.
> >> >> >
> >> >> > At this time, under any user profile, you cannot get these computers
> >> >> > to
> >> >> > print to this printer.
> >> >> >
> >> >> > We can install another printer on these computers and it works fine,
> >> >> > and,
> >> >> > other computers, both XP and Win2k, can print to this printer (HP
> >> >> > 4350)
> >> >> > with
> >> >> > no problems, so the printer is just fine and the drivers, which are
> >> >> > the
> >> >> > latest, are ok.
> >> >> >
> >> >> > Any ideas on how to get these computers to be able to print to this
> >> >> > printer
> >> >> > would be appreciated. Thanks...
> >> >> >
> >> >> > Mike
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>

>
>
>