VM cant access host share

Status
Not open for further replies.

D3m0nicSoul

Cadet
Joined
Jan 28, 2017
Messages
9
Hello!

So I have FreeNAS setup with plex and there is a share I dump the movies into when I want to add new ones. I created a VM on this same server and I can ping the host but cant access the share by IP address or hostname. I know the share works because on my main computer i can access it fine. I am currently running the latest version of FreeNAS which I believe is 11.1. Any ideas or what I should check? I am currently running windows 10 x64 1803 with the VirtIO NIC.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
What's your mount command and what is the output when it fails?
 

D3m0nicSoul

Cadet
Joined
Jan 28, 2017
Messages
9
Not sure what you mean by mount command. The error is just "windows cannot access" I know the share itself works because another computer can access it. It just seems like an issue with the vm and host.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
OK, so let's look at the bridge setup.

ifconfig
 

D3m0nicSoul

Cadet
Joined
Jan 28, 2017
Messages
9
Code:
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500												 

	    options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>													  		 

		ether  <Removed>																								 

		hwaddr  <Removed>																			  					

		inet 10.10.10.254 netmask 0xffffff00 broadcast 10.10.10.255																

		nd6 options=9<PERFORMNUD,IFDISABLED>														  							 

		media: Ethernet autoselect (1000baseT <full-duplex>)																	   

		status: active																	  										

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384																 

	    options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>																	  

		inet6 ::1 prefixlen 128																									

		inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2																				 

		inet 127.0.0.1 netmask 0xff000000																						 

		nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>																				  

		groups: lo																												 

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500													 

		ether <Removed>

		nd6 options=1<PERFORMNUD>																								  

		groups: bridge																											 

		id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15																

		maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200																   

		root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0																   

		member: epair1a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>															 

				ifmaxaddr 0 port 6 priority 128 path cost 2000																	 

		member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>																 

				ifmaxaddr 0 port 5 priority 128 path cost 2000000																 

		member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>													    	   

				ifmaxaddr 0 port 4 priority 128 path cost 2000																	 

		member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>												  				 

				ifmaxaddr 0 port 1 priority 128 path cost 20000																	

epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500											   

		options=8<VLAN_MTU>																										

		ether <Removed>																								 

		hwaddr <Removed>																								 

		nd6 options=1<PERFORMNUD>												    											   

		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)																		

		status: active													 														 

		groups: epair																											 

tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500												 

		options=80000<LINKSTATE>																								   

		ether <Removed>																								 

		hwaddr <Removed>																								 

		nd6 options=1<PERFORMNUD>																								   

		media: Ethernet autoselect																								 

		status: active																											  

		groups: tap																												

		Opened by PID 5400																										 

epair1a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500											   

		options=8<VLAN_MTU>		   

ether <Removed>																								   
		hwaddr <Removed>																								   
		nd6 options=1<PERFORMNUD>																								   
		media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)																		 
		status: active																											 
		groups: epair				   
					 



 

D3m0nicSoul

Cadet
Joined
Jan 28, 2017
Messages
9
So it ended up being some weird windows settings. Not sure if maybe my freenas server permissions or shares are setup wrong? Here is what I did.

Turns out, if you type the ip in "Run", and only in "Run", a very specific error shows up that contains this message: "your organization's security policies blocks access..."

Searching that lead me to this solution:

Computer configuration\administrative templates\network\Lanman Workstation "Enable insecure guest logons"

After that I could reach the share by ip address but not by hostname. I changed my DNS settings manually to my gateway IP and I could connect to the share normally by name.

So my questions is why am I using an insecure guest logon? Something with freenas settings I should change?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Sounds like it may be in reference to NTLM V1...

Under Services... SMB settings, look for NTLMv1 auth and turn it off... see if the error goes away... maybe your access will too though... some people have reported problems with that in some cases. I can't confirm, but run my setup with it turned off and can connect to SMB shares from a Mac with no issue.
 
Status
Not open for further replies.
Top