Discussion:
WinXP hordes os/2 server connections
(too old to reply)
Jim Moe
2008-01-03 22:08:37 UTC
Permalink
Hello,
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that convinces
it to actually release connections when a file closes?
If, for instance, the XP user happens to open and close a large number
of files, after a while no one else, windows or os/2, can log on to the
server. Once the XP user logs off, everyone else can then access the
server again.
--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
William L. Hartzell
2008-01-04 02:08:20 UTC
Permalink
Post by Jim Moe
Hello,
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that convinces
it to actually release connections when a file closes?
If, for instance, the XP user happens to open and close a large number
of files, after a while no one else, windows or os/2, can log on to the
server. Once the XP user logs off, everyone else can then access the
server again.
I ran across a program that closes sockets in 'idle wait' state. Would
closing these sockets on the OS/2 machine fix this or not?
<ftp://happyos2.darktech.org/gfd/net/misc/>
--
Bill
Thanks a Million!
Jim Moe
2008-01-04 07:50:46 UTC
Permalink
Post by William L. Hartzell
Post by Jim Moe
If, for instance, the XP user happens to open and close a large number
of files, after a while no one else, windows or os/2, can log on to the
server. Once the XP user logs off, everyone else can then access the
server again.
I ran across a program that closes sockets in 'idle wait' state. Would
closing these sockets on the OS/2 machine fix this or not?
<ftp://happyos2.darktech.org/gfd/net/misc/>
No, I have a program that does that. It makes no difference.
I have also applied some other registry changes that seemed to help with
win2k.
--
jmm (hyphen) list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)
William L. Hartzell
2008-01-04 08:57:15 UTC
Permalink
Post by Jim Moe
Post by William L. Hartzell
Post by Jim Moe
If, for instance, the XP user happens to open and close a large number
of files, after a while no one else, windows or os/2, can log on to the
server. Once the XP user logs off, everyone else can then access the
server again.
I ran across a program that closes sockets in 'idle wait' state. Would
closing these sockets on the OS/2 machine fix this or not?
<ftp://happyos2.darktech.org/gfd/net/misc/>
No, I have a program that does that. It makes no difference.
I have also applied some other registry changes that seemed to help with
win2k.
Too bad. I looked for a program that would count the number of open
sockets on the win32 machine and make the user to log out when some
amount was reached. Did not find one.

What happens if you edit
HKLM\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections to limit
the number of connections to say 100 per machine, instead of thousands
that W2K and later allow?
--
Bill
Thanks a Million!
Alex Taylor
2008-01-04 23:12:01 UTC
Permalink
Post by Jim Moe
Hello,
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that convinces
it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
--
Alex Taylor
http://www.cs-club.org/~alex

Please take off hat when replying.
Bob Eager
2008-01-04 23:18:08 UTC
Permalink
On Fri, 4 Jan 2008 23:12:01 UTC, "Alex Taylor"
Post by Alex Taylor
Post by Jim Moe
Hello,
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that convinces
it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
I've kept my one XP machine well up to date (although not on very
often). When I *have used it, it's taken out the server within a few
days. Only stopped when I replaced it with a low power (in all senses)
FreeBSD server. I never share stuff to XP on the other OS/2 machines so
it's not been an issue.
Alex Taylor
2008-01-05 22:53:02 UTC
Permalink
Post by Bob Eager
Post by Alex Taylor
Post by Jim Moe
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that
convinces it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
I've kept my one XP machine well up to date (although not on very
often). When I *have used it, it's taken out the server within a few
days. Only stopped when I replaced it with a low power (in all senses)
FreeBSD server. I never share stuff to XP on the other OS/2 machines so
it's not been an issue.
I think this is the reference I was looking for:
http://support.microsoft.com/kb/323582
--
Alex Taylor
Fukushima, Japan
http://www.cs-club.org/~alex

Please take off hat when replying.
Bob Eager
2008-01-06 00:37:30 UTC
Permalink
On Sat, 5 Jan 2008 22:53:02 UTC, "Alex Taylor"
Post by Alex Taylor
Post by Bob Eager
Post by Alex Taylor
Post by Jim Moe
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that
convinces it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
I've kept my one XP machine well up to date (although not on very
often). When I *have used it, it's taken out the server within a few
days. Only stopped when I replaced it with a low power (in all senses)
FreeBSD server. I never share stuff to XP on the other OS/2 machines so
it's not been an issue.
http://support.microsoft.com/kb/323582
Unfortunately, it continued to happen even after installing the service
pack...!
Andy Willis
2008-01-06 05:35:17 UTC
Permalink
Post by Bob Eager
On Sat, 5 Jan 2008 22:53:02 UTC, "Alex Taylor"
Post by Alex Taylor
Post by Bob Eager
Post by Alex Taylor
Post by Jim Moe
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that
convinces it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
I've kept my one XP machine well up to date (although not on very
often). When I *have used it, it's taken out the server within a few
days. Only stopped when I replaced it with a low power (in all senses)
FreeBSD server. I never share stuff to XP on the other OS/2 machines so
it's not been an issue.
http://support.microsoft.com/kb/323582
Unfortunately, it continued to happen even after installing the service
pack...!
I'd have sworn I had seen posts that people that had set the registry
entry referenced had said the entry worked for them.
Andy
Bob Eager
2008-01-06 09:24:36 UTC
Permalink
On Sun, 6 Jan 2008 05:35:17 UTC, Andy Willis
Post by Andy Willis
Post by Bob Eager
On Sat, 5 Jan 2008 22:53:02 UTC, "Alex Taylor"
Post by Alex Taylor
Post by Bob Eager
Post by Alex Taylor
Post by Jim Moe
WinXP (sp2) does not release connections, session or file, until the
current user logs off. Is there any registry setting for XP that
convinces it to actually release connections when a file closes?
Wasn't this fixed in a service pack at one point?
I've kept my one XP machine well up to date (although not on very
often). When I *have used it, it's taken out the server within a few
days. Only stopped when I replaced it with a low power (in all senses)
FreeBSD server. I never share stuff to XP on the other OS/2 machines so
it's not been an issue.
http://support.microsoft.com/kb/323582
Unfortunately, it continued to happen even after installing the service
pack...!
I'd have sworn I had seen posts that people that had set the registry
entry referenced had said the entry worked for them.
Oh, it reduced the problem. But it still failed eventually. If I had an
intensive session or three on the XP machine, the server eventually
failed.

Loading...