Local wireless file transfers stalling

I'm using a Linksys WPC11 wireless card through a BEFW11S4 router.
The wireless connection works fine, and gets the max my DSL can handle
to the internet. But file transfers from the wireless notebook to a
local wired desktop are slow.

What I see is a transfer at the max rate for a second or two, then
nothing for 4 seconds or so, then max rate, the nothing, etc. Both
machines show minimal CPU/disk activity during the stall period. Both
FTP and Windows file sharing exhibit the same behavior.

Both systems are WinXP, >1GHz processors. I have the latest drivers,
etc., the signal is excellent. If I use a wired connection between
the notebook and the router, things go fast as expected, so the only
difference is the wireless link.

Any ideas where to look? I've tried the usual things (changing
channels, disabling firewalls, playing with RTS and fragmentation) but
nothing has changed the basic pattern.

x-no-archive: yes
"Loose Wire" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm using a Linksys WPC11 wireless card through a BEFW11S4 router.
> The wireless connection works fine, and gets the max my DSL can handle
> to the internet. But file transfers from the wireless notebook to a
> local wired desktop are slow.
>
> What I see is a transfer at the max rate for a second or two, then
> nothing for 4 seconds or so, then max rate, the nothing, etc. Both
> machines show minimal CPU/disk activity during the stall period. Both
> FTP and Windows file sharing exhibit the same behavior.
>
> Both systems are WinXP, >1GHz processors. I have the latest drivers,
> etc., the signal is excellent. If I use a wired connection between
> the notebook and the router, things go fast as expected, so the only
> difference is the wireless link.
>
> Any ideas where to look? I've tried the usual things (changing
> channels, disabling firewalls, playing with RTS and fragmentation) but
> nothing has changed the basic pattern.

Let me as a rookie give you this to try: Did you run the XP Nework setup
(Wizard) on the notebook, with correct network name etc.? Did you try
pinging the two machines? What are the speeds? Do you use a VPN on your
wireless network to get onto your employers intranet? If so, what are your
security and disk sharing settings? Try ipconfig in a DOS window; does your
notebook show an ip address consistent with your router's assignment block?
If not, log off of VPN (if used) and try ipconfig /release and then
ipconfig /renew (to get an IP address from your router's DHCP if you have
it set as dynamic). In any case, if it is dynamic, try using a static IP
address on the notebook. That's all I can think of for now.

Dan

On Thu, 11 Sep 2003 22:15:06 -0400, "Dan Finn" <(E-Mail Removed)>
wrote:


>Let me as a rookie give you this to try: Did you run the XP Nework setup
>(Wizard) on the notebook, with correct network name etc.? Did you try
>pinging the two machines? What are the speeds? Do you use a VPN on your
>wireless network to get onto your employers intranet? If so, what are your
>security and disk sharing settings? Try ipconfig in a DOS window; does your
>notebook show an ip address consistent with your router's assignment block?
>If not, log off of VPN (if used) and try ipconfig /release and then
>ipconfig /renew (to get an IP address from your router's DHCP if you have
>it set as dynamic). In any case, if it is dynamic, try using a static IP
>address on the notebook. That's all I can think of for now.
>
>Dan
>

Thanks for the suggestions, but those aren't the problem. Network
setup is OK, and it all works great when I use a cable to the router.
The wireless setup happens when I insert the wireless card, and it
also looks OK, and works fine for slower things like internet browsing
at 1.5Mb DSL. But when I try to push it to the limit with a local
file transfer, it gives me this odd behavior. Pings are all <10ms.
No VPN. IP addresses are all reasonable, and I did try making them
static, but it didn't change anything.

It seems like the wireless link is somehow failing and recovering
(despite saying I have an excellent signal), and taking way too long
to do it. Or there's something that decides the link is congested and
way overreacts. Or ????