Lewis G Rosenthal wrote:

 

On 12/07/2003 08:34 pm, Sam Lewis thus wrote :

   

Lewis G Rosenthal wrote:



     

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.



     

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...

   

I have two AP's one at each end of the house and I have full signal
strength.  About 30' going through one wall.  Works fine in Windoze.


         

Hmmm... Something must be saturating the bandwidth, though. While I
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.

     

I realize. What's happening is solely on the client side.

   

The signal strength indicator on WifiState drops to yellow and
the system locks up and/or becomes sluggish until I get WifiState closed and
then the system is responsive again.

     

That's interesting to note. With WiFiState closed, if you start a
transfer, does it behave normally?
   

No.  I can no longer access my shares at this point.

 

   

WifiState doesn't detect the card again
until I reboot.



     

Once the driver crashes, this is "normal." Anything gettiung recorded in
LANTRAN.LOG?
   

I thought that the lantran.log only logged stuff on bootup?

 

What debug level do you have set in the driver? Try setting
it up to FFFF (verbose), and see what you get.
   

What is this debug level and how would I go about setting it?

 

   

I tried copying data to and from my server again today and it worked fine.
Then all of a sudden It started these symptom again this afternoon.  No idea
what caused it.


     

Was WiFiState running when you began the transfer?
   

Yes.  Isn't WifiState required?

Thanks,
Sam

 

--
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA
  Rosenthal & Rosenthal
Accountants / Network Consultants
 New York / Northern Virginia           www.2rosenthals.com
Team OS/2  / NetWare Users International      www.novell.com
------------------------------------------------------------
This OS/2 system (Apollo) uptime is 2 days 01:23 hours and 18 seconds

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
   

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=