Hi Folks,

This is not a question, just some information for the archives.

A while back I had asked questions about providing access to domain resources to a Mac user.

One of the issues I raised was how to enable a Mac user to log into a Windows Remote Desktop Protocol server in order to run a Windows-only program.

I have figured out how to do this, but since the method seemed odd to me, I thought I'd report it here.

Our router controls access to the RDP server using same-interface routing. This means that truly remote users (not using our internet connection) must use the router's public IP address plus a port number to access the RDP server. However, for any Windows user who is sharing our internet connection, whether or not that user is logged into the domain, that user must either use the machine name for the RDP server or its local IP address. The public IP address will not work.

But the machine name will not work for the Mac user, even though he is using our internet connection and has a list of all machine names on the network in the Network dialog. He can only connect using the local IP address for the RDP server.

Took me quite a few iterations of possible combinations of configuration settings, plus more than one internet search for help, to find that out.

Ken Dibble
www.stic-cil.org


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to