"A connection will not be made because credentials may not be sent to the remote computer" FIX*

Question

_{Wednesday, December 3, 2008 12:58 PM | 12 votes}

I got this error message when i was trying to connect to one of my virtual machines running in Hyper V -Virtual Machine Connection:

"A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator.

Would you like to try connecting again?

[connect] [exit]"

*****FIX****

To resolve this issue, follow these steps:

1. In the Hyper-V MMC snap-in, right-click the Hyper-V server that hosts the virtual machine to which you want to connect, and then click Hyper-V Settings.
2. Click User Credentials, click to clear the Use default credentials automatically (no prompt) check box, and then click Apply.
3. Click Delete Saved Credentials, click Delete, and then click OK. If there are no saved credentials, the Delete button will be dimmed.

Note Repeat steps 1 through 3 for each Hyper-V server for which you want to be prompted for credentials when you connect to a virtual machine.

All replies (11)

_{Friday, July 23, 2010 1:11 AM}

Thank You

It worked great!

C

_{Tuesday, July 27, 2010 4:34 PM}

Thank You

It worked great!

C

Thanks a lot. I was running into same issue.

_{Monday, August 8, 2011 7:49 AM | 2 votes}

Strange - I had to do the opposite! Use default credentials was unchecked, I checked it, clicked apply, now it works.Andrew www.pursuittechnology.co.uk

_{Wednesday, April 4, 2012 10:14 AM | 1 vote}

Had the same problem and resolved checking the "use default credentials" checkbox... the opposite.

_{Tuesday, May 1, 2012 4:45 PM}

I've had this Hyper-V server up and running for 2 years. Never had this problem before, but when .NET Framework 4 Update on 4/27/2012, I started getting this error. The above fix did not work in either direction. HELP!

_{Wednesday, June 13, 2012 5:17 PM}

I have the same issue, I have 10 workstations that connect this way to the hyper-v server and only my workstation gives this error.  I believe mine also did a .net upgrade.

Any one with an answer?

Myk Lougee

_{Wednesday, June 27, 2012 9:49 AM}

Hmm. I have this exact same error in SCVMM 2012, but there are no "Hyper-V settings" in the console. Anyone have any ideas?

_{Wednesday, June 27, 2012 7:25 PM}

I've had this Hyper-V server up and running for 2 years. Never had this problem before, but when .NET Framework 4 Update on 4/27/2012, I started getting this error. The above fix did not work in either direction. HELP!

I guess we don't rate an answer.  I now do not have access at all to my VMs. They are running. I can see them using my Hyper-V Manager. I can even start and stop them, I just can't log on to them.

_{Friday, December 14, 2012 1:21 AM}

Obviously something must have changed in 2012. I can find the "Hyper-V Settings" but there are no options for "User Credentials".

_{Friday, December 14, 2012 1:31 AM}

Obviously something must have changed in 2012. I can find the "Hyper-V Settings" but there are no options for "User Credentials".

Scratch that, I was looking at the Hyper-V manager on the Windows 2012 server. The HVM on my Windows 7 desktop had that option and using the checkbox worked. Thanks!

_{Friday, March 22, 2013 1:35 PM}

If you are trying to reach VM located on a host managed by SCVMM2012 SP1 from a client in the same domain, make sure to do following:

Start - Run - type gpedit.msc /force

Under "Computer configuration" open "Admin Templates" and then "System" and choose "Credentials delegation"

In there, "Allow delegating default credentials with NTML-only server authentication" must be set to enabled and server list server must contain *

Same is for "Allow delegating default credentials" right under it. Remember to add * to list of the servers.

That solutions works on Server 2012 as well.