[Dorset] LAN connectivity problem

2022-01-23 Thread Graeme Gemmill
I would be grateful for suggestions to solve the following connection 
problem.

In the following description, D stands for 192.168.1
My router, D.1, has a control panel that identifies the following 
ethernet connected devices:

192.168.1.10     f0:2f:74:1f:d0:99       y
192.168.1.16 b8:27:eb:50:44:91    y
192.168.1.3       f4:30:b9:83:84:1c y
192.168.1.6       74:03:bd:0c:b0:38    y
192.168.1.9       40:16:7e:b4:09:e2    y

y indicates that the device passes traffic to the WAN

My laptop, D.3 shown the following devices by ip neigh:

192.168.1.1    enp1s0    c4:ea:1d:e4:27:a2    REACHABLE      Y
192.168.1.10  enp1s0    f0:2f:74:1f:d0:99   STALE     N
192.168.1.6    enp1s0    74:03:bd:0c:b0:38    STALE N
192.168.1.9    enp1s0    40:16:7e:b4:09:e2    STALE N

Y/N indicates ping success.
D.3 "knows about" D.6, D.9 and D.10 because they are in /etc/fstab as a 
result of previously successful connections.


D.9 acts as a server and shows the following by ip neigh:
192.168.1.1        enp2s0    c4:ea:1d:e4:27:a2   REACHABLE    Y
192.168.1.10      enp2s0    f0:2f:74:1f:d0:99  REACHABLE    Y
192.168.1.16      enp2s0    b8:27:eb:50:44:91 STALE   Y
192.168.1.6        enp2s0    74:03:bd:0c:b0:38 STALE   Y

D.10 is my main work PC, and shows the following via ip neigh:

192.168.1.1        enp5s0    c4:ea:1d:e4:27:a2    REACHABLE    Y
192.168.1.16      enp5s0    b8:27:eb:50:44:91    REACHABLE    Y
192.168.1.6        enp5s0    74:03:bd:0c:b0:38    STALE     Y
192.168.1.9        enp5s0    40:16:7e:b4:09:e2    REACHABLE    Y

D.6 ia a NAS box that both D.9 and D.10 can and do write to.
D.6, D.9, D.10 and D.16 are connected to D.1 via an 8-way Netgear hub
My problem: D.3 cannot reach D.9 or D.10, and neither D.9 nor D.10 can 
reach D.3, despite all being connected to D.1
(I hope the attempt at tabulating this data survives the translation to 
other mail clients)


--
Graeme Gemmill 01308 482178, 07792 713433
--
 Next meeting: Online, Jitsi, Tuesday, 2022-02-01 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk
 New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk


Re: [Dorset] LAN connectivity problem

2022-01-23 Thread Tim


How are the IP assign, DHCP or static?

If DHCP, are you sure you only have one DHCP server on the network

If on DHCP, try changing the ip renew time to something short like 2 
hours and then test?


Go to each PC and write down their network configuration, IP, Subnet, 
DNS, Gateway and then compare and make sure that are all the same (other 
than IP address)


Reboot the Netgear switch and router

Are you using a firewall\IPtables on any of the devices, can you turn 
off to test?


You don't say if there are all ethernet or mixed wifi ethernet

You could try installing wireshark on the device that are not talking to 
each other and see what wire shark says when you try to connect


Check workgroup\Domain names make sure they all have the same

When faced with a network issue these are the basics I look at, if all 
this comes back OK then we start looking for the bigger problems.



Tim H



On 23/01/2022 15:21, Graeme Gemmill wrote:
I would be grateful for suggestions to solve the following connection 
problem.

In the following description, D stands for 192.168.1
My router, D.1, has a control panel that identifies the following 
ethernet connected devices:

192.168.1.10     f0:2f:74:1f:d0:99       y
192.168.1.16 b8:27:eb:50:44:91    y
192.168.1.3       f4:30:b9:83:84:1c y
192.168.1.6       74:03:bd:0c:b0:38    y
192.168.1.9       40:16:7e:b4:09:e2    y

y indicates that the device passes traffic to the WAN

My laptop, D.3 shown the following devices by ip neigh:

192.168.1.1    enp1s0    c4:ea:1d:e4:27:a2    REACHABLE      Y
192.168.1.10  enp1s0    f0:2f:74:1f:d0:99   STALE     N
192.168.1.6    enp1s0    74:03:bd:0c:b0:38    STALE N
192.168.1.9    enp1s0    40:16:7e:b4:09:e2    STALE N

Y/N indicates ping success.
D.3 "knows about" D.6, D.9 and D.10 because they are in /etc/fstab as 
a result of previously successful connections.


D.9 acts as a server and shows the following by ip neigh:
192.168.1.1        enp2s0    c4:ea:1d:e4:27:a2   REACHABLE    Y
192.168.1.10      enp2s0    f0:2f:74:1f:d0:99  REACHABLE    Y
192.168.1.16      enp2s0    b8:27:eb:50:44:91 STALE Y
192.168.1.6        enp2s0    74:03:bd:0c:b0:38 STALE Y

D.10 is my main work PC, and shows the following via ip neigh:

192.168.1.1        enp5s0    c4:ea:1d:e4:27:a2    REACHABLE    Y
192.168.1.16      enp5s0    b8:27:eb:50:44:91    REACHABLE    Y
192.168.1.6        enp5s0    74:03:bd:0c:b0:38    STALE     Y
192.168.1.9        enp5s0    40:16:7e:b4:09:e2    REACHABLE    Y

D.6 ia a NAS box that both D.9 and D.10 can and do write to.
D.6, D.9, D.10 and D.16 are connected to D.1 via an 8-way Netgear hub
My problem: D.3 cannot reach D.9 or D.10, and neither D.9 nor D.10 can 
reach D.3, despite all being connected to D.1
(I hope the attempt at tabulating this data survives the translation 
to other mail clients)




--
 Next meeting: Online, Jitsi, Tuesday, 2022-02-01 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk
 New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk