Wireless Connectivity

When I take a laptop from work and go to a coffee shop and try to connect to the internet, I get on the wireless access point, see that i have an IP from the DHCP server for the place, can ping a public ip address but for some reason just can't connect to the internet.  It's clearly DNS related. Below is a copy of the message I see in the event log.  help?
I tested the coffee shop with two laptops that are not part of our domain and they connect just fine.

The system failed to register host (A) resource records (RRs) for network adapter
with settings:

   Adapter Name : {93E705BD-D57A-429C-A635-CE6A9BF6E7CE}
   Host Name : DalesWorld
   Primary Domain Suffix : thesummit.local
   DNS server list :
   Sent update to server : <?>
   IP Address(es) :

 The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.

 To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
Who is Participating?
kman48185Author Commented:
It turns out that someone has put a STATIC DNS in the TCP IP config.  Yes that is right they had it set to DHCP for the ip but then for some reason put a static DNS entry into the config.  I didn't notice this until I saw the DNS ip address above and realized that this was our server ip address.

But thanks for the FLUSH DNS tip.

Try flushing your DNS -- open a DOS prompt (start --> command) and type ipconfig /flushdns.  Then type ipconfig /renew.  This should help with your DNS issues at hotspots.
'STATIC DNS in the TCP IP config' - that's a common error...
Why people do not use DHCP automatic IP assigning is beyond me ...
Probably system admin showing off that they know how to write IP number....
Baahhh ....
kman48185Author Commented:
Three  comments from other newsgroups:
I am only posting these as this question will become part of my database.

1, Certainly.
Corporate office. One DNS server allows Internet access to the privileged. One DNS server allows regular employees to have internal resolution only and maybe a few selected Internet sites like vendors websites.

2. Theres another reason  having your own server but being on a network that you dont control.  I have one particular client this way  they dont control the infrastructure (it is a university) and if they use DHCP, theyll get an IP address and a public DNS server (not their Windows server).  So they HAVE to have DNS set statically to their own server or else they wont properly get their resources.

3. Many people enable static DNS even if computers are using DHCP due to problems obtaining the DNS server address from the DHCP particularly with remote access connections. I have had some people who have used VPNs where the DNS entries dont get set properly when connecting to the VPN. When they establish the VPN connection they arent able to connect to network resources by IP address. Forcing the DNS setting gets around this problem sometimes.

This is usually indicative of a configuration problem on a device or a setup by someone that doesnt know how to do it properly. If the firewall is not configured to provide the DNS servers properly this problem can happen. Some people like forcing the DNS setting but if everything is setup correctly, this is rarely necessary.

Keep in mind that a lot of people dont know how to setup DHCP properly even on Windows servers. I have seen some pretty messy setups where I dont know what the person was thinking when they configured it.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.