Failed to retrieve share list from server.

[trinidad]

Yes sir you can.

TC

[Robo_Pi]

You do not need the router for ad hoc. Uses no DHCP. Just leave it how you have it and set up your ad hocs.

Are you saying that I can just have the computers talk directly to each other using WiFi without using any router at all? 

I didn't know that. 

I don't know what you mean by "ad hocs".  I'll read your tutorials.   It sounds quite interesting.

[trinidad]

You certainly can network together ad hoc WIFI any machines you want to, Linux or Windows, and still be able to easily connect to the Internet via WIFI on the Linux machines. It's two different connections in NM on Linux. Turn them on and off with NM whichever you want to use at the time. Read through some of my old tutorials on this forum and you should be able to figure out a network set up that will be convenient for you.You do not need the router for ad hoc. Uses no DHCP. Just leave it how you have it and set up your ad hocs.

TC

hint: Linux addr convention will be 10.xx.xx.xx Windows will be 169.xx.xx.xx

[Robo_Pi]

Thanks for the info Trinidad,

I would love to isolate all but one of my computers from the Internet.   At least for the majority of the time.  I do use the "apt-get install" function on the linux machines quite often so I would need to be able to have Internet access for that.  But other than that my robots do not need access to the Internet and I would actually prefer if they were totally isolate from the Internet.

In fact, here's a question for you.

Could I disconnect my Netgear router from the verizon router entirely and run it as a "stand alone" WiFi connection for my robots so that it's not connected to the Internet at all?

I only need the WiFi for the robots.  I don't need the Internet.   I could always logon to the Verizon router if I need to download something from the Internet.   I've been meaning to look into this.  Now's the time to actually do it.

[trinidad]

Barefruits is simply working normally. It's kicking the logon because it's not Android.

Secondly you should consider ad hoc (default reserved for administrator maintenance) 169..x.x.x address range for the WIFI connections you wish to isolate from the web running Windows. You can directly connect them via WIFI then without running through your ISP or a router. The range is shorter but fine at 50feet in most cases. Windows won't tell you the address range is there but it is. You must set it up as an administrator from the command line in Windows. Linux will find the connection. Windows uses the APIPA (Automatic Private IP Addressing) Windows reserved range of IPv4 addresses (169.254.0.1 to 169.254.255.254) for its basic network manager auto-configure DHCP functionality. Basically these addresses are simply client fall back IP addresses included in Windows ARP to allow IP addresses to be assigned for connectivity when DHCP fails on a remote server, or for some reason on a Windows client. Tjhe only minor nuisance is that after using these addresses for connections to a Windows machine you must re-enable DHCP if you wish to connect the machine to the Internet again via WIFI.

https://www.linuxliteos.com/forums/tutorials/tutorial-ad-hoc-wifi-windows-10-and-ll-administrative-file-access/


TC

[ralphy]

No problem. I understand; that is a direct link from Malwayebytes website. Irrespective, if your PC is not infected, just make sure that it uses the local DNS from your network, then go back to your Linux Lite box and reconfigure it as needed. I think there is enough information in this thread to get you going.

Cheers!

[Robo_Pi]

This is really out of the scope of Linux Lite forum and support but since we've gobe this far, maybe it isn't too bad to also help you there.

Download MalwareBytes, install it, let it update and run a full scan. Remove all the bad stuff it finds.

https://data-cdn.mbamupdates.com/web/mb3-setup-consumer/mb3-setup-consumer-3.4.4.2398-1.0.322-1.0.4478.exe

With all due respect, I'm not about to run an executable file that someone just handed me on an Internet forum. 

That a big no-no for me. 

I'm going to bed now anyway.  So I'll return to looking into this tomorrow.   I can download MalewareBytes tomorrow.   I've run MalewareBytes before, but not on the Overseer.  Sheesh!  I just got done loading a brand new copy of Windows 10 on it from scratch.   This computer isn't much more than a week old in terms of the OS.   Brand new empty hard drive too.

I did download SharpDevelop, Geany, LibreOffice, and Quartus II FPGA design software.

Oh, yeah, I downloaded Visual Studio 2017 too.  But actually I could do without that.  SharpDevelop is much faster and does everything I need.  Visual Studio has some nice features, but it's clumsy slow.

Anyway, I'm off to bed for now.

Thanks for all your help thus far.

[ralphy]

By the way, I actually also found this:

Barefruit appears to be part of Verizon's DNS assistance program, where any DNS result that returns 'NXDOMAIN' gets forwarded to Barefruit to provide DNS suggestions and also to collect and sell information about your browsing habits. So, yes it's "legit" but a little shady. I'm not sure of the settings for non-US service, but there is a way to opt out of DNS suggestions in the States, by changing the DNS server IP used from .12 to .14 in your Verizon router.


https://askubuntu.com/questions/587895/why-is-the-ip-92-242-140-21-connecting-to-one-of-my-ports-is-it-malware

https://www.verizon.com/support/residential/internet/home-network/settings/opt-out-of-dns-assist


The strange thing to me is that in your case, your PC is redirecting (forwarding queries) to that IP address... as if it were infected and then DNS redirects to NXDOMAIN to prevent you from going to wherever something in it was taking you to.


Just run the scan to be safe. Then, let's look at that PC DNS settings, proxy settings, etc.

[Robo_Pi]

I just looked up the unallocated.barefruit.co.uk on Google.  From what I see it appears to have come from Verizon!  My IPS provider!

Gee whiz.  If it's coming from my Verizon router there isn't much hope in getting rid of it with any permanency.

[ralphy]

This is really out of the scope of Linux Lite forum and support but since we've gobe this far, maybe it isn't too bad to also help you there.

Download MalwareBytes, install it, let it update and run a full scan. Remove all the bad stuff it finds.

https://data-cdn.mbamupdates.com/web/mb3-setup-consumer/mb3-setup-consumer-3.4.4.2398-1.0.322-1.0.4478.exe

[Robo_Pi]

The IP 92.242.140.21 (unallocated.barefruit.co.uk) is not safe. The site has been known to distribute various adware. Chances are your PC is infected and being proxied out. So it is not using the local DNS for resolution. You need to clean that PC and remove the proxy settings. You've got owned!

Oh dag blast it!]

I just put a brand new hard drive in this machine and reinstalled Windows 10 from scratch.   And I'm already infected?

This sucks.

So how do I clean this out?  My computer is constantly running anti virus scans and reporting back that it never finds anything.   I try to only download from trusted sites, and I don't download anything I don't actually need.

So how do I get rid of this barefruit parasite?   

In fact, one reason I bought the second router is so I can use the WiFi without connecting to the Internet.   My robots don't need to be connected to the Internet.  But they do need to connect to each other via WiFi. 

I've been seriously thinking about taking all my computers off-line but one.   In fact, this is one reason why I moved over to Linux Lite.  The only problem there is that my favorite software (i.e. SharpDevelop for C#) won't run on Linux.  So I'm kind of stuck keeping Windows just for that alone.

So now I need to find out how to get rid of the barefruit parasite.   Owl go look that that up on Google right now.

[ralphy]

@Robo_Pi


Great job! Now you're becoming more aware about your network.


The IP 92.242.140.21 (unallocated.barefruit.co.uk) is not safe. The site has been known to distribute various adware. Chances are your PC is infected and being proxied out. So it is not using the local DNS for resolution. You need to clean that PC and remove the proxy settings. You've got owned! 


1- All computers on the network should use .home as the DNS resolver in your network. That's 192.168.1.1 in your case. By default that should be the DNS IP that should show up when running in a command prompt (Windows):

Code: [Select]

ipconfig /all | find "DNS Servers"

By default (as long as your PCs are not infected) they should be able to ping each other by using hostname.home (e.g.: ping Alysha.home)


Assuming that a PC is unable to find another PC by hostname (not being infected of course) you can manually force the suffix domain .home:





2- Some of your PCs are resolving on IPv6. You may want to consider disabling IPv6 on those computers and using IPv4 instead but this isn't a must.


After cleaning the infected machine and ensuring all machines can ping each other by hostname, let us know and we will get back to setting up Samba in Linux Lite. You're very close to get it all straighten and you have the skills for that and much more. Keep it up!

[Robo_Pi]

By the way, I noticed during the ping party that when Linux tries to access the Overseer it's using a really strange IP address as a "guess"?

All my computers are on 192.168.1.x

But when Linux tries to ping the Overseer by name it's using an IP address of 92.242.140.21

Where in the world is it coming up with that address?  That's not even close to my network at all.

[Robo_Pi]

I think that your main issue is a NetBIOS resolution issue on your network. Here are some more basic things you should try:

Code: [Select]

sudo apt-get install nmbd
sudo service nmbd start

I'll look into that.  But I think I have some issues on my Windows computers as well.  I may have more than one problem going on.

Of course, make sure you do not have a 3rd party firewall in windows either and if you do, then turn it off.

I'm just using whatever came with Windows 10.    I guess it's called "Windows Defender Firewall".   I haven't really done any special adjustments to it.  But I did turn it off for a while to try that, and that didn't seem to help.   I don't like leaving it off because I don't wan to leave myself open to getting some virus or something. 

On a side note, I am learning how to use Sockets which is my next step up in robot communications.  And I noticed that when I write a socket program Windows Defender asks me if I want to give it special firewall privileges when I go to run it.  Which I do.  But I'm not using sockets right now.  Right now I'm just trying to communicate with the robots using text files and FileSystemWatcher.

I'll upgrade to using socket later. After I learn more about how to use them.   They are complicated when it comes to programming because you need to use Delegates and Lamba functions in order to do other things while the socket server is running.  So I'm learning all about multithreading techniques. I'm getting there, but I have a lot to learn before I get that all ironed out.

Right now I just want to communicate by exchanging text files.  That's works really well for my purposes.  I've actually been doing this between Windows computers and it works well.  But I can't get the Raspberry Pi to write me a file.  So that's my big hold up right now.   My robots have Raspberry Pi brains. 

[Robo_Pi]

Ready for a PING PARTY? 

I'll be pinging from 6 computers the status of the other 5.

Here are the names of my 3 Windows computers:

Overseer - a freshly reinstalled Windows 10
HP-Elite - Brand new Windows 10 notebook
Win-8-HP - An older Windows 8 notebook that was slowly upgraded to Windows 10 by Microsoft.

Here are the names of 3 of my Linux computers:

Presario-CQ57 - Freshly installed Linux Lite notebook computer. (used to be a Windows computer)
Alysha - a Raspberry Pi A+ robot "brain"
Arathoon - a Raspberry Pi A+ robot "brain"

I have run an Advanced IP Scanner on the network and it reports the following:



I forget to mention I have two WiFi routers.  I hope that's not a problem.  It's a very long story as to why I'm using two. 
But just for the record the one named "verizon" above is the Verizon router provided by Verizon as my ISP.
The one named WNR2000v5 is a netgear router that is physically plugged into the Verizon router with a hardware cable.
This Netgear Router is what I logon to as my WiFi connection.  The Netgear router is called Robo_SID as a WiFi name.
I manually set the Netgear router to IP address 192.168.1.12 because I didn't want it to be assigned a dynamic IP from the verizon router.   These routers have been like this for several years.  I haven't noticed a problem until now.  So I hope it's not a problem with this router arrangement.  (there are more reasons why I did this that I think would be a distraction at this point in time, so I won't get into that here)

I also notice on the IP Scan that everything has a .home after it except the Overseer and the Win-8-HP suggesting that something is different about those two computers.

Things to note about the Windows computers.

I set the Overseer to a constant IP address of 192.168.1.10
I did this because I'm using the Overseer to oversee the robots.  So the Robots need to know the IP address of their overseer.
The other two Windows computers are assigned IP addresses dynamically by Robo_SID (the NetGear Router)

This Linux computers.

Presario-CQ57 is the Linux Lite notebook.  It also has a dynamically assigned IP address by the Robo_SID WiFi router.
Alysha and Arathoon both have static IP addresses set to 192.168.1.200 and 201.

And now for the Ping Party,....

The Linux Presario-CQ57 pings all other computers:

Code: [Select]

Pinging Overseer by name

james-cq57@Presario-CQ57:~$ ping Overseer
PING Overseer (92.242.140.21) 56(84) bytes of data.

--- Overseer ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2017ms

Pinging Overseer by IP address

james-cq57@Presario-CQ57:~$ ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_seq=1 ttl=128 time=3.35 ms
64 bytes from 192.168.1.10: icmp_seq=2 ttl=128 time=2.93 ms
64 bytes from 192.168.1.10: icmp_seq=3 ttl=128 time=3.09 ms
^C
--- 192.168.1.10 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.939/3.128/3.356/0.178 ms

Pinging HP-Elite by name

james-cq57@Presario-CQ57:~$ ping HP-Elite
PING HP-Elite.home (192.168.1.13) 56(84) bytes of data.
64 bytes from HP-Elite.home (192.168.1.13): icmp_seq=1 ttl=128 time=3.51 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_seq=2 ttl=128 time=2.97 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_seq=3 ttl=128 time=3.31 ms
^C
--- HP-Elite.home ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.978/3.268/3.515/0.221 ms


Pinging Win-8-HP by name

james-cq57@Presario-CQ57:~$ ping win-8-hp
PING win-8-hp.home (192.168.1.8) 56(84) bytes of data.
From Presario-CQ57.home (192.168.1.7) icmp_seq=1 Destination Host Unreachable
From Presario-CQ57.home (192.168.1.7) icmp_seq=2 Destination Host Unreachable
From Presario-CQ57.home (192.168.1.7) icmp_seq=3 Destination Host Unreachable

--- win-8-hp.home ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5026ms

Pinging Win-8-HP by IP address

james-cq57@Presario-CQ57:~$ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
64 bytes from 192.168.1.4: icmp_seq=1 ttl=128 time=3.58 ms
64 bytes from 192.168.1.4: icmp_seq=2 ttl=128 time=14.7 ms
64 bytes from 192.168.1.4: icmp_seq=3 ttl=128 time=16.9 ms

--- 192.168.1.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 3.582/11.823/16.923/4.911 ms

Pinging Alysha

james-cq57@Presario-CQ57:~$ ping Alysha
PING Alysha.home (192.168.1.200) 56(84) bytes of data.
64 bytes from Alysha.home (192.168.1.200): icmp_seq=1 ttl=64 time=13.9 ms
64 bytes from Alysha.home (192.168.1.200): icmp_seq=2 ttl=64 time=7.55 ms
64 bytes from Alysha.home (192.168.1.200): icmp_seq=3 ttl=64 time=7.65 ms
^C
--- Alysha.home ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 7.550/9.710/13.932/2.987 ms

Pinging Arathoon

james-cq57@Presario-CQ57:~$ ping Arathoon
PING Arathoon.home (192.168.1.11) 56(84) bytes of data.
From Presario-CQ57.home (192.168.1.7) icmp_seq=1 Destination Host Unreachable
From Presario-CQ57.home (192.168.1.7) icmp_seq=2 Destination Host Unreachable
From Presario-CQ57.home (192.168.1.7) icmp_seq=3 Destination Host Unreachable

--- Arathoon.home ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4023ms

Pinging Arathoon by IP Address

james-cq57@Presario-CQ57:~$ ping 192.168.1.201
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_seq=1 ttl=64 time=286 ms
64 bytes from 192.168.1.201: icmp_seq=2 ttl=64 time=9.22 ms
64 bytes from 192.168.1.201: icmp_seq=3 ttl=64 time=114 ms
64 bytes from 192.168.1.201: icmp_seq=4 ttl=64 time=135 ms
^C
--- 192.168.1.201 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 9.221/136.483/286.547/98.996 ms

The Linux Raspberry Pi Alysha pings all other computers:
(note: The results here are pretty much identical to what Linux Lite got on the Notebook.)

Code: [Select]

Pinging Overseer by name

pi@Alysha ~ $ ping Overseer
PING Overseer (92.242.140.21) 56(84) bytes of data.
^C
--- Overseer ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6002ms

Pinging Overseer by IP Address

pi@Alysha ~ $ ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_req=1 ttl=128 time=17.8 ms
64 bytes from 192.168.1.10: icmp_req=2 ttl=128 time=4.98 ms
64 bytes from 192.168.1.10: icmp_req=3 ttl=128 time=6.45 ms
64 bytes from 192.168.1.10: icmp_req=4 ttl=128 time=6.57 ms
^C
--- 192.168.1.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 4.980/8.971/17.875/5.179 ms

Pinging HP-Elite by name

pi@Alysha ~ $ ping HP-Elite
PING HP-Elite.home (192.168.1.13) 56(84) bytes of data.
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=1 ttl=128 time=7.23 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=2 ttl=128 time=7.38 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=3 ttl=128 time=7.13 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=4 ttl=128 time=7.10 ms
^C
--- HP-Elite.home ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 7.104/7.214/7.386/0.150 ms

Pinging Win-8-HP by name

pi@Alysha ~ $ ping Win-8-HP
PING Win-8-HP.home (192.168.1.8) 56(84) bytes of data.
From Alysha.home (192.168.1.200) icmp_seq=1 Destination Host Unreachable
From Alysha.home (192.168.1.200) icmp_seq=2 Destination Host Unreachable
From Alysha.home (192.168.1.200) icmp_seq=3 Destination Host Unreachable
^C
--- Win-8-HP.home ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4075ms
pipe 3

Pinging Win-8-HP by IP Address

pi@Alysha ~ $ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
64 bytes from 192.168.1.4: icmp_req=1 ttl=128 time=13.4 ms
64 bytes from 192.168.1.4: icmp_req=2 ttl=128 time=12.1 ms
64 bytes from 192.168.1.4: icmp_req=3 ttl=128 time=9.89 ms
64 bytes from 192.168.1.4: icmp_req=4 ttl=128 time=7.63 ms
^C
--- 192.168.1.4 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 7.634/10.784/13.459/2.222 ms

Pinging Arathoon by name

pi@Alysha ~ $ ping Arathoon
PING Arathoon.home (192.168.1.11) 56(84) bytes of data.
From Alysha.home (192.168.1.200) icmp_seq=1 Destination Host Unreachable
From Alysha.home (192.168.1.200) icmp_seq=2 Destination Host Unreachable
From Alysha.home (192.168.1.200) icmp_seq=3 Destination Host Unreachable
^C
--- Arathoon.home ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3045ms
pipe 3

Pinging Arathoon by IP Address

pi@Alysha ~ $ ping 192.168.1.201
PING 192.168.1.201 (192.168.1.201) 56(84) bytes of data.
64 bytes from 192.168.1.201: icmp_req=1 ttl=64 time=1607 ms
64 bytes from 192.168.1.201: icmp_req=2 ttl=64 time=604 ms
64 bytes from 192.168.1.201: icmp_req=3 ttl=64 time=12.9 ms
64 bytes from 192.168.1.201: icmp_req=4 ttl=64 time=12.9 ms
^C
--- 192.168.1.201 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 12.928/559.529/1607.327/651.433 ms, pipe 2

Pinging Presario-CQ57 (Linux Lite Notebook)

pi@Alysha ~ $ ping Presario-CQ57
PING Presario-CQ57.home (192.168.1.7) 56(84) bytes of data.
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=1 ttl=64 time=932 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=2 ttl=64 time=33.6 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=3 ttl=64 time=56.5 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=4 ttl=64 time=7.85 ms
^C
--- Presario-CQ57.home ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 7.855/257.580/932.240/389.896 ms



The Linux Raspberry Pi Arathoon pings all other computers:
WHOA!  WHAT'S THIS???   unallocated.barefruit.co.uk when trying to Ping Overseer by name?
Everything else looks pretty much the same as the other Linux computers.

Code: [Select]

Pinging Overseer by name

pi@Arathoon ~ $ ping Overseer
PING Overseer (92.242.140.21) 56(84) bytes of data.
64 bytes from unallocated.barefruit.co.uk (92.242.140.21): icmp_req=1 ttl=246 time=83.8 ms
64 bytes from unallocated.barefruit.co.uk (92.242.140.21): icmp_req=2 ttl=246 time=80.7 ms
64 bytes from unallocated.barefruit.co.uk (92.242.140.21): icmp_req=3 ttl=246 time=78.7 ms
^C
--- Overseer ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 78.743/81.091/83.820/2.115 ms

Pinging Overseer by name again,...

pi@Arathoon ~ $ ping Overseer
PING Overseer (92.242.140.21) 56(84) bytes of data.
^C
--- Overseer ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10006ms

Pinging Overseer by IP Address

pi@Arathoon ~ $ ping 192.168.1.10
PING 192.168.1.10 (192.168.1.10) 56(84) bytes of data.
64 bytes from 192.168.1.10: icmp_req=1 ttl=128 time=388 ms
64 bytes from 192.168.1.10: icmp_req=2 ttl=128 time=7.49 ms
64 bytes from 192.168.1.10: icmp_req=3 ttl=128 time=6.51 ms
64 bytes from 192.168.1.10: icmp_req=4 ttl=128 time=6.49 ms
^C
--- 192.168.1.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 6.494/102.271/388.578/165.299 ms

Pinging HP-Elite by name

pi@Arathoon ~ $ ping HP-Elite
PING HP-Elite.home (192.168.1.13) 56(84) bytes of data.
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=1 ttl=128 time=7.08 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=2 ttl=128 time=6.96 ms
64 bytes from HP-Elite.home (192.168.1.13): icmp_req=3 ttl=128 time=7.32 ms
^C
--- HP-Elite.home ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 6.963/7.123/7.320/0.148 ms

Pinging Win-8-HP by name

pi@Arathoon ~ $ ping Win-8-HP
PING Win-8-HP.home (192.168.1.8) 56(84) bytes of data.
From Arathoon.home (192.168.1.201) icmp_seq=1 Destination Host Unreachable
From Arathoon.home (192.168.1.201) icmp_seq=2 Destination Host Unreachable
From Arathoon.home (192.168.1.201) icmp_seq=3 Destination Host Unreachable
^C
--- Win-8-HP.home ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3045ms
pipe 3

Pinging Win-8-HP by IP Address

pi@Arathoon ~ $ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.
64 bytes from 192.168.1.4: icmp_req=1 ttl=128 time=9.60 ms
64 bytes from 192.168.1.4: icmp_req=2 ttl=128 time=14.0 ms
64 bytes from 192.168.1.4: icmp_req=3 ttl=128 time=8.38 ms
^C
--- 192.168.1.4 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 8.387/10.668/14.015/2.420 ms

Pinging Alysha

pi@Arathoon ~ $ ping Alysha
PING Alysha.home (192.168.1.200) 56(84) bytes of data.
64 bytes from Alysha.home (192.168.1.200): icmp_req=1 ttl=64 time=11.5 ms
64 bytes from Alysha.home (192.168.1.200): icmp_req=2 ttl=64 time=11.9 ms
64 bytes from Alysha.home (192.168.1.200): icmp_req=3 ttl=64 time=218 ms
64 bytes from Alysha.home (192.168.1.200): icmp_req=4 ttl=64 time=36.1 ms
^C
--- Alysha.home ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 11.578/69.540/218.481/86.565 ms

Pinging Presario-CQ57 (Linux Lite on Notebook)

pi@Arathoon ~ $ ping Presario-CQ57
PING Presario-CQ57.home (192.168.1.7) 56(84) bytes of data.
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=1 ttl=64 time=7.85 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=2 ttl=64 time=7.47 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=3 ttl=64 time=9.15 ms
64 bytes from Presario-CQ57.home (192.168.1.7): icmp_req=4 ttl=64 time=9.47 ms
^C
--- Presario-CQ57.home ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 7.476/8.489/9.471/0.845 ms

The Windows Overseer pings all other computers:
(note: The Overseer seems to be weird in that it appears to be using strange Hex numbers in some cases.)

Code: [Select]

Pinging HP-Elite by name

C:\Users\antiq>ping HP-Elite

Pinging HP-Elite [fe80::ad3a:c714:bfae:4b2%7] with 32 bytes of data:
Reply from fe80::ad3a:c714:bfae:4b2%7: time=2ms
Reply from fe80::ad3a:c714:bfae:4b2%7: time=2ms
Reply from fe80::ad3a:c714:bfae:4b2%7: time=6ms
Reply from fe80::ad3a:c714:bfae:4b2%7: time=1ms

Ping statistics for fe80::ad3a:c714:bfae:4b2%7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 6ms, Average = 2ms

Pinging HP-Elite by IP Address

C:\Users\antiq>ping 192.168.1.13

Pinging 192.168.1.13 with 32 bytes of data:
Reply from 192.168.1.13: bytes=32 time=4ms TTL=128
Reply from 192.168.1.13: bytes=32 time=1ms TTL=128
Reply from 192.168.1.13: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.13:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 4ms, Average = 2ms

Pinging Win-8-HP by name

C:\Users\antiq>ping Win-8-HP

Pinging Win-8-HP [fe80::c5e7:23c3:54a4:97c3%7] with 32 bytes of data:
Reply from fe80::c5e7:23c3:54a4:97c3%7: time=6ms
Reply from fe80::c5e7:23c3:54a4:97c3%7: time=6ms
Reply from fe80::c5e7:23c3:54a4:97c3%7: time=10ms
Reply from fe80::c5e7:23c3:54a4:97c3%7: time=6ms

Ping statistics for fe80::c5e7:23c3:54a4:97c3%7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 10ms, Average = 7ms

Pinging Win-8-HP by IP Address

C:\Users\antiq>ping 192.168.1.4

Pinging 192.168.1.4 with 32 bytes of data:
Reply from 192.168.1.4: bytes=32 time=14ms TTL=128
Reply from 192.168.1.4: bytes=32 time=5ms TTL=128
Reply from 192.168.1.4: bytes=32 time=4ms TTL=128

Ping statistics for 192.168.1.4:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 14ms, Average = 7ms

Pinging  Alysha by name

C:\Users\antiq>ping Alysha
Ping request could not find host Alysha. Please check the name and try again.

PInging Alysha by IP Address

C:\Users\antiq>ping 192.168.1.200

Pinging 192.168.1.200 with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=6ms TTL=64
Reply from 192.168.1.200: bytes=32 time=179ms TTL=64
Reply from 192.168.1.200: bytes=32 time=192ms TTL=64
Reply from 192.168.1.200: bytes=32 time=212ms TTL=64

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 212ms, Average = 147ms

Pinging Arathoon by name

C:\Users\antiq>ping Arathoon
Ping request could not find host Arathoon. Please check the name and try again.

Pinging Arathoon by IP Address

C:\Users\antiq>ping 192.168.1.201

Pinging 192.168.1.201 with 32 bytes of data:
Reply from 192.168.1.201: bytes=32 time=24ms TTL=64
Reply from 192.168.1.201: bytes=32 time=28ms TTL=64
Reply from 192.168.1.201: bytes=32 time=35ms TTL=64
Reply from 192.168.1.201: bytes=32 time=43ms TTL=64

Ping statistics for 192.168.1.201:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 43ms, Average = 32ms

Pinging Presario-CQ57 by name (Linux Lite notebook)

C:\Users\antiq>ping Presario-CQ57

Pinging Presario-CQ57 [192.168.1.7] with 32 bytes of data:
Reply from 192.168.1.7: bytes=32 time=2ms TTL=64
Reply from 192.168.1.7: bytes=32 time=2ms TTL=64
Reply from 192.168.1.7: bytes=32 time=4ms TTL=64
Reply from 192.168.1.7: bytes=32 time=553ms TTL=64

Ping statistics for 192.168.1.7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 553ms, Average = 140ms

Hey!  That worked!

The Windows HP-Elite pings all other computers:
(note: using strange hex numbers when pinging Overseer by name)

Code: [Select]

Pinging the Overseer by name

C:\Users\antiq>ping Overseer

Pinging Overseer [fe80::98af:5c2a:ed9a:dad1%5] with 32 bytes of data:
Reply from fe80::98af:5c2a:ed9a:dad1%5: time=1ms
Reply from fe80::98af:5c2a:ed9a:dad1%5: time=2ms
Reply from fe80::98af:5c2a:ed9a:dad1%5: time=3ms
Reply from fe80::98af:5c2a:ed9a:dad1%5: time=1ms

Ping statistics for fe80::98af:5c2a:ed9a:dad1%5:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 3ms, Average = 1ms

Pinging the Overseer by IP Address

C:\Users\antiq>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time=2ms TTL=128
Reply from 192.168.1.10: bytes=32 time=2ms TTL=128
Reply from 192.168.1.10: bytes=32 time=1ms TTL=128
Reply from 192.168.1.10: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

Pinging Win-8-HP by name

C:\Users\antiq>ping Win-8-HP

Pinging Win-8-HP.home [192.168.1.4] with 32 bytes of data:
Reply from 192.168.1.4: bytes=32 time=11ms TTL=128
Reply from 192.168.1.4: bytes=32 time=5ms TTL=128
Reply from 192.168.1.4: bytes=32 time=21ms TTL=128
Reply from 192.168.1.4: bytes=32 time=9ms TTL=128

Ping statistics for 192.168.1.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 21ms, Average = 11ms

Pinging Alysha by name

C:\Users\antiq>ping Alysha

Pinging Alysha.home [192.168.1.200] with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time=135ms TTL=64
Reply from 192.168.1.200: bytes=32 time=151ms TTL=64
Reply from 192.168.1.200: bytes=32 time=159ms TTL=64
Reply from 192.168.1.200: bytes=32 time=178ms TTL=64

Ping statistics for 192.168.1.200:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 135ms, Maximum = 178ms, Average = 155ms

Pinging Arathoon by name

C:\Users\antiq>ping Arathoon

Pinging Arathoon.home [192.168.1.201] with 32 bytes of data:
Reply from 192.168.1.201: bytes=32 time=94ms TTL=64
Reply from 192.168.1.201: bytes=32 time=112ms TTL=64
Reply from 192.168.1.201: bytes=32 time=123ms TTL=64
Reply from 192.168.1.201: bytes=32 time=142ms TTL=64

Ping statistics for 192.168.1.201:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 94ms, Maximum = 142ms, Average = 117ms

Pinging Presario-CQ57 (Linux Lite notebook) by name

C:\Users\antiq>ping Presario-CQ57

Pinging Presario-CQ57.home [192.168.1.7] with 32 bytes of data:
Reply from 192.168.1.7: bytes=32 time=542ms TTL=64
Reply from 192.168.1.7: bytes=32 time=556ms TTL=64
Reply from 192.168.1.7: bytes=32 time=576ms TTL=64
Reply from 192.168.1.7: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 576ms, Average = 419msC:\Users\antiq>ping Presario-CQ57

Pinging Presario-CQ57.home [192.168.1.7] with 32 bytes of data:
Reply from 192.168.1.7: bytes=32 time=542ms TTL=64
Reply from 192.168.1.7: bytes=32 time=556ms TTL=64
Reply from 192.168.1.7: bytes=32 time=576ms TTL=64
Reply from 192.168.1.7: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 576ms, Average = 419ms

The Windows Win-8-HP pings all other computers:

Code: [Select]

Sorry, the command prompt on this computer won't allow copying of text.

In any case the Win-8-HP computer was able to ping all other computer successfully by name.
In ever case it reported back the correct IP addresses for all computers.
EXCEPT in the case of the Overseer, which it appears to have pinged ok by name,
but once again it reported back using strange Hex numbers instead of decimal IP addresses.

Clearly something's different about the Overseer that it's using hex numbers instead of decimal IP addresses.
I have no clue why.

Well, there's the data.  I'm not well-versed in IP/name resolution to know what's going on.

I have all this data printed out.  It will no doubt be helpful as I continue to try to figure out what's going on.

I've lost a week on this already, and it looks like I'm going to be spending another week trying to figure out what's wrong.

At least now I know that I have some inconsistencies in my networking configurations.  The problem most likely doesn't have anything to do with Samba.  Although I still don't understand why the Linux machines can't see each other.  They seem to be able to ping each other by name.   Why aren't they showing up on each other's WORKGROUP?  They are all set to WORKGROUP.

I might have a whole can of worms here.