B
Bob S.
Right after I post this, I'll off to the MS KB to start searching for the
answer but I'm not even sure how to ask the question I need an answer to -
the reason for posting this now.
Have an 8 system, peer-to-peer network, all running XP Home that I'm working
on. I'm well aware of the max users that can be connected (5) at one time on
XP Home. As a test, I'm running a little program (Tcpview) that shows me
which workstations are connected. I've noticed that even though a
workstation is not being used - actively accessing the pseudo-server, the
connection for a workstation remains alive for a period of minutes (~5
min...) and eventually, the connection is closed by XP.
Is there a registry setting or other means which that "connection timeout"
can be adjusted so I can lessen the amount of time?
Thanks,
Bob S.
PS - any "Mitchell 1" users out there?
answer but I'm not even sure how to ask the question I need an answer to -
the reason for posting this now.
Have an 8 system, peer-to-peer network, all running XP Home that I'm working
on. I'm well aware of the max users that can be connected (5) at one time on
XP Home. As a test, I'm running a little program (Tcpview) that shows me
which workstations are connected. I've noticed that even though a
workstation is not being used - actively accessing the pseudo-server, the
connection for a workstation remains alive for a period of minutes (~5
min...) and eventually, the connection is closed by XP.
Is there a registry setting or other means which that "connection timeout"
can be adjusted so I can lessen the amount of time?
Thanks,
Bob S.
PS - any "Mitchell 1" users out there?