When I take a domain based computer (Windows XP) and plug it into a network that doesn't have access to the AD, the first time I select a local printer (printing directly to printer) on the current network it takes a good 20-30 seconds before I can select the printer. Doing a little investigating using wireshark I can see the computer is trying to hit AD for some reason and it just keeps timing out. I also tried the same experiment with just a plain workgroup computer and it was able to bring the printer up immediately. Does anyone know how to prevent the machine from trying to contact AD?
Asked
Active
Viewed 398 times
1
-
The printer is not shared or published in AD. – Mar 16 '10 at 11:00
-
1Are you logging in with cached credentials, or a local account? – Chris Thorpe May 12 '10 at 09:00
1 Answers
0
Manually add the printer using a local TCP/IP port. This will make your client to point directly to the printer IP but of course you will lose the printer server queue management advantages as you are printing directly to printer.
Regards, D.
Danilo Brambilla
- 1,031
- 2
- 14
- 33