Author: stefstef
Date: Apr 1, 2008 16:00
Hello,
Running on a win2k server, I did a tcp/ip server like in C (vc6-sp4)
which waits client connections (and does thing after but no the
problem, I think...)
If I run the server under a cmd.exe, everything works fine, I can up
to 200/300 "simultaneous" client connections.
(I'm using non-blocking select() with FD_SETSIZE set to 1024)
Perfect...
But now, If I set the server in "service mode" (with XYNTService tool
for example), I got WSAECONNRESET 100054 socket error after 165 client
entries !!
I don't have this behavior under windows-XP, windows-2003 and
windows-2008... only on windows 2000 family.
Before going deeply into code explanations, could you just tell me if
there's something "special" with socket under win2k (some kind of
console limitation !?)
Thanks for your help
|