Help with Windows 10 VM

[blazestar]

Hey guys,

I installed a Windows 10 VM with the following options:

• HD is SCSI, with VirtIO controller, qcow2 format and cache set to writeback
• NIC is in bridge, paravirtualized with VirtIO

I've installed the VirtIO drivers v 0.1.173 for the HD and the NIC.

Now there's something really weird going on.

The VM has access to Internet so the NIC is working fine.

I want to access my shares on my NAS at 10.0.5.1
On the NAS the shares are broadcasted and accessible with SMB / CIFS.

In Edge I can access my NAS webUI by typing 10.0.5.1, so there IS a route, and HTTP works fine.

But when in Windows Explorer, I try to access \\10.0.5.1 it will tell me that "Windows cannot access \\10.0.5.1".
Of course the Diagnose option doesn't detect anything wrong.

Also in the Network section of Windows Explorer, the VM doesn't see anything else than itself.
File sharing and discovery is enabled in full.

It works on all other physical Windows 10 machines so there has to be something wrong with my VM.

I've tried messing around with the Network settings, the network is set as private, all permissions are allowed... I have no idea what's going on.

Any help would be greatly appreciated

 

[apoc]

But when in Windows Explorer, I try to access \\10.0.5.1 it will tell me that "Windows cannot access \\10.0.5.1".

This indicates you have an issue with your client (in this case the Win10 VM)

Of course the Diagnose option doesn't detect anything wrong.

Has this Windows feature ever worked ?

I don't think that this has something to do with Proxmox or the fact you are virtualizing the system.
There is something different from the configuration of your physical WIN10 and this virtual one.
Are they running the same patchlevel?
Are they exactly configured the same?
What kind of NAS do you try to access? Linux based? Any details?

 

[Mike Lupe]

Maybe your NAS is running on an old SMB version. I thought e.g. Windows 10 stopped support for SMBv1.

https://en.wikipedia.org/wiki/Server_Message_Block

 

[blazestar]

Maybe your NAS is running on an old SMB version. I thought e.g. Windows 10 stopped support for SMBv1.

https://en.wikipedia.org/wiki/Server_Message_Block

Like I said, many other Windows 10 physical machines can connect to the same NAS, so I don't think it's an issue with that !

 

[blazestar]

This indicates you have an issue with your client (in this case the Win10 VM)

Yes I agree.

Has this Windows feature ever worked ?

Ha! I don't think so.

I don't think that this has something to do with Proxmox or the fact you are virtualizing the system.
There is something different from the configuration of your physical WIN10 and this virtual one.
Are they running the same patchlevel?
Are they exactly configured the same?
What kind of NAS do you try to access? Linux based? Any details?

I'm running FreeNAS.
It's running on FreeBSD.
SMB shares are running SMB3_11, which is compatible with Windows 10.

But I don't think it's a SMB problem.
My Windows 10 VM doesn't even see the NAS !
It doesn't see the device, so I really think it's a network issue... I just can't figure out what!

In CMD I can also ping 10.0.5.1 so it's not like it's unreachable.

It has to be a problem with a sharing / network discovery setting or something but for the life of me, I can't figure out WHAT!

 

[blazestar]

Well after messing around endlessly I ended up finding this:
https://serverfault.com/questions/888690/windows-10-cannot-access-network-shared-locations-or-drives

AND IT WORKS

So, case closed.

Thanks all for your replies