Can't Connect To Internet on Ethernet

audiodan

macrumors newbie
Original poster
Oct 27, 2007
15
0
Hey all,

I think this happened when I upgraded to Leopard, but never checked. I can connect to my home network over airport, but not ethernet. All settings are correct, went through the diagnostics, but can't figure it out. Anyone know what's up?
 

atszyman

macrumors 68020
Sep 16, 2003
2,437
1
The Dallas 'burbs
What do your TCP/IP settings look like when you are on Airport and on Ethernet. I assume you are connecting with DHCP are you getting 192.168.1.xxx addresses for your IP when connecting via Ethernet?

The more information you can provide the faster we can try to diagnose the problem.
 

audiodan

macrumors newbie
Original poster
Oct 27, 2007
15
0
What do your TCP/IP settings look like when you are on Airport and on Ethernet. I assume you are connecting with DHCP are you getting 192.168.1.xxx addresses for your IP when connecting via Ethernet?

The more information you can provide the faster we can try to diagnose the problem.
It says Ethernet is not connected, but when I connect to Airport it says :

IPv4 Address: 192.168.0.103
Subnet Mask: 255.255.255.0
Router: 192.168.0.1
 

atszyman

macrumors 68020
Sep 16, 2003
2,437
1
The Dallas 'burbs
It says Ethernet is not connected, but when I connect to Airport it says :

IPv4 Address: 192.168.0.103
Subnet Mask: 255.255.255.0
Router: 192.168.0.1
OK, Is it saying Ethernet is not connected when an ethernet cable is plugged in? Or is this when running wireless? What happens when you plug an Ethernet cable in (if it's not already)?
 

atszyman

macrumors 68020
Sep 16, 2003
2,437
1
The Dallas 'burbs
Both say it is unplugged.
OK, then it's either a dead ethernet port (on the router or your Mac), OS driver issue, or a bad cable. (nothing like narrowing a problem down)

Do you have any other computers that you can use to verify that the wired connection is indeed working?

When you installed Leopard did you do an upgrade, clean, or archive & install?
 

audiodan

macrumors newbie
Original poster
Oct 27, 2007
15
0
Yeah, I figured out it was a bad cable, it just stopped working I suppose. Odd.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.