0

I am using Windows 10 to connect to a Windows Server 2012 R2 (VM) installed on a Hyper-V core host. The VM is set to share a second virtual disk where I allowed previously share and gave full control permission.

When I try to access a shared folder from the Windows 10 client, I receive a login window, enter my credentials, and windows seems to authenticate, but the password box is then cleared and not error is presented.

To try to understand what is happening, I tried to connect from the client machine using Remote Computer management, the connection first failed, then I disabled the firewall on both sides, then this time the connection succeeded but an error message appeared: "You have no permission to show the shares list of the Windows Clients".

On the VM, I went to the Network and sharing center -> Advanced sharing settings, checked "Turn on network discovery" and saved, but this action could not be taken, and the option was reinitialized to Off again.

I guess something in the Hyper-V core server inhibits the communication between the two machines.

For additional information: please note that this is a non domain configuration (only Workgroup), and the same administrator account credentials is set and used on the 3 machines.

Could somebody have an idea ?

25
  • I don't really understand this part: "...windows seemed to authenty, but the login window only emptied the password zone without giving any error." Without a domain you will probably have to enter a username and password to access any shares. The credentials you enter should be from the local accounts list on the computer that is doing the sharing, not from the computer that is the client of the share. Commented Feb 29, 2016 at 15:46
  • I guess something in the Hyper-V core server inhibits the communication between the two machines. - This doesn't have anything to do with Hyper-V. What would be the point of Hyper-V if it prevented communication with virtual machines running under Hyper-V? Commented Feb 29, 2016 at 16:01
  • @Todd, sorry for the mistake, it was updated, and please note that I can usually access other shares on the network without having to provide each time credentials, the difference here is that I am trying to access a vhdx file on a Hyper-V host. Commented Feb 29, 2016 at 16:18
  • @ joeqwerty I suspect the VM related vhdx files access is denied or some permissions are missing on the Hyper-V host. Commented Feb 29, 2016 at 16:25
  • If you can access a share without a domain and without providing credentials, then the share and the underlying file system permissions both allow access to the "Everyone" object. That's a very bad idea from a security standpoint, but if you want to avoid having to enter credentials, that's a way to do it. Commented Feb 29, 2016 at 16:32

1 Answer 1

1

You need to check two settings.

In the Windows 2012 R2 VM make sure that the share permissions AND the NTFS permissions allow the user you are logging in with to access the directory.

The second thing is that when you login you MUST include the name of the computer with the username. Here is what I mean by this.

Server ServerName

Client ClientName

So to login to the Server share from the Client the username is ServerName\administrator. If you just put administrator the Server will read the username as ClientName\administrator.

1
  • thank you for correcting to the question, please note that share permissions and the NTFS permissions was double checked. And also I used the login in the following maner: ServerName\administrator and this does'nt work. Commented Feb 29, 2016 at 16:35

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.