[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 930
  • Last Modified:

Printer is not listed in Terminal Server Session

I installed a new Brother MFC-9440CN Printer and it prints fine locally. However, when I'm logged into the Terminal Server Session the printer is not listed in my printers.
I added the printer drivers to the Terminal Server. If I look at the printer properties the printer is on port: BRN016124 Standard TCP/IP Port.

Any suggestions on how I can add it to my terminal server session and print?
0
tolinrome
Asked:
tolinrome
  • 6
  • 5
1 Solution
 
Rob WilliamsCommented:
Interesting that it would show up as a TCP/IP port.

How did you add the drivers. Have a look at the following, it may be of some help:
To set up printing with remote desktop:
-On the users workstation when they start the remote desktop connection client, click the options button, and then go to the local resources tab. Check the box for printers and save.
-the drivers for the printer have to be installed on the terminal server, assuming they are not native to the operating system. Do not install the printer on the server but rather; open printers and faxes, on the menu bar go to file, server properties, add, and point to the diver .inf file. You will have to download the drivers first to a temporary folder. If you do this remotely, you should log off and back on before trying to print
-if still having problems, again on the terminal server, go to printers and faxes, on the menu bar go to file, server properties, ports. Look at the port type. If it is a Dot4, you will need to use the following Microsoft fix: http://support.microsoft.com/default.aspx?scid=kb;en-us;q302361
-if it is an option, often connecting the printer to another local computer and sharing it, then connecting to the share rather than having it attached locally, often resolves the problem. If you are using a VPN client this is not always possible, due to routing issues.
-if you are using a USB printer, though it usually works (some multi-function units do not), Microsoft does not officially support USB printing through remote desktop sessions. Vista is supposed to resolve this, though it doesn't help you now.
-avoid PCL6 drivers with terminal services
-Microsoft has released an updated version of the Remote desktop Connection (ver 6) which should be more compatible with USB printers. Certainly offers more USB options, assuming these are compatible with existing O/S's.
http://www.microsoft.com/downloads/details.aspx?familyid=26F11F0C-0D18-4306-ABCF-D4F18C8F5DF9&displaylang=en
0
 
tolinromeAuthor Commented:
If I look at the printer properties the printer is on port: BRN016124 Standard TCP/IP Port. This is on the client pc not the Server ...sorry for the confusion on that one.

The client is printing from home remoting into the office on a vpn connection.

I'll check the RDP properties for the printing.
0
 
Rob WilliamsCommented:
OK.
Most of the configuration is done on the server end.
Is the printer connected by a network cable or USB?
Also, any chance you are connecting by means of a VPN, and then using remote desktop?
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
tolinromeAuthor Commented:
ahhhh..

Ok, On the server end I installed the drivers just as you outlined above.
The printer is connected with a network cable.
Yes, the client is connecting via RDP over a vpn connection.

he already has a printer that he uses this with the rdp over vpn and it works fine but just cant get the new printer to show up in his terminal server session.
0
 
Rob WilliamsCommented:
With a VPN present it might be a routing issue. I didn't think to ask if it is a site to site tunnel, or VPN client to site. If the latter; most VPN's in their default configuration do not allow simultaneous connections to the local LAN, while connected to the VPN. This is to protect the server network from unauthorized access by local devices. Therefore a networked printer is not available, i.e. blocked. If this is the case you need to enable split-tunneling. This is done in different ways with different VPN's. In Most cases it has to be done by the VPN administrator. If however you are using the built-in Windows VPN client; on the client/connecting PC, go to control panel | network connections | right click on the VPN/Virtual adapter and choose properties | Networking | TCP/IP -properties | Advanced | General | un-check  "Use default gateway on remote network"

If it is a site to site hardware based VPN solution, you can actually install and map a TCP/IP port on the server for the new printer.

0
 
tolinromeAuthor Commented:
ok, it's a site - site vpn connection between to netgear devices. I setup the printer on the client with a static ip address (local tcpip port) and its fine locally.

What do you mean by mapping a tcpip port on the server for the printer?

0
 
tolinromeAuthor Commented:
what I did was add a tcp/ip port on the server and install the printer drivers there using the same IP address as the local printer in his house.

Now when I print a document from his terminal server session the document is stuck in the printer queue on the terminal server.
0
 
tolinromeAuthor Commented:
also the printer in the terminal session is status offline but locally it is status online
0
 
Rob WilliamsCommented:
>>"what I did was add a tcp/ip port on the server and install the printer drivers there using the same IP address as the local printer in his house."
In theory with a site to site VPN that should work.
First thing to test is can the server ping the IP of the printer? That will verify routing and any firewalls are configured.
Next verify the printer is configured correctly. Right click on the printer at the server end and choose properties, then under the ports tab verify the port is set to "Standard TCP/IP" port and the appropriate IP.
In this case the printer should actually be installed on the server, rather than just the drivers. The latter is for temporary printers created only during a terminal server session.
0
 
tolinromeAuthor Commented:
I rebooted both vpn devices and problem was solved.
Thanks!
0
 
Rob WilliamsCommented:
"When in doubt - reboot" Should be stamped on every piece of equipment :-)
Great, glad to hear.
Thanks tolinrome.
Cheers !
--Rob
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now