NAS Herder / Discussion / General Discussion: Ping / Communication failure query....

Andy Barnett - 2017-02-04

Hi ,

I have a couple of ReadyNAS 1100's here on the network, and having been
using your excellent tool for quite a while, I've just noticed that my
laptop can't see either box (not sure for how long, but I know it used to
work!)...

The boxes are working fine and I can ping both of them with about a 3 ms
response, and RAIDar can see both devices, but for some unknown reason my
NAS Herders are having a problem.

I'm running as recommended with 2 separate instances of Ver 1.25 on Windows
10 Home, but the ping fails as does the scan on both instances.

I've just checked yet again and each instance has the correct host name MAC
and IP address configured, but the ping and scan both fail even with the
laptops firewall down, I'm not sure where to go from here...

Any ideas?

Andy B.

alternate

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

EMO - 2017-02-07

Hi Andy,
Thank you for using this app.
There might be an issure in parsing RAIDar response. Could you post the responses from your systems by copy and paste from Raw Response box in Scan Dialog?
EMO

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-21

Hi EMO,

Apologies for not getting back to you sooner, my wife has been very ill (in Hospital)

I've attached a screen grab from RAIDar which proves the connectivity, however looking at the scan the raw data is blank...

I've also attached a copy of the current log for nas-1 (192.168.123.20) though I don't think it will tell you much.

Have no idea where to go from here, unless it's something to do with me using Wi-Fi?

Andy B

2017-02-21_195823.png

log20170221.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-22

Interestingly enough if I change to use SSL rather than RAIDar ping starts to work but thats about all - scan/raw data is still empty, log and screen grab attached...

Andy B.

Last edit: Andy Barnett 2017-02-22

2017-02-22_134109.png

log20170222.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- EMO - 2017-02-23
  
  Hi, Andy,
  
  I need the response(s) from ReadyNAS systems.
  Go "Tool" -> Go "Scan" -> Push "Scan ReadyNAS in LAN" -> Check "Show raw response" -> Push "Copy to clipboard" -> Paste the content here.
  
  EMO
  
  Last edit: EMO 2017-02-23
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-23

Hi EMO,

Sorry if I didn't make myself clear previously "Scan" does not detect any connected devices and the raw response is empty. so there is nothing for me to cut and paste. RAIDar however works quite happily.

For information, the source machine is running Windows 10 Home, Nas Herder is running "as administrator", the firewall is currently off, and RAIDar happily indicates my two devices as expected.

Could this be a .NET issue?

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-24

OK, I've been playing around a bit more...

Spinning up a Windows 7 VM (Virtual Box on the same laptop) to test with works exactly as expected, detecting both my NAS devices and pulling in live monitor information.

Now I'm really confused!

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-24

Make that even more confued, if I uninstall Virtual Box from my laptop Nas Herder works perfectly for both my devices...

Thoughts?

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-26

OK, having now tried VMware Workstation Player as well as Virtual Box...

It would appear that the installation of either of these packages breaks network connectivity in Nas Herder, I'm guessing that the modifications either of these packages make to network connectivity are at the root of the problem.

It's interesting to note however that with either of these packages installed RAIDar (4.3.8) carries on working as expected...

Andy B

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- EMO - 2017-02-27
  
  Hi, Andy,
  
  Thank you for your information on investigating this issue.
  It seems that the network communication by this app is somehow blocked. It uses the standard UDP client functions of .NET Framework for getting basic information from NAS systems. If such communication is blocked by some security or firewall software (It often happens), there is nothing this app can do on its own. It calls for responses from NAS systems by UDP bloadcasting and if it is blocked, no response will be returned.
  I have no idea on what conditions such communication is allowed or blocked under each specific environment.
  
  EMO
  
  Last edit: EMO 2017-02-27
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-27

Hi EMO,

I think the situation may be simpler than that, I have a sneaking feeling Nas Herder may be "looking on the wrong network" when virtualization software is installed. Unfofrtunately I don't have a machine with two network cards spare to play with at the moment, but how would Nas Herder handle the scan if there were two cards?

Out of interest I spun up a Windows 7 client on Virtual Box while I was testing installing Nas Herder on the client worked flawlesly, it just seems to be screwed up on the host...

Thoughts?

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-02-27

Sussed it!

The problem is caused by the virtual "Host Only" network card installed with either application which somehow interferes with Nas Herders network connectivity. (It's used to create a host only private network for the client machines to communicate with each other, however on the host machine it looks like an additional network card.)

Disabling this virtual network card by-passes the issue but obviously reduces the functionality of the virtualization software.

Andy B.

Last edit: Andy Barnett 2017-02-28

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- EMO - 2017-02-28
  
  Hi, Andy,
  
  It's interestring. Actually, this app neither know about each network interface nor select a specific network interface to be used. It is left to .NET Framework and OS.
  
  EMO
  
  Last edit: EMO 2017-02-28
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-03-01

Hi EMO,

At least I've got everything I need working now (virtual linux boxes using nfs shares from a nas with monitoring) and you have an idea about what could be happening if someone else has similar problems.

Thanks for your time...

Andy B

PS I'm happy to beta test etc in the future if needed!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

EMO - 2017-03-02

Hi, Andy,
Could you try the test program and post its result?
https://sourceforge.net/projects/nasherder/files/samplecode/RAIDarProtocolTest.zip/download
It may or may not change though.

EMO

Last edit: EMO 2017-03-02

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-03-03

No Problem EMO,

With the Virtual Host-Only Network card ENABLED (ie with the problem) I get:

[Address:255.255.255.255, Enabled:True]
No response
[Address:255.255.255.255, Enabled:False]
No response
[Address:192.168.255.255, Enabled:True]
No response
[End]

With the Virtual Host-Only Network card DISABLED I get:

[Address:255.255.255.255, Enabled:True]
00:0d:a2:10:22:6b
nas-1
192.168.123.20
power!!1.5!!status=ok::descr=1.600::expected=1.5
power!!2.5!!status=ok::descr=2.608::expected=2.5
power!!3.3!!status=ok::descr=3.424::expected=3.3
power!!5.0!!status=ok::descr=5.130::expected=5.0
temp!!1!!status=ok::descr=39.0C/102.2F::expected=2-80C/35-176F
temp!!2!!status=ok::descr=28.0C/82.4F::expected=2-60C/35-140F
fan!!1!!status=ok::descr=4560RPM
fan!!2!!status=ok::descr=3924RPM
fan!!3!!status=ok::descr=6026RPM
ups!!1!!status=ok::descr=APC Smart-UPS 750 Battery charge: 100%, 28 min
volume!!1!!status=ok::descr=Volume C: RAID Level X, Redundant; 1970 GB (35%) of 5538 GB used
disk!!1!!status=ok::descr=Channel 1: Seagate ST2000DM001-1CH164 1863 GB, 19C/66F
disk!!2!!status=ok::descr=Channel 2: Seagate ST2000DM001-1CH164 1863 GB, 18C/64F
disk!!3!!status=ok::descr=Channel 3: Seagate ST2000DM001-1ER164 1863 GB, 17C/62F
disk!!4!!status=ok::descr=Channel 4: Seagate ST2000DM001-1ER164 1863 GB, 18C/64F
model!!0!!mode=pro::descr=ReadyNAS 1100::arch=nsp
RAIDiator!!version=4.1.15,time=1430169576
66

[Address:255.255.255.255, Enabled:False]
00:0d:a2:10:30:1e
nas-2
192.168.123.21
power!!1.5!!status=ok::descr=1.600::expected=1.5
power!!2.5!!status=ok::descr=2.592::expected=2.5
power!!3.3!!status=ok::descr=3.456::expected=3.3
power!!5.0!!status=ok::descr=5.184::expected=5.0
temp!!1!!status=ok::descr=38.0C/100.4F::expected=2-80C/35-176F
temp!!2!!status=ok::descr=27.0C/80.6F::expected=2-60C/35-140F
fan!!1!!status=ok::descr=4821RPM
fan!!2!!status=ok::descr=4017RPM
fan!!3!!status=ok::descr=6490RPM
ups!!1!!status=ok::descr=Remote APC Smart-UPS 750 Battery charge: 100%, 29 min
volume!!1!!status=ok::descr=Volume C: RAID Level X, Redundant; 1925 GB (34%) of 5538 GB used
disk!!1!!status=ok::descr=Channel 1: Seagate ST2000DM001-1CH164 1863 GB, 18C/64F
disk!!2!!status=ok::descr=Channel 2: Seagate ST2000DM001-1CH164 1863 GB, 17C/62F
disk!!3!!status=ok::descr=Channel 3: Seagate ST2000DM001-1CH164 1863 GB, 17C/62F
disk!!4!!status=ok::descr=Channel 4: Seagate ST2000DM001-1CH164 1863 GB, 17C/62F
model!!0!!mode=pro::descr=ReadyNAS 1100::arch=nsp
RAIDiator!!version=4.1.15,time=1430169576
66

[Address:192.168.255.255, Enabled:True]
No response
[End]

I'm intrigued now, please keep me in the loop!

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- EMO - 2017-03-03
  
  Hi, Andy,
  
  Thank you for testing.
  Unfortunately, the test result shows that the change of settings when sending the request will not help. May I clarify you are running this app on host OS or guest OS? If guest OS, there will be no wonder it cannot communicate outside of host OS.
  
  EMO
  
  Last edit: EMO 2017-03-03
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-03-04

Hi EMO,

Nas Herder/the Test Program is running on the host which is running windows 10 Home 64 bit,

I usually use virtulazation to run a linux client (Debian), However when I first started to investigate the Nas Herder issue I built a Windows 7 32 bit client and configured it to use a bridged network. Contary to your feeling, it ran Nas Herder quite happily even though the host was failing to do so at the same time.

It is definately related to the presence of an enabled Host-Only network card on the host. If I disable this card everything works as expected (except Host-Only networking!) - see attached...

Note: a similar host-only adapter is created if I use VMware Player (instead of Virtual Box) which has exactly the same issue on the host.

Andy B.

Last edit: Andy Barnett 2017-03-04

2017-03-04_064337.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

EMO - 2017-03-08

Hi Andy,

I myself tried VMware Workstation Player on the latest Windows 10 and ran this app from this host OS while running another Windows 10 as guest OS. It worked fine and successfully received a response from NAS system regardless of whether host-only settings is on or off.
I have no further clue.

EMO

Last edit: EMO 2017-03-08

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andy Barnett - 2017-03-08

Hi EMO,

I have the connectivity I need for the moment so I'll just say many thanks for your time - I shall pester you no more...

Many thanks for yhour time!

Andy B.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ping / Communication failure query....

A remote management tool for ReadyNAS series of NAS

Forums

Help

Ping / Communication failure query....

Ping / Communication failure query....

A remote management tool for ReadyNAS series of NAS

Forums

Help

Ping / Communication failure query.... document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

Ping / Communication failure query....