The ip addresses are all stable: they have been the same throughout all the time they've logged onto this network.Without knowing the specifics of the failure to connect, it is difficult to be specific; I'd start by checking to see if this is an addressing problem.
Use ifconfig (or ipconfig on Windows) to check the IP address of each system, and make sure they are sensible; examine the IP address and netmask to make sure they really are all on the same subnet (if that is what you want). Then ping from one to another using those IP addresses; don't use DNS or MDNS addresses, such as .local.
Sorry, but how would I tell?If they are on different subnets, use 'route' to work work out how packets might be routed (or mis-routed) between them.
And if it won't ping from A-B, then it doesn't have a route. Although I can ssh from A-C and ping from C-B, but I can't ping from C-A...
Is the simple answer just to tell it to refresh its connection? If so, then what's the best way to do that?Don't forget that if IP addresses are assigned using DHCP, they are dynamically allocated at boot-time, so relatively minor changes in the system configuration, or even the order in which systems are booted, can have an effect on the address value - and any mis-assignment may persist for quite a while, until the DHCP lease period expires.
Statistics: Posted by Hairyloon — Fri May 10, 2024 10:12 am