| Initializing Windows Sockets hangs 1 min. |
 Posted by
Rik Bartolini
on Thursday, October 26, 2006 at 4:20:29 AM (EST)
I don't remember when the problem appears for the first time.... maybe in the upgrade before the last one (that is before 2004.0.06.1017).
So, e.g., now I got:
9.26.58 SMTP: Internet address read - total of 3 addresses (aliases) for 1 user
9.26.58 SMTP: Initializing Windows Sockets...
9.28.20 SMTP Initializing SMTP service...
.
.
.
9.28.22 Checking mailbox folders is complete.
Every time I start the software, it takes more the 1':20" to be ready. In this time Internet is locked. If I exclude the program from autostart (is not a service) don't have that Internet lock, so is surely that initialization that freeze the sockets.
Any idea to solve this daily delay?
Best regards, Rik
|
 Posted by
Robert Smith
on Thursday, October 26, 2006 at 10:03:52 AM (EST)
Hmm..mine doesn't act this way. Shut down Lan Suite and do:
netstat -an
..and see if you have some ports open like 25, etc. It sounds to me like maybe you do.. Might be Antivirus or something conflicting.
|
Posted by
Rik Bartolini
on Thursday, October 26, 2006 at 10:46:28 AM (EST)
The ports Lansuite uses are:
21, 25, 53.
Without Lansuite are closed.
I have problem only when the computer starts (or maybe only at the first launch of Lan Suite). After that, if I close and reopen LanSuite the winsock initializing takes only 3 seconds.
I don't use antivirus on SMTP. I've also tried with Firewall (Outpost) closed.
If you have any other idea let me know.
Rik.
|
Posted by
Rik Bartolini
on Friday, October 27, 2006 at 3:33:50 AM (EST)
Status: The problem is on Windows start. If I launch Lan Suite, for the first time, after 1 minute is all ok.
So, some operations at start are the cause of the delay. Maybe VMWare, or Winconnect, or Firewall or them combined.
|
Posted by
Fritz Schlechter
on Friday, October 27, 2006 at 6:29:17 AM (EST)
I have a similiar problem, only Lansuite 2004 chew's up my CPU usage, it will run between 96% - 99%. This causing my system, WINserver 2003 to become slow and unstable. What's wrong, as it's fine when 602 is off. And was fine when my internet connection was running from a router.
|
|
