wireless problems with 3225

I've noticed people discussing wireless problems with other models, but my trouble is with a 3225. Could the same solutions pertain? (ie, using a different driver?) My wireless connection flickers on and off in the most annoying way, cutting off downloads in midstream, dropping emails into nowhere, etc.

 

As soon as I fired Windows as the controller of my wireless connections, my performance improved immediately and I haven't been dropped since. I used to have all kinds of problems; signal drops, no re-connect after coming out of standy, etc. I have a 6130 and let the downloaded Ralink driver control the wireless settings. It works well on the two access points I use. Neither broadcast and SSID, and one uses encryption and I haven't had a single problem since I fired Windows.

 

OK, I'd like to give that a shot - how do I go about firing windows? My driver is from Broadcom, can I use a Ralink driver instead? How do I go about switching from having windows control the wireless card?

 

Okay, I figured out how to get my Broadcom driver to control the wireless connection, but there is virtually no change. Every couple seconds, my connection is dropped, then reestablished in a fraction of a section.

 

user,

"How do I go about switching from having windows control the wireless card"

1) right click on your wireless icon in the tool bar
2)select "open network connection"
3)locate the "wireless network connection" and right click on it and choose "properties"
4)select the "wireless networks" tab and remove the check from the box "use Windows to configure my wireless..."
5) hit "ok" and reboot.

 

Thanks DamnageD, I couldn't remember those steps off the top of my head. Something else to try; my network at home was slowing down and using the Ralink utility I noticed there were two other wireless networks near me and all of us were trying to use channel 6. I switched the router to channel 3 and viola, it runs much faster. I think I lot of them operate on channel 6 as a default, so unless you change that you may be having signal conflicts with a neighbor.

 

Thanks Damnage. I tried that, and successfully "fired" windows, but it didn't really help my problem. My connection still flickers in and out constantly. How do I change the channel that my router broadcasts on?

 

3225,

Sorry, insufficient memory at this time....

But honestly, thats not something I can answer.

DD

 

To change the channel your router broadcasts on you need to "log-in" to your router. Generally you do this through a web browser. Find out what your IP address is from the network connections tab on XP. It is probably something like 192.168.1.100, or maybe 192.168.0.100. At any rate, the important part of the number is the first three sections: 192.168.1.? Type those numbers into your browser (whatever yours are) and replace the question mark with a 1.
Then you should get a password log-on window. You should check your router manual for the correct username and password or google the model of your router and you can find the default password that way. I think linksys is username: -blank- password: admin, and d-link is username: admin password: -blank-. Or maybe its the other way around. Anyway, once you get into the router, you should be able to find the wireless tab and change the broadcast channel. Also a good idea to change the password while you are in there, otherwise your next door neighbor can log into your router. Encryption is a good idea as well, or at the very least, change the SSID name of your router, and stop broadcasting the SSID. You would then have to manually type in the new name to log in, but a stranger would never be able to guess your network name (hopefully)and would therefore be kept out.

 

Singlecoil,
Thanks, I tried your suggestion, but I always get a "connection refused" message whenever I try to hit enter after having typed in my IP address. This contrasts with when I try to access a given web page which might take 3-4 enters, but eventually goes through when the connection is re-established. The IP address goes to 0 in conjunction with a little message popping up and disappearing quickly from my system tray informing me of the loss and re-establishment of my connection. Argh.

 

You should be typing in your router's IP address, not your computer's. Basically take your computer's IP address, drop the last set of digits after the third period (.) and replace them with a 1 Type that new number into your browser. You may also want to try plugging your computer directly into your router with an ethernet cable, and not relying on the wireless. What brand and model of router do you have?

 

Oh, I see. Okay, I tried that, replacing the value after the third period with a 1, but same result: connection refused. I am using a 2Wire HomePortal DSL modem. An HP computer is plugged into the ethernet port on the modem. When I connect with my laptop via ethernet, there is no problem. Incidentally, the connection flashes on and off in a quite regular way: 20 seconds on, 3 seconds off. Like clockwork.

 

Well, apparently that 2wire product is an entirely different animal. It comes pre-configured to use encryption, so unless you set up your wireless settings on your laptop with the proper encryption key, it won't work. Encryption is only for wireless, so that would explain why the wired connection works. It sounds like you need to read the manual carefully and do what it says, particularly this part:

Configuring Other Wireless Ethernet Adapters
The following steps are completed using the configuration program provided with your
wireless adapter. If you have not already done so, install the wireless adapter
configuration software before continuing.
1. Set the network type to Infrastructure. Refer to your wireless adapter
documentation for instructions on editing the adapter’s network profile. Your
wireless adapter should be configured to operate with an access point or
residential gateway. This mode of operation is typically enabled by setting network
type to Infrastructure.
2. Set the wireless network name. The wireless network name of your HomePortal is
2WIRE in all capital letters, followed by the last three digit of the HomePortal serial
number located on the bottom of your HomePortal. For example, if the last three
digits of your HomePortal serial number are 102, your HomePortal network name
would be 2WIRE102.
The wireless network name is sometimes referred to as the Network Name, SSID,
ESS ID, or Wireless LAN ID.
3. Enable wireless security. Your HomePortal is pre-configured to take advantage of
wireless security. Referring to the instructions provided with your wireless adapter,
enable wireless security.
Wireless security is sometimes referred to as WEP (wired equivalent privacy), 64-
bit encryption, or 40-bit encryption.
4. Enter the encryption key. Once you have enabled security on your wireless
adapter, you need to enter the unique security key for your HomePortal. To do this,
set the network encryption type to hexadecimal, and enter your 10-digit wireless
encryption key found on the bottom of your HomePortal.
5. In general, accept your adapter’s defaults. The default value for the remainder of
configurable settings for your network adapter should allow your wireless adapter
to communicate with the HomePortal. Although the HomePortal is set by default to
communicate using channel 6, it is not required to change your adapter to this
setting as most adapters will automatically detect the appropriate channel.

 

Well, I seem to have fixed the problem and in case anyone else has this problem, I'll mention what I did: just reinstalled the SBC Yahoo networking software. The problem arose when I added a new housemate's desktop computer to the network without running the SBC Yahoo CD. THe new housemate's computer used to be on a SBC Yahoo connection before, so I figured it was fine. Her computer was plugged in to the ethernet port on the router. It worked fine for her, but my computer's connection was that having that weird pattern of 20 seconds on, 3 seconds off. And my connection was that way on the campus wireless network too. Now that I've reinstalled, things seem to be running fine.