Configuring Microsoft Remote Desktop via NBM Proxy Services
Novell Cool Solutions: Feature
By Martin Zinaich
Digg This -
Posted: 3 May 2006
This is a quick setup guide to allow a client PC on the inside of a network to use Microsoft's Remote Desktop to remote-control a PC or server on the Internet, via BorderManager proxy services.
Here are the steps to follow:
1. Create a Generic TCP proxy.
Normally this is standard Terminal Services port 3389 as Origin. In this example the vendor (www.target.host) is using port 33333. The Proxy Port can be any available port on NBM's Private Card; in this case we used the same port as Origin.
Figure 1 - Generic TCP proxy
2. If you are using Access Rules, add an exception for the Remote Desktop site.
Figure 2 - Exception for Remote Desktop site
3. Create the proper filter exceptions.
Create one new TCP Packet type. (If you need the standard RDP port 3389, an RDP packet type may already be defined; if, so you can skip to the next step.) In this case, we open 33333, which has to match Step 1 - Origin Server Port.
Figure 3 - Filter exceptions
4. Using the new Packet Type (or RDP if you are using the standard port), create an outbound filter exception as follows:
Figure 4 - Outbound filter exception
Note: Public.ip is the Proxy Server Public Card's IP address.
5. Using the new Packet Type, create an inbound filter exception as follows. (Again if using the standard RDP port, pick that packet type.)
Figure 5 - Inbound filter exception
6. In the Remote Desktop Client, enter the BorderManager private card and Generic TCP Proxy Port as set above in Step 1:
Figure 6 - Private card and Generic TCP Proxy Port
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com