The Problem is Some RDC user accounts will allow Outlook to send and receive others do not.
Users who connect remotely have access to Outlook installed on the server.
New user accounts copied from a known working account do not acquire a working email account. The mail server is off site maintained by a third party. The standard network users have no problems retrieving emails. it is only some of the remote users. The mail server can be pinged and traced(ert)
reported error (0x80042108) : 'Outlook is unable to connect to your incoming (POP3) e-mail server. Using the IP of the server or the DNS name makes no difference. Turning the Antivirus software off makes no difference. OExpress gives The connection to the server has failed. Account: email account, Server: 'mail.clientname.com', Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 10061, Error Number: 0x800CCC0E. It all fairly rapid no wait for the error. Recreating the profile doesn't work either. Logging in into the webfront end confirms the account details are correct. I suspect it may be a GRP or security issue.. the profiles are set to owner=username. I am going bald mad and insane over this. The firewall is a ICOP but the normal users do not have email problems only some of the RDC users. So what the is fix? what to check next?
I also tried logging on locally with a problem account and guess what! no send and receive got a can't find profile error etc etc which make me even more sure about a profile problem, delete the profile and re create it? Any way of comparing a good working profile with a duff one?
And
netstat -an dumped it to a text file and behold and lo not a mention of port 25 or 110 and then the crunch did the same on a working profile and up guessed it no port 25 or 110 either.
As far as I have thought this one through It definitely has some thing to do with the profile which in some way stops the messaging sub system form talking to the TCP/IP stack. Reading through and I do mean READING a lot of it the messaging subsystem both SMTP and POP3 call ports and random ports beyond 25 and 110 that and some of the routines and sub routines that get called along the way, and I/you thought it was 'ere s a message, you got anything for me?'. The corrupt profiles, turning the AV off etc as refered to in the 'Troubleshooting error messages that you receive when you try to send and receive e-mail in Outlook and Outlook Express' would only apply if it was across the platfom and effecting the way the standard network users as well
Responses to Outlook and OE can't send and receive see below answers in bold!
* You are not connected to the Internet or a network, or your mail server is temporarily unavailable. NO cos alot of people can are using email
* Your account settings are incorrect. No cos I can log on to the webfront end
* Your user profile in Outlook is damaged. No cos if I delete it or create a new one it wont work
* An e-mail item on your POP3 server is damaged. See 2 and other people can do it
* The configuration of your AV software is incorrect. AV is common on the server to all accounts which are also some working
* Outlook Express was removed from the computer or the installation is damaged. Common install of software it work on some not on others
* The configuration of your personal firewall software is incorrect. No cos other people can email
No easy fix there. Hard thinking says it has to be the profile or a corruption within the profile. It as if the email client can't talk won't talk to the application layer in the TCPiP stack? You can't get a telnet connection from the remote desktop connection failed on both ports (remember you can ping it) Q's what does the email client send on and receive on ok 25 and 110 on the mail server....but what is the other end.