| ????????? #4107 ?????? ?????? ???????? os2-wireless_users@2rosenthals.com |
????????? ? ?????? |
|
|---|
Lewis G Rosenthal wrote:Okay, got it. Native NetBIOS and TCP/IP. And it appears that the NetBIOS transport is either hogging the CPU (causing the driver to fail) or...
So you're connecting to the server via NetBIOS over TCP (TCPBIOS)?
No. Two separate protocols. Netbios for file and print sharing and TCP/IP
for internet access.
I realize. What's happening is solely on the client side.I have two AP's one at each end of the house and I have full signalHmmm... Something must be saturating the bandwidth, though. While I
strength. About 30' going through one wall. Works fine in Windoze.
suppose that excessive ethernet collisions could cause a slowdown
(packet storming), the 802.11 spec provides for collision avoidance (as
opposed to wired ethernet, which utilizes only collision detection),
however, these should not cause the actual signal strength to drop.
Perhaps Jens may be able to shed some more light on this.
The signal strength from the AP's isn't dropping, my wireless bridge still
works fine.
The signal strength indicator on WifiState drops to yellow andThat's interesting to note. With WiFiState closed, if you start a transfer, does it behave normally?
the system locks up and/or becomes sluggish until I get WifiState closed and
then the system is responsive again.
WifiState doesn't detect the card againOnce the driver crashes, this is "normal." Anything gettiung recorded in LANTRAN.LOG? What debug level do you have set in the driver? Try setting it up to FFFF (verbose), and see what you get.
until I reboot.
I tried copying data to and from my server again today and it worked fine.Was WiFiState running when you began the transfer?
Then all of a sudden It started these symptom again this afternoon. No idea
what caused it.
|
???????????: ?????????,
????????,
?????????. ?????????? ???????? ?????????????? ?????? ???????? |