Only a small remark on the sidelines. To be very precise, XP
Home is limited to 5 simultaneous inbound connections.
One way around this is to open the connections only when you
actually need them, and close them afterwards. I think an unused
network connection closes automatically after 15 minutes, but
this is only from my poor memory.
Hans-Georg
HG,
The distinction "simultaneous connections" is relevant - but more so with
multiple computers randomly accessing the same server. With randomly sequenced
accesses, timed out connections are a workaround. Remember that some folks then
complain of mapped drives with a red X under My Computer, and that opening the
drives in question always involves an unacceptable delay (while the connection
is reestablished) (no delay is ever acceptable).
In Harald's case, he was actually seeing an explicit refusal to connect because
the previous connections had not yet timed out. The timeout period is indeed
adjustable, but at the risk of causing a timeout while activity is continuing,
though paused briefly.
AFAIK, adjustment of the timeout period is a Registry Editor issue. I don't
know of an alternate gui, or scriptable, method of changing it. :-(
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.