On Mon, 2017-04-03 at 07:51 -0700, Gordon Messmer wrote: > On 04/03/2017 03:18 AM, Patrick O'Callaghan wrote: > > Using the Windows file manager on W to open the Network tab, I see > > several entries, including the Samba service on D and the NAS (called > > STORAGE). Opening the D entry shows me the shares from D. Trying to > > open the STORAGE tab gets an error: "Windows cannot access \\STORAGE. > > Check the spelling of the name. Otherwise there might be a problem with > > your network, ...". The log file on N shows no activity. > > > Ah, see... that's not a permission error. That error probably indicates > that W is trying to locate the "STORAGE" host using NMB broadcast, and > can't, which in turn probably means you're using the default NAT > networking under libvirt. It's true that I didn't change the default. However note that W is showing STORAGE in its network tab without me doing any specific configuration (i.e. this is a new install of Windows 10) so it must be getting it from somewhere. > One solution to that problem would be to run "virsh iface-bridge eth0 > br0" to create a bridge interface, and then connect the W VM to the new > bridge. That'll put the guest on the same broadcast domain as D, and > should resolve the problem. I assumed it was already using bridging: $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default ZyXEL 0.0.0.0 UG 100 0 0 enp3s0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp3s0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 However I tried it anyway (after shutting down W due to excessive caution): $ sudo virsh iface-bridge enp3s0 br0 error: An error occurred, but the cause is unknown > The other solution would be to edit the W "hosts" file so that it can > resolve the name "STORAGE" to an IP address, which *should* also work. I already have it in /etc/hosts (on W), as "storage" (lower case) but I didn't think that mattered with WINS. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
