![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Networking Support General Networking Support Forum |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Feb 2008
Posts: 2
OS: XP2
|
Can't connect to Wireless Network
I recently had to reinstall XP on my desktop and have not been able to reconnect wirelessly. Message is "Windows is unable to connect to selected network...." I have spent hours on the phone with ATT wireless support, but have had no success. The computer has an functioning ethernet connection, and locates my local wireless connection point, but will not connect. Other computers are able to make the connection, and the settings appear to be similar. My guess is something is blocking the connection, but I don't know what.
The details: Running XP with a Westell 327W router and a Linksys WUSB300N wireless device. On the router, the network is named, wireless operation is enabled, the security is WEP-64 bit, and Key 1 is filled with a 10 digit number. This is the connection point that the computer finds, but will not connect to - even though other computers find the same site, and will connect. Firewall and password status on the modem is all marked "none". When I run "full diagnostics", all tests pass except "IP" and the message says "Cannot access ping. fastaccess.com...." ATT techs indicate this is not a problem, so not to worry about it. I can find no other error messages. We run Windows firewall and AVG anti-virus (as we do on the other computers which do connect), but turning both off seems to make no difference. I have turned off modems, computers, rebooted numerous times, but no joy! Any suggestions? Thanks in advance. |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#2 (permalink) |
|
Registered User
Join Date: Aug 2004
Location: Northfield, MN
Posts: 115
OS: XP, Linux
|
Re: Can't connect to Wireless Network
several things to check would be... on your router, is there a limited number of dhcp addresses available - and are the leases set to "forever", if so - increase the number of addresses in the address pool. second, check to make sure that your mac address is allowed on your router.
__________________
Mike.D |
|
|
|
|
|
#3 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,679
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Can't connect to Wireless Network
Try these simple tests.
Hold the Windows key and press R, then type CMD (COMMAND for W98/WME) to open a command prompt: In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key: NOTE: For the items below in red surrounded with < >, see comments below for the actual information content, they are value substitutions from the previous command output! IPCONFIG /ALL PING <computer_IP_address> PING <default_gateway_address> PING <dns_servers> PING 206.190.60.37 PING yahoo.com Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard. Paste the results in a message here. <computer_IP_address> - The IP Address of your computer, obtained from the IPCONFIG command above. <default_gateway_address> - The IP address of the Default Gateway, obtained from the IPCONFIG command above. <dns_servers> - The IP address of the first (or only) address for DNS Servers, obtained from the IPCONFIG command above. If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#4 (permalink) |
|
Registered User
Join Date: Feb 2008
Posts: 2
OS: XP2
|
Re: Can't connect to Wireless Network
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Paul>cd\ C:\>ping 74.244.26.25 Pinging 74.244.26.25 with 32 bytes of data: Reply from 74.244.26.25: bytes=32 time<1ms TTL=64 Reply from 74.244.26.25: bytes=32 time<1ms TTL=64 Reply from 74.244.26.25: bytes=32 time<1ms TTL=64 Reply from 74.244.26.25: bytes=32 time<1ms TTL=64 Ping statistics for 74.244.26.25: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 192.168.1.254 Pinging 192.168.1.254 with 32 bytes of data: Reply from 192.168.1.254: bytes=32 time=1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms C:\>ping 192.168.1.254 Pinging 192.168.1.254 with 32 bytes of data: Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Reply from 192.168.1.254: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.254: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 206.190.60.37 Pinging 206.190.60.37 with 32 bytes of data: Reply from 206.190.60.37: bytes=32 time=178ms TTL=53 Reply from 206.190.60.37: bytes=32 time=141ms TTL=53 Reply from 206.190.60.37: bytes=32 time=1151ms TTL=53 Reply from 206.190.60.37: bytes=32 time=396ms TTL=53 Ping statistics for 206.190.60.37: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 141ms, Maximum = 1151ms, Average = 466ms C:\>ping yahoo.com Pinging yahoo.com [206.190.60.37] with 32 bytes of data: Reply from 206.190.60.37: bytes=32 time=659ms TTL=53 Reply from 206.190.60.37: bytes=32 time=1138ms TTL=53 Reply from 206.190.60.37: bytes=32 time=929ms TTL=53 Reply from 206.190.60.37: bytes=32 time=35ms TTL=53 Ping statistics for 206.190.60.37: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 1138ms, Average = 690ms C:\> |
|
|
|
![]() |
| Thread Tools | |
|
|