nico-
asked on
Cross Forest Printing
Hello
I'm setting up a print server for Company A. Company A requires its (migrated) users to print via the print server in Company B. Do I add the printers on the print server in Company A to point to the relevant print queue on the print server on Company B?
Any ideas anyone ?
Thank you
I'm setting up a print server for Company A. Company A requires its (migrated) users to print via the print server in Company B. Do I add the printers on the print server in Company A to point to the relevant print queue on the print server on Company B?
Any ideas anyone ?
Thank you
If you don't want to setup a trust, you can enable LPR on Company A's print server and LPD on Company B's print server. Then you create print queues on Company A's print server to point to existing print queues on Company B's print server. This eliminates all issues with authentication/having to have a trust between domains.
If you are interested in this path, just let me know the OS version of both print servers and I can give you specific instructions.
If you are interested in this path, just let me know the OS version of both print servers and I can give you specific instructions.
ASKER
Thanks eerwalters
There's a Forest Trust setup, but they want the printing path to be
printer client Company A -> Print Queue on Print Server Company A -> Print queue on Print Server Company B -> Print Device Company B
User in Company A will receive the printer from Group Policy Preferences from Company A GPO.
Easier ways of doing it, but this is the way they want it to happen.
OS : Windows 2008 R2 Company A -
Windows 2003 or 2008 R2 Company B
There's a Forest Trust setup, but they want the printing path to be
printer client Company A -> Print Queue on Print Server Company A -> Print queue on Print Server Company B -> Print Device Company B
User in Company A will receive the printer from Group Policy Preferences from Company A GPO.
Easier ways of doing it, but this is the way they want it to happen.
OS : Windows 2008 R2 Company A -
Windows 2003 or 2008 R2 Company B
ASKER
Eerwalters
I suppose the ultimate question is what is the method of creating print queue's on Company A's servers to point to existing print queues on Company B's print servers when there *is* a trust in existence ?
Thanks for your help
I suppose the ultimate question is what is the method of creating print queue's on Company A's servers to point to existing print queues on Company B's print servers when there *is* a trust in existence ?
Thanks for your help
The creation process for print queues on workstations and how you choose to deploy the printers does not not change in either environment with LPR setup between the print servers.
The only thing that changes is that the output from the print queues on Company A can send to the print queues on Company B without having to have any trust. If you have a trust, it does not effect the LPR/LPD transfer of print jobs.
I'll create the instructions this afternoon and post them.
The only thing that changes is that the output from the print queues on Company A can send to the print queues on Company B without having to have any trust. If you have a trust, it does not effect the LPR/LPD transfer of print jobs.
I'll create the instructions this afternoon and post them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello
My mistake. Company A PS to Company B Print Device. Good solution though and good to know. Thanks! Points imminent
My mistake. Company A PS to Company B Print Device. Good solution though and good to know. Thanks! Points imminent
ASKER
Very quick to respond and details. Thanks for the other chap who replied. Not quite what I was after.
You can still use the solution to point directly to a printer at Company B, just:
Remove
Steps 1 and 2
Replace
Step 5g = Use the TCP/IP address of the printer
Step 5h = Use "raw" without the quotes.
(This is assuming that the printer supports LPR and that it is not disabled. Most do support it and are enabled by default.)
Only port 515 would need to be open between the Company A print server and the desired printer at Company B.
Remove
Steps 1 and 2
Replace
Step 5g = Use the TCP/IP address of the printer
Step 5h = Use "raw" without the quotes.
(This is assuming that the printer supports LPR and that it is not disabled. Most do support it and are enabled by default.)
Only port 515 would need to be open between the Company A print server and the desired printer at Company B.
ASKER
Thanks
Would LPD/LPR still be used over the standard new printer creation in the windows 2008 server ? i thought that was more a UNIX solution or a workaround? Performance is the benefit to using this approach rather than the standard MS approach?
Would LPD/LPR still be used over the standard new printer creation in the windows 2008 server ? i thought that was more a UNIX solution or a workaround? Performance is the benefit to using this approach rather than the standard MS approach?
The only thing that we are varying in this scenario is the outbound connectivity from the print queue to the printer. The inbound connectivity to the print queue from the workstations is still the same.
Using LPR per the instructions above does provide a less chatty protocol for talking with the printer than the default settings for the Standard Port Monitor in Windows. LPR is also very fast. However, you can disable the SNMP monitoring in a standard windows setup to make it less chatty too.
LPR/LPD is a UNIX standard that has been around for years and so it is compatible with just about everything that you want to have talk to each other for printing purposes. I personally prefer to use LPR on the inbound side of the print queue too and make the print queues be binary pass-through queues. That turns them into traffic cops for just directing print jobs to their destinations and does not touch the contents of the print job. That setup also eliminates the driver lockup issues that normal Windows servers experience. That's an entirely different solution than what we have been referring.
Back to your issue. The solution that I suggested will work for printing to the Company B print servers (regardless of whether there is a trust or not) or directly to the Company B printers (with the instruction modifications). However, there is no reason that you can't use the standard Windows setup (Standard TCP/IP printing) to the Company B printers if they will allow the Company A print server to connect to them.
(...meaning vs printing thru the Company B print servers as they would have to allow the Company A print server to connect directly to the printers for LPR too)
I personally would prefer handing off print jobs from one print server to the other as it:
1- only requires 1 firewall rule between the print servers for Company A to print to every printer at Company B
2- makes your troubleshooting easier as once it's handed off, it's the responsibility of Company B to insure that the print job is delivered to the printer
3- is easier to isolate any problems caused by print jobs from Company A (if I were responsible for Company B printing)
Using LPR per the instructions above does provide a less chatty protocol for talking with the printer than the default settings for the Standard Port Monitor in Windows. LPR is also very fast. However, you can disable the SNMP monitoring in a standard windows setup to make it less chatty too.
LPR/LPD is a UNIX standard that has been around for years and so it is compatible with just about everything that you want to have talk to each other for printing purposes. I personally prefer to use LPR on the inbound side of the print queue too and make the print queues be binary pass-through queues. That turns them into traffic cops for just directing print jobs to their destinations and does not touch the contents of the print job. That setup also eliminates the driver lockup issues that normal Windows servers experience. That's an entirely different solution than what we have been referring.
Back to your issue. The solution that I suggested will work for printing to the Company B print servers (regardless of whether there is a trust or not) or directly to the Company B printers (with the instruction modifications). However, there is no reason that you can't use the standard Windows setup (Standard TCP/IP printing) to the Company B printers if they will allow the Company A print server to connect to them.
(...meaning vs printing thru the Company B print servers as they would have to allow the Company A print server to connect directly to the printers for LPR too)
I personally would prefer handing off print jobs from one print server to the other as it:
1- only requires 1 firewall rule between the print servers for Company A to print to every printer at Company B
2- makes your troubleshooting easier as once it's handed off, it's the responsibility of Company B to insure that the print job is delivered to the printer
3- is easier to isolate any problems caused by print jobs from Company A (if I were responsible for Company B printing)
Trust between 2 forest should resolve your issue. Below is more details about same.
Printing to printer on a different domain
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/7409f43a-1118-4c0b-8144-2995d8562f30
http://community.spiceworks.com/topic/98440-sharing-printers-across-domains