Hi there. I have what must (?) be a simple problem, but it's got me
stumped. It's to do with why I can browse, but not ping, my default
gateway.
The Home Network:
Everything XP. Cable modem to DLink wireless router. Desktop LAN
connection to router. Router is default gateway for network. Router's
LAN-side IP is 192.168.0.1. Multiple laptops are on WLAN w/ encryption
key. Router is DHCP server, giving out IPs in the 192.168.0.1xx range.
No IP/MAC filter on router.
What Works:
Home desktop and laptops (all DHCP) work great. I bring home a work
laptop (also XP), and sign in to the WLAN with the key. Connected. Go
to cmd>ipconfig and I have new, valid IP (.0.1xx), same subnet mask and
default gateway as every other machine (192.168.0.1). Fire up IE on
work laptop and browse the built-in web interface on the router
(
http://192.168.0.1) and it pops up; log in and I can manage router.
Fine.
Where it Stops Working:
So you'd think if the router/default gateway is giving me TCP/IP
settings via DHCP and I can browse the web admin console on it, that
I'd be able to ping the router/gateway, right? Nope. Okay, can I ping
from the other machines? Sure. Try putting work laptop a wired
connection... restart... new IP address (within range of other WLAN
laptops), same gateway and mask ... still Destination Net Unreachable.
Check router filters ... nothing blocking pings ... add explicit rule
allowing to be sure; no difference.
What puzzles me is, if 192.168.0.1 is an unreachable destination from
my work laptop via ping, why can I hit it on http without a problem,
and get my DHCP settings (esp as I can ping from all other machines on
network)?
Am I missing something obvious? Any suggestions would be greatly
appreciated.
Thanks for any help,
Jeff
Similar Threads
