<div>
There isn't any special command to RDP through one computer to reach another. I'm assuming the server you can connect to is acting as a firewall between you and the computers you would like to connect to. Are you connecting to a remote network over the Internet or are you connecting to computers on the same LAN or maybe a corporate WAN? Are the computers behind the firewall accessible from your computer (can you ping their IP? if you are accessing from the Internet, are they using public or private IPs?)<br />
<br />
If the server is acting as a firewall and router effectively hiding the computers behind it, you will need to configure the server/firewall for port forwarding to allow you to connect to the computers on the internal network. If the server is just blocking the traffic and not performing NAT, then you just need to add a rule to allow RDP to whatever computer you want to connect to.<br />
<br />
Another way of getting to the computers in the network would be to RDP to the server, then RDP from there to the computers on the inside.<br />
<br />
If you still need help, please provide us with more details about how the network is setup and exactly what you are trying to do.
</div>


<div>
Hi,<br />
<br />
I able to connect using the server address remote.xxxx.xxx either remotely or on the lan, then result is the same, a desktop session to the server which makes sense since that is how the normal port forwarding works through the firewall Internet resolve &quot;remote.xxxx.xxx&quot; to internet IP address&gt; firewall&gt; 3389 port forward&gt;server IP. &nbsp;Great, but I have several users who would like to connect to their Windows desktops from their home MACS (big surprise) and I cannot simply hand them the server credentials and have piggybacked remote sessions running amok.<br />
<br />
So, the SBS 2008 server is not acting as a firewall, but routes the users through the TS gateway. &nbsp;The RDP clients CoRD and MS RDP do not seem to have a mechanism for having the users be routed differently from the fixed firewall rules.<br />
<br />
This may not be possible, but it seems so close. &nbsp;I have tried remote.xxxx.xxx:LAN IP, remote.xxxx.xxx\computerna<wbr />me which of course don't work.<br />
<br />
I doubt having a port forward rule that has a different port for each computer on the LAN would work either since they would not be routed through the TS gateway and how would the RDP client know which user was which? &nbsp;If you input WAN IP:3390 on the RDP client would that = machine &quot;A&quot; WAN IP:3391= machine &quot;B&quot; etc? 
</div>


<div>
Actually, it looks like TS gateway on SBS 2008 will do what you want. Here is a page that describes some options:<br />
<a href="http://blogs.technet.com/b/sbs/archive/2008/09/26/can-i-use-terminal-services-in-sbs-2008.aspx" rel="ugc">http://blogs.technet.com/b/sbs/archive/2008/09/26/can-i-use-terminal-services-in-sbs-2008.aspx</a><br />
and here is a step-by-step for setting up TS gateway:<br />
<a href="http://technet.microsoft.com/en-us/library/cc771530(WS.10).aspx" rel="ugc">http://technet.microsoft.com/en-us/library/cc771530(WS.10).aspx</a><br />
<br />
There are quite a few steps, but you've probably already got some of them done if you have the TS gateway setup. It's possible you just need to configure it allow access to the computers you want to allow access to.<br />
<br />
If you take a look at those links and still need help, let us know where you need more help at and we'll see what we can do.<br />
<br />
Hope this helps.
</div>


<div>
RWW already works perfectly and has since it's installation. &nbsp;That is not the question. &nbsp;Does the mac rdp client support user routing is the question.
</div>


<div>
From what I can find, the MS RDP client for Mac OS X doesn't support TS Gateway. I did find one that does: <a href="http://itap-mobile.com/desktop/rdp" rel="ugc">http://itap-mobile.com/desktop/rdp</a><br />
<br />
Hope this helps.
</div>


<div>
ok, so if 3389 is forwarded to a specific machine and RWW does not use 3389 one client should work and not break the RWW others are using. &nbsp;Wild shot is to then have the 2nd CoRD rdp type in remote.xxxxxx.xxx:3390 and port forward that to the second lan machine ip? &nbsp;I'll try it and doubt it will work. &nbsp;Machine rdp host would need to accept port change.
</div>


<div>
I have been banging at this and have at least some success in a test environment, but can't get it going in production. &nbsp;When I changed the firewall rules on a Sonicwall TZ190 to allow port 3389 WAN&gt;LAN to an individual machine on the SBS LAN I could then RDP from a Mac running CoRD. &nbsp;<br />
<br />
This does not affect the function of SBS RWW as I can still connect to any SBS LAN machine with RWW. &nbsp;I gather the &nbsp;SBS TS gateway is handling the forwarding of 443 to individual machines on 3389. &nbsp;So at least that works, next I'll try the multiple 3390&gt;3389, 3391&gt;3389.<br />
<br />
When I changed the same firewall rule on a Sonicwall NSA240 to allow 3389 to an individual machine on an SBS LAN I still can't connect. &nbsp;I've been going over the firewall and can't find why it's not working.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I can connect to a remote desktop session with either Microsoft RDP client for MAC or CoRD. &nbsp;However, I can only seem to connect to the server. &nbsp;Is there a conditional command when connecting that will allow a connection to a specfic computer on the SBS network behind the firewall?<br />
<br />
Thank You
</div>
</div>


Hi,

I can connect to a remote desktop session with either Microsoft RDP client for MAC or CoRD.  However, I can only seem to connect to the server.  Is there a conditional command when connecting that will allow a connection to a specfic computer on the SBS network behind the firewall?

Thank You

CoRD client over SBS 2008 network.

Apple devices including Macs, iPhones, iPods and iPad support standard wired and wireless networking technologies, but they also utilize custom applications and some special techniques for networking with each other and with non-Apple devices. Apple manufacturers the AirPort line of wireless networking products, and has its own networking protocols, AppleTalk and AFP (Apple Filing Protocol).

Apple Networking

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.