Quantcast
Channel: Print/Fax forum
Viewing all articles
Browse latest Browse all 3156

Printers are not able to communicate with the server

$
0
0

Printers are not able to communicate with the server.

The printers are greyed out on the transfered "to" computer.

I used printbrm to copy printer configuration from one workstation to another using the following commands:

This creates a PrintBRM data file named OT.Print.printerExport saved to the c:\temp folder

"C:\windows\System32\Spool\Tools\Printbrm -b -f c:\temp\OT.Print.printerExport -o Force"

This restores a Printers using PrintBRM data file named OT.Print.printerExport saved to the "c:\temp" folder

"C:\windows\System32\Spool\Tools\Printbrm -r -f c:\temp\OT.JCKL.First.printerExport -o Force"

-----------------------

Used Symantec's Ghost to put the same build on the workstaions in question.

The user has administrator rights to the worstation and print server.

The initial printer setup for the workstation involves creating a "local port" such as \\server_name\queue_name: Add a Printer-->Add a locol Printer-->Create a new port:Local Port--> Enter a port name: \\server_name\queue_name. After clicking OK, I attach the printer associated with that queue.

After logging off then back on to the workstation with the printbrm copy, the printers are greyed out (meaning, the local printers don't see the print server).

When I try to manually create the port and upon clicking the OK button, I receive a "Port \\server_name\queue_name already exists>" message. Also, these created ports are not visiable in the port tab of the printer properties GUI.

I wanted to send to message off to you before checked the registry configurations and get feed back using some VB scripts.

Any suggestions or guestions?


Viewing all articles
Browse latest Browse all 3156

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>