No network/SMB

How show /home/osmc/.kodi when i don’t see it on Transmit.

I see it now, thanks.

I copied sources.xml & modified smb.conf.

You were right, smb.conf was set to 2-3.

Thanks for your time and patience :slight_smile:

Actually, FSTAB edit show :

rootfs is not mounted in fstab as we do it via initramfs. Uncomment for remount (slower boot)

#/dev/vero-nand/root / ext4 defaults,noatime 0 0

Can i just copy & paste at the end the line mentioned before ? Thanks

On which device? On the Vero4k and/or on the RPi3?

Yes you just can paste the line at the end (just put an empty line for better overview.
But if you now have copied the sources.xml over and it is working you might not need to go down the fstab way

On the Vero 4K

Thanks. Indeed but, in another post i described playback play/stop issues and everyone suggested me to update FSTAB. I don’ know the differences, it’s just to have the best solution.

And on the Pi?

So after copying the sources.xml the access to the samba share from the Vero4k works? If that is the case than it was not the SMB1 problem but just most likely a Name or IP issue.

They use different versions of the “driver” to access Samba shares. So yes best would be to mount via fstab and then just add via local file system in Kodi.

In RP3 there was the following lines :
preferred master = no
local master = no
domain master = no
client lanman auth = yes
lanman auth = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
lock directory = /home/osmc/.smb/
client use spnego = no
client ntlmv2 auth = no
name resolve order = bcast host

[quote=“fzinken, post:25, topic:38077”]
So after copying the sources.xml the access to the samba share from the Vero4k works? If that is the case than it was not the SMB1 problem but just most likely a Name or IP issue.[/quote]

Solution was to change SMB to 1, copying source.xml just added sources.

OK, thanks

Ok, good to know than that was your problem and on the Pi3 the file was just not updated with the new security config because you had an existing smb.conf in that directory.

Thanks again :slight_smile:

Hi,

For the second time this weekend I’ve lost access to my LAN/SMB, but I still have access to internet.

Here is the log : https://paste.osmc.tv/ludixuzuca

Any idea ?

Thanks

I don’t have the problem with my RP3.

You should try as @sam_nazarko first suggested to mount your shares via fstab instead of using Kodi. Search this forum and you will find plenty of information as to how to use fstab.

You’re using hostnames in your SMB:// shares.
Use static IPs. When you use hostnames, the access to the share
will be delayed unnecessarily when the nameserver is consulted.

Your DNS might be different on Pi and Vero 4K.

Hostname resolution is hit and miss at best. Alternatively, add
a hostname to IP mapping in /etc/hosts.

Another suggestion was “if it works. Why change ?” :wink:

Since it’s obviously not working, give fstab, or @sam_nazarko’s other suggestion to use IP addresses (I didn’t think of that one)

Since 2012 (Raspbmc), I’ve been telling people to never use SMB shares with
hostnames. Using Kodi’s built-in SMB client is fine (until you get to very high bitrate
material); but using hostnames isn’t due to the average home network and implementation
in routers.

@sam_nazarko

Il not doing anything but plugin the Vero 4k to my TV, except modifying the SMB version.

I’m not sure to understand what you’re suggesting, can you please explaining again considering its new to me ? Thanks

Because we’ve seen again and again that fstab mounts perform better and are far more stable.

Instead of using Hostname in your sources, he’s suggesting that you change to using IP, so the like would be something like:

 smb://USERNAME:PASSWORD@192.168.1.1/share

where you replace the 192.168.1.1 with the IP of your server.

Ok si what do I have to do ? Thanks

No need to move to fstab mounts if Kodi ones do work OK.

The suggestion is to use the IP address of the server instead of the
hostname.

The reason it ‘sometimes’ works is because sometimes DNS resolution
works and sometimes it doesn’t. It can be particularly touchy in home
network environments.

If you use IPs for both Pi and Vero 4K, you will find it a better
experience.

Sam