FIFBA
asked on
Printing between remote IPSEC networks
I have 2 networks physically located in 2 cities, they are connected together with IPSEC devices that have been configured to allow unfettered access between the 2 networks. Each network has an Win2003 SBS. One network use 172.16.6.x the other 10.0.0.x. Currently we are using RDP to allow access to machines between the networks. IE from the 172 network, logged into the winXP machine named "Test" at 172.16.6.101, I connect to the "Test2" machine at 10.0.0.108. Running MSWord on the "Test2" machine I attempt to print to the "Test" machine an am unable to.
I have turned on the the printer flag within the RDP configuration without success. I have created entries in the HOSTS file without success, I have attempted to add another zone in the DNS server with a host record created for the remote machine again without success.
Any help would be appreciated. Thanks
I have turned on the the printer flag within the RDP configuration without success. I have created entries in the HOSTS file without success, I have attempted to add another zone in the DNS server with a host record created for the remote machine again without success.
Any help would be appreciated. Thanks
If you want to go another router you can port tunnel to your printer on TCP 9100 and print directly to it across the internet. You can also do the same with IPP (internet printing protocol) on TCP 631.
The client machine running the Remote Desktop Client can have those remote printers installed as local printers but the ports are remote ports.
Now the above would only be possible if the target printers are networked printers - meaning they have a network interface.
However, seeing that you have a 2003 SBS, you can use the print server function on the server and it will host LPR or IPP for the printers for you.
The client machine running the Remote Desktop Client can have those remote printers installed as local printers but the ports are remote ports.
Now the above would only be possible if the target printers are networked printers - meaning they have a network interface.
However, seeing that you have a 2003 SBS, you can use the print server function on the server and it will host LPR or IPP for the printers for you.
ASKER
Virtually all of the remote desktop methods have failed. between the combination of printers that are being used (multipurpose) and porte being used (USB). I wen thtrough each of the stes detailed in the first recommended solutions and followed the Microsoft rocesess to their ends without success.
Can I get some more information on the TCP 9100 solution? is this secure when postng files to the printer?
Regards,
Kevin Gibson
kgibson@nksag.com
Can I get some more information on the TCP 9100 solution? is this secure when postng files to the printer?
Regards,
Kevin Gibson
kgibson@nksag.com
"Can I get some more information on the TCP 9100 solution? is this secure when postng files to the printer?"
It is possible that some random individual could discover TCP 9100 open and print garbage to your printer. Other than that, I cannot think of anything.
On your SBS network, make sure that TCP 9100 is forwarded to your laser printer. At the remote site, add the printer as if it were local, except you are going to create a new TCP/IP Printer Port. When prompted for the address of the printer port, input the external ip of your SBS network.
If you would like step-by-step details I will provide them.
It is possible that some random individual could discover TCP 9100 open and print garbage to your printer. Other than that, I cannot think of anything.
On your SBS network, make sure that TCP 9100 is forwarded to your laser printer. At the remote site, add the printer as if it were local, except you are going to create a new TCP/IP Printer Port. When prompted for the address of the printer port, input the external ip of your SBS network.
If you would like step-by-step details I will provide them.
As a first step troubleshooting, directly after starting a remote desktop session, go to the event viewer and look for errors with source of Print and Event ID 1111. This will tell you if the printer is even being recognized.
Must say multi-function USB printers are likely the worst ones to get to work with Remote Desktop.
Must say multi-function USB printers are likely the worst ones to get to work with Remote Desktop.
ASKER
I have 2 networks (10.0.0.0) and (172.16.6.0) There is an IPSec tunnel that exists between the 2 there is no restriction with respect to port traffic between the 2. shouldn't I be able to send the 9100 traffic between the 2 without going to the internet?
i guess I'm a little slow, is there an instruction that I can step through.
thanks for all your help.
Kevin Gibson
kgibson@nksag.com
i guess I'm a little slow, is there an instruction that I can step through.
thanks for all your help.
Kevin Gibson
kgibson@nksag.com
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
-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 computer to which you are connecting, assuming they are not native to the operating system. Do not install the printer on the computer to which you are connecting but rather; on the "server" computer, 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 computer to which you are connecting, 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