If you have ever worked in an environment with multiple Windows servers to manage, you know how useful Microsoft's Remote Desktop, aka Terminal Server client, is. In a situation where you have to access a NAT-ed, remote site with multiple servers, having servers listen on ports other than the default (3389) is quite handy.Unfortunately, Microsoft 'the Remote Desktop Connection Client for the Mac supports only port 3389. 3389 is the default port.' I was frustrated with this until recently, when on a whim, I entered the port number preceded by a colon immediately after the IP address of the remote site (e.g., 10.10.).

Workshop manual; Husqvarna Rider 13 Workshop Manual. Husqvarna 13 AWD Operator's Manual 56 pages. Rider 16 2003- 282H070110 ordered from an authorized service workshop. Rider 11 and Rider 13 are fitted with a single It is important that only original spare parts are cylinder side-valve engine of 10.5 resp. 12.5 hp used when repairing. Husqvarna rider 13 awd service manual.

Keyword Name,: Mac, RDP, Remote Connection, Desktop, RDC. Using the Microsoft Remote Desktop Client Hot Fix v1.2.1 app.

I can now access all of the servers, regardless of their port, using my Mac. Amazing, I had no idea that MS claimed to not support this function. I've been using it for a loooong time and mkutny is absolutely right, it is VERY handy. My room mates and I all use Mac laptops and Windows XP desktops, and this makes it possible for us all to connect to our home systems while at work or on the road.For those who don't know, the Microsoft Knowledgebase article shows how to change the port number on the Windows side of things.The gist of it is to change the PortNumber key in the registry at: HKEYLOCALMACHINESystemCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp.

I am a somewhat experienced Windows and Macintosh admin.I have never been able to get Remote Desktop Client to work.The client on the Macintosh takes a very very long time, thinking about the connection, then gives up. The Windows XP Pro machine claims to be allowing Remote Desktop users, and the network connection claims to have a firewall rule set to allow connections on port 3389. I added a rule for port 3389 to my Macintosh firewall via the System Settings:Sharing Preference Pane. Still no luck.What am I missing here?. I was having a similar problem until I realized that Zone Alarm was not allowing the connections. Now I'm used to being prompted with Zone Alarm, but it was refusing to prompt on requested connections or even when I tried to force it locally. Only after disabling zone alarm was I able to restore the connection functionality.

Strange indeed.Another thing I noticed is you can specify exceptions for specific network interfaces (assuming you have more than one). You may want to make sure that the interface you have connected to the 'net is also marked to exclude 3389 from it's firewall filtering.