Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Connect to non-standard ports with MS Remote Desktop' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Connect to non-standard ports with MS Remote Desktop
Authored by: watersb on Oct 14, '04 06:32:56PM

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?



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: watersb on Oct 14, '04 06:35:01PM

I can ping both ways between machines, also SSH works between the Windows and Mac: they see each other's TCP network services. But no Remote Desktop!



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: carlost on Oct 14, '04 09:15:14PM

Are you sure you've enabled (or ublocked the port in the firewall settings) Remote Desktop? If you are trying to connect to W2K Server then make sure Terminal services are installed as well.

HTH

CJ

---
To mess up an OS X box, you need to work at it; to mess up your Windows box, you just need to work on it.



[ Reply to This | # ]
Connect to non-standard ports with MS Remote Desktop
Authored by: rhithyn on Oct 14, '04 10:56:10PM

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.



[ Reply to This | # ]
Comcast, ...
Authored by: jimhoyt on Oct 15, '04 07:41:23PM

... bless their icy little heart, block port 3389 to "protect us." No amount of pleading, cajoling or screaming will get it unblocked.

My kids live in another state and use PCs. Maybe this hint will finally get our machines to talk.



[ Reply to This | # ]