Hi Doc!
Could it be a DNS issue on the DHCP network?
slashdot.org resolves to: 216.105.38.15 across multiple public DNS servers when testing just now.
Have you flushed DNS on your CentOS laptop?
What DNS servers are you using on the Windows machine and on your DHCP network?
Hope that helps, let me know - thanks!
~Brian
The setup:
AT&T U-verse (new router) with internal DHCP and 3-bit IPv4 (five user
fixed IP addresses) network.
Windows 10 PC on copper Ethernet assigned to one of those fixed IP addresses.
CentOS 7.4 laptop on WiFi issued a non-routable DHCP address.
The problem:
The DHCP WiFi laptop cannot connect to slashdot.org (216.34.181.45). DNS
resolution works fine, but traceroute to the name and IP address both fail
after 30 hops.
The fixed IP Windows PC connects perfectly.
How can this be?
--Doc Savage
Fairview Heights, IL
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.