Search  
You are here:  Forums    
Latest Posts Minimize
RE: Multiple copies being sent + smtp 451 by gyroscopes on 12-03-2008 11:23 PM
RE: connection limit? by RemyV on 12-03-2008 9:28 PM
connection limit? by NateDawg on 12-03-2008 7:38 PM
RE: Multiple copies being sent + smtp 451 by gyroscopes on 12-02-2008 12:00 AM
RE: vbs script for deleting users with MLSRVX.DLL by SteveT on 12-01-2008 11:04 PM
RE: Export server and users configuration by SteveT on 12-01-2008 11:00 PM
Multiple copies being sent + smtp 451 by gyroscopes on 12-01-2008 10:02 PM
Export server and users configuration by gcvoiron on 12-01-2008 8:46 AM
RE: vbs script for deleting users with MLSRVX.DLL by krommetje on 11-30-2008 3:02 PM
I can send, but can't receive by amanda on 11-29-2008 9:26 PM

Top 10 Links Minimize

ArGoStuff User to User Support Forums Minimize
Forums > General Discussion Forums > Error Code Discussion and DNS Issues
Subject: error winsock
Prev Next
You are not authorized to post a reply.

Author Messages
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-14-2007 5:34 PM  
What does this error mean, winsock error when communicating with ......
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-14-2007 9:11 PM  

Dan,

It depends on which error it indicates.   Check out this document and see if it answers your question:

Error Code Reference
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-15-2007 6:42 AM  
it is a winsock 10060 connection timed out..... I get this alot from all kinds of different domains??? so all my mails are bouncing.
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-15-2007 8:31 AM  
Dan,

Start with turning off the MX Cache. Delete the mxcache.cds. Run Maintenance.

See if that clears it up.
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-15-2007 11:20 AM  
yes I turned MX cache ON on the new server, maybe that is the cause.
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-15-2007 2:28 PM  
Dan,

Monitor the situation and keep up posted on the status.
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-16-2007 3:29 AM  

I have run the maintenancen now and removed MX cache... I get these bounce messages

 

15-04-2007 17:27:46 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 17:28:07 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 17:28:29 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 17:28:50 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 17:29:11 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 17:59:32 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 17:59:53 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 18:00:14 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 18:00:35 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 18:00:56 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 18:31:18 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 18:31:39 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 18:32:00 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 18:32:21 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 18:32:42 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 19:03:04 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 19:03:25 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 19:03:46 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 19:04:07 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 19:04:28 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 19:34:50 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 19:35:11 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 19:35:32 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 19:35:53 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 19:36:14 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 20:06:35 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 20:06:57 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 20:07:18 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 20:07:39 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 20:08:00 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 20:38:22 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 20:38:43 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 20:39:04 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 20:39:25 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 20:39:46 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 21:10:07 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 21:10:28 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 21:10:49 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 21:11:10 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 21:11:32 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 21:41:53 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 21:42:14 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 21:42:35 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out

15-04-2007 21:42:57 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 21:43:18 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 22:13:40 - Winsock error when communicating with exchanger mx04.stofanet.dk: 212.10.10.14: �] Connection timed out

15-04-2007 22:14:01 - Winsock error when communicating with exchanger mx05.stofanet.dk: 212.10.10.25: �] Connection timed out

15-04-2007 22:14:22 - Winsock error when communicating with exchanger mx01.stofanet.dk: 212.10.10.11: �] Connection timed out

15-04-2007 22:14:43 - Winsock error when communicating with exchanger mx02.stofanet.dk: 212.10.10.12: �] Connection timed out

15-04-2007 22:15:04 - Winsock error when communicating with exchanger mx03.stofanet.dk: 212.10.10.13: �] Connection timed out
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-16-2007 3:30 AM  
As you see its on 5 different mailservers, so I really need to have this problem solved sooooonn .-)
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-16-2007 4:54 AM  

Dan,

You can relax.. I ran DNS Report against the target server:

http://www.dnsreport.com/tools/dnsreport.ch?domain=stofanet.dk

Mail FAIL Connect to mail servers ERROR: I could not complete a connection to one or more of your mailservers:
ERROR: mx01.stofanet.dk Greeting indicates server is down: 421 mx01.stofanet.dk: Too much load; please try again later .
mx01.stofanet.dk: The mailserver terminated the connection before the transaction was complete (state 2). This is not RFC compliant, and therefore either due to an error, or it may be the result of a non-RFC-compliant mailserver or non-RFC-compliant anti-spam program.
ERROR: mx05.stofanet.dk Greeting indicates server is down: 421 mx05.stofanet.dk: Too much load; please try again later .
mx05.stofanet.dk: The mailserver terminated the connection before the transaction was complete (state 2). This is not RFC compliant, and therefore either due to an error, or it may be the result of a non-RFC-compliant mailserver or non-RFC-compliant anti-spam program.

As you can see, it's not your server this time, its the receiving server.
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-16-2007 4:54 AM  
I just found the error....
It was caused by me binding the server to ip 192.168.1.1 ????

I needed this bind to make sure the mailserver only picks up mails from my spam filter tunnel... why the heck does bind to ip not work in Argo??
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-16-2007 4:56 AM  
Is that target domain one of yours?

I don't use the Bind. I have eWall on port 25 and Argo on port 2525. Port 2525 is not accessible outside my firewall.
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-16-2007 5:03 AM  
Steve
It happend to 90 % of the outgoing mails to all kinds of domains including Gmail and so on :-(

Regarding bind to IP, I used the local ip 192.168.1.1....

The setup is like this

WAN IP ->
SMTP Tunnel filter takes ingoing ip and forwards to a new ip (set to 192.168.1.1) ->
Argo mailserver (should only listen to 192.168.1.1 or else the SMTP filter could be bypased if ARgo also listens to the WAN ip
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-16-2007 5:10 AM  
Can Spam Tunnel be configured to forward to a different Port? That would remove the need to bind. Did this config work on your system before the mishap?

It happend to 90 % of the outgoing mails to all kinds of domains including Gmail and so on :-(


Funny, I did my check from here on that domain and got the error. Would that not eliminate your server from the picture?

Have you tried Ping & Tracert to see if there is some bottleneck on the network/internet?
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
Dan

Posts: 345
Online: User is Offline
ArGoNuke Lt. Commander
ArGoNuke Lt. Commander
04-16-2007 5:22 AM  
yes it did happen before as well (I just forgot about it)

The spamfilter can forward to another port, but it is not a feasible solution, as outgoing emails will then go out through the filter and mess up the statistics etc.

And yes the test you mad eleminated my server, but thats only one domain (that might have been down) what about all the other domains that also caused winsock 10060...

Any way it is solved now, but without the bind, I just can not figure out why I can not bind the server to one specific address..
Any way what is the difference between bind IP and home IP addresses?
SteveT
Forum Administrator

Posts: 2583
Online: User is Offline
ArGoNuke Admiral
ArGoNuke Admiral
04-17-2007 1:38 AM  
Any way what is the difference between bind IP and home IP addresses?

Honestly, I don't know...
Top Cat Computing BOINC Team StatsRegards,
Steve Topilnycky
Top Cat Computing
http://www.topcatcomputing.com
You are not authorized to post a reply.
Forums > General Discussion Forums > Error Code Discussion and DNS Issues > error winsock


ActiveForums 3.7

Donations Minimize

Find our site useful? Make a donation to show your support

Donate

logo_ccMC.giflogo_ccVisa.giflogo_ccDiscover.giflogo_ccAmex.gif

ArGoStuff Supporters

 

News from ArGoSoft Minimize
1 2 3 4 5 6

Mail Server Pro v1.8.9.6
  • Improved Export to .NET function - sometimes email messages were not getting exported, because the database of email messages was not up to date. Now each folder gets rebuilt before the export function;
12/2/2008 11:19:02 PM
Email Address Validator

We have discontinued our email address validation service, and launched new web site:

http://www.emailaddressvalidator.com

It provides the web service interface to validate lists of email addresses. We hope that our service will help to reduce unwanted traffic on Internet, ensuring that mail is sent only to valid and legitimate addresses.

Sign up now, and get 150 free validations!

11/25/2008 10:13:02 AM
Mail Server v1.0.5.8

Mail Server

  • Mailbags now have an option to accept mail only when specified server is down - will help to fight with spam which attempt to deliver mail bypassing the main server;
  • When delivering mail, if main exchanger returns 4xx reply (temporary problem), the server will not try other exchangers, will retry later the main exchanger;
  • Server options moved from registry to a XML file. 64 bit versions of Vista and 2008 server appear to be having access rights problems to the Windows registry, and the change will make our server more compatible with 64 bit versions;
  • Added an option to specify the number of lines on the log screen, when using the user interface. Was causing memory problems if left running for long time;
  • Fixed couple of problems, which were showing when SQL server was set up to use case sensitive SQL statements;
  • Made changes in the remoting interface to allow logging in using aliases;

Web Interface

  • Made changes to allow logging in using aliases;
  • When viewing folders, web interface now displays the name of logged in user;
11/12/2008 2:31:31 PM
FTP Server v1.0.1.6
  • Server settings have been moved from registry to the XML file, which will be located in the common application data directory. 64 bit versions of Windows were having trouble writing into the registry; similar change is coming to the mail server;
  • If used, XML files (Users.XML, Groups.XML and ServerOptions.XML) will also be moved to the common application data directory;
11/8/2008 11:41:29 PM
FTP Server v1.0.1.5
  • When performing active data transfers on systems with multiple IP addresses, data connections were using first available IP address, rather than one on which the control connection was active. It was causing confusion with firewalls and routers;
11/2/2008 9:39:24 PM

1 2 3 4 5 6

DNSSTUFF.COM 


Home:ArGoStuff:Forums:Articles:Cyber Security Tips:FAQ:Downloads:Links
Copyright 2006-2008 by ArGoStuff Terms Of Use Privacy Statement