Hello, I recently needed to install a new router which necessitated moving my NAS from 192.168.0.1 to 192.168.0.100 (new router reserved 192.168.0.1). All works as it should except the Vero4K. I get a message of “Error - File Exists” when I click on the menu to access the NAS files. I also get a message of “Remote Share - Could not connect to network server”. The NAS name, on the network did not change. I have been through every file I can seem to access and cannot see anything wrong nor any IP address settings e.g. :-
location id=“2”>smb://homebackup/tv shows/location>
location id=“3”>smb://maindesk/tv shows/location>
The “maindesk” is a PC with a shared drive and that is accessible with no issues.
The “homebackup” is the NAS that I am having problems accessing.
The NAS is accessible, with no issues, from the rest of the network… only the Vero4K
has a problem.
I have spent ages trying to solve this no no avail.
I am obviously missing something (wrt to knowledge).
Sorry, my level of knowledge is the issue.
I can see the sources.xml file
Not sure how I can post the contents here.
To my eye it looks OK.
The NAS is identified as homebackup and not as the IP address.
I did try to add a video source by defining the IP address but that came up with a message that the network location could not be found… most likely due to my error with syntax ?
OK, I typed the line:- nano ~/.kodi/userdata/advancedsettings.xml
Note that a left pointing arrow, above, causes the following text not to be displayed but is correct on the terminal screen.
I cannot see how I save that to the advancedsettings.xml
You can select the xml code and press the “</>” on the editing bar to display the code for future reference.
To save the file and exit nano you hold down ctrl and press “x”, then a prompt shows up at the bottom of the screen and you press “y” and then “enter”. You will need to reboot for the change to take effect.
SMBDirectory->GetDirectory: Unable to open directory : 'smb://192.168.0.100/movies'
unix_err:'11' error : 'File exists'
But I think that maybe your NAS is refusing the connection. I would check that as it might need some kind of a permission setting changed there. Maybe also check to make sure you can see the NAS at all by (via ssh) typing ping 192.168.0.100