Apple’s Worldwide Developers Conference to kick off June 10 at 10 a.m. PDT with Keynote address
The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.
The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.
Looks like no one’s replied in a while. To start the conversation again, simply
ask a new question.
This is a really strange problem ... to set the scene, I've got a late 2008 MacBook.
After installing Snow Leopard I cannot use my ethernet port to access the internet, but I can use it to access my home network (files stored on a server via SMB).
Also, the AirPort works perfectly fine!
I think have a solution, at least it worked in my case. I had the exact same problem: Ethernet wasn't working but airnet was. I was using DHCP to get a dynamically generated IP address from my router (Verizon wireless broadband router for FIOS). In my case, the address was 192.168.1.2. I went into the configuration page for my router (
http://192.168.1.1) and I changed the IP address for my iMac to be statically assigned to 192.168.1.2. I had to enter my computer's Ethernet card physical address (MAC address) in the setup window. Now, the Ethernet is working again, I can access any Internet address.
Actually, I now have a final solution that has held up for a few days. The problem appears to have been my campus' DNS server (or Snow Leopard's ability to properly communicate with it).
To clarify the problem: If I use Ethernet with my campus' DHCP server (setting up a fixed IP address is not an option for me) and allow the campus' DNS server addresses to be inserted for my DNS server, after a few minutes, I will start having issues with communicated off of my subnet. I was able to figure this out because I was able to go to some off-campus sites, but not all, which is typical messed-up DNS setting behavior.
I hard-coded the DNS server settings to an OpenDNS server (see www.opendns.com for details) in the Network Preference Pane. This is done by
1) Selecting the Network Preference Pane in the System Preferences
2) Select the "Ethernet" interface.
3) On the "DNS Server:" line, I added "208.67.222.222, 208.67.220.220" instead of the default campus DNS servers.
Having done that, I have had a perfectly functioning connection for a few days now.
I suspect there is an incompatibility between Snow Leopard and my campus' DNS server software since Leopard handled this just fine. I don't know if the bug is in Snow Leopard or the DNS server software, but this has remedied the problem for me for now. I am trying to get the details to Apple's engineering people so they can look into it.
I had the same problem and "solved" it the same way.
Automatic DHCP/DNS configuration refuses to work properly, I had to constantly send SIGHUP to mDNSResponder so Safari could load a page (but ping would always work). Setting the DNS addresses by hand "solves" this problem (although it shouldn't be needed).
