> >> What protocol is your server using? (Not that I think this has anything
> >> whatsoever to do with this problem, but I'd like to have a clearer
> >> picture of what we're dealing with.)
> >>
> >
> > NetBios and TCP/IP
> >
> >
> 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.
>
>
> >> What about going the opposite
> >> direction, i.e., downloading to your local drive from the server?
> >
> > Same thing.
>
> At least it's consistent.
>
> >> How
> >> far are you from the AP?
> >
> > 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. 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. WifiState doesn't detect the card again
until I reboot.
>
>
> >> How is the server connected to the network
> >> (wired or wireless)?
> >
> > Both are wired to the house backbone.
>
> That keeps things simple for this excersize, at least.
>
> > Lewis, didn't someone else have the same problem a while back? I know
> > it used to work because my Web Browser's default download path was to
> > a server share. Strange problem.
> >
> Strange, indeed. I think, though, that the last problem was with channel
> overlap, and it was experienced when trying to connect to anything, not
> just during file transfers. A searh through the archives here should
> confirm that (or confirm that my memory is failing - they say that's the
> first thing to go!). =-O
>
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.
>
> --
> 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 1 days 21:42 hours and 11 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).