[quote user="Janos"]
5. Connect failes, 2."
[/quote]
If this is *really* what it says (allowing for the "failes" typo), then there's something very wrong with your system. The "5" tells me that the function that is failing is the Windows Sockets "connect" function, and the "2" is the error return from that function. Now, "2" is not a valid error return that I can find anywhere in the Windows Sockets reference, so something is messed up in your system, at the network layer level.
Anticipating what's likely to happen next, I have a couple of pre-emptive comments:
- It really doesn't matter if "no other application on the system is having any problems" or "Outlook doesn't have this error". No two pieces of software interact with the operating system in the same way, and the fact that one application encounters an error that another does not is merely a reflection of that difference.
- This is a Windows error. I can tell you that with absolute certainty. The function that is failing is a Windows function, and there are four lines of code between the point of failure and the time it gets reported. Either there is a configuration or software error in the Windows TCP/IP stack, or it is being passed parameters that it can't handle.
My best suggestion to you is to make sure that all the parameters are correct (hostname doesn't contain typos, port is correct and so on), and if they are, try fiddling with your Windows internet settings until you find a combination that works.
Cheers!
-- David --
[quote user="Janos"]<p>5. Connect failes, 2."</p><p>[/quote]
If this is *really* what it says (allowing for the "failes" typo), then there's something very wrong with your system. The "5" tells me that the function that is failing is the Windows Sockets "connect" function, and the "2" is the error return from that function. Now, "2" is not a valid error return that I can find anywhere in the Windows Sockets reference, so something is messed up in your system, at the network layer level.
Anticipating what's likely to happen next, I have a couple of pre-emptive comments:
</p><ol><li>It really doesn't matter if "no other application on the system is having any problems" or "Outlook doesn't have this error". No two pieces of software interact with the operating system in the same way, and the fact that one application encounters an error that another does not is merely a reflection of that difference.
</li><li>This is a Windows error. I can tell you that with absolute certainty. The function that is failing is a Windows function, and there are four lines of code between the point of failure and the time it gets reported. Either there is a configuration or software error in the Windows TCP/IP stack, or it is being passed parameters that it can't handle.
</li></ol>My best suggestion to you is to make sure that all the parameters are correct (hostname doesn't contain typos, port is correct and so on), and if they are, try fiddling with your Windows internet settings until you find a combination that works.
Cheers!
-- David --