Why might one host be unable to access the Internet, when it can ping the router and when all other hosts can?
Posted
by
user1444233
on Server Fault
See other posts from Server Fault
or by user1444233
Published on 2013-07-03T14:56:03Z
Indexed on
2013/07/03
17:08 UTC
Read the original article
Hit count: 314
I have a Draytek Vigor 2830n. It's kicking out a 192.168.3.0 LAN. It performs load-balancing across dual-WAN ports, although I've turned off the second WAN to simplify testing. There are many hosts on the LAN. All IPs are allocated through DHCP, most freely allocated from the pool, but one or two are bound to NIC MAC addresses.
All hosts can access the Internet, save one. That host (192.168.3.100 or 'dot100' for short) gets allocated an IP address (and the right gateway address, DNS server addresses, subnet etc.) dot100 can ping itself. It can ping the gateway, and access the latter's web interface via port 80. It's responsive and loss-free (sustained ping over a couple of minutes reports no data loss). Yet, for some reason that evades me, dot100 can't ping an external IP address or domain name. I suspect it's never been able to, because it was getting some Internet access from a second adaptor (different subnet), but that's now been turned off, which exposed the problem.
In dot100, I've tried:
- two operating systems (Windows 8 and Knoppix), to rule out anti-virus programs etc.
- two physical adaptors
- two cables, on each adaptor
- two IPs (e.g. .100 and .103 assigned by Mac and .26 from the pool)
- both dynamic and assigned (MAC-bound) DHCP-allocated IPs
but none of this experiments yielded any variation in the result. dot100 is a crucial host. It's a file server for the network, so I need it to be reliably allocated a consistent IP. Can anyone offer a potential solution or a way forward with the analysis please?
My guess
My analysis so far leads me to believe it's a router issue. I've checked the web interface very carefully. There are no filters setup in Firewall -> General Setup or Filter Setup. I suspect it's a corrupted internal routing table, but the web UI shows this as the Routing table:
Key: C - connected, S - static, R - RIP, * - default, ~ - private
* 0.0.0.0/ 0.0.0.0 via 62.XX.XX.X WAN1
* 62.XX.XX.X/ 255.255.255.255 via 62.XX.XX.X WAN1
S 82.YY.YYY.YYY/ 255.255.255.255 via 82.YY.YYY.YYY WAN1
C 192.168.1.0/ 255.255.255.0 directly connected WAN2
C~ 192.168.3.0/ 255.255.255.0 directly connected LAN2
© Server Fault or respective owner