Inspiron 6000 and secure wireless network

Do you have the latest firmeware for your router?  I remember the BEFW11S4 versions 1 and 2 gave us a lot of headaches in wireless support until a particular firmware release came out for it (its been a few years, so I don't remember which update fixed the problem).  You should be able to get the latest firmware update from the Linksys site.  If you are not sure how to do the update I highly recommend you have their support walk you through the process.

Is your installation of Windows XP up to date with all Service Packs?

 

Steve

I do have the latest version of the firmware (1.45.10). You're right that it was released a while ago - I upgraded it the other night hoping that might fix the problem, reset the router to the original factory settings, then set up the wireless network again. The Inspiron could connect until I re-enabled the wireless security. After double-checking the wep key, it still doesn't connect.

 

I also checked for any critical updates from Microsoft as you recommended. I'm already running Windows XP SP 3 but made sure I had the other updates listed. After rebooting, the laptop still can't connect to the secure network.

You probably already knew this, but just to be sure ... ;)

 

You used the WEP key from the router, and not the passphrase that creates the WEP key for you, correct? (a post on another thread from volcano11 reminded me about that posibility. :D)

Yes, thanks. I know that's probably a common mistake, but I'm entering the key itself, not the passphrase. I wish it were that simple....

---

@Davet50 wrote:

Um Curious

Why did you download the 2915abg driver when you have a 2200 card?

There is a seperate driver for the 2200.

---

Actually, both cards use R155386.exe if you are using the latest Dell release of the driver. ;)

Um Curious

Why did you download the 2915abg driver when you have a 2200 card?

There is a seperate driver for the 2200.

"If you disable encryption on the router, will the card connect?"

 

Yes, this is why this has me going in circles. I've taken the router back down to the basics several times to troubleshoot. Each time, I start with the network unencrypted and can connect the laptop just fine (the ssid is straightforward and I create the profile from the ssid that is being broadcast, not by typing it in myself).

 

Problems start occurring when I enable the security. Since the laptop was connected to someone else's network with the same security setup not even a week ago, I know this would suggest to user error on my part in connecting the laptop to our home network, but I have checked all the usual human errors - ssid name, wep key, etc. This all started when the machine was reformatted - until then it was connecting just fine. So I'm missing something that is preventing this laptop from connecting to my secure network despite the fact that it can connect to others. The network/router doesn't seem to be the problem, since the other laptop in the house is connected just fine. 

 

Regarding the firewall, I thought of that as well and disabled it in case that was causing problems. I also started the laptop up in safe mode in case there was other software starting up that was interfering. The same problems occur. I really appreciate all of the suggestions that have been provided, but I think I may just have to invest in a new router. If I figure out a solution, I'll post it. 

---

@rtoth wrote:
Yes, thanks. I know that's probably a common mistake, but I'm entering the key itself, not the passphrase. I wish it were that simple....

---

Yeah, I saw it quite often when dealing with wireless configuration calls.

 

Rereading your OP it seems quite obvious all of the hardware is working correctly, and that a firewall is almost sure to not be part of the problem (unless you forgot to include this particular router as a trusted address).  That leaves a configuration setting on either the router or the card being the problem.

 

Another simple and obvious thing: have you made sure you have the correct SSID entered on the card (SSID is case sensitive, and spaces are part of it)?  Typoes and spaces are the most common problem there.

 

Does the card see that particular router in the list of available networks?  If it does, creating a new profile from that (after removing any existing profiles) might bypass the SSID spelling issue, and at the same time remove any oopses in the profile setup.

 

If you disable encryption on the router, will the card connect?

 

I'm not sure where exactly to look next, as it has been a few years since I've done wireless tech support regularly.  However, based on the troubleshooting you have done, and the descriptions you give, I'm convinced that the problem is only (only, as if that makes it any better ;)) a configuration problem either on the card or, less likely, with the router.  I assume you haven't added any new settings to the router, which means it is most likely a setting on the card iteself.

 

When it used to work, did you use the Intel ProSet to configure the card, or the Windows Wireless Zero Config?  That might at least get us going in the correct direction ...

It does make it better knowing that it's only a configuration problem. :smileyhappy:

 

When it used to work, I used the Intel ProSet to configure the card. Since I started having problems, I've tried both, since some of the message boards said to disable Intel ProSet and use Windows directly. You're right in assuming that I hadn't changed anything on the router, although in upgrading the firmware I did reset everything and reconfigure it using the same settings as before.

If you have another computer using the 2200 Intel card that works, I'd try comparing the configurations.  They should match exactly.  If you don't have another 2200 card, check the profiles on other Intel wireless cards, since they should still have the same profile setup (assuming they are also using the ProSet).  From what you are describing the most likely cause is something set differently on that one computer.