12
1
I have a user with a new high-end MacBook Pro that can't use the internet. He can connect to either our wired or wireless network and do things like browse file shares, but can get no further.
When I brought the machine in for testing, I found that I could do an nslookup just fine, and I'm able to ping addresses returned by nslookup just fine. I'm even able to bring up web pages by entering the IP address into the address bar directly. However, when I try to ping the domain name rather than the IP address, it just sits there. So apparently I can either do name resolution or communicate with an address, but not both at the same time.
Again, these symptoms occur on both the wired and wireless network. Other machines on our network, including a few other Macs, don't have this issue.
Any ideas?
This has persisted across several reboots, but the fact that nslookup returns an address while anything else that needs to do resolution fails still indicates mDNSResponder as a good candidate for the problem. – Joel Coehoorn – 2010-09-14T18:45:25.560
Amazing what difference another year's experience makes. I come review this today because someone voted for the question, and most of your answer is now 2nd nature to me, where before I was shooting blind. That said, I've said this before now, but mDNS/Bonjour is a great steaming pile that Apple should never have unleashed into production equipment. – Joel Coehoorn – 2011-11-10T17:35:16.753
Oh, and the student ended up resolving this before we had the machine back to try this, but reading the symptoms and suggestion now, I'm certain this was the problem, and that re-installing the Bonjour service may have been needed. – Joel Coehoorn – 2011-11-10T17:37:01.010
@Joel Thanks for the followup. It's nice to hear when an Answer has been helpful. – Spiff – 2011-11-10T20:25:02.220