The LAN side of main
router (at IP address
192.168.1.254) is supplying the following services for your local area network (LAN):
o Default Gateway
o DHCP Server
o DNS Server
When you ping the numeric IP address,
69.72.169.241, for ComputerHope; the
routing table within the "pinging" computer has no specific route for that address so it uses the
default route identified in route table by a Network Destination and Netmask of "0.0.0.0 0.0.0.0". The default route sends it to 192.168.1.254 (
default gateway to get off your LAN) through interface
192.168.1.65 (your wireless network adapter).
This ping is successful both with or without wired LAN adapter connected because there's no ambiguity in the route table. There's only one default route entry. (Note: You should be able to access ComputerHope website in browser by typing "
http://69.72.169.241" in address field).
When you ping a Fully Qualified Domain Name (FQDN) of a website which is not in your local DNS cache or hosts file such as "
www.computerhope.com" or "
www.msn.com"; your computer submits a Domain Name System (DNS) resolution request to the
DNS server (
192.168.1.254) to translate the FQDN to a numeric IP address.
With wired LAN adapter
disconnected, the route table uses Network Destination
192.168.1.0 whose gateway is
192.168.1.65 through interface 192.168.1.65. Again, the DNS resolution request is successfully sent because there's no ambiguity in the route. (And you have internet access).
With wired LAN adapter
connected, the route table picks up several additional entries. One of these is another entry for Network Destination
192.168.1.0 whose metric is
20 (lower than 25, so it's considered better route than original). Now when your computer submits a DNS resolution request to
DNS server 192.168.1.254, I believe the new
better route is selected. Route table says use gateway 192.168.1.1 accessed through interface 192.168.1.1 (wired network adapter). DNS server isn't on that route, so
www.computerhope.com or whatever never gets resolved to a numeric IP address and browser doesn't know where to connect (
so you have no internet).
To test this theory,
modify route table when wired network adapter is connected. Try one of the following three options starting at the top:
a.
Add specific route for DNS server
192.168.1.254. Try command:
"route ADD 192.168.1.254 MASK 255.255.255.255 192.168.1.65 METRIC 10"
b.
Modify the
metric for Network Destination
192.168.1.0 to make path through interface 192.168.1.65 better (either lower it or raise value for 192.168.1.1). Try command:
"route CHANGE 192.168.1.0 MASK 255.255.255.0 192.168.1.65 METRIC 10"
c.
Delete the
dead end route (consequences are unknown). Try command:
"route DELETE 192.168.1.0 MASK 255.255.255.0 192.168.1.1"
Doesn't seem like you should be having these problems or have to manually adjust route table. I'm guessing network isn't setup correctly. Will try to get back on after I review a tutorial I've bookmarked. That tutorial suggests best choice when using crossover cable would be to setup a
Network Bridge Connection. Internet Connection Sharing (ICS) should not be used (configured) if you go with the Bridge.
I think you could setup ICS, but documentation points out it requires more TCP/IP configuration and maintainence than the Network Bridge.
