Windows 7 x64, Domain connected unable to install network printer
We are in the process of migrating to Windows 7 and this will include at least 1000 64bit machines. During the testing we have found that once we join the Windows 7 x64 computer to the domain we are unable to install any network printers that are hosted on our Windows 2008 x86 print server. When we try to connect we immediatly recieve the following error: "Windows couldn't connect to the printer. Check the printer and try again. If this is a network printer, make sure that the printer is turned n, and that the printer address is correct" All our Windows 7 x86 computers can install this same printer without any issues. The printer has been configured to include the x64 drivers and will install on a non domain connected Windows 7 x64 computer. We did find a reference somewhere that suggested uninstalling "Client for Microsoft Networks" and then reinstalling it. Suprising this actually works however I don't really see this as a suitable solution when we are doing automated builds and deployments. Has anyone else come accross this problem and do you have a better way to fix the issue?
November 18th, 2010 2:48am

To resolve this kind of issues, there are several methods. I suggest you use one of the following two ways. Method 1: Download universal drivers that are compatible with bit 32bit and 64bit systems. Then reinstall the printers with these drivers on server, share and deploy them. I suggest you go to Microsoft Update Catalog to search the drivers. Method 2: Install printers on one Windows 7 64bit client and deploy the printers from it. Step1: Install the network and shared printers 1. Click Start, click Control Panel and double click Devices and Printers. 2. Click Add a Printer. 3. Select "Add a local printer". 4. Select "Create a new port". Choose "Local Port" as the type of the port. 5. In the box "Enter a port name", type the address as the following format. \\<IP address of the host computer>\<The Share Name of the printer> Or \\<IP address of the network printer> Then click Next. 6. Select the correct driver in from the driver list. If the required driver is not present, click the “Windows Update” button. After the update finishes, search for the proper driver again. If you have downloaded the driver and extract the package to local drive, click “Have Disk” to locate to the proper *.inf file. Step 2: Deploy the printers. 1. Open Print Management in the Windows 7 system . 2. In the Print Management tree, select the local computer under the “Print Servers”, click Printers. 3. In the results pane, right-click the printer you want to deploy, and then click Deploy with Group Policy. 4. In the Deploy with Group Policy dialog box, click Browse, and then choose a Group Policy object. 5. To assign the printer connection setting to the GPO, do one or both of the following: As a per-user setting, select the The users that this GPO applies to (per user) check box. As a per-machine setting, select the The computers that this GPO applies to (per machine) check box. Arthur Xie TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2010 2:33am

Thanks for your reply Arthur however these options will not help me. As I mentioned in the original post I have installed the x64 drivers on the server and I can successfully add the printer to a Windows 7 x64 computer prior to it being in the domain. Once I add a Windows 7 x64 computer to the domain I can no longer add the printer without first uninstalling and reinstalling "Client for Microsoft Networks". This to me says there is no problem with the way the printer is configured and shared on the server. I have a workaround in place where I add a computer to the domain and uninstall and reinstall "Client for Microsoft Networks" prior to running sysprep and capturing the image. However I only see this as a workaround and was hoping someone knew what causes the issue and knows of a more permanent fix
November 21st, 2010 9:53pm

I know that you have installed x64 drivers on the server. However, please note that the driver will not be loaded properly by x64 clients if you do not add and deploy a printer with that driver. Have you tried my suggestions? With either method you will not need to turn off and turn on Client for Microsoft Networks.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 1:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics