asked on

Accessing Hyper-V 2019 share from Win7 guest

Hi

Just deployed a Hyper-V 2019 host with a Win 7 guest VM (both fully patched to date).
I am having issues accessing a file share on the host from the guest machine - I can ping the host, "see" the file share but no matter what I can't seem to authenticate to the host.
No obvious error - I just get a credentials prompt that will not succeed. Nothing relevant in Event Viewer. I can access said share from Win10 clients on the network (unfortunately I don't have any Win7 machines around anymore).

Any idea / pointer most welcome

RAFA

Hello

For what you comment, it can be a problem of permission, likewise please validate the following videos, try to share files, you indicate the results.

https://blog.soporteti.net/hyper-v-compartir-archivos-entre-el-host-y-la-maquina-virtual-video-tutorial/

https://www.youtube.com/watch?v=oUmEncEkrTA

https://www.youtube.com/watch?v=w3hUSAdE0z8

Coolie Sheppard

Is it Windows 7 home or pro?

Windows 7 Home will cause that issue since it doesn't have domain access.

If its pro, try mapping to the drive and select "use different credentials" and use credentials that you know works. See if that helps

David Johnson, CD

1. check your credential store and remove any credentials that point to your host
2. from a command prompt

 net use * \\host\share /user:hostcomputername\username /savecred hostusername'spassword

Open in new window

John

In addition to the above comments, make sure SMBv1 has been removed from the Windows 7 machine.
What numerical error do you get when you run David's NET USE command?
Upgrade your Windows 7 machines to Windows 10. The gap you are trying to bridge is huge

Alexandre Takacs

ASKER

Thanks for the various pointers.

This is a Win10 Enterprise VM.

There is no domain ("simple" standalone HyperV server). As you might guess moving that VM to Win 10 is not an option (the rest of our setup is migrated).

David Johnson, CD

Hmm

 net use * \\host\share  /savecred

Open in new window

so in your case is HV2017 the pc using ip 172.16.101.220? and does it have a user named alex using the password you entered?
try

net use * \\HV2017\common

Open in new window

and enter your credentials if you get error 53 then the credentials are wrong

Alexandre Takacs

ASKER

Thanks

HV2017 is the Hyper-V host using ip 172.16.101.220. I might not have DNS resolution for it but I don't think I need it. Still

Yes i am using correct credentials. They are working for other Win 10 workstations and a Mac on the same network. The issue is specific to Win7 (the fact that it is a VM is probably irrelevant)

David Johnson, CD

you don't need dns
can you ping hv2017 ? is there a user Alex that you know the password for on hv2017

Alexandre Takacs

ASKER

yes (I have shown a ping in the first screenshot) and yes the credentials are correct.

Access denied is probably not a wrong credentials issue IMHO.

David Johnson, CD

no you showed a ping using an ip address I said using the computername
then use the computer name and not the ip address

Alexandre Takacs

ASKER

nope that won't work as I don't have DNS resolution in place.

but will take care of it I on the off chance it helps.

David Johnson, CD

you don't need dns resolution to be in place
are both machines on the same network and both have file and print sharing enabled and are members of a private or domain network?

Alexandre Takacs

ASKER

you don't need dns resolution to be in place

Just tested an indeed doesn't make a difference

are both machines on the same network and both have file and print sharing enabled and are members of a private or domain network?

Well the VM is hosted on the Hyper-V host... so yes they are pretty much on the same network :)

John

Is the time on the Windows 7 machine correct? (System error 5)
Windows 7 had the "handle" error earlier this year. Did you run all the 2019 updates?

Alexandre Takacs

ASKER

Is the time on the Windows 7 machine correct? (System error 5)

Within 200ms

Windows 7 had the "handle" error earlier this year. Did you run all the 2019 updates?

Yup - both server and client up to date.

Further update: I am now also running a win10 Vm on the same host. No problem to access the share.

Alexandre Takacs

ASKER

I have deployed further 2019 server and it would seem that the problem is with any Win7 machine accessing a server 2019 share. I have googled it and surprisingly few results so far.

Do I need to enable SMB1? I'm sure that Win7 (fully patched) can do SMB2 or even SMB3 ? Bit perplexed

John

You should not enable SMBv1and SMBv2 should work.

Alexandre Takacs

ASKER

agreed...

I tried out of "dispair" but it did not help...

bit baffled here

ASKER CERTIFIED SOLUTION

Alexandre Takacs

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

David Johnson, CD

FYI I have no problem at all with windows 7 and Server 2016/2019