Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linksys PCI 802.11G Speedbooster cannon get IP from router! 2

Status
Not open for further replies.
Mar 25, 2004
146
US
I had a network set up with 2 computers. I have a gateway laptop with a 802.11G card in it and it works great. I also have a Compaq with a G PCI card installed and when I get the drivers off the cd it will show a signal but won't all me to get to the internet. I can't ping the router or the internet.

The weird thing is when I bought the pci card I came home installed it and it worked great no problem. My harddrive failed so I had to do a clean install. Know I have these problems.

When I do an Ipconif all it has a wired Ip address and it's not placed the gateway as the router IP. It's like DHCP isn't working.

I trield manually entering the tcp/ip stuff via linksys help guide but that still doesn't help.

Both systems are WinXP

I've tried SP1 and SP2 no luck with either. In SP2 it say you are connected with limited functionality please contact your network admin?????

Any help would be appreciated!
 
bcastner I ran the winsock utility and it didn't work. I'm pasting what ipconfig tells me below. It's weird it says I have a good signal but still no internet. I have it set to autoobtain. The router has wep set up and uses dhcp.

Windows IP Configuration

Host Name . . . . . . . . . . . . : desktop1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter with
SpeedBooster
Physical Address. . . . . . . . . : 00-0F-66-6C-63-94
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 255.255.255.255
 
Notice in the listing:
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0

You are not reaching the DHCP server in the router.
This is exactly what the limited functionality notification in Service Pack 2 means. Start, Run, gpedit.msc

Expand:
User Configuration
Administrative Templates
Network
Network Connections

And click once on the last entry in the Group Policies that are listed. Read the description of the message.

To resolve:

. See if there is a newer driver set for the adapter. Install, reboot, test.

. Temporarily turn of WEP or WPA on both router and network adapter settings;

bcastner said:
From the FAQ link above: Service Pack 2 adds a new command to repair the Winsock corruption problem that can be caused by adware, spyware, or some other causes.

netsh winsock reset catalog

Reboot. Test.

. Since you ran WinsockFix, you know the issue appears not to be Winsock stack corruption. So, repair your TCP/IP service stack.
bcastner said:
From the FAQ link above: A recent Microsoft KB article that provides some diagnostic steps, and suggests a reasonable method of doing-it-yourself: The second half of this KB article describes how to reset the TCP/IP service stack, which is sometimes necessary.

Reboot. Test. Report back.

Best,
Bill Castner
 
Update still no luck


I've tried everyting but this:
From the FAQ link above: A recent Microsoft KB article that provides some diagnostic steps, and suggests a reasonable method of doing-it-yourself: The second half of this KB article describes how to reset the TCP/IP service stack, which is sometimes necessary.

and turning off WEP

Just thought I would post what ipconfig all is saying now as it's a little different.


Windows IP Configuration

Host Name . . . . . . . . . . . . : desktop1
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter with
SpeedBooster
Physical Address. . . . . . . . . : 00-0F-66-6C-63-94
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.7.178
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
 
hi,

check your network connections > see if the WIRELESS ADAPTER is associated with the BRIDGE ,if it is associated >right click and remove from BRIDGE.

OR DELETE THE BRIDGE simply on the list.

WEP IS OFF or ON ?
 
The APIA IP ( Autoconfiguration IP Address. . . : 169.254.7.178) still shows a failure to reach the DHCP server on the router.

. Turn off WEP
. Enable SSID broadcast on the router if turned off
. Rebuild the TCP/IP service stack
. Run WinsockFIx again

Reboot and test.

 
Here's something new. Ok I went to the router and disabled the WEP. Now I can connect both and receive the internet on both systems without a problem!

But there's no way I can have a wireless network up with no key......any thoughts??
 
Now lets do the WEP keys again.

Start with the router. You can use the passphrase generator to create the keys. Write down all four keys.

Now at the client, type in the keys by hand. Do not attempt to generate them from the passphrase. If you are using XP SP2, use 128-bit encryption keys.

 
Well enabled wep....went to labtop entered on key and it connected fine. The went to desktop (the problem child) and entered key after a long time it connected still with limited connectivity and the same details as above. Entered a seperate key by the way.

I don't understand......

I might try undoing wep again and just try connected the desktop. I'll let you know if anything comes from that...
 
Well i did like i said I was going to in the post above and still no luck. Really the only difference between the two is one is a pci and one's a notebook adapter. Of course the adapter in my laptop is a gateway adapter and the one on my desktop is a linksys. It's almost like wep isn't working on my pci adatper......is there something I can do to check.

Thx for the help!
 
The two adapters likely have a different notion of WEP key length and character requirements. You have to find the common denominator between the WEP length of both cards. Do not use a passphrase generator: type the WEP keys in by hand.

WEP Math:

40 is the same as 64
104 is the same as 128

(In both cases there are 24 bits of padding, so add 24 to 40 or 104)

1 ASCII Character=8 Bits
1 HEX Character=4 Bits

40 or 64 bit ASCII WEP code has 5 characters
40 or 64 bit HEX WEP code has 10 characters

104 or 128 bit ASCII WEP code has 13 characters
104 or 128 bit HEX WEP code has 26 characters

 
ok weird but I've finally got it. After your last post i noticed there was one auto generated key that was shorter than the rest. I used it and it connected fine???? Weird but as long as it works!

Thank BCastner!

Your deserve some stars!!
 
I had a similar experience with Linksys equipment. See my post here: thread916-928990 (copy it to the search box) about how I got it going.

Basically, remove the network card and uninstall the software, reboot, install the software (without the card), shut down, install the card, boot up, and go through the install process.

chris
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top