Y'all,
I had similar problems. Repeated loss of access, even though the wireless
NIC still had a valid IP, and everything else looked normal.
The network would go away every 2-3 hours. Repeatedly.
This morning I cranked down the WEP from 128 bit to 64 bit, and the network
hasn't gone down all day. (10 hours so far).
??
The PC in question has a AMD Sempron 3000, plenty of horsepower. Like
BillyBob, my 7 year old desktop (300Mhz) with a different wireless NIC,
never had a hiccup. This PC is the replacement, and I couldn't get it to
stay on the network.
Equipment:
TRENDnet TEW-423PI wireless NIC 54gbps 802.11g PCI card
Buffalo Airstation WLAR-L11-L (this is 802.11b only)
WinXP SP2
brand new install
For now I am sticking with 64bit WEP. I will consider including MAC
restrictions, though I know that isn't foolproof either.
Thanks for the tip.
-D
"BillyBob" <(E-Mail Removed)> wrote in message
news:9E871B1A-45D6-472A-86B4-(E-Mail Removed)...
>
> I can't try reducing the encryption, because my son-in-law has gone back
> home with his laptop. But that is an interesting idea that coming down to
> 64
> bit will solve the problem. But I agree that is not acceptable, though I
> would try it if he was still here with his computer. Can you briefly try
> it
> Jeff, or Dirge? The strange thing about this cure to me is that it is
> referring to the Westell modem from BellSouth? That is the same one I
> have
> (Westell anyway, not sure about model number -- whichever one they are
> sending out now to customers), recently installed brand new. I did not
> even
> know that this device had any kind of encryption. If the computer was
> still
> here, I would also try BellSouth customer service, as I have had very
> excellent results in the past with them solving connection problems.
>
> But even if I was in a position to try this and it was a solution to the
> problem, it still remains a very strange problem. Because the connection
> worked fine with the old beat up laptop that our daughter brought with
> her,
> and works fine with my laptop that I am writing this response on now.
> Everything works fine with my desktop. It's only my son-in-law's newer
> IBM
> laptop that will briefly bring up a web page or two, and then start
> bogging
> down. But I would give it a try if he was still here. No need to call
> him
> and telling him to try it, because his laptop works just fine at his home
> and
> on everybody else's networks.
>
> Jeff, though we apparently have the same problem exactly, I have no
> solutions whatsoever. If you try something and it works, such as lowering
> the encryption values, please let me know. Though at the moment, it
> sounds
> like you and the rest of us are waiting for some very knowledgeable
> computer
> person to tell us what the trick is. To tell us what kind of setting or
> problem exists on the one computer that will connect strongly and load web
> pages for a minute or two and then become unusable. But only on one
> network,
> while continuing to work just fine on all the other networks. And while
> multiple other computers work just fine on the network that his won't
> bring
> up web pages on.
>
>
> "Jeff" wrote:
>
>> Yes but going from 128 bit WEP key to a 64 bit one is really reducing the
>> security and that is not good.
>>
>> I use WPA, not WEP, because it is more secure. But everything worked fine
>> until a couple of weeks ago. Windows should be able to handle that. What
>> you
>> say makes me wonder if it is some other software update that is taking up
>> more of the available ram and therefore messing things up. I do not
>> remember adding new software into memory but will check for that. Maybe
>> my
>> virus checker database has gotten bigger or the new firefox 1.5 is taking
>> up
>> more ram than the earlier 1.0.x. Don't know.
>>
>> I wish one of the experts would help us poor newbies.
>>
>> Jeff
>
|