On Sat, 20 May 2006 13:03:37 -0400, Claude Schneegans
No, as I said, the problem is only when I browse directories on the
server, from the station.
OK. Some causes would have affected both, so it was worth asking,
especially as one such cause can also kill data (failing HD)
Then I have no network anymore, but I tried to connect to the server
through a phisical cable.
Still the same refresh problem, although, since the connexion is faster,
it is not crucial.
O...K... not chalk-and-cheese, then. A duff or out of spec (e.g. too
long, too many hops, sub-CAT5 quality UTP, door jamb and dog teeth
damage) LAN cable can cause extra overhead in much the same way as a
sick HD - retries to send the same data - and I'd guess that bad
reception or interference would do the same for WiFi.
AFAIK, WiFi is slightly slower than Ethernet, so your mileage makes
sense for things that affect both equally.
No, no problem and no refresh with local folders.
Guuuud, as above
The local HD is (or should be!) so much faster than LAN that a
per-item overhead may not be "felt" there, so I'm not so sure that
this would be a pure network problem.
Then again, there's whatever's on the other end of the cable; maybe
something is slow there?
Is there any parameter to deactivate this refresh? I'm big enough to
refresh myself if I find it necessary.
There used to be a setting in Win.ini or System.ini from the Win3.yuk
days, that may have persisted into early Win9x; I doubt if it would
still have an effect. Explorer's laggy enough on changes as it is
(e.g. a folder deleted in the right pane is still shown in the left
tree pane), so I'd think in two directions:
- why is the refresh taking so long?
- is there something causing far too many refreshes?
Well, I hope so, ... what is WEP, and were is it enabled? ;-)
WEP was the first "good enough" Wireless security scheme, that wasn't
good enough after all. Automated tools may crack it in a few minutes,
and yet it is left On by default so that "old" WiFi gear will still
work. Now we are told not to use WEP, but to trust WPA instead,
because that is "good enough". Personally, I prefer cables.
The thing about WiFi LAN is that most defenses are Internet-facing,
and assume the LAN side of the router is populated only by "good
guys". Hence dumb-ass ideas such as hidden admin shares that expose
everything (can you say, "Startup dropper"?) under a guessable name
and whatever non-blank password "protects" XP Pro's user accounts.
IMO, the only way I can be sure of "who" is on the LAN, is to
physicaly limit that to where the cables go.
-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...