Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1186
  • Last Modified:

MS Remote Desktop Connection for Mac Doesn't Connect to Windows 7

Hey everyone,

I've got a Mac user that we're trying to set up an SSL-VPN connection for.  I've installed the Microsoft Remote Desktop Connection for Mac version 2.1.0 on her machine.  

While physically connected to the network, I try to connect to a Windows XP machine and it works just fine.  However, when I try to connect to her Windows 7 machine, it comes back with the following error:

"Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.  Try reconnecting to the Windows-based computer, or contact our administrator."

Everything on the RDC preferences is set at its default.  Under the Security tab, it is set to "Warn me if authentication fails."

On the Windows 7 machine, the user is in the Remote Desktop Users group.  The machine's remote desktop settings are configured for "Allow connections from computers running any version of Remote Desktop (less secure)" via group policy.  

Can anyone tell me what I'm missing here?  This is happening regardless if I'm using standard user creds or domain administrator creds.

The user is using OS X version 10.6.6
error.jpg
0
wanderson75
Asked:
wanderson75
  • 10
  • 7
1 Solution
 
strungCommented:
What happens when you click OK in the screen above? On my computer it just goes ahead and connects.
0
 
wanderson75Author Commented:
It takes me right back to the prompt to enter the computer name.
0
 
wanderson75Author Commented:
hmmm...one thing I am seeing though is that the Mac isn't reporting a hostname to the DHCP server.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
wanderson75Author Commented:
Sorry to multipost as I find stuff.  I'm also seeing the unique ID in the DHCP tables as a 16 digit number where the 12 digit MAC address should be.  Could this have something to do with it?
0
 
strungCommented:
Try using the computer IP address instead.
0
 
wanderson75Author Commented:
Yeah, I tried that one already.  It gives me the exact same error.
0
 
strungCommented:
Strange, I get a similar error (see attached screen shot) but it still connects.
Screen-shot-2011-03-15-at-1.42.1.pdf
0
 
wanderson75Author Commented:
See, that's the one that I've seen on the walkthroughs too, but it's different than what I see on mine.  There isn't a nice explanation or a connect button.  What version of RDC are you using?
0
 
strungCommented:
Longshot, but if the unique ID is 16 digits, you may be trying to use IPV6. Try turning off IPV6 in the Mac network prefs.
0
 
strungCommented:
I am using RDC 2.0.0.

You could also try CoRD:  http://cord.sourceforge.net/
0
 
wanderson75Author Commented:
Cord would probably work as a workaround on the local network, but it's not supported by the company that made the SSL-VPN appliance.  So I'm kind of stuck with this or nothing.  I just can't figure out what would make it look and act different.
0
 
strungCommented:
This might be the most helpful since it is OS X specific:  

http://www.retainrelease.com/blog/?p=9
0
 
wanderson75Author Commented:
That did it!  Kinda funny how it's the simple things.
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

  • 10
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now