Hello Wilfried!
I've downloaded the Your zip file (if you have more test files further on,
you can send them directly to me if it is easier for you).
Here are the results from the Swedish jury :-)
Best Regards
Henrik
On a computer where the component error is not showing:
Hello Henrik,
So it hangs in the TWSocket.DNSLookup, and OnDNSLookupDone is never
fired. You could try also by filling in the IP address of the smtp
server instead of the host name. Probably it will not hang anymore.
But as DZ mentioned, this is pure winsock call. So it is really winsock
that
Hi again Wilfried and thank You for Your endurance!
I'm sorry to say that using the IP address doesn't do the trick. A
difference is that no log entry is made at all the second time connecting
before the application hangs.
Since I really appreciate Your effort Wilfried I reinstalled the TCP
Hi again Wilfried!
The other computer where the example application hangs also has an Intel
Dual Core CPU and Win XP.
(According to Arno he had tested the example procedure we have been talking
about on a computer with Intel Dual Core and XP without any problems. I
don't know if he really got the
One thing that troubles me is that smtp-components from other vendors
works
fine also on the computers where ICS gets into trouble.
What is ICS doing that none of the other smtp components or applications
are not?
Dynamically load/unload WinSock when needed ?
Contribute to the SSL Effort.
Hi,
apparently I haven't enabled SSL for data transfers, only for the
initial connection and FTP commands. Some servers refuse data transfer,
saying that SSL is required, although an SSL connection has been set
up successfully.
Where/how do I enable secure transfers for data? I am using
Hi Francois!
Yes, perhaps You're right - It could be an error in the Winsock load/unload
of ICS.
Best Regards
Henrik
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För
Francois Piette
Skickat: den 18 december 2006 16:58
Till: ICS support mailing
Ämne: Re:
Hello Henrik,
It could be an error in the Winsock load/unload of ICS.
Or a windows bug for the dynamically load / unload. Or a winsock
bug because of the dual cpu. Or some combination.
The latter is easy to test. Put in boot.ini:
/NUMPROC=1
or
/ONECPU
and reboot.
---
Rgds, Wilfried [TeamICS]
Henrik wrote:
(According to Arno he had tested the example procedure we have been
talking
about on a computer with Intel Dual Core and XP without any problems.
Correct.
since he continued to talk about external issues... :-)
Correct, since we cannot be sure that you tried everything
you
