Archived from groups: microsoft.public.windows.tabletpc,microsoft.public.windows.networking.wireless (
More info?)
Thanks. Already did that upgrade.
After reading around a bit, I suspect that it may be my 2.4GHz cordless
telephone that may be causing the drops. The base station for the phone is
in the same room as the WAP. Will change the channel on the WAP to see if
that helps.
"WNewquay" <WNewquay@discussions.microsoft.com> wrote in message
news:B7DA286E-C18B-4BA9-BF4E-73B4AEC2E55A@microsoft.com...
> Hi David,
>
> Since the connections are dropped with two different clients, I would
> suggest that you check on the Linksys site for firmware updates for the
WRTG
> 54
> General Downloads page:
http://linksys.com/download/
>
> I found a recent firmware update 8/4/2004
>
http://linksys.com/download/firmware.asp?fwid=201
>
>
>
> "David Lipetz" wrote:
>
> > I am cross posting this to both the Tablet PC and Wireless newsgroups -
not
> > sure which is most appropriate.
> >
> > My Gateway M1300 connects via wireless to a Linksys WRT54G wireless
router.
> > I've found that the connection will drop, all of the sudden, and the
router
> > can not be found. Then after a few minutes, or seconds, it will
re-establish
> > a connection. Sometimes it won't and I have to reboot the router.
> >
> > Now, this has occurred with and without SP2 installed. Prior to
implementing
> > the WRT54G, I had a 1st gen Linksys wireless router (BEF11W???) which
also
> > displayed the same behavior. In fact, that's why I replaced it with the
> > WRT54G - thought it was a defective router.
> >
> > Interestingly, my Dell laptop (Win2K, using a Microsoft wireless 802.11
B/G
> > PC card) also has the same behavior, whether it was with the old or new
> > Linksys router. But I rarely use the Dell at home, so my focus is on the
> > M1300.
> >
> > I think that a recent Windows update, or some common software to both
the
> > Dell and the Gateway, or maybe even a router configuration issue, may be
the
> > root of the problem.
> >
> > I seem to recall reading somewhere that a Windows hotfix caused a
similar
> > issue.
> >
> > Ideas?
> >
> > Thanks,
> > David
> >
> >
> >