Re: [twsocket] Strange Service/SSL bug that does not happen on GUIproject

2011-10-12 Thread Fastream Technologies
I found the issue. The TrustedCABundle.pem was in relative path to process
folder. In services this is not working as the current path is not the path
of the exe!!
Best Regards,

SZ
On Wed, Oct 12, 2011 at 08:36, Fastream Technologies ga...@fastream.comwrote:

 No error message. The background exception handler catches it silently.
 Regards,

 SZ
 On Wed, Oct 12, 2011 at 08:07, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Hello,
 
  I am trying to run our tsslhttpcli service against _any_ SSL web site
  such as https://encrypted.google.com and it raises an exception in
  handshake.

 And the exception error message is..?

 --
 Arno Garrels
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Service/SSL bug that does not happen on GUIproject

2011-10-11 Thread Fastream Technologies
No error message. The background exception handler catches it silently.
Regards,

SZ
On Wed, Oct 12, 2011 at 08:07, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Hello,
 
  I am trying to run our tsslhttpcli service against _any_ SSL web site
  such as https://encrypted.google.com and it raises an exception in
  handshake.

 And the exception error message is..?

 --
 Arno Garrels
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange SSL-components problem

2011-03-30 Thread Arno Garrels
Hi,

at first you should get atest ICS source code and OpenSSL DLLs from
http://wiki.overbyte.be/wiki/index.php/ICS_Download

The problem with undeclared identifiers is easily solved by rebuilding
the project, a simple compile is not enough after changing the USE_SSL
directive.

-- 
Arno Garrels



Dimitris Botsis wrote:
 Hi all,
 
 I have a very strange problem with ICS.
 I try to use ICS v7 (Oct/2010) fresh downloaded from you website
 (overbyte.be). I install it on Delphi 7.
 All is OK when starting.
 I have an empty form and drop 2 components on it :
 - a Tsslhttpcli
 - a TsslContext
 I have already included the proper paths for ICS in the Delphi
 environment so when I build it's all OK and for SSL I use ssleay32.dll
 and libeay32.dll but due to problems of versions I have disabled SSL
 version checking from OverbyteIcsSslDefs.inc.
 
 After some builds of the same project, without having changed anything
 in the project, I get the error that
 Tsslhttpcli and Tsscontext are undeclared identifiers, although
 previously they were fine.
 If I close and open Delphi and project again, problem is still the
 same. 
 
 The only way to correct it, is to delete all contents of Delphi/Vc32,
 copy there fresh files from the downloaded zip from Overbyte's website
 and rebuild again the OverbyteIcsD7Run.dpk.
 Then it starts working fine for some time tries until it stops with
 the same errors again after some builds.
 
 This happens only with SSL components of ICS, with other components
 everything is OK. Even when the 2 components I refer to seem to be
 undeclared identifiers if I use another non-SSL component (before
 rebuilding-that solves temporarily the problem) all other work fine.
 
 Please note that :
 - I don't have any other problem with no other components installed
 - When I manage to compile project correct, then executable file is
 fine for always. The problem appears only in the Delphi environment
 together with ICS, while in build process.
 
 Thank you very much.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange SSL-components problem

2011-03-30 Thread Dimitris Botsis

Hi Arno, thank you for replying.

I rebuild the project every time the problem occurs.
I even uninstall the whole package and install it again.
First times it works fine without problems.
And then, starts reporting about undeclared identifiers of 
SSL-components. Only for SSL components.

It's the first time I see something like this.

On 30/3/2011 10:15 μμ, Arno Garrels wrote:

Hi,

at first you should get atest ICS source code and OpenSSL DLLs from
http://wiki.overbyte.be/wiki/index.php/ICS_Download

The problem with undeclared identifiers is easily solved by rebuilding
the project, a simple compile is not enough after changing the USE_SSL
directive.



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] Strange SSL-components problem

2011-03-30 Thread Dimitris Botsis

Hi all,

I corrected the problem, thank you Arno and Francois for helping.
I did not have USE_SSL enabled but although it was not enabled, the 
first times the build was succesful with SSL support - I don't know why.

Anyway, now I have rebuilt the whole package with USE_SSL and it's fine.
Thank you once more.

On 30/3/2011 10:20 μμ, Dimitris Botsis wrote:

Hi Arno, thank you for replying.

I rebuild the project every time the problem occurs.
I even uninstall the whole package and install it again.
First times it works fine without problems.
And then, starts reporting about undeclared identifiers of
SSL-components. Only for SSL components.
It's the first time I see something like this.

On 30/3/2011 10:15 μμ, Arno Garrels wrote:

Hi,

at first you should get atest ICS source code and OpenSSL DLLs from
http://wiki.overbyte.be/wiki/index.php/ICS_Download

The problem with undeclared identifiers is easily solved by rebuilding
the project, a simple compile is not enough after changing the USE_SSL
directive.



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be





--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] Strange SSL-components problem

2011-03-30 Thread Arno Garrels
Dimitris Botsis wrote:
 Hi Arno, thank you for replying.
 
 I rebuild the project every time the problem occurs.
 I even uninstall the whole package and install it again.
 First times it works fine without problems.

That's because the package is built with USE_SSL enabled by default.
However you have to set USE_SSL in the project options as well.

Anyway whenever you see this error check whether or not
USE_SSL is defined in project's options and rebuild the project.

-- 
Arno Garrels


--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS application issue (MadExcept report)

2010-12-04 Thread Arno Garrels
Fastream Technologies wrote:
 Hello,
 
 I have received the below report from a tester. What could be the
 cause of it, any idea?

From the stack trace it looks like the exception is raised
in TComponent.RemoveFreeNotifications of the CtrlSocket. 

Is the SslContext or an IcsLogger instance shared across multiple
threads? If so, they might have been destroyed by another thread yet?

Do you make sure that all threads are finished before you exit the
application?

-- 
Arno Garrels






--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS application issue (MadExcept report)

2010-12-04 Thread Arno Garrels
Fastream Technologies wrote:
 Dear Arno,
 
 On Sat, Dec 4, 2010 at 2:11 PM, Arno Garrels arno.garr...@gmx.de
 wrote: 
 
 Fastream Technologies wrote:
 Hello,
 
 I have received the below report from a tester. What could be the
 cause of it, any idea?
 
 From the stack trace it looks like the exception is raised
 in TComponent.RemoveFreeNotifications of the CtrlSocket.
 
 Is the SslContext or an IcsLogger instance shared across multiple
 threads? If so, they might have been destroyed by another thread yet?
 
 Do you make sure that all threads are finished before you exit the
 application?

 We do not use IcsLoggers as NO_DEBUG_LOG is defined. We have
 TSslContext objects defined in the listener thread which has many
 worker threads with THttpConnection's and TSslHttpCli's inside. This
 exception is not thrown when the program is exiting and when the
 worker threads are destructed. We have separate thread,

The VCL and its component notification system is not thread-safe, 
that's likely the cause of the AV. Change your code to use one 
instance of TSslContext per thread, that should resolve it (I 
remember I claimed that TSslContext was thread-safe some years 
back, but did not take component notification into account, sorry).  

-- 
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS application issue (MadExcept report)

2010-12-04 Thread Fastream Technologies
Hello,

On Sat, Dec 4, 2010 at 3:55 PM, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Dear Arno,
 
  On Sat, Dec 4, 2010 at 2:11 PM, Arno Garrels arno.garr...@gmx.de
  wrote:
 
  Fastream Technologies wrote:
  Hello,
 
  I have received the below report from a tester. What could be the
  cause of it, any idea?
 
  From the stack trace it looks like the exception is raised
  in TComponent.RemoveFreeNotifications of the CtrlSocket.
 
  Is the SslContext or an IcsLogger instance shared across multiple
  threads? If so, they might have been destroyed by another thread yet?
 
  Do you make sure that all threads are finished before you exit the
  application?

  We do not use IcsLoggers as NO_DEBUG_LOG is defined. We have
  TSslContext objects defined in the listener thread which has many
  worker threads with THttpConnection's and TSslHttpCli's inside. This
  exception is not thrown when the program is exiting and when the
  worker threads are destructed. We have separate thread,

 The VCL and its component notification system is not thread-safe,
 that's likely the cause of the AV. Change your code to use one
 instance of TSslContext per thread, that should resolve it (I
 remember I claimed that TSslContext was thread-safe some years
 back, but did not take component notification into account, sorry).

 --
 Arno Garrels



The site that is having problems is NOT using SSL at all. In their case
there is just a listener SSL port with no traffic (but has a TSslContext)
and some TSslHttpCli's which connect to HTTP web server--does your advice
still apply?

Regards,

SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS application issue (MadExcept report)

2010-12-04 Thread Fastream Technologies
Dear Arno,

I have written the below code after your suggestion and wish to get your
feedback before uploading as a beta:

void __fastcall ReverseProxyClientThread::Execute() // multiple worker
client objects, both TSslHttpCli's and THttpConnections are in the context
of this
{
// Place thread code here 
FreeOnTerminate = true;

 initSSLContexes();

while(!Terminated)
messagePump();

destroySSLContexes();
}
//---
void __fastcall ReverseProxyClientThread::initSSLContexes(void)
{
sslContextList = new TList();

TSslContext *HTTPSSLContext;
 EncryptionSettings *encryptionSettings;

lockCriticalSection(serverThread-SNIContainer-CS);

for(int i = 0; i  serverThread-SNIContainer-SNIDomains-Count; ++i)
{
 HTTPSSLContext = new TSslContext(NULL);
sslContextList-Add(HTTPSSLContext);

encryptionSettings =
(EncryptionSettings*)serverThread-SNIContainer-SNIDomains-Objects[i]; //
contains different SNI domains' configuration data--protected by the
SNIContainer-CS critical section

HTTPSSLContext-SslVerifyPeer = false;
HTTPSSLContext-SslVerifyDepth = 9;
 HTTPSSLContext-SslOptions  sslOpt_MICROSOFT_SESS_ID_BUG 
sslOpt_NETSCAPE_CHALLENGE_BUG  sslOpt_NETSCAPE_REUSE_CIPHER_CHANGE_BUG 
sslOpt_SSLREF2_REUSE_CERT_TYPE_BUG  sslOpt_MICROSOFT_BIG_SSLV3_BUFFER 
sslOpt_SSLEAY_080_CLIENT_DH_BUG  sslOpt_TLS_D5_BUG 
sslOpt_TLS_BLOCK_PADDING_BUG, sslOpt_TLS_ROLLBACK_BUG  sslOpt_NO_SSLv2 
sslOpt_NETSCAPE_CA_DN_BUG  sslOpt_NO_SESSION_RESUMPTION_ON_RENEGOTIATION
 sslOpt_NETSCAPE_DEMO_CIPHER_CHANGE_BUG;
 HTTPSSLContext-SslVerifyPeerModes  SslVerifyMode_PEER;
HTTPSSLContext-SslSessionCacheModes  sslSESS_CACHE_SERVER;
 HTTPSSLContext-SslCipherList = ALL:!ADH:!DES:RC4:@STRENGTH;
HTTPSSLContext-SslVersionMethod = sslV23_SERVER;
 HTTPSSLContext-SslSessionTimeout = 300;
HTTPSSLContext-SslSessionCacheSize = 20480;

HTTPSSLContext-SslCertFile = encryptionSettings-certFile;
HTTPSSLContext-SslPrivKeyFile = encryptionSettings-privateKey;
 HTTPSSLContext-SslCAFile = encryptionSettings-CAFile;
HTTPSSLContext-SslCAPath = encryptionSettings-CAPath;

HTTPSSLContext-SslOptions  sslOpt_NO_SSLv2  sslOpt_NO_SSLv3 
sslOpt_NO_TLSv1;

if(!encryptionSettings-useSSLv2)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_SSLv2;
if(!encryptionSettings-useSSLv3)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_SSLv3;
if(!encryptionSettings-useTLSv1)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_TLSv1;

HTTPSSLContext-SslSessionCacheModes = TSslSessCacheModes() 
sslSESS_CACHE_SERVER  sslSESS_CACHE_NO_INTERNAL_LOOKUP 
sslSESS_CACHE_NO_INTERNAL_STORE;
 HTTPSSLContext-SslOptions  sslOpt_CIPHER_SERVER_PREFERENCE;

try
 {
HTTPSSLContext-InitContext();
}
 catch(Exception e)
{
}
 }

releaseCriticalSection(serverThread-SNIContainer-CS);
}
//---
void __fastcall ReverseProxyClientThread::destroySSLContexes(void)
{
for(int i = sslContextList-Count - 1; i = 0; --i)
 delete (TSslContext*)sslContextList-Items[i];

delete sslContextList;
}
//---

This seems okay to me but maybe you have something to say!

Best Regards,

SZ

On Sat, Dec 4, 2010 at 5:17 PM, Fastream Technologies ga...@fastream.comwrote:

 Hello,

 On Sat, Dec 4, 2010 at 3:55 PM, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Dear Arno,
 
  On Sat, Dec 4, 2010 at 2:11 PM, Arno Garrels arno.garr...@gmx.de
  wrote:
 
  Fastream Technologies wrote:
  Hello,
 
  I have received the below report from a tester. What could be the
  cause of it, any idea?
 
  From the stack trace it looks like the exception is raised
  in TComponent.RemoveFreeNotifications of the CtrlSocket.
 
  Is the SslContext or an IcsLogger instance shared across multiple
  threads? If so, they might have been destroyed by another thread yet?
 
  Do you make sure that all threads are finished before you exit the
  application?

  We do not use IcsLoggers as NO_DEBUG_LOG is defined. We have
  TSslContext objects defined in the listener thread which has many
  worker threads with THttpConnection's and TSslHttpCli's inside. This
  exception is not thrown when the program is exiting and when the
  worker threads are destructed. We have separate thread,

 The VCL and its component notification system is not thread-safe,
 that's likely the cause of the AV. Change your code to use one
 instance of TSslContext per thread, that should resolve it (I
 remember I claimed that TSslContext was thread-safe some years
 back, but did not take component notification into account, sorry).

 --
 Arno Garrels



 The site that is having problems is NOT using SSL at all. In their case
 there is just a listener SSL port with no traffic (but has a TSslContext)
 and some TSslHttpCli's which connect to HTTP web server--does your advice
 still apply?

 Regards,

 SZ

--
To unsubscribe or change your settings for TWSocket 

Re: [twsocket] Strange ICS application issue (MadExcept report)

2010-12-04 Thread Arno Garrels
Fastream Technologies wrote:
 Dear Arno,
 
 I have written the below code after your suggestion and wish to get
 your feedback before uploading as a beta:

I can't say whether it's OK or not. Just make sure that all your 
TSsl objects in that thread are assigned a SslContext created
in the same thread context. No TSsl object must be assigned a 
SslContext created in a different thread context. With such a design
you are on the safe side. If that doesn't help to fix the AV there
must be still something else going wrong.

-- 
Arno Garrels

 
 void __fastcall ReverseProxyClientThread::Execute() // multiple worker
 client objects, both TSslHttpCli's and THttpConnections are in the
 context 
 of this
 {
 // Place thread code here 
 FreeOnTerminate = true;
 
 initSSLContexes();
 
 while(!Terminated)
 messagePump();
 
 destroySSLContexes();
 }
 //---
 void __fastcall ReverseProxyClientThread::initSSLContexes(void)
 {
 sslContextList = new TList();
 
 TSslContext *HTTPSSLContext;
 EncryptionSettings *encryptionSettings;
 
 lockCriticalSection(serverThread-SNIContainer-CS);
 
 for(int i = 0; i  serverThread-SNIContainer-SNIDomains-Count; ++i)
 {
 HTTPSSLContext = new TSslContext(NULL);
 sslContextList-Add(HTTPSSLContext);
 
 encryptionSettings =
 (EncryptionSettings*)serverThread-SNIContainer-SNIDomains-Objects[i];
 // contains different SNI domains' configuration data--protected by
 the SNIContainer-CS critical section
 
 HTTPSSLContext-SslVerifyPeer = false;
 HTTPSSLContext-SslVerifyDepth = 9;
 HTTPSSLContext-SslOptions  sslOpt_MICROSOFT_SESS_ID_BUG 
 sslOpt_NETSCAPE_CHALLENGE_BUG 
 sslOpt_NETSCAPE_REUSE_CIPHER_CHANGE_BUG 
 sslOpt_SSLREF2_REUSE_CERT_TYPE_BUG 
 sslOpt_MICROSOFT_BIG_SSLV3_BUFFER  sslOpt_SSLEAY_080_CLIENT_DH_BUG
  sslOpt_TLS_D5_BUG  sslOpt_TLS_BLOCK_PADDING_BUG,
 sslOpt_TLS_ROLLBACK_BUG  sslOpt_NO_SSLv2 
 sslOpt_NETSCAPE_CA_DN_BUG 
 sslOpt_NO_SESSION_RESUMPTION_ON_RENEGOTIATION 
 sslOpt_NETSCAPE_DEMO_CIPHER_CHANGE_BUG;   
 HTTPSSLContext-SslVerifyPeerModes  SslVerifyMode_PEER;
 HTTPSSLContext-SslSessionCacheModes  sslSESS_CACHE_SERVER;
 HTTPSSLContext-SslCipherList = ALL:!ADH:!DES:RC4:@STRENGTH;
 HTTPSSLContext-SslVersionMethod = sslV23_SERVER;
 HTTPSSLContext-SslSessionTimeout = 300;
 HTTPSSLContext-SslSessionCacheSize = 20480;
 
 HTTPSSLContext-SslCertFile = encryptionSettings-certFile;
 HTTPSSLContext-SslPrivKeyFile = encryptionSettings-privateKey;
 HTTPSSLContext-SslCAFile = encryptionSettings-CAFile;
 HTTPSSLContext-SslCAPath = encryptionSettings-CAPath;
 
 HTTPSSLContext-SslOptions  sslOpt_NO_SSLv2  sslOpt_NO_SSLv3 
 sslOpt_NO_TLSv1;
 
 if(!encryptionSettings-useSSLv2)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_SSLv2;
 if(!encryptionSettings-useSSLv3)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_SSLv3;
 if(!encryptionSettings-useTLSv1)
 HTTPSSLContext-SslOptions = TSslOptions()  sslOpt_NO_TLSv1;
 
 HTTPSSLContext-SslSessionCacheModes = TSslSessCacheModes() 
 sslSESS_CACHE_SERVER  sslSESS_CACHE_NO_INTERNAL_LOOKUP 
 sslSESS_CACHE_NO_INTERNAL_STORE;
 HTTPSSLContext-SslOptions  sslOpt_CIPHER_SERVER_PREFERENCE;
 
 try
 {
 HTTPSSLContext-InitContext();
 }
 catch(Exception e)
 {
 }
 }
 
 releaseCriticalSection(serverThread-SNIContainer-CS);
 }
 //---
 void __fastcall ReverseProxyClientThread::destroySSLContexes(void)
 {
 for(int i = sslContextList-Count - 1; i = 0; --i)
 delete (TSslContext*)sslContextList-Items[i];
 
 delete sslContextList;
 }
 //---
 
 This seems okay to me but maybe you have something to say!
 
 Best Regards,
 
 SZ
 
 On Sat, Dec 4, 2010 at 5:17 PM, Fastream Technologies
 ga...@fastream.comwrote: 
 
 Hello,
 
 On Sat, Dec 4, 2010 at 3:55 PM, Arno Garrels arno.garr...@gmx.de
 wrote: 
 
 Fastream Technologies wrote:
 Dear Arno,
 
 On Sat, Dec 4, 2010 at 2:11 PM, Arno Garrels arno.garr...@gmx.de
 wrote:
 
 Fastream Technologies wrote:
 Hello,
 
 I have received the below report from a tester. What could be the
 cause of it, any idea?
 
 From the stack trace it looks like the exception is raised
 in TComponent.RemoveFreeNotifications of the CtrlSocket.
 
 Is the SslContext or an IcsLogger instance shared across multiple
 threads? If so, they might have been destroyed by another thread
 yet? 
 
 Do you make sure that all threads are finished before you exit the
 application?
 
 We do not use IcsLoggers as NO_DEBUG_LOG is defined. We have
 TSslContext objects defined in the listener thread which has many
 worker threads with THttpConnection's and TSslHttpCli's inside.
 This exception is not thrown when the program is exiting and when
 the worker threads are destructed. We have separate thread,
 
 The VCL and its component notification system is not thread-safe,
 that's likely the cause of the AV. Change your code to use one
 instance of 

Re: [twsocket] Strange threads in ICS applications in Win7

2010-09-13 Thread Fastream Technologies
I wonder if this is the case with Win2008R2 as well...

SZ

On Mon, Sep 13, 2010 at 10:40 AM, Arno Garrels arno.garr...@gmx.de wrote:

 Hi,

 FYI:

 http://stackoverflow.com/questions/2484921/strange-threads-in-application-in-win7-wow64

 --
 Arno Garrels


 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-24 Thread Fastream Technologies
I have made some more tests on my Win7Pro and saw that MS was clever enough
to raise the 1 handles per process limit in newer Windows'. I think the
new limit is something like 24-25000. To support 20k connections with ICS,
we still need to raise the WH_MAX_MSG though. Any comment on making this a
property?

Regards,

SZ

On Sun, May 23, 2010 at 2:08 PM, Fastream Technologies
ga...@fastream.comwrote:

 Hi and welcome back Francois.

 On Sun, May 23, 2010 at 12:12 PM, Francois PIETTE 
 francois.pie...@skynet.be wrote:

 Not sure how the debug GUI exe works but I found a solution for the
 service:

 In ...WndControl.pas,

 const
  TIcsWndControlVersion  = 110;
  CopyRight : String = ' TIcsWndControl (c) 2002-2008 F. Piette V1.10
 ';

  WH_MAX_MSG   = 400; == MODIFIED THIS from 100

 so that it would create less windows per same number of messages. With
 this
 change, My also ICS stress tester can open  15k connections
 concurrently.
 In a real life case, since there will not be a stress tester on the same
 machine, I think it is ok. This must be a non-paged RAM drought issue...

 Could you make WH_MAX_MSG a property so that each time users update ICS,
 they would not need to change ICS source?


 It is likely that Windows has different settings for a service application
 and a GUI application. Since a GUI application is likely to use a lot of
 windows (visible or not), probably Windows size his internal tables
 accordingly. A GUI application has a default 10.000 handles allowed. This is
 why I created TIcsWndControl in the first place. This allow to open more
 concurrent sockets since with TIcsWndControl a single window handle a lot of
 sockets (100 by default) and you don't run out of handle anymore.

 This article could be a starting point for you:
 http://weblogs.asp.net/mikedopp/archive/2008/05/16/increasing-user-handle-and-gdi-handle-limits.aspx
 And also this one:
 http://www.google.be/search?q=windows+handle+limit+1

 --
 francois.pie...@overbyte.be
 The author of the freeware multi-tier middleware MidWare
 The author of the freeware Internet Component Suite (ICS)
 http://www.overbyte.be


 I still think we should make the const a property as the number of handles
 per process limit (1) as your links mention, could sometimes be exceeded
 by server apps which compete with UNIX-kind- apps/sync apps. As I said, I
 tested here that when I double or quadraple the const WH_MAX_MSG, it WORKS
 for 20k sockets.

 BTW, let me tell you what I think: Windows design is getting older and old
 every day. The limit of non-paged RAM should be higher and for handles and
 for threads as well--provided that MS really wants the Win2008+ to be a
 solid SERVER OS.

 Best Regards,

 SZ

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-23 Thread Francois PIETTE
Not sure how the debug GUI exe works but I found a solution for the 
service:


In ...WndControl.pas,

const
 TIcsWndControlVersion  = 110;
 CopyRight : String = ' TIcsWndControl (c) 2002-2008 F. Piette V1.10 
';


 WH_MAX_MSG   = 400; == MODIFIED THIS from 100

so that it would create less windows per same number of messages. With 
this

change, My also ICS stress tester can open  15k connections concurrently.
In a real life case, since there will not be a stress tester on the same
machine, I think it is ok. This must be a non-paged RAM drought issue...

Could you make WH_MAX_MSG a property so that each time users update ICS,
they would not need to change ICS source?


It is likely that Windows has different settings for a service application 
and a GUI application. Since a GUI application is likely to use a lot of 
windows (visible or not), probably Windows size his internal tables 
accordingly. A GUI application has a default 10.000 handles allowed. This is 
why I created TIcsWndControl in the first place. This allow to open more 
concurrent sockets since with TIcsWndControl a single window handle a lot of 
sockets (100 by default) and you don't run out of handle anymore.


This article could be a starting point for you: 
http://weblogs.asp.net/mikedopp/archive/2008/05/16/increasing-user-handle-and-gdi-handle-limits.aspx

And also this one: http://www.google.be/search?q=windows+handle+limit+1

--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-23 Thread Fastream Technologies
Hi and welcome back Francois.

On Sun, May 23, 2010 at 12:12 PM, Francois PIETTE francois.pie...@skynet.be
 wrote:

 Not sure how the debug GUI exe works but I found a solution for the
 service:

 In ...WndControl.pas,

 const
  TIcsWndControlVersion  = 110;
  CopyRight : String = ' TIcsWndControl (c) 2002-2008 F. Piette V1.10
 ';

  WH_MAX_MSG   = 400; == MODIFIED THIS from 100

 so that it would create less windows per same number of messages. With
 this
 change, My also ICS stress tester can open  15k connections concurrently.
 In a real life case, since there will not be a stress tester on the same
 machine, I think it is ok. This must be a non-paged RAM drought issue...

 Could you make WH_MAX_MSG a property so that each time users update ICS,
 they would not need to change ICS source?


 It is likely that Windows has different settings for a service application
 and a GUI application. Since a GUI application is likely to use a lot of
 windows (visible or not), probably Windows size his internal tables
 accordingly. A GUI application has a default 10.000 handles allowed. This is
 why I created TIcsWndControl in the first place. This allow to open more
 concurrent sockets since with TIcsWndControl a single window handle a lot of
 sockets (100 by default) and you don't run out of handle anymore.

 This article could be a starting point for you:
 http://weblogs.asp.net/mikedopp/archive/2008/05/16/increasing-user-handle-and-gdi-handle-limits.aspx
 And also this one:
 http://www.google.be/search?q=windows+handle+limit+1

 --
 francois.pie...@overbyte.be
 The author of the freeware multi-tier middleware MidWare
 The author of the freeware Internet Component Suite (ICS)
 http://www.overbyte.be


I still think we should make the const a property as the number of handles
per process limit (1) as your links mention, could sometimes be exceeded
by server apps which compete with UNIX-kind- apps/sync apps. As I said, I
tested here that when I double or quadraple the const WH_MAX_MSG, it WORKS
for 20k sockets.

BTW, let me tell you what I think: Windows design is getting older and old
every day. The limit of non-paged RAM should be higher and for handles and
for threads as well--provided that MS really wants the Win2008+ to be a
solid SERVER OS.

Best Regards,

SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-21 Thread Fastream Technologies
Hi Arno,

Not sure how the debug GUI exe works but I found a solution for the service:

In ...WndControl.pas,

const
  TIcsWndControlVersion  = 110;
  CopyRight : String = ' TIcsWndControl (c) 2002-2008 F. Piette V1.10 ';

  WH_MAX_MSG   = 400; == MODIFIED THIS from 100

so that it would create less windows per same number of messages. With this
change, My also ICS stress tester can open  15k connections concurrently.
In a real life case, since there will not be a stress tester on the same
machine, I think it is ok. This must be a non-paged RAM drought issue...

Could you make WH_MAX_MSG a property so that each time users update ICS,
they would not need to change ICS source?

Regards,

SZ

On Thu, May 20, 2010 at 9:46 PM, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Yes I see but under the same computer, same Win7Pro, same 4GB RAM,
  the GUI -debug- project that does exactly the same thing works very
  well!!

 I guess both use the same ICS, isn't it?
 So most likely something in your service-code makes the difference.

 --
 Arno Garrels




--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-20 Thread Fastream Technologies
Here is what I have done more: - attached the debugger to service process
and got,
http://www.fastream.com/ics/icserror8.png

Hope you can help,

SZ

On Thu, May 20, 2010 at 7:10 PM, Fastream Technologies
ga...@fastream.comwrote:

 Hello,

 When under stress test, the service -project- crashes and needs a Task
 manager kill with more than 5,860 connections. When I use the same source
 with GUI project, it easily scales up to 20,000 connections. Any idea what
 we should be taking care of that we have not??

 Thanks,

 SZ

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-20 Thread Arno Garrels
Fastream Technologies wrote:
 Here is what I have done more: - attached the debugger to service
 process and got,
 http://www.fastream.com/ics/icserror8.png

  ERROR_NOT_ENOUGH_MEMORY 8 (0x8)
--
Arno Garrels

 
 Hope you can help,
 
 SZ
 
 On Thu, May 20, 2010 at 7:10 PM, Fastream Technologies
 ga...@fastream.comwrote:
 
 Hello,
 
 When under stress test, the service -project- crashes and needs a
 Task manager kill with more than 5,860 connections. When I use the
 same source with GUI project, it easily scales up to 20,000
 connections. Any idea what we should be taking care of that we have
 not?? 
 
 Thanks,
 
 SZ
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-20 Thread Fastream Technologies
Yes I see but under the same computer, same Win7Pro, same 4GB RAM, the GUI
-debug- project that does exactly the same thing works very well!! I am
trying to push the 32-bit compiler to its limits.

On Thu, May 20, 2010 at 8:17 PM, Arno Garrels arno.garr...@gmx.de wrote:

 Fastream Technologies wrote:
  Here is what I have done more: - attached the debugger to service
  process and got,
  http://www.fastream.com/ics/icserror8.png

   ERROR_NOT_ENOUGH_MEMORY 8 (0x8)
 --
 Arno Garrels

 
  Hope you can help,
 
  SZ
 
  On Thu, May 20, 2010 at 7:10 PM, Fastream Technologies
  ga...@fastream.comwrote:
 
  Hello,
 
  When under stress test, the service -project- crashes and needs a
  Task manager kill with more than 5,860 connections. When I use the
  same source with GUI project, it easily scales up to 20,000
  connections. Any idea what we should be taking care of that we have
  not??
 
  Thanks,
 
  SZ
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange ICS proxy server in service app problem

2010-05-20 Thread Arno Garrels
Fastream Technologies wrote:
 Yes I see but under the same computer, same Win7Pro, same 4GB RAM,
 the GUI -debug- project that does exactly the same thing works very
 well!! 

I guess both use the same ICS, isn't it?
So most likely something in your service-code makes the difference.

--
Arno Garrels



--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange bug in WSocketServer

2010-03-10 Thread Arno Garrels
Bjørnar Nielsen wrote:
 I use Codegear2010 C++-builder and have a strange problem. The
 following code gives me the error: 
 --
 TWSocketServer * WSocketServer1=new TWSocketServer(this);
 WSocketServer1-Listen();
 -

No problem here, of course I get a socket exception Port not assigned.

--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange bug in WSocketServer

2010-03-10 Thread Bjørnar Nielsen
Thanks for testing.

It seems I've messed up my packages. Recompiling all installed third party 
components seems to fix my problem.

Sorry for wasting anybodys time.

Regards 
Bjørnar

-Original Message-
From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On 
Behalf Of Arno Garrels
Sent: 10. mars 2010 14:39
To: ICS support mailing
Subject: Re: [twsocket] Strange bug in WSocketServer

Bjørnar Nielsen wrote:
 I use Codegear2010 C++-builder and have a strange problem. The
 following code gives me the error: 
 --
 TWSocketServer * WSocketServer1=new TWSocketServer(this);
 WSocketServer1-Listen();
 -

No problem here, of course I get a socket exception Port not assigned.

--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange bug in WSocketServer

2010-03-10 Thread Fastream Technologies
FYI, you are not alone--that happens pretty frequently in BCB.

On Wed, Mar 10, 2010 at 3:51 PM, Bjørnar Nielsen bjor...@sentinel.nowrote:

 Thanks for testing.

 It seems I've messed up my packages. Recompiling all installed third party
 components seems to fix my problem.

 Sorry for wasting anybodys time.

 Regards
 Bjørnar

 -Original Message-
 From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On
 Behalf Of Arno Garrels
 Sent: 10. mars 2010 14:39
 To: ICS support mailing
 Subject: Re: [twsocket] Strange bug in WSocketServer

 Bjørnar Nielsen wrote:
  I use Codegear2010 C++-builder and have a strange problem. The
  following code gives me the error:
  --
  TWSocketServer * WSocketServer1=new TWSocketServer(this);
  WSocketServer1-Listen();
  -

 No problem here, of course I get a socket exception Port not assigned.

 --
 Arno Garrels
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
Fastream Technologies
Software IQ: Innovation  Quality
www.fastream.com | www.iqproxyserver.com
Email: sa...@fastream.com | supp...@fastream.com
Pbx: +90-312-223-2830 | MSN: g_a...@hotmail.com | Twitter:
http://twitter.com/fastream
Join IQWF Server Yahoo group at http://groups.yahoo.com/group/IQWFServer
Join IQ Proxy Server Yahoo group at
http://groups.yahoo.com/group/IQProxyServer
THIS IS NOT A NONSENSE SIGNATURE--PLEASE DO JOIN OUR YAHOO GROUPS FOR
ANNOUNCEMENTS ABOUT OUR PRODUCTS!
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] Strange e-mail problems Server 2003

2008-01-02 Thread Dod
Hello Arno,

I see in the log that there is 5 seconds delay between DATA and the
10054 error. This may be interesting.

During  this  delay  do you send data ? I say this because some server
will  close cnx if no data transmitted fast enought and do not receive
data for xx seconds, usually the timeout is between 1 or 3 minutes but
I know a server that wait only 3 seconds (may be bad configuration).

The  best  is  to ask client to manualy telnet port 25 into the server
and  type  a  SMTP  sequence and wait 5 seconds betweent each line you
type.

Also may be there is some check-back cnx to the client's machine and
if FW is ON then machine cannot be checked.

regards.

AG One of my customers reported problems sending mail with an TSmtpCli
AG application when the Windows firewall is turned on. Strange is that
AG sending mail data fails for some reason and the server drops the 
AG connection after ~2 minutes (of inactivity) even though port 25
AG is explicitely opened.

AG First log is with firewall turned off, mail is sent successfully,
AG second log with firewall turned on and port 25 explicitely opened:

AG 01.01.08 2:22:47 PM  MAIL FROM:[EMAIL PROTECTED]
AG 01.01.08 2:22:48 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
AG 01.01.08 2:22:48 PM  RCPT TO:[EMAIL PROTECTED]
AG 01.01.08 2:22:48 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
AG 01.01.08 2:22:48 PM  DATA
AG 01.01.08 2:22:48 PM  354 Enter mail, end with . on a line by itself
AG 01.01.08 2:22:48 PM  .
AG 01.01.08 2:22:48 PM  250 2.0.0 m01JMoVp009311 Message accepted for delivery
AG 01.01.08 2:22:48 PM  QUIT
AG 01.01.08 2:22:48 PM  221 2.0.0 ms-smtp-xyz.com closing connection


AG 01.01.08 4:43:40 PM  MAIL FROM:[EMAIL PROTECTED]
AG 01.01.08 4:43:41 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
AG 01.01.08 4:43:41 PM  RCPT TO:[EMAIL PROTECTED]
AG 01.01.08 4:43:41 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
AG 01.01.08 4:43:41 PM  DATA
AG 01.01.08 4:43:41 PM  354 Enter mail, end with . on a line by itself
AG 01.01.08 4:45:46 PM  Error=10054 Session aborted!

AG Adding the application to the exception list makes no difference.
AG Anybody any idea?

AG --
AG Arno Garrels 


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange e-mail problems Server 2003

2008-01-02 Thread Arno Garrels
Dod wrote:
 Hello Arno,
 
 I see in the log that there is 5 seconds delay between DATA and the
 10054 error. This may be interesting.

No, the delay is 2 minutes and 5 seconds.
One thing I can imagine is a problem with MTU Discovery,
since small packets (SMTP command/response) go thru,
may be the required ICMP packets are filtered?
Does someone know what has to be configured to ensure MTU Discovery
will not fail?

--
Arno Garrels
  

 
 During  this  delay  do you send data ? I say this because some server
 will  close cnx if no data transmitted fast enought and do not receive
 data for xx seconds, usually the timeout is between 1 or 3 minutes but
 I know a server that wait only 3 seconds (may be bad configuration).
 
 The  best  is  to ask client to manualy telnet port 25 into the server
 and  type  a  SMTP  sequence and wait 5 seconds betweent each line you
 type.
 
 Also may be there is some check-back cnx to the client's machine and
 if FW is ON then machine cannot be checked.
 
 regards.
 
 AG One of my customers reported problems sending mail with an
 TSmtpCli AG application when the Windows firewall is turned on.
 Strange is that AG sending mail data fails for some reason and the
 server drops the AG connection after ~2 minutes (of inactivity) even
 though port 25 AG is explicitely opened.
 
 AG First log is with firewall turned off, mail is sent successfully,
 AG second log with firewall turned on and port 25 explicitely opened:
 
 AG 01.01.08 2:22:47 PM  MAIL FROM:[EMAIL PROTECTED]
 AG 01.01.08 2:22:48 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
 AG 01.01.08 2:22:48 PM  RCPT TO:[EMAIL PROTECTED]
 AG 01.01.08 2:22:48 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
 AG 01.01.08 2:22:48 PM  DATA
 AG 01.01.08 2:22:48 PM  354 Enter mail, end with . on a line by
 itself AG 01.01.08 2:22:48 PM  .
 AG 01.01.08 2:22:48 PM  250 2.0.0 m01JMoVp009311 Message accepted
 for delivery AG 01.01.08 2:22:48 PM  QUIT
 AG 01.01.08 2:22:48 PM  221 2.0.0 ms-smtp-xyz.com closing connection
 
 
 AG 01.01.08 4:43:40 PM  MAIL FROM:[EMAIL PROTECTED]
 AG 01.01.08 4:43:41 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
 AG 01.01.08 4:43:41 PM  RCPT TO:[EMAIL PROTECTED]
 AG 01.01.08 4:43:41 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
 AG 01.01.08 4:43:41 PM  DATA
 AG 01.01.08 4:43:41 PM  354 Enter mail, end with . on a line by
 itself AG 01.01.08 4:45:46 PM  Error=10054 Session aborted!
 
 AG Adding the application to the exception list makes no difference.
 AG Anybody any idea?
 
 AG --
 AG Arno Garrels
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange e-mail problems Server 2003

2008-01-02 Thread retnyg
did you try telnetting manually to the smtp server, or use another
client ? maybe some antivirus stuff involved ?

AG Dod wrote:
 Hello Arno,
 
 I see in the log that there is 5 seconds delay between DATA and the
 10054 error. This may be interesting.

AG No, the delay is 2 minutes and 5 seconds.
AG One thing I can imagine is a problem with MTU Discovery,
AG since small packets (SMTP command/response) go thru,
AG may be the required ICMP packets are filtered?
AG Does someone know what has to be configured to ensure MTU Discovery
AG will not fail?

AG --
AG Arno Garrels
  

 
 During  this  delay  do you send data ? I say this because some server
 will  close cnx if no data transmitted fast enought and do not receive
 data for xx seconds, usually the timeout is between 1 or 3 minutes but
 I know a server that wait only 3 seconds (may be bad configuration).
 
 The  best  is  to ask client to manualy telnet port 25 into the server
 and  type  a  SMTP  sequence and wait 5 seconds betweent each line you
 type.
 
 Also may be there is some check-back cnx to the client's machine and
 if FW is ON then machine cannot be checked.
 
 regards.
 
 AG One of my customers reported problems sending mail with an
 TSmtpCli AG application when the Windows firewall is turned on.
 Strange is that AG sending mail data fails for some reason and the
 server drops the AG connection after ~2 minutes (of inactivity) even
 though port 25 AG is explicitely opened.
 
 AG First log is with firewall turned off, mail is sent successfully,
 AG second log with firewall turned on and port 25 explicitely opened:
 
 AG 01.01.08 2:22:47 PM  MAIL FROM:[EMAIL PROTECTED]
 AG 01.01.08 2:22:48 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
 AG 01.01.08 2:22:48 PM  RCPT TO:[EMAIL PROTECTED]
 AG 01.01.08 2:22:48 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
 AG 01.01.08 2:22:48 PM  DATA
 AG 01.01.08 2:22:48 PM  354 Enter mail, end with . on a line by
 itself AG 01.01.08 2:22:48 PM  .
 AG 01.01.08 2:22:48 PM  250 2.0.0 m01JMoVp009311 Message accepted
 for delivery AG 01.01.08 2:22:48 PM  QUIT
 AG 01.01.08 2:22:48 PM  221 2.0.0 ms-smtp-xyz.com closing connection
 
 
 AG 01.01.08 4:43:40 PM  MAIL FROM:[EMAIL PROTECTED]
 AG 01.01.08 4:43:41 PM  250 2.1.0 [EMAIL PROTECTED]... Sender ok
 AG 01.01.08 4:43:41 PM  RCPT TO:[EMAIL PROTECTED]
 AG 01.01.08 4:43:41 PM  250 2.1.5 [EMAIL PROTECTED]... Recipient ok
 AG 01.01.08 4:43:41 PM  DATA
 AG 01.01.08 4:43:41 PM  354 Enter mail, end with . on a line by
 itself AG 01.01.08 4:45:46 PM  Error=10054 Session aborted!
 
 AG Adding the application to the exception list makes no difference.
 AG Anybody any idea?
 
 AG --
 AG Arno Garrels



-- 
Mit freundlichen Grüßen
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread DZ-Jay

On May 4, 2007, at 10:02, Fastream Technologies wrote:

 I would not believe -before trying myself- this is what M$ called
 rewriting of TCP/IP stack!!

It may not be a code efficiency problem, it may be intentionally 
crippled to prevent you from using the client version for any 
high-performance communications, and force you to buy the server 
version.

*That* I would believe from Microsoft.

dZ.

-- 
DZ-Jay [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread Angus Robertson - Magenta Systems Ltd
 *Subject:* Re: [twsocket] Strange Vista winsock behavior--any way 
 to by-pass?
 *From:* DZ-Jay [EMAIL PROTECTED]
 It may not be a code efficiency problem, it may be intentionally 
 crippled to prevent you from using the client version for any 
 high-performance communications, and force you to buy the server 
 version.

Exactly, that's why the workstation OSs have a limit of 10 TCP/IP shares.
Unfortunately, Microsoft seems to have invalidated the patch to the
tcpip.sys that I used for a few years to raise the limit to 50. 

Windows 2007, aka Longhorn, the next server release, is currently on open
beta from the Microsoft web site.  I've tried to download it with Firefox
and MSIE, but the Microsoft 'shop' software always returns 'error'.   

http://www.microsoft.com/windowsserver/longhorn/audsel.mspx

http://msdn2.microsoft.com/en-gb/evalcenter/bb383571.aspx

Has anyone started testing ICS on Windows 2007?

Angus
 
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread Darin McGee
I just downloaded it - not too big - 1.8GB for the x86 version - 2.4GB
for the x64 version- No problems. You do have to order it on-line for
the free D/L.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Angus Robertson - Magenta Systems Ltd
Sent: Saturday, May 05, 2007 9:51 AM
To: twsocket@elists.org
Subject: Re: [twsocket] Strange Vista winsock behavior--any way to
by-pass?

 *Subject:* Re: [twsocket] Strange Vista winsock behavior--any way 
 to by-pass?
 *From:* DZ-Jay [EMAIL PROTECTED]
 It may not be a code efficiency problem, it may be intentionally 
 crippled to prevent you from using the client version for any 
 high-performance communications, and force you to buy the server 
 version.

Exactly, that's why the workstation OSs have a limit of 10 TCP/IP
shares.
Unfortunately, Microsoft seems to have invalidated the patch to the
tcpip.sys that I used for a few years to raise the limit to 50. 

Windows 2007, aka Longhorn, the next server release, is currently on
open
beta from the Microsoft web site.  I've tried to download it with
Firefox
and MSIE, but the Microsoft 'shop' software always returns 'error'.   

http://www.microsoft.com/windowsserver/longhorn/audsel.mspx

http://msdn2.microsoft.com/en-gb/evalcenter/bb383571.aspx

Has anyone started testing ICS on Windows 2007?

Angus
 
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread Fastream Technologies
Perhaps you guys can test the IE7 on Windows 2007 with my stress tester:

http://www.fastream.com/ics/WebStressTester.zip

Try with a small file and a large static file. Also try connection:
close and keep-alive. Very user friendly and hi-performance--does not
open 1 thread for each connection.

Best Regards,

SZ

On 5/5/07, Darin McGee [EMAIL PROTECTED] wrote:
 I just downloaded it - not too big - 1.8GB for the x86 version - 2.4GB
 for the x64 version- No problems. You do have to order it on-line for
 the free D/L.

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 On Behalf Of Angus Robertson - Magenta Systems Ltd
 Sent: Saturday, May 05, 2007 9:51 AM
 To: twsocket@elists.org
 Subject: Re: [twsocket] Strange Vista winsock behavior--any way to
 by-pass?

  *Subject:* Re: [twsocket] Strange Vista winsock behavior--any way
  to by-pass?
  *From:* DZ-Jay [EMAIL PROTECTED]
  It may not be a code efficiency problem, it may be intentionally
  crippled to prevent you from using the client version for any
  high-performance communications, and force you to buy the server
  version.

 Exactly, that's why the workstation OSs have a limit of 10 TCP/IP
 shares.
 Unfortunately, Microsoft seems to have invalidated the patch to the
 tcpip.sys that I used for a few years to raise the limit to 50.

 Windows 2007, aka Longhorn, the next server release, is currently on
 open
 beta from the Microsoft web site.  I've tried to download it with
 Firefox
 and MSIE, but the Microsoft 'shop' software always returns 'error'.

 http://www.microsoft.com/windowsserver/longhorn/audsel.mspx

 http://msdn2.microsoft.com/en-gb/evalcenter/bb383571.aspx

 Has anyone started testing ICS on Windows 2007?

 Angus

 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread Arno Garrels
Angus Robertson - Magenta Systems Ltd wrote:
 *Subject:* Re: [twsocket] Strange Vista winsock behavior--any way
 to by-pass?
 *From:* DZ-Jay [EMAIL PROTECTED]
 It may not be a code efficiency problem, it may be intentionally
 crippled to prevent you from using the client version for any
 high-performance communications, and force you to buy the server
 version.
 
 Exactly, that's why the workstation OSs have a limit of 10 TCP/IP
 shares. Unfortunately, Microsoft seems to have invalidated the patch
 to the tcpip.sys that I used for a few years to raise the limit to 50.

Nice tool that patches even latest versions of tcpip.sys 
(mine was MD5 checksum 1DBF125862891817F374F407626967F4, size 359.808 bytes):
http://xp-antispy.org/?lang=enoption=com_frontpageItemid=1

 
 Windows 2007, aka Longhorn, the next server release, is currently on
 open beta from the Microsoft web site.  I've tried to download it
 with Firefox and MSIE, but the Microsoft 'shop' software always
 returns 'error'. 
 
 http://www.microsoft.com/windowsserver/longhorn/audsel.mspx
 
 http://msdn2.microsoft.com/en-gb/evalcenter/bb383571.aspx
 
 Has anyone started testing ICS on Windows 2007?

Thanks, I'm currently downloading with DownThemAll, a nice plugin for
FireFox.

--
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

 
 Angus
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-05 Thread Angus Robertson - Magenta Systems Ltd
 http://xp-antispy.org/

Mine was from LvlLord, but looking in my folder it seems my latest Sophos
anti-virus has deleted it...  Hopefully Anti=Spy will last longer. 

 Windows 2007, a I'm currently downloading 

I wonder why thr shop dislike me and won't let me download it!

Angus
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-04 Thread Fastream Technologies
Yes that's what I guessed as well but if it's inherent to Vista then
Vista is not much suitable as server OS. I wonder if the issue is in
client side or server sockets? Unfortunately I sold my other desktop
and my laptop in in service so I cannot check against XP/2003.

Best Regards,

SZ

On 5/3/07, Arno Garrels [EMAIL PROTECTED] wrote:
 Fastream Technologies wrote:
  Hello,
 
  Recently I have upgraded my workstation to Vista Business 64-bit and
  face the following problem:
 
  - when run against IE7 or any other server, the ICS stress tester that
  I posted here before as well as Socrates, get into strange behavior:
 
  1) After 1-2 mins, the sockets begin to not being accepted. The server
  simply does not work for the stress tester client. It works for
  browsers.
 
  2) The socket establishment for IIS 7 in Connection: close mode is
  2000 connections/sec where it was 4-5000 connections/sec on IIS6 on
  XP-x64.
 
  Any explanation/solution for these?

 May be some Vista setting to avoid such attacks?
 Or may be Vista is just slower than XP?

 --
 Arno Garrels [TeamICS]
 http://www.overbyte.be/eng/overbyte/teamics.html

 
  WARM Regards from Turkey where it is already hot!
 
  SZ
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-04 Thread Darin McGee
That's way Vista is sold as a client OS and Microsoft sells separate
server software.  Also, read your XP and Vista licenses, they are not to
be used as servers.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Fastream Technologies
Sent: Friday, May 04, 2007 2:53 AM
To: ICS support mailing
Subject: Re: [twsocket] Strange Vista winsock behavior--any way to
by-pass?

Yes that's what I guessed as well but if it's inherent to Vista then
Vista is not much suitable as server OS. I wonder if the issue is in
client side or server sockets? Unfortunately I sold my other desktop
and my laptop in in service so I cannot check against XP/2003.

Best Regards,

SZ

On 5/3/07, Arno Garrels [EMAIL PROTECTED] wrote:
 Fastream Technologies wrote:
  Hello,
 
  Recently I have upgraded my workstation to Vista Business 64-bit and
  face the following problem:
 
  - when run against IE7 or any other server, the ICS stress tester
that
  I posted here before as well as Socrates, get into strange behavior:
 
  1) After 1-2 mins, the sockets begin to not being accepted. The
server
  simply does not work for the stress tester client. It works for
  browsers.
 
  2) The socket establishment for IIS 7 in Connection: close mode is
  2000 connections/sec where it was 4-5000 connections/sec on IIS6 on
  XP-x64.
 
  Any explanation/solution for these?

 May be some Vista setting to avoid such attacks?
 Or may be Vista is just slower than XP?

 --
 Arno Garrels [TeamICS]
 http://www.overbyte.be/eng/overbyte/teamics.html

 
  WARM Regards from Turkey where it is already hot!
 
  SZ
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-04 Thread Dave Baxter
From the limited exposure I've had to Vista (Home Basic) client use.
A Clean install on the same hardware (P4 2GHz, 512MB Ram, 80G drive,
nVidia graphics) it run's at about half the speed of XP(Home) in just
about all respects.  Whatever tweaks you do to it.

Where'd the Wow go?

Less than impressed (we re-installed XP as a result, did all the
updates, and the same machine really rocks again!)  Of course, the
reseller will not take it back as the box is opened, will hang on to it
till we can get something bigger better and much faster to load it on.

Dave B.


 -Original Message-
 From: Darin McGee [mailto:[EMAIL PROTECTED] 
 Sent: Friday, May 04, 2007 12:00 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange Vista winsock behavior--any 
 way to by-pass?
 
 That's way Vista is sold as a client OS and Microsoft sells 
 separate server software.  Also, read your XP and Vista 
 licenses, they are not to be used as servers.
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 On Behalf Of Fastream Technologies
 Sent: Friday, May 04, 2007 2:53 AM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange Vista winsock behavior--any 
 way to by-pass?
 
 Yes that's what I guessed as well but if it's inherent to 
 Vista then Vista is not much suitable as server OS. I wonder 
 if the issue is in client side or server sockets? 
 Unfortunately I sold my other desktop and my laptop in in 
 service so I cannot check against XP/2003.
 
 Best Regards,
 
 SZ
 
 On 5/3/07, Arno Garrels [EMAIL PROTECTED] wrote:
  Fastream Technologies wrote:
   Hello,
  
   Recently I have upgraded my workstation to Vista Business 
 64-bit and 
   face the following problem:
  
   - when run against IE7 or any other server, the ICS stress tester
 that
   I posted here before as well as Socrates, get into 
 strange behavior:
  
   1) After 1-2 mins, the sockets begin to not being accepted. The
 server
   simply does not work for the stress tester client. It works for 
   browsers.
  
   2) The socket establishment for IIS 7 in Connection: 
 close mode is 
   2000 connections/sec where it was 4-5000 connections/sec 
 on IIS6 on 
   XP-x64.
  
   Any explanation/solution for these?
 
  May be some Vista setting to avoid such attacks?
  Or may be Vista is just slower than XP?
 
  --
  Arno Garrels [TeamICS]
  http://www.overbyte.be/eng/overbyte/teamics.html
 
  
   WARM Regards from Turkey where it is already hot!
  
   SZ
  --
This mail has been scanned by Palmer Cook Computer Services Limited.  
www.palmercook.co.uk
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-04 Thread Fastream Technologies
I would not believe -before trying myself- this is what M$ called
rewriting of TCP/IP stack!!

:((

On 5/4/07, Dave Baxter [EMAIL PROTECTED] wrote:
 From the limited exposure I've had to Vista (Home Basic) client use.
 A Clean install on the same hardware (P4 2GHz, 512MB Ram, 80G drive,
 nVidia graphics) it run's at about half the speed of XP(Home) in just
 about all respects.  Whatever tweaks you do to it.

 Where'd the Wow go?

 Less than impressed (we re-installed XP as a result, did all the
 updates, and the same machine really rocks again!)  Of course, the
 reseller will not take it back as the box is opened, will hang on to it
 till we can get something bigger better and much faster to load it on.

 Dave B.


  -Original Message-
  From: Darin McGee [mailto:[EMAIL PROTECTED]
  Sent: Friday, May 04, 2007 12:00 PM
  To: ICS support mailing
  Subject: Re: [twsocket] Strange Vista winsock behavior--any
  way to by-pass?
 
  That's way Vista is sold as a client OS and Microsoft sells
  separate server software.  Also, read your XP and Vista
  licenses, they are not to be used as servers.
 
  -Original Message-
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
  On Behalf Of Fastream Technologies
  Sent: Friday, May 04, 2007 2:53 AM
  To: ICS support mailing
  Subject: Re: [twsocket] Strange Vista winsock behavior--any
  way to by-pass?
 
  Yes that's what I guessed as well but if it's inherent to
  Vista then Vista is not much suitable as server OS. I wonder
  if the issue is in client side or server sockets?
  Unfortunately I sold my other desktop and my laptop in in
  service so I cannot check against XP/2003.
 
  Best Regards,
 
  SZ
 
  On 5/3/07, Arno Garrels [EMAIL PROTECTED] wrote:
   Fastream Technologies wrote:
Hello,
   
Recently I have upgraded my workstation to Vista Business
  64-bit and
face the following problem:
   
- when run against IE7 or any other server, the ICS stress tester
  that
I posted here before as well as Socrates, get into
  strange behavior:
   
1) After 1-2 mins, the sockets begin to not being accepted. The
  server
simply does not work for the stress tester client. It works for
browsers.
   
2) The socket establishment for IIS 7 in Connection:
  close mode is
2000 connections/sec where it was 4-5000 connections/sec
  on IIS6 on
XP-x64.
   
Any explanation/solution for these?
  
   May be some Vista setting to avoid such attacks?
   Or may be Vista is just slower than XP?
  
   --
   Arno Garrels [TeamICS]
   http://www.overbyte.be/eng/overbyte/teamics.html
  
   
WARM Regards from Turkey where it is already hot!
   
SZ
   --
 This mail has been scanned by Palmer Cook Computer Services Limited.  
 www.palmercook.co.uk
 --
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange Vista winsock behavior--any way to by-pass?

2007-05-03 Thread Arno Garrels
Fastream Technologies wrote:
 Hello,
 
 Recently I have upgraded my workstation to Vista Business 64-bit and
 face the following problem:
 
 - when run against IE7 or any other server, the ICS stress tester that
 I posted here before as well as Socrates, get into strange behavior:
 
 1) After 1-2 mins, the sockets begin to not being accepted. The server
 simply does not work for the stress tester client. It works for
 browsers.
 
 2) The socket establishment for IIS 7 in Connection: close mode is
 2000 connections/sec where it was 4-5000 connections/sec on IIS6 on
 XP-x64.
 
 Any explanation/solution for these?

May be some Vista setting to avoid such attacks?
Or may be Vista is just slower than XP?

--
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html 

 
 WARM Regards from Turkey where it is already hot!
 
 SZ
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange service folder mapping problem for ICS web server

2006-12-06 Thread Arno Garrels
Fastream Technologies wrote:
 Hello,
 
 When I use the UNC name as \\server\sharedFolder it works in
 FindFirst but not z:\ where Z:\ is actually mapped to sharedfolder
 under the same admin account in Windows. This happens with Win2003,
 XP.

Drive mappings are not available in services by default, it may work if
the service runs as currently, interactively logged on user (not 100% sure).

---
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange HTTPServer problem on Load balancer

2005-12-30 Thread Fastream Technologies
I cannot capture local packets with Ethereal! Anyone know how to do it?

Also, it may be worng to say that ethereal changes behavior. I may be wrong.

Regards,

SZ

- Original Message - 
From: Francois PIETTE [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Friday, December 30, 2005 11:22 AM
Subject: Re: [twsocket] Starnge HTTPServer problem on Load balancer


 When I connect to Apache for a page full of frames and java applets,
 the browser gets into an infinite waiting state. When I do the same
 with Etherreal and/or socketspy, everything is fine.

 I can't understand the behavious is different when Ethereal is used:
 Ethereal doesn't change the content, it just peek the packets on the fly !

 Some of the objects on the page returns 304 some 404 and some simply 200.
 Any idea?

 There is probably some cookie to grab and send back. If you don't, you are
 redirected to the page where you should grab the cookie but as you don't,
 you are redirected again and again.

 --
 Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 http://www.overbyte.be


 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Fastream Technologies
Hi,

Is there a proxy setting on the second PC? That's what my problem was once.

Regards,

SZ

- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: twsocket@elists.org
Sent: Tuesday, December 06, 2005 3:31 PM
Subject: [twsocket] Strange


 Hi,

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional with 
 SP2
 installed. The server my application is connecting is on the same 100 Mbps
 LAN as the 2 PC's above. From the firs PC, after calling WSocket.Connect,
 the connection is established very fast and OnSessionConnected is called. 
 On
 the second PC, after calling Connect, nothing happens for about 30 
 seconds.
 The server the application is connecting does no receive any connection 
 for
 the time specified above. So, to resume, on the first PC the connection is
 established right after WSocket.Connect and on the second PC the 
 connection
 is established after an anoying delay.
 Does someone experience any similar situation? I have tried wsoTcpNoDelay 
 on
 both server and client. No results.
 Please help.

 / Ionut Muntean

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Marcello Vezzelli
Ionut Muntean wrote:

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional with SP2
 installed. The server my application is connecting is on the same 100 Mbps

verify firewall and internet connection sharing: try to set them disabled.
Reboot and try again.
Verify if the problem arises with windows telnet too.

-- 
Marcello Vezzelli
CTO
Software Development Department
E-Works s.r.l.
tel. +39 059 2929081
fax +39 059 2925035
Direzionale 70 - Via Giardini 456/c
41100 Modena - Italy

-
La presente comunicazione, che potrebbe contenere informazioni riservate e/o 
protette da segreto professionale, è indirizzata esclusivamente ai 
destinatari della medesima qui indicati. Le opinioni, le conclusioni e le 
altre informazioni qui contenute, che non siano relative alla nostra 
attività caratteristica, devono essere considerate come non inviate né 
avvalorate da noi. Tutti i pareri e le informazioni qui contenuti sono 
soggetti ai termini ed alle condizioni previsti dagli accordi che regolano 
il nostro rapporto con il cliente. Nel caso in cui abbiate ricevuto per 
errore la presente comunicazione, vogliate cortesemente darcene immediata 
notizia, rispondendo a questo stesso indirizzo di e-mail, e poi procedere 
alla cancellazione di questo messaggio dal Vostro sistema. E' strettamente 
proibito e potrebbe essere fonte di violazione di legge qualsiasi uso, 
comunicazione, copia o diffusione dei contenuti di questa comunicazione da 
parte di chi la abbia ricevuta per errore o in violazione degli scopi della 
presente.
-
This communication, that may contain confidential and/or legally privileged 
information, is intended solely for the use of the intended addressees. 
Opinions, conclusions and other information contained in this message, that 
do not relate to the official business of this firm, shall be considered as 
not given or endorsed by it. Every opinion or advice contained in this 
communication is subject to the terms and conditions provided by the 
agreement governing the engagement with such a client. If you have received 
this communication in error, please notify us immediately by responding to 
this email and then delete it from your system. Any use, disclosure, copying 
or distribution of the contents of this communication by a not-intended 
recipient or in violation of the purposes of this communication is strictly 
prohibited and may be unlawful.
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Florin Vancea
Do you use symbolic names for the target host?
What are your DNS settings on both machines?
Maybe the DNS on the second machine is having a hard time resolving the name
(i.e. a dead or not available DNS server specified first).

- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: twsocket@elists.org
Sent: Tuesday, December 06, 2005 3:31 PM
Subject: [twsocket] Strange


 Hi,

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional with
SP2
 installed. The server my application is connecting is on the same 100 Mbps
 LAN as the 2 PC's above. From the firs PC, after calling WSocket.Connect,
 the connection is established very fast and OnSessionConnected is called.
On
 the second PC, after calling Connect, nothing happens for about 30
seconds.
 The server the application is connecting does no receive any connection
for
 the time specified above. So, to resume, on the first PC the connection is
 established right after WSocket.Connect and on the second PC the
connection
 is established after an anoying delay.
 Does someone experience any similar situation? I have tried wsoTcpNoDelay
on
 both server and client. No results.
 Please help.

 / Ionut Muntean

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Francois Piette
 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional with SP2
 installed. The server my application is connecting is on the same 100 Mbps
 LAN as the 2 PC's above. From the firs PC, after calling WSocket.Connect,
 the connection is established very fast and OnSessionConnected is called. On
 the second PC, after calling Connect, nothing happens for about 30 seconds.
 The server the application is connecting does no receive any connection for
 the time specified above. So, to resume, on the first PC the connection is
 established right after WSocket.Connect and on the second PC the connection
 is established after an anoying delay.
 Does someone experience any similar situation? I have tried wsoTcpNoDelay on
 both server and client. No results.
 Please help.

I could be a DNS problem. Try connecting by specifying the IP address instead 
of hostname to be sure
it is not a DNS problem.
What is the ping time ? Try ping using the IP address and ping using the 
hostname.
Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port
If it is slow also, then defenitely there is a problem within the OS, I guess a 
DNS problem.

--
Contribute to the SSL Effort. Visit
http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware)
Author of MidWare (Multi-tier framework, freeware)
http://www.overbyte.be


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Ionut Muntean
Of course, the first thing I thought was that there is a DNS problem so I've
used numeric ip addresses in the Addr field. The result is the same. :(
Anyway, the both machines are using the same (local) DNS server. The ping
time between the server and the 2 PC's is under 0.3 ms...

10x for the quick response.

/ Ionut

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Florin Vancea
Sent: 6 decembrie 2005 05:19 PM
To: ICS support mailing
Subject: Re: [twsocket] Strange

Do you use symbolic names for the target host?
What are your DNS settings on both machines?
Maybe the DNS on the second machine is having a hard time resolving the name
(i.e. a dead or not available DNS server specified first).

- Original Message -
From: Ionut Muntean [EMAIL PROTECTED]
To: twsocket@elists.org
Sent: Tuesday, December 06, 2005 3:31 PM
Subject: [twsocket] Strange


 Hi,

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional with
SP2
 installed. The server my application is connecting is on the same 100 Mbps
 LAN as the 2 PC's above. From the firs PC, after calling WSocket.Connect,
 the connection is established very fast and OnSessionConnected is called.
On
 the second PC, after calling Connect, nothing happens for about 30
seconds.
 The server the application is connecting does no receive any connection
for
 the time specified above. So, to resume, on the first PC the connection is
 established right after WSocket.Connect and on the second PC the
connection
 is established after an anoying delay.
 Does someone experience any similar situation? I have tried wsoTcpNoDelay
on
 both server and client. No results.
 Please help.

 / Ionut Muntean

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Ionut Muntean
The telnet connection on the specified port on the server is working well.
:(

/ Ionut Muntean 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Francois Piette
Sent: 6 decembrie 2005 05:23 PM
To: ICS support mailing
Subject: Re: [twsocket] Strange

 I'm experiencing a strange behavior of WSocket.Connect - 
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my 
 applications and a laptop. Both of them are Windows XP Proffesional 
 with SP2 installed. The server my application is connecting is on the 
 same 100 Mbps LAN as the 2 PC's above. From the firs PC, after calling 
 WSocket.Connect, the connection is established very fast and 
 OnSessionConnected is called. On the second PC, after calling Connect,
nothing happens for about 30 seconds.
 The server the application is connecting does no receive any 
 connection for the time specified above. So, to resume, on the first 
 PC the connection is established right after WSocket.Connect and on 
 the second PC the connection is established after an anoying delay.
 Does someone experience any similar situation? I have tried 
 wsoTcpNoDelay on both server and client. No results.
 Please help.

I could be a DNS problem. Try connecting by specifying the IP address
instead of hostname to be sure it is not a DNS problem.
What is the ping time ? Try ping using the IP address and ping using the
hostname.
Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port If it is slow also, then
defenitely there is a problem within the OS, I guess a DNS problem.

--
Contribute to the SSL Effort. Visit
http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
Author of ICS (Internet Component Suite, freeware) Author of MidWare
(Multi-tier framework, freeware) http://www.overbyte.be


--
To unsubscribe or change your settings for TWSocket mailing list please goto
http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Florin Vancea
Save some time, pick the big gun :)

I mean: Start the packet monitor (you said it's a WXP-SP2) and see what's
happening first hand on each machine.

And please post back, as it looks interesting...

- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 5:49 PM
Subject: Re: [twsocket] Strange


 Of course, the first thing I thought was that there is a DNS problem so
I've
 used numeric ip addresses in the Addr field. The result is the same. :(
 Anyway, the both machines are using the same (local) DNS server. The ping
 time between the server and the 2 PC's is under 0.3 ms...

 10x for the quick response.

 / Ionut

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Florin Vancea
 Sent: 6 decembrie 2005 05:19 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 Do you use symbolic names for the target host?
 What are your DNS settings on both machines?
 Maybe the DNS on the second machine is having a hard time resolving the
name
 (i.e. a dead or not available DNS server specified first).

 - Original Message -
 From: Ionut Muntean [EMAIL PROTECTED]
 To: twsocket@elists.org
 Sent: Tuesday, December 06, 2005 3:31 PM
 Subject: [twsocket] Strange


  Hi,
 
  I'm experiencing a strange behavior of WSocket.Connect -
  WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
  applications and a laptop. Both of them are Windows XP Proffesional with
 SP2
  installed. The server my application is connecting is on the same 100
Mbps
  LAN as the 2 PC's above. From the firs PC, after calling
WSocket.Connect,
  the connection is established very fast and OnSessionConnected is
called.
 On
  the second PC, after calling Connect, nothing happens for about 30
 seconds.
  The server the application is connecting does no receive any connection
 for
  the time specified above. So, to resume, on the first PC the connection
is
  established right after WSocket.Connect and on the second PC the
 connection
  is established after an anoying delay.
  Does someone experience any similar situation? I have tried
wsoTcpNoDelay
 on
  both server and client. No results.
  Please help.
 
  / Ionut Muntean
 
  -- 
  To unsubscribe or change your settings for TWSocket mailing list
  please goto http://www.elists.org/mailman/listinfo/twsocket
  Visit our website at http://www.overbyte.be
 
 


 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Ionut Muntean
Excuse my ignorance, but please, is there a packet monitor in Window$ XP? I
am a Linux user, and now I am forced to develop an windows app. :(

/ Ionut Muntean 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Florin Vancea
Sent: 6 decembrie 2005 06:24 PM
To: ICS support mailing
Subject: Re: [twsocket] Strange

Save some time, pick the big gun :)

I mean: Start the packet monitor (you said it's a WXP-SP2) and see what's
happening first hand on each machine.

And please post back, as it looks interesting...

- Original Message -
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 5:49 PM
Subject: Re: [twsocket] Strange


 Of course, the first thing I thought was that there is a DNS problem so
I've
 used numeric ip addresses in the Addr field. The result is the same. :(
 Anyway, the both machines are using the same (local) DNS server. The ping
 time between the server and the 2 PC's is under 0.3 ms...

 10x for the quick response.

 / Ionut

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Florin Vancea
 Sent: 6 decembrie 2005 05:19 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 Do you use symbolic names for the target host?
 What are your DNS settings on both machines?
 Maybe the DNS on the second machine is having a hard time resolving the
name
 (i.e. a dead or not available DNS server specified first).

 - Original Message -
 From: Ionut Muntean [EMAIL PROTECTED]
 To: twsocket@elists.org
 Sent: Tuesday, December 06, 2005 3:31 PM
 Subject: [twsocket] Strange


  Hi,
 
  I'm experiencing a strange behavior of WSocket.Connect -
  WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
  applications and a laptop. Both of them are Windows XP Proffesional with
 SP2
  installed. The server my application is connecting is on the same 100
Mbps
  LAN as the 2 PC's above. From the firs PC, after calling
WSocket.Connect,
  the connection is established very fast and OnSessionConnected is
called.
 On
  the second PC, after calling Connect, nothing happens for about 30
 seconds.
  The server the application is connecting does no receive any connection
 for
  the time specified above. So, to resume, on the first PC the connection
is
  established right after WSocket.Connect and on the second PC the
 connection
  is established after an anoying delay.
  Does someone experience any similar situation? I have tried
wsoTcpNoDelay
 on
  both server and client. No results.
  Please help.
 
  / Ionut Muntean
 
  -- 
  To unsubscribe or change your settings for TWSocket mailing list
  please goto http://www.elists.org/mailman/listinfo/twsocket
  Visit our website at http://www.overbyte.be
 
 


 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Francois PIETTE
 Excuse my ignorance, but please, is there a packet monitor in Window$ XP? 
 I
 am a Linux user, and now I am forced to develop an windows app. :(

Use Ethereal. Link on the link page at my website. It's a free tool.
I'm using LanWatch which is a commercial tool. Search Google...

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Francois PIETTE
 The telnet connection on the specified port on the server is working well.
 :(

OK, so let's try with one of the ICS provided demos so that we are sure you 
have not a bug in your own code. Use TnClient for example.

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be



- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 4:51 PM
Subject: Re: [twsocket] Strange


 The telnet connection on the specified port on the server is working well.
 :(

 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Francois Piette
 Sent: 6 decembrie 2005 05:23 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional
 with SP2 installed. The server my application is connecting is on the
 same 100 Mbps LAN as the 2 PC's above. From the firs PC, after calling
 WSocket.Connect, the connection is established very fast and
 OnSessionConnected is called. On the second PC, after calling Connect,
 nothing happens for about 30 seconds.
 The server the application is connecting does no receive any
 connection for the time specified above. So, to resume, on the first
 PC the connection is established right after WSocket.Connect and on
 the second PC the connection is established after an anoying delay.
 Does someone experience any similar situation? I have tried
 wsoTcpNoDelay on both server and client. No results.
 Please help.

 I could be a DNS problem. Try connecting by specifying the IP address
 instead of hostname to be sure it is not a DNS problem.
 What is the ping time ? Try ping using the IP address and ping using the
 hostname.
 Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port If it is slow also, then
 defenitely there is a problem within the OS, I guess a DNS problem.

 --
 Contribute to the SSL Effort. Visit
 http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 Author of ICS (Internet Component Suite, freeware) Author of MidWare
 (Multi-tier framework, freeware) http://www.overbyte.be


 --
 To unsubscribe or change your settings for TWSocket mailing list please 
 goto
 http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Fastream Technologies
Why don't you first try socketspy from usermade page? It should compile on 
Kylix, right Francois?

Regards,

SubZ

- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 6:30 PM
Subject: Re: [twsocket] Strange


 Excuse my ignorance, but please, is there a packet monitor in Window$ XP? 
 I
 am a Linux user, and now I am forced to develop an windows app. :(

 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Florin Vancea
 Sent: 6 decembrie 2005 06:24 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 Save some time, pick the big gun :)

 I mean: Start the packet monitor (you said it's a WXP-SP2) and see what's
 happening first hand on each machine.

 And please post back, as it looks interesting...

 - Original Message -
 From: Ionut Muntean [EMAIL PROTECTED]
 To: 'ICS support mailing' twsocket@elists.org
 Sent: Tuesday, December 06, 2005 5:49 PM
 Subject: Re: [twsocket] Strange


 Of course, the first thing I thought was that there is a DNS problem so
 I've
 used numeric ip addresses in the Addr field. The result is the same. :(
 Anyway, the both machines are using the same (local) DNS server. The ping
 time between the server and the 2 PC's is under 0.3 ms...

 10x for the quick response.

 / Ionut

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Florin Vancea
 Sent: 6 decembrie 2005 05:19 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 Do you use symbolic names for the target host?
 What are your DNS settings on both machines?
 Maybe the DNS on the second machine is having a hard time resolving the
 name
 (i.e. a dead or not available DNS server specified first).

 - Original Message -
 From: Ionut Muntean [EMAIL PROTECTED]
 To: twsocket@elists.org
 Sent: Tuesday, December 06, 2005 3:31 PM
 Subject: [twsocket] Strange


  Hi,
 
  I'm experiencing a strange behavior of WSocket.Connect -
  WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
  applications and a laptop. Both of them are Windows XP Proffesional 
  with
 SP2
  installed. The server my application is connecting is on the same 100
 Mbps
  LAN as the 2 PC's above. From the firs PC, after calling
 WSocket.Connect,
  the connection is established very fast and OnSessionConnected is
 called.
 On
  the second PC, after calling Connect, nothing happens for about 30
 seconds.
  The server the application is connecting does no receive any connection
 for
  the time specified above. So, to resume, on the first PC the connection
 is
  established right after WSocket.Connect and on the second PC the
 connection
  is established after an anoying delay.
  Does someone experience any similar situation? I have tried
 wsoTcpNoDelay
 on
  both server and client. No results.
  Please help.
 
  / Ionut Muntean
 
  -- 
  To unsubscribe or change your settings for TWSocket mailing list
  please goto http://www.elists.org/mailman/listinfo/twsocket
  Visit our website at http://www.overbyte.be
 
 


 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be




 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Ionut Muntean
TnClient is behaving the same strange way. TnClient displays: Connecting to
xxx.xxx.xxx.xxx and then Connected but the welcome banner of the server
is displayed with 20-30 secs delay. On the other machine, the welcome banner
is displayed right after Connected.

My gues is it can be an OS bug, on the specific hardware platform (ethernet
NIC, etc.).

I've downloaded a packet sniffer, and 3 packets are captured when the
connection is initialized: one from the client to the server, one from the
server to the client and again, one from the client, and then the data
transfer is delayed.

The server is build around ucspi-tcp from http://cr.yp.to, on linux. On
short, the tcpserver program is listening on a specified port and when a
connection is established they launch an external program, rewriting
input/output filedescriptors of that program on the incoming socket. It
works very well, as it is also used for the (*nix users wellknowed) qmail.

10x again,
/ Ionut Muntean

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Francois PIETTE
Sent: 6 decembrie 2005 07:56 PM
To: ICS support mailing
Subject: Re: [twsocket] Strange

 The telnet connection on the specified port on the server is working well.
 :(

OK, so let's try with one of the ICS provided demos so that we are sure you
have not a bug in your own code. Use TnClient for example.

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be



- Original Message -
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 4:51 PM
Subject: Re: [twsocket] Strange


 The telnet connection on the specified port on the server is working well.
 :(

 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Francois Piette
 Sent: 6 decembrie 2005 05:23 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional
 with SP2 installed. The server my application is connecting is on the
 same 100 Mbps LAN as the 2 PC's above. From the firs PC, after calling
 WSocket.Connect, the connection is established very fast and
 OnSessionConnected is called. On the second PC, after calling Connect,
 nothing happens for about 30 seconds.
 The server the application is connecting does no receive any
 connection for the time specified above. So, to resume, on the first
 PC the connection is established right after WSocket.Connect and on
 the second PC the connection is established after an anoying delay.
 Does someone experience any similar situation? I have tried
 wsoTcpNoDelay on both server and client. No results.
 Please help.

 I could be a DNS problem. Try connecting by specifying the IP address
 instead of hostname to be sure it is not a DNS problem.
 What is the ping time ? Try ping using the IP address and ping using the
 hostname.
 Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port If it is slow also, then
 defenitely there is a problem within the OS, I guess a DNS problem.

 --
 Contribute to the SSL Effort. Visit
 http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 Author of ICS (Internet Component Suite, freeware) Author of MidWare
 (Multi-tier framework, freeware) http://www.overbyte.be


 --
 To unsubscribe or change your settings for TWSocket mailing list please 
 goto
 http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Ionut Muntean
The problem is solved. :) The server is trying to get ident information from
the client machine when a connection is established, and since there is no
response from the client machine ... it waits until timeout.

Thanks to all,

/ Ionut Muntean



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Francois PIETTE
Sent: 6 decembrie 2005 07:56 PM
To: ICS support mailing
Subject: Re: [twsocket] Strange

 The telnet connection on the specified port on the server is working well.
 :(

OK, so let's try with one of the ICS provided demos so that we are sure you
have not a bug in your own code. Use TnClient for example.

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be



- Original Message -
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 4:51 PM
Subject: Re: [twsocket] Strange


 The telnet connection on the specified port on the server is working well.
 :(

 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Francois Piette
 Sent: 6 decembrie 2005 05:23 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional
 with SP2 installed. The server my application is connecting is on the
 same 100 Mbps LAN as the 2 PC's above. From the firs PC, after calling
 WSocket.Connect, the connection is established very fast and
 OnSessionConnected is called. On the second PC, after calling Connect,
 nothing happens for about 30 seconds.
 The server the application is connecting does no receive any
 connection for the time specified above. So, to resume, on the first
 PC the connection is established right after WSocket.Connect and on
 the second PC the connection is established after an anoying delay.
 Does someone experience any similar situation? I have tried
 wsoTcpNoDelay on both server and client. No results.
 Please help.

 I could be a DNS problem. Try connecting by specifying the IP address
 instead of hostname to be sure it is not a DNS problem.
 What is the ping time ? Try ping using the IP address and ping using the
 hostname.
 Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port If it is slow also, then
 defenitely there is a problem within the OS, I guess a DNS problem.

 --
 Contribute to the SSL Effort. Visit
 http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 Author of ICS (Internet Component Suite, freeware) Author of MidWare
 (Multi-tier framework, freeware) http://www.overbyte.be


 --
 To unsubscribe or change your settings for TWSocket mailing list please 
 goto
 http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange

2005-12-06 Thread Francois PIETTE
 TnClient is behaving the same strange way. TnClient displays: Connecting 
 to
 xxx.xxx.xxx.xxx and then Connected but the welcome banner of the server
 is displayed with 20-30 secs delay. On the other machine, the welcome 
 banner
 is displayed right after Connected.

It is possible that the server has problem sending data packets to the 
client. I have no idea why because connection initialization packets are 
transmitted without delay.

To help you withthe sniffer:
A TCP session is established with a 3 control packets (without mention ARP 
packets to resolve IP/MAC addresses):
Client send SYN
Server respond with SYN-ACK
client respond with ACK
then data and ack packets are sent/received by either party.

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be



- Original Message - 
From: Ionut Muntean [EMAIL PROTECTED]
To: 'ICS support mailing' twsocket@elists.org
Sent: Tuesday, December 06, 2005 7:51 PM
Subject: Re: [twsocket] Strange


 TnClient is behaving the same strange way. TnClient displays: Connecting 
 to
 xxx.xxx.xxx.xxx and then Connected but the welcome banner of the server
 is displayed with 20-30 secs delay. On the other machine, the welcome 
 banner
 is displayed right after Connected.

 My gues is it can be an OS bug, on the specific hardware platform 
 (ethernet
 NIC, etc.).

 I've downloaded a packet sniffer, and 3 packets are captured when the
 connection is initialized: one from the client to the server, one from the
 server to the client and again, one from the client, and then the data
 transfer is delayed.

 The server is build around ucspi-tcp from http://cr.yp.to, on linux. On
 short, the tcpserver program is listening on a specified port and when a
 connection is established they launch an external program, rewriting
 input/output filedescriptors of that program on the incoming socket. It
 works very well, as it is also used for the (*nix users wellknowed) 
 qmail.

 10x again,
 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Francois PIETTE
 Sent: 6 decembrie 2005 07:56 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 The telnet connection on the specified port on the server is working 
 well.
 :(

 OK, so let's try with one of the ICS provided demos so that we are sure 
 you
 have not a bug in your own code. Use TnClient for example.

 --
 Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 http://www.overbyte.be



 - Original Message -
 From: Ionut Muntean [EMAIL PROTECTED]
 To: 'ICS support mailing' twsocket@elists.org
 Sent: Tuesday, December 06, 2005 4:51 PM
 Subject: Re: [twsocket] Strange


 The telnet connection on the specified port on the server is working 
 well.
 :(

 / Ionut Muntean

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
 Behalf Of Francois Piette
 Sent: 6 decembrie 2005 05:23 PM
 To: ICS support mailing
 Subject: Re: [twsocket] Strange

 I'm experiencing a strange behavior of WSocket.Connect -
 WSocket.OnSessionConnected. I have 2 PC. One on which I develop my
 applications and a laptop. Both of them are Windows XP Proffesional
 with SP2 installed. The server my application is connecting is on the
 same 100 Mbps LAN as the 2 PC's above. From the firs PC, after calling
 WSocket.Connect, the connection is established very fast and
 OnSessionConnected is called. On the second PC, after calling Connect,
 nothing happens for about 30 seconds.
 The server the application is connecting does no receive any
 connection for the time specified above. So, to resume, on the first
 PC the connection is established right after WSocket.Connect and on
 the second PC the connection is established after an anoying delay.
 Does someone experience any similar situation? I have tried
 wsoTcpNoDelay on both server and client. No results.
 Please help.

 I could be a DNS problem. Try connecting by specifying the IP address
 instead of hostname to be sure it is not a DNS problem.
 What is the ping time ? Try ping using the IP address and ping using the
 hostname.
 Try using the command line telnet to connect to your server:
telnet your_server_name your_server_port If it is slow also, then
 defenitely there is a problem within the OS, I guess a DNS problem.

 --
 Contribute to the SSL Effort. Visit
 http://www.overbyte.be/eng/ssl.html
 --
 [EMAIL PROTECTED]
 Author of ICS (Internet Component Suite, freeware) Author of MidWare
 (Multi-tier framework, freeware) http://www.overbyte.be


 --
 To unsubscribe or change your settings for TWSocket mailing list please
 goto
 http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be

Re: [twsocket] Strange behavior or not?

2005-11-10 Thread Larini
Thanks Wilfred, but I need to send the next message only after I receive the
ok from server.



Wilfried Mestdagh wrote:

Hello Larini,

I'm getting unstable times, from 70 ms to 3 seconds.


This can happen. It is depending the traffic on the network. If very
heavy on a large network it _can_ take a while.

while gWait do
begin
application.ProcessMessages;
sleep(1);
end;


This is not needed, you only waste CPU here. Use ClientDataAvailable to
send the next, not for flagging a loop !

---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz

Wednesday, November 9, 2005, 21:26, Larini wrote:

Hi, here is my simple app, one client and one server. The mission: send a
message from client to server and wait for replay.
I'm getting unstable times, from 70 ms to 3 seconds. My question is: this
is
normal? What kind of client-server configuration I must have to get more
stable results (like 200 ms most of time)?



Client:
procedure TForm2.clientSessionConnected(Sender: TObject; ErrCode: Word);
var a:Integer;
begin
for a:=0 to 500 do
begin
LastTick:=Gettickcount;
Client.SendLine('* msg to
server *');
gWait:=true;
while gWait do
begin
application.ProcessMessages;
sleep(1);
end;
end;
end;


procedure TForm2.clientDataAvailable(Sender: TObject; ErrCode: Word);
var s:String;
begin
if ErrCode0 then
exit;
s:=Client.ReceiveStr;
memo1.lines.add(Inttostr(Gettickcount-LastTick)+' - '+ trim(s));
gWait:=false;
end;


Server:
procedure TForm1.CliSocketDataAvailable(Sender: TObject; ErrCode: Word);
var s:String;
begin
if ErrCode0 then
exit;
s:=(sender as TWSocket).ReceiveStr;
memo1.Lines.Add(trim(s));
(sender as TWSocket).SendLine(trim(s));
end;




This mail was sent by
Webmail 2.5

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] Strange behavior or not?

2005-11-09 Thread Wilfried Mestdagh
Hello Larini,

 I'm getting unstable times, from 70 ms to 3 seconds.

This can happen. It is depending the traffic on the network. If very
heavy on a large network it _can_ take a while.

 while gWait do
 begin
 application.ProcessMessages;
 sleep(1);
 end;

This is not needed, you only waste CPU here. Use ClientDataAvailable to
send the next, not for flagging a loop !

---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz

Wednesday, November 9, 2005, 21:26, Larini wrote:

 Hi, here is my simple app, one client and one server. The mission: send a
 message from client to server and wait for replay.
 I'm getting unstable times, from 70 ms to 3 seconds. My question is: this is
 normal? What kind of client-server configuration I must have to get more
 stable results (like 200 ms most of time)?


 Client:
 procedure TForm2.clientSessionConnected(Sender: TObject; ErrCode: Word);
 var a:Integer;
 begin
 for a:=0 to 500 do
 begin
 LastTick:=Gettickcount;
 Client.SendLine('* msg to
 server *');
 gWait:=true;
 while gWait do
 begin
 application.ProcessMessages;
 sleep(1);
 end;
 end;
 end;

 procedure TForm2.clientDataAvailable(Sender: TObject; ErrCode: Word);
 var s:String;
 begin
 if ErrCode0 then
 exit;
 s:=Client.ReceiveStr;
 memo1.lines.add(Inttostr(Gettickcount-LastTick)+' - '+ trim(s));
 gWait:=false;
 end;

 Server:
 procedure TForm1.CliSocketDataAvailable(Sender: TObject; ErrCode: Word);
 var s:String;
 begin
 if ErrCode0 then
 exit;
 s:=(sender as TWSocket).ReceiveStr;
 memo1.Lines.Add(trim(s));
 (sender as TWSocket).SendLine(trim(s));
 end;


 Result:
 109 - * msg to server
 *
 78 - * msg to server
 *
 47 - * msg to server
 *
 78 - * msg to server
 *
 4343 - * msg to server
 *
 63 - * msg to server
 *
 47 - * msg to server
 *
 63 - * msg to server
 *
 78 - * msg to server
 *
 62 - * msg to server
 *
 219 - * msg to server
 *
 78 - * msg to server
 *
 63 - * msg to server
 *
 47 - * msg to server
 *
 63 - * msg to server
 *
 296 - * msg to server
 *
 78 - * msg to server
 *
 78 - * msg to server
 *
 781 - * msg to server
 *
 329 - * msg to server
 *
 188 - * msg to server
 *
 157 - * msg to server
 *
 141 - * msg to server
 *
 907 - * msg to server
 *
 235 - * msg to server
 *


 
 This mail was sent by
 Webmail 2.5


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be