Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 46
  • Last Modified:

DNS Server issue with Wireless adapter

I have a Windows XP machine in the office that will connect to our wireless network just fine.  Once the machine leaves the building however, all connectivity is lost.

Connecting to a Verizon MiFi:
We pulled up a command prompt and verified that name lookups were failing by trying to ping www.yahoo.com which did not resolve.  Pinging known hosts by  ip address, however, was successful.  The two hosts that responded by IP address were the our company VPN concentrator  and one of Verizon’s DNS servers (4.2.2.2).

The next thing that we tried was performing an NSLOOKUP against www.yahoo.com at the command line.  This failed as well and indicated that it was trying to resolve the name against internal  servers (10.X.X.X) and (10.X.X.X).  The internal DNS servers should not be used in this instance since we are connected to the Verizon public network and should resolve against external servers.  I have no idea why this was happening.  Hardcoding the TCP options in the wireless adapter to use OPEN DNS servers (208.67.222.222 and 208.67.220.220) did nothing.  NSLOOKUP still indicated that it was trying to reach internal company servers.

Running the IPCONFIG command did show the correct servers but obviously they were not being used for look ups.

Anybody else seen this issue?
0
mdrcoast
Asked:
mdrcoast
  • 3
1 Solution
 
Steve MarinIT ConsultantCommented:
Is this machine on a domain? What is the output of ipconfig /all? Have you tried running ipconfig /flushdns once you are away from the Work WiFi? If all else fails you can try and run this utility as you may have a borked TCP Stack.

http://www.snapfiles.com/get/winsockxpfix.html

I've seen this utility fix wonders on XP.
0
 
mdrcoastAuthor Commented:
Thank you for the tool, and to answer your question IPconfig /all provided the correct DNS entires.

I had to reimage the machine as time was short and we have a more up to date image.  Should be getting another today to look at.

My theory is an old group policy has somehow affected my Windows XP builds causing the issues.  Will be investigating and will post results.
0
 
mdrcoastAuthor Commented:
Group policy Issue
0
 
mdrcoastAuthor Commented:
I did figure this one out by testing and a group policy was affecting VPN users only when they dialed in to the subnet containing the VPN server.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now