Link to home
Start Free TrialLog in
Avatar of hypercube
hypercubeFlag for United States of America

asked on

Can't access web site via wireless interface on just one XP computer

Using GoToMyPC on a new Lenovo T61 laptop as a client / monitor computer - WinXP.
Have both ethernet and wireless interfaces available on the LAN.
- wired connection can access the GoToMyPC website URL.
- the wireless connection cannot.
Other wireless connected clients on the same LAN can access the website OK.

So, it appears that there's something strange about the one wireless connection specifically - but what?  All the firewalls, etc. are the same.  Maybe Lenovo adds some wireless security feature???

Any suggestions appreciated.
Avatar of captain
captain
Flag of United Kingdom of Great Britain and Northern Ireland image

Hi fmarshall
have you had a look whether the wireless zero config service has stopped on this laptop.

You don't say whether it can connect to other sites...?

If so, have you checkcked that security zone settings , windows firewall settings are identical and clear out all history and cache files.

Still not working, compare IP on this and a working one (cmc = >IPCONFIG /all) and let us know

All the best
Avatar of hypercube

ASKER

This one works in all other respects.  Gets to other web pages, etc.
Ethernet works... including for the site that the wireless can't reach.
Sorry, just to clarify. You can access alls sites even with wireles bar the Gotomypc www.?

Can you access other https sites?
Also, can you ping the website from your wireless connection?
Yes, we can ping the website via the wireless connection.
How about other HTTPS sites? Just trying to isolate any common anomaly...
Yes, it appears that other https sites are reachable via the wireless.
ASKER CERTIFIED SOLUTION
Avatar of captain
captain
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I eventually went back on site and did this:

Used IE with the IP address as you suggested.  That worked.

Now, the strange thing is that *then* the URL worked fine thereafter!!

So, at least it did appear to be a DNS problem of some sort.  So, I investigated the DNS chain a bit.  

Any suggested explanations?
baffling, as other PCs on your Network did not have the issue your DNS server cannot be the issue,
maybe a cached entry somewhere, emptying out browseer history and temp IE files will sometimes clear that, or a refresh of the cache which the IP lookup did.

Glad it is solved, guess the nslookup works now as it should and the URL does too.

atb
Yep.  In the process I'd rebooted the Access Point (which might have an affect).  I also changed the DNS setting on an interim router from DHCP to static DNS addresses to avoid a DNS handoff hop.  The servers aren't likely going to change this decade.  So that's a trade between future simplicity of configuring and robustness.