X-UIDL: 3436 X-Mozilla-Keys: Return-Path: os2-wireless_users-owner@2rosenthals.com Received: from mail.2rosenthals.com (localhost [127.0.0.1] ) by mail.2rosenthals.com (Hethmon Brothers Smtpd) ; Tue, 9 Dec 2003 02:14:17 -0500 Received: from mail1.no-ip.com (mail1.no-ip.com [63.215.241.221] ) by mail.2rosenthals.com (Hethmon Brothers Smtpd) ; Tue, 9 Dec 2003 02:14:14 -0500 X-Envelope-To: Received: (qmail 30499 invoked by uid 89); 9 Dec 2003 07:13:39 -0000 Received: from unknown (HELO MAIL03.toast.net) (206.244.185.10) by mail1.no-ip.com with SMTP; 9 Dec 2003 07:13:39 -0000 Received: from 2rosenthals.com (unverified [206.149.156.54]) by MAIL03.toast.net (Vircom SMTPRS 3.0.273) with ESMTP id for ; Tue, 9 Dec 2003 02:11:56 -0500 Message-ID: <3FD5763E.40300@2rosenthals.com> Organization: Rosenthal & Rosenthal User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.6a) Gecko/20031103 MultiZilla/1.5.0.4e X-Accept-Language: en-us, en MIME-Version: 1.0 References: <3FD20939.E246271B@rollanet.org> <3FD38464.7070703@2rosenthals.com> <3FD38BAC.AC0DE349@rollanet.org> <3FD3C72B.8030603@2rosenthals.com> <3FD3D51C.D39A1C79@rollanet.org> <3FD3F860.5040305@2rosenthals.com> <3FD40248.FF4FA3C@rollanet.org> In-Reply-To: <3FD40248.FF4FA3C@rollanet.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 09 Dec 2003 02:14:06 -0500 Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: Lewis G Rosenthal To: os2-wireless_users@2rosenthals.com Subject: [OS2Wireless] Can't copy to/from server X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com Briefly, Sam: * LANTRAN.LOG logs more than just startup messages; * I believe Jens has hit on this, with his reference to the Prism 2.5 chipset. The problem appears to be with handling both protocols at the same time, so... * Why don't you switch to TCPBIOS instead of NetBIOS? This is a much more efficient transport, anyway, and shouldn;t cause you the difficulty, as there is really only one protocol (TCP) over the air; * WiFiState is just a utility to see how your connection is doing and/or select a different profile on the fly. It is not required for any transport to take place. On 12/07/2003 11:47 pm, Sam Lewis thus wrote : >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). > >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > > -- 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 0 days 01:11 hours and 52 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). =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=