M
M. Hockings
I am having some problem in that when my son connects his school
computer to our home network either wired or wirelessly it causes either
the router or the modem to go into some error state that make it
inoperative. If you have any thoughts on what we can change on the XP
machine to fix this we'd be most appreciative.
The details.
The network consists of a cluster of various machines Win95, Win98,
Win2K, and Linux attached either wired or wirelessly. Most connections
are wired through a d-link 24 port switch to a Linksys 4 port router and
via a cable modem to the internet. The wireless is via an SMC wireless
router into the same d-link switch. The linksys provides the dhcp and
dhcp is turned off on the smc. The smc is basically just acting as a
wireless access point. This has worked flawlessly for ages and only
needs to get reset (cycle the power) when there is a glip in our power
(i.e., runs fine for months at a time).
Enter XP ....
Configuring the laptop (IBM R41 I think) for wireless was a bit of a
mystery with XP's settings but we got it going. Problem is that within
a few minutes of connecting XP will toast the SMC for all users
requiring that it be powered off & on to get it going again. This is
not doing anything weird just running a browser or mail reader. Ok, so
go to wired, but hey, given a few hours of operation and XP seems to
constipate things somehow. All the lights are on but no data is going
out! Only a power off-on of the linksys and cable modem get it going again.
Yes, both the linksys and the smc are at their latest software levels as
are all the connecting machines. Any ideas what we can change on the XP
machine to make it play well with others? I'd call MS and get a
problem ticket opened on this but I have no way to trace what is going
on and say what the problem might be. Personally I'm inclined to ditch
XP for 2K or Linux but this is a pre-install on my son's laptop for his
school and I think they'd frown upon that kind of thing.
Mike
P.S. When describing this problem to a co-worker I found out that I am
not the only person seeing this same problem (XP hoses the router) and
that others are seeing the same problem with different hardware but the
same OS (WinXP).
computer to our home network either wired or wirelessly it causes either
the router or the modem to go into some error state that make it
inoperative. If you have any thoughts on what we can change on the XP
machine to fix this we'd be most appreciative.
The details.
The network consists of a cluster of various machines Win95, Win98,
Win2K, and Linux attached either wired or wirelessly. Most connections
are wired through a d-link 24 port switch to a Linksys 4 port router and
via a cable modem to the internet. The wireless is via an SMC wireless
router into the same d-link switch. The linksys provides the dhcp and
dhcp is turned off on the smc. The smc is basically just acting as a
wireless access point. This has worked flawlessly for ages and only
needs to get reset (cycle the power) when there is a glip in our power
(i.e., runs fine for months at a time).
Enter XP ....
Configuring the laptop (IBM R41 I think) for wireless was a bit of a
mystery with XP's settings but we got it going. Problem is that within
a few minutes of connecting XP will toast the SMC for all users
requiring that it be powered off & on to get it going again. This is
not doing anything weird just running a browser or mail reader. Ok, so
go to wired, but hey, given a few hours of operation and XP seems to
constipate things somehow. All the lights are on but no data is going
out! Only a power off-on of the linksys and cable modem get it going again.
Yes, both the linksys and the smc are at their latest software levels as
are all the connecting machines. Any ideas what we can change on the XP
machine to make it play well with others? I'd call MS and get a
problem ticket opened on this but I have no way to trace what is going
on and say what the problem might be. Personally I'm inclined to ditch
XP for 2K or Linux but this is a pre-install on my son's laptop for his
school and I think they'd frown upon that kind of thing.
Mike
P.S. When describing this problem to a co-worker I found out that I am
not the only person seeing this same problem (XP hoses the router) and
that others are seeing the same problem with different hardware but the
same OS (WinXP).