Can connect via the command line, but not any way else

jfruh · 10-20-2009, 04:40 PM

Hello all-

I have two Windows XP -- one Home, one Professional -- machines attempting to connect wirelessly to a vanilla Netgear access point. The XP Pro machine connects fine. The XP Home machine sees the Wi-Fi network, connects, accepts the password, and says it's connected -- but Web browsers and other Windows network apps will not connect to the Internet (they just hang for a long time before timing out).

But! If I open a command prompt, I can ping external sites and even use command-line ftp to connect to sites without a problem!

I've gone over the network configuration of both machines and can't see any difference between the two. Both are using the same network submask and DNS server addresses. The Netgear access point doesn't have any kind of MAC address filtering turned on. Is there something I should be looking for that I'm missing?

As an extra added strange data point -- I've tried to connect to the network via a Mac OS X machine and saw the same behavior as on the XP Home machine -- GUI-based programs won't connect, but command-line utilities will. Meanwhile, an Apple iPhone was able to connect and work perfectly.

Thanks in advance for any advice!

Josh

steveb1234 · 10-20-2009, 04:44 PM

Try a browser reset

jfruh · 10-20-2009, 04:47 PM

Quote:

Originally Posted by steveb1234

Try a browser reset

I have tried rebooting the whole computer, repeatedly. This is a long-term problem. (I'm actually at my parents' house trying to troubleshoot for them, and it's been like this for some time.)

**johnwill** · 10-21-2009, 09:31 AM

Some things you can try here.

Update the network drivers (wired and wireless) on your computer to the latest available.
Update the firmware to the latest version available on the manufacturer's site.
Reset the router to factory defaults and reconfigure.

10-20-2009, 04:40 PM	#1 (permalink)
jfruh Registered User Join Date: Oct 2009 Posts: 2 OS: Windows XP	Can connect via the command line, but not any way else Hello all- I have two Windows XP -- one Home, one Professional -- machines attempting to connect wirelessly to a vanilla Netgear access point. The XP Pro machine connects fine. The XP Home machine sees the Wi-Fi network, connects, accepts the password, and says it's connected -- but Web browsers and other Windows network apps will not connect to the Internet (they just hang for a long time before timing out). But! If I open a command prompt, I can ping external sites and even use command-line ftp to connect to sites without a problem! I've gone over the network configuration of both machines and can't see any difference between the two. Both are using the same network submask and DNS server addresses. The Netgear access point doesn't have any kind of MAC address filtering turned on. Is there something I should be looking for that I'm missing? As an extra added strange data point -- I've tried to connect to the network via a Mac OS X machine and saw the same behavior as on the XP Home machine -- GUI-based programs won't connect, but command-line utilities will. Meanwhile, an Apple iPhone was able to connect and work perfectly. Thanks in advance for any advice! Josh

10-20-2009, 04:44 PM	#2 (permalink)
steveb1234 Registered User Join Date: May 2009 Posts: 373 OS: xp, windows 7	Re: Can connect via the command line, but not any way else Try a browser reset

10-21-2009, 09:31 AM	#4 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 41,685 OS: Windows 7, XP-Pro, Vista, Linux Blog Entries: 1	Re: Can connect via the command line, but not any way else Some things you can try here. Update the network drivers (wired and wireless) on your computer to the latest available. Update the firmware to the latest version available on the manufacturer's site. Reset the router to factory defaults and reconfigure. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience