Printing from terminal server to client
Hi,
I would like to print to from a terminal server back to a client computers local label printer.
The label printer will be connected to the client machine via USB and will be printing to a Generic Text Driver. I have found that when bringing across the printers via the RDP client that they do not appear on the terminal server through the session. Yes, I have installed the driver on both client and TS computers.
I would like to setup a TCP/IP port which prints via LPR to the client computer. I have heard this is a more reliable way to print over the internet back to clients local printer, RDP mapping the local printer in its session is not too consistent.
I have the option of using a netgear print server instead of USB on the label printer to connect on the client side.
Am I right in saying that on the client side. If I add a TCP/IP printer port and assign it to the printer server IP address of the label printer, then forward port 515 from my router to the print server. Create a dyndns address for the client side internet connection.
Terminal Server Side: Add a printer via a new TCP/IP port and type in the name of the dyndns address of the client connection as the IP address. Then select custom and use LPR with a print queue name of "LP", along with a generic text print driver.
With this setup, when I connect from the client to the terminal server and want to print from an application to the label printer, will this all work correctly?
Is this the right way to acheive reliable internet printing? Can someone please explain the steps?
Thank you...
I would like to print to from a terminal server back to a client computers local label printer.
The label printer will be connected to the client machine via USB and will be printing to a Generic Text Driver. I have found that when bringing across the printers via the RDP client that they do not appear on the terminal server through the session. Yes, I have installed the driver on both client and TS computers.
I would like to setup a TCP/IP port which prints via LPR to the client computer. I have heard this is a more reliable way to print over the internet back to clients local printer, RDP mapping the local printer in its session is not too consistent.
I have the option of using a netgear print server instead of USB on the label printer to connect on the client side.
Am I right in saying that on the client side. If I add a TCP/IP printer port and assign it to the printer server IP address of the label printer, then forward port 515 from my router to the print server. Create a dyndns address for the client side internet connection.
Terminal Server Side: Add a printer via a new TCP/IP port and type in the name of the dyndns address of the client connection as the IP address. Then select custom and use LPR with a print queue name of "LP", along with a generic text print driver.
With this setup, when I connect from the client to the terminal server and want to print from an application to the label printer, will this all work correctly?
Is this the right way to acheive reliable internet printing? Can someone please explain the steps?
Thank you...
ASKER
Ok, what I have done so far is this...
Print Server side: Fowarded both ports 9100 & 515 to printers IP address x.x.x.x.
Client Computer: Added a new printer using a standard TCP/IP port with the internet IP addess of the router my print server is connected to. I have selected RAW with port 9100 in the custom options. I have installed the correct driver from the manufacturers website.
Tried a test page and it goes to the print queue then receives an error. The print job constantly restarts itself and receives a print error until I physically cancel it from the queue.
Is there something I am getting wrong here?
Print Server side: Fowarded both ports 9100 & 515 to printers IP address x.x.x.x.
Client Computer: Added a new printer using a standard TCP/IP port with the internet IP addess of the router my print server is connected to. I have selected RAW with port 9100 in the custom options. I have installed the correct driver from the manufacturers website.
Tried a test page and it goes to the print queue then receives an error. The print job constantly restarts itself and receives a print error until I physically cancel it from the queue.
Is there something I am getting wrong here?
Why do you use the IP addrss of the router instead of that of the printer? The port will send direct to the printer, not to the router. Please change the Standard TCP/IP port to use the printer's IP address
ASKER
The terminal sever is located at a different physical location to the client computer which is logging into the TS. They each have internet connections and sperate routers. The printer I am trying to print to is located on the client side.
I want to create a port on the TS side to print via TCP/IP, over the internet, hit the client side router, and have the router forward the packets to the printers IP address on the client side.
I am doing this so that when I login to the terminal server from the client (over the internet), I can print back to my local printer.
Sorry for the misunderstanding.
I want to create a port on the TS side to print via TCP/IP, over the internet, hit the client side router, and have the router forward the packets to the printers IP address on the client side.
I am doing this so that when I login to the terminal server from the client (over the internet), I can print back to my local printer.
Sorry for the misunderstanding.
ASKER
The router is transparent to the network traffic. You need to send the packets to the printer and that's why the Standard TCP/IP Port you create has to use the IP address of the printer. The Standard TCP/IP Port uses the LPD (port 515) or Appsocket (port 9100) protocols, which are printer protocols, and have nothing to do with the router.
Have you tried giving the Standard TCP/IP port the IP address of the printer?
The only thing you may have to do is to make sure the router does not block those ports. Some routers are set that way, but again this has nothing to do with the IP address used in the Standard TCP/IP port.
Have you tried giving the Standard TCP/IP port the IP address of the printer?
The only thing you may have to do is to make sure the router does not block those ports. Some routers are set that way, but again this has nothing to do with the IP address used in the Standard TCP/IP port.
ASKER
Did you see the diagram????????
How can I add a printer to the terminal server (TCP/IP port) and send it to 192.168.1.50 on a totally different network across the internet??? It wont work!
How can I add a printer to the terminal server (TCP/IP port) and send it to 192.168.1.50 on a totally different network across the internet??? It wont work!
ASKER
Internet routers will trash any packets destined for a private IP....
ASKER
I do not have a VPN...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you want to print from the server, all you need to do is create a standard TCP/IP port on the server for it. You have to make sure that the routers are set up to pass port 9100 or port 515 (lpr/lpd) traffic to the printers. You should not have to do anything to the client PC because, once the print server is installed, the local PC is no longer in the loop.
As far as the client is concerned, this is then just another printer attached to the server.