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 (188.8.131.52).
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 (184.108.40.206 and 220.127.116.11) 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?