Re: same USB printers cause new hardware detection



Terry R. <F1ComNOSPAM@xxxxxxxxx> wrote:
The date and time was 5/21/2008 7:45 AM, and on a whim, smlunatick
pounded out on the keyboard:

On May 21, 10:14 am, "Terry R." <F1ComNOS...@xxxxxxxxx> wrote:
On one network I admin, we have over a dozen laptops used for
"check-in" purposes. When I configure them for printing, I use
just one of the printers, all of which are identical. Whenever
many of them are used, I would get reports that printing didn't
work. Yesterday I reconfigured 3 laptops with one printer and checked
okay. Yet when a user hooked 3 laptops to 3 printers, two of them
wouldn't print. I was onsite at the time and found that Windows
had re-installed drivers and created copies of the printer and the
default printer no longer would print at all. A few of the laptops
still have LPT1 ports and printing that way isn't an issue. Only
USB. What would cause Windows to see each of these printers differently
even though they are all the same make and model (Zebra TLP
2844-Z)? As a last resort, I guess we can mark each laptop
specifically for a printer, but that is a PIA, since there are many
staff that also use their laptops occasionally and if someone else
is using "their" printer, they're out of luck.

Thanks for any suggestions,


This is caused by the Plug and Play (PnP) system. Each and every
printer would have their own unique device ID and the PnP system will
re-install the newly detected printer. One possible way is to
connect these printers to a print server on the network. These
laptops would not detect the printer and you would need to configure
the IP address(es) to access these printer.

Thanks for the response. Unfortunately, these need to be mobile so
using a print server won't work. It looks like USB isn't "plug &
play" at least in this situation.

Well, it *is* plug and play, but each printer is a new one to the computer
the first time you connect it. You haven't really explained what doesn't
work. So you connect a printer, it detects it, and it doesn't print at all?





.



Relevant Pages

  • Re: Limited User Printer Issue
    ... Direct IP printing is, printing directly to a network printer, versus going through the print server. ... It will be fine for the rest of the day, but when they log back onto their laptops using their credentials, the issue returns. ...
    (microsoft.public.windows.server.general)
  • Re: same USB printers cause new hardware detection
    ... When I configure them for printing, ... Yesterday I reconfigured 3 laptops with one printer and checked ... I was onsite at the time and found that Windows ... I can't expect the users to go through the process to reset the Windows default printer, open the Check-in program and select a new printer every time another one is detected by Windows. ...
    (microsoft.public.windowsxp.general)
  • Re: Limited User Printer Issue
    ... JohnB wrote: ... Direct IP printing is, printing directly to a network printer, versus going through the print server. ... It will be fine for the rest of the day, but when they log back onto their laptops using their credentials, the issue returns. ... When trying to select the printer properties via the Printers and Faxes dialog box... ...
    (microsoft.public.windows.server.general)
  • Re: Limited User Printer Issue
    ... There are no credentials required. ... Direct IP printing is, printing directly to a network printer, versus going through the print server. ... It will be fine for the rest of the day, but when they log back onto their laptops using their credentials, the issue returns. ... When trying to select the printer properties via the Printers and Faxes dialog box... ...
    (microsoft.public.windows.server.general)
  • Re: same USB printers cause new hardware detection
    ... When I configure them for printing, I use just one of the ... Yesterday I reconfigured 3 laptops with one printer and checked okay. ... these need to be mobile so using a print server won't work. ... It looks like USB isn't "plug & play" at least in this situation. ...
    (microsoft.public.windowsxp.general)