NAS to the Furture Pt-3 - Cannot connect to newtork

The place to post if you need help or advice

Moderators: ChriThor, LXF moderators

NAS to the Furture Pt-3 - Cannot connect to newtork

Postby GeordieJedi » Mon Mar 06, 2017 8:24 pm

Hi all.

I'm experiencing some issues with trying to connect my Ras Pi running OSMC to my NAS
box, and I'd really appreciate some help please.

Issue -
Essentailly I cannot connect my Ras Pi (running OSMC/Kodi) to my NAS box in order
to watch my media.

This has been working for the last couple of years without any problems at all,
via an old install of (Kodi, version 15 I beleive).
However I started to get a lot of pausing and buffering issues with my old install
of Kodi, so I decided to go for a complete wipe and re-install of OSMC/Kodi on my
SD card.

When I try to add my shares or connect to the NAS via the Ras Pi,
I get the following error message =
"Couldn't connect to network server"

Trouble shooting steps -

01. I can ping (Ras Pi) / OSMC
02. I can connect to the Ras Pi via SSH
03. I can connect to the NAS from both my PC's
04. Given the Ras Pi a static IP (from inside my network via DHCP).
05. Added the hostname of the Ras Pi to the hosts file on the NAS.
06. Added the hostname of the Ras Pi to the hosts allowed file on the NAS.
07. Added the hostname of the NAS to the hosts, and hosts allowed files on the Ras Pi
08. Add the permissions to the Ras Pi (On the NAS web console).
09. Rebooted the NAS
10. I'm am using the NFS protocol to connect between my NAS and Raspberry Pi.

Q-01. What am I missing, to allow me to connect my Ras Pi to my NAS box ?

TIA for any help or advice.

Useful information -
Kodi: version 17 (Krypton)
NAS:Synology DS410J
Raspberry Pi: Model B+

Network -
Virgin media cable modem/router (downstairs)
Cat cable run upstairs to switch (upstairs in office)
PCs and NAS connected to switch (upstairs in office)
Ras Pi connected to modem/router via Cat cable (downstairs)

Host name information -
Hoth = NAS box
corellia = desktop (new)
stardestroyer = laptop
Yavin = desktop (old)

[Edit - Added more information. Hostnames]
Last edited by GeordieJedi on Mon May 08, 2017 4:53 pm, edited 1 time in total.
GeordieJedi
LXF regular
 
Posts: 369
Joined: Thu Jun 14, 2007 10:36 pm
Location: North East England

Re: NAS to the Furture Pt-3 - Cannot connect to newtork

Postby Dutch_Master » Tue Mar 07, 2017 5:07 pm

It might be an NFS problem, as I too have been unable to connect to an NFS share on my server. Part of my problem is that said server is still running Debian Jessie, while my desktop runs Funtoo Current. This will probably cause a mismatch between the NFS versions/protocols, although in theory, it shouldn't! The only way to test is install NFS on another server running Funtoo Current, but I haven't gotten round to it yet. You may want to investigate this route for yourself though.
Dutch_Master
LXF regular
 
Posts: 2585
Joined: Tue Mar 27, 2007 1:49 am

Re: NAS to the Furture Pt-3 - Cannot connect to newtork

Postby nelz » Tue Mar 07, 2017 7:21 pm

The showmount command can show which shares are available from an NFS server

Code: Select all
showmount -e hostname


Comparing the output from this when run on the Pi and your computer may shed some light.

I would also SSH into the server and tail -f the system log, then watch the output while trying to mount from the Pi.
"Insanity: doing the same thing over and over again and expecting different results." (Albert Einstein)
User avatar
nelz
Site admin
 
Posts: 9038
Joined: Mon Apr 04, 2005 11:52 am
Location: Warrington, UK

Re: NAS to the Furture Pt-3 - Cannot connect to newtork

Postby LinXGeorge » Sun Mar 12, 2017 8:17 pm

Can confirm this was a NFS problem. Had the same problem and installed on a diff server and same problem. Hopes this can help someone!
galnacasinofilmer /George
Hello Happy People
LinXGeorge
 
Posts: 1
Joined: Tue Mar 07, 2017 6:29 am
Location: Stockholm/phuket

Re: NAS to the Furture Pt-3 - Cannot connect to newtork

Postby GeordieJedi » Mon May 08, 2017 4:52 pm

Hi there Guys, thanks very much for the advice so far.

Here are the results of the current testing & commands:

01.Done on laptop (stardestroyer)
Code: Select all
showmount -e hoth


Code: Select all
/volume1/video        corellia,Yavin,stardestroyer
/volume1/photo        corellia,Yavin,stardestroyer
/volume1/music        corellia,Yavin,stardestroyer
/volume1/sharedata_03 stardestroyer,Yavin
/volume1/homes        stardestroyer



02.ssh'd into Raspberry Pi, from laptop)
Code: Select all
showmount -e hoth


2.1. error message =
Code: Select all
clnt_create: RPC: Port mapper failure - Unable to receive: errno 111 (Connection refused)

(This was when the NAS hdds werent available/span up)

2.2. error message =
Code: Select all
clnt_create: RPC: Port mapper failure - Unable to receive: errno 111 (Connection refused)

(This was when the NAS hdds were available/span up)


03.Done on desktop (corellia)
Code: Select all
showmount -e hoth


Code: Select all
/volume1/video        corellia,Yavin,stardestroyer
/volume1/photo        corellia,Yavin,stardestroyer
/volume1/music        corellia,Yavin,stardestroyer
/volume1/sharedata_03 stardestroyer,Yavin
/volume1/homes        stardestroyer



hostname information
Hoth = NAS box
corellia = desktop (new)
stardestroyer = laptop
Yavin = desktop (old)
GeordieJedi
LXF regular
 
Posts: 369
Joined: Thu Jun 14, 2007 10:36 pm
Location: North East England


Return to Help!

Who is online

Users browsing this forum: No registered users and 5 guests