Re: 100% signal, can't connect

[OldCobber]

Hi. I have a Sony Vaio, series PCG-FRV25 laptop bought in 2003. I have a Linksys router model # WRT54GS, version 7.2.00 and a wireless G notebook adapter, model #WPC54GS, version 2.1. I have Windows xp, sp2 and have recently added hot fix patch KB893357, which I read was necessary to enable the router/adapter connection. As I sit here posting ,the wireless icon in the system tray is still trying to aquire a network address....speed 54 Mbps; signal strenth excellent; status...aquiring network address. How can I fix this?

[johnwill]

Even though it appears you're having the same problem, please start a new thread when you have a new issue. It's very difficult to keep two problems straight and who's working on what in a single thread.

I've created a new thread for your issue here.

Note: You will need to post complete details of your configuration and your specific issue in this new thread for us to help you.

Thanks for your cooperation.

[johnwill]

Please supply the following information.

If wireless, encryption used, (none, WEP, WPA, or WPA2)
Version and patch level of Windows on all affected machines, i.e. XP-Home (or XP-Pro), SP1-SP2, Vista, etc.






If you're using a wireless connection, have you tried a direct connection with a cable to see if that changes the symptoms?

If there are other computers on the same network, are they experiencing the same issue, or do they function normally?




On any affected computer, I'd also like to see this:

Hold the Windows key and press R, then type CMD to open a command prompt:

Type the following commands:

PING 216.109.112.135

PING yahoo.com

NBTSTAT -n

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

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.

[OldCobber]

* The wireless encryption I am using is WPA Personal. Is this the same as WPA2? I am using Windows XP home. I don't know what you mean by patch level of Windows. I downloaded the Widows hot fix patch KB893357 based on an article I found here:
http://support.microsoft.com%3Fkbid=893357/

Based on my limited computer knowledge, I'm guessing that the problem may be the operator (me) in configuring wireless addresses and accompanying passcodes that don't seem to match up due to my attempting to get wireless up and running. When I pull up the Linksys notebook adapter with speed boost, everything checks out as working but no association with access point.
Thank you for your patience and willingness to help a green computer operator.



Please supply the following information.

If wireless, encryption used, (none, WEP, WPA, or WPA2)
Version and patch level of Windows on all affected machines, i.e. XP-Home (or XP-Pro), SP1-SP2, Vista, etc.






If you're using a wireless connection, have you tried a direct connection with a cable to see if that changes the symptoms?

If there are other computers on the same network, are they experiencing the same issue, or do they function normally?

I followed your instructions....see results below:

On any affected computer, I'd also like to see this:

Hold the Windows key and press R, then type CMD to open a command prompt:

Type the following commands:

PING 216.109.112.135

PING yahoo.com

NBTSTAT -n

IPCONFIG /ALL

WINDOWS IP CONFIGURATION


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Susan McAtee>ping 216.109.112.135

Pinging 216.109.112.135 with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=49ms TTL=53
Reply from 216.109.112.135: bytes=32 time=49ms TTL=53
Reply from 216.109.112.135: bytes=32 time=48ms TTL=53
Reply from 216.109.112.135: bytes=32 time=49ms TTL=53

Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 49ms, Average = 48ms

C:\Documents and Settings\Susan McAtee>ping yahoo.com

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=64ms TTL=50
Reply from 66.94.234.13: bytes=32 time=65ms TTL=51
Reply from 66.94.234.13: bytes=32 time=64ms TTL=50
Reply from 66.94.234.13: bytes=32 time=63ms TTL=51

Ping statistics for 66.94.234.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 65ms, Average = 64ms

C:\Documents and Settings\Susan McAtee>nbstat -n
'nbstat' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Susan McAtee>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Susan
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : earthlink.net

Ethernet adapter Wireless Network Connection 8:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Wireless-G Notebook Adapter WPC54GS
V2 #2
Physical Address. . . . . . . . . : 00-1C-10-BC-C4-4A

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : earthlink.net
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 08-00-46-A7-EE-3F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 207.69.188.186
207.69.188.187
Lease Obtained. . . . . . . . . . : Sunday, April 13, 2008 10:18:11 AM
Lease Expires . . . . . . . . . . : Monday, April 14, 2008 10:18:11 AM

C:\Documents and Settings\Susan McAtee>

[johnwill]

Obviously, this was with a wired connection, and appears to be working. I'd start by configuring the router with no encryption and see if you can connect that way. Then make SURE your encryption keys match and see if you can connect. If you use WEP (I recommend WPA), use only the HEX keys, not the passphrase option.