• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Outlook 2002 Won't send Emails

T
#1
I have a desktop and a laptop computer, both with Outlook 2002 with identical

configurations for the email accounts. A few days ago, the laptop just

stopped sending emails. It will still receive but not send through any

account where the outgoing server has "smtp" in it. Other email accounts will

still send email.

The error message that I get when I try to send a test msg suggests that I

verify the E-Mail Address field - which is correct. Absolutely nothing was

changed to the computer from when it was working to when it stopped working.

The other computer with the identical configuration continues to work

normally and can still sends emails via Outlook. The error code when I try to

send an email is 0x800CCC0F.

I have tried everything that I can think of, including un-installing and

re-installing.

Any suggestion on how to fix the problem?
 
L

Leonid S. Knyshov // SBS Expert

#2
On 2/26/2010 3:36 PM, Tomj wrote:
> I have a desktop and a laptop computer, both with Outlook 2002 with identical
> configurations for the email accounts. A few days ago, the laptop just
> stopped sending emails. It will still receive but not send through any
> account where the outgoing server has "smtp" in it. Other email accounts will
> still send email.

> The error message that I get when I try to send a test msg suggests that I
> verify the E-Mail Address field - which is correct. Absolutely nothing was
> changed to the computer from when it was working to when it stopped working.
> The other computer with the identical configuration continues to work
> normally and can still sends emails via Outlook. The error code when I try to
> send an email is 0x800CCC0F.

> I have tried everything that I can think of, including un-installing and
> re-installing.

> Any suggestion on how to fix the problem?


I suspect it's an ISP issue. It can also be a number of other things.

Work with your ISP to verify that the outbound SMTP settings are correct

for your network.

Is the other computer on the same network?

Quick test:

1. Check what is the smtp server name for the problematic account

2. Open a command prompt (start -> run -> cmd -> ok)

3. Type "ping SMTP_SERVER_NAME_TEXT" where the text is identical to your

Outook entry

4. Type "telnet SMTP_SERVER_NAME_TEXT 25" where the text is identical to

your Outlook entry

If you get a mail server prompt (220 blah blah blah ESMTP), the SMTP

server is likely to be configured correctly.

If not, work with your ISP to correct the outbound SMTP settings.

Let us know either way.

Leonid S. Knyshov

 
T
#3
Thanks. It pinged okay, but the telnet connection did not open either on the

computer where I have the problem or on the computer where Outlook works fine.

Yes, they are on the same network, sitting side by side. To remove any doubt

as to whether or not this affected the situation, I plugged them into the

same router.

"Leonid S. Knyshov // SBS Expert" wrote:


> On 2/26/2010 3:36 PM, Tomj wrote:
> > I have a desktop and a laptop computer, both with Outlook 2002 with identical
> > configurations for the email accounts. A few days ago, the laptop just
> > stopped sending emails. It will still receive but not send through any
> > account where the outgoing server has "smtp" in it. Other email accounts will
> > still send email.
> > The error message that I get when I try to send a test msg suggests that I
> > verify the E-Mail Address field - which is correct. Absolutely nothing was
> > changed to the computer from when it was working to when it stopped working.
> > The other computer with the identical configuration continues to work
> > normally and can still sends emails via Outlook. The error code when I try to
> > send an email is 0x800CCC0F.
> > I have tried everything that I can think of, including un-installing and
> > re-installing.
> > Any suggestion on how to fix the problem?

> I suspect it's an ISP issue. It can also be a number of other things.

> Work with your ISP to verify that the outbound SMTP settings are correct
> for your network.

> Is the other computer on the same network?

> Quick test:
> 1. Check what is the smtp server name for the problematic account
> 2. Open a command prompt (start -> run -> cmd -> ok)
> 3. Type "ping SMTP_SERVER_NAME_TEXT" where the text is identical to your
> Outook entry
> 4. Type "telnet SMTP_SERVER_NAME_TEXT 25" where the text is identical to
> your Outlook entry

> If you get a mail server prompt (220 blah blah blah ESMTP), the SMTP
> server is likely to be configured correctly.

> If not, work with your ISP to correct the outbound SMTP settings.

> Let us know either way.
> > Leonid S. Knyshov
>

>

>

> >

>

> .
>
 
L

Leonid S. Knyshov // SBS Expert

#4
On 2/27/2010 8:18 AM, Tomj wrote:
> Thanks. It pinged okay, but the telnet connection did not open either on the
> computer where I have the problem or on the computer where Outlook works fine.

> Yes, they are on the same network, sitting side by side. To remove any doubt
> as to whether or not this affected the situation, I plugged them into the
> same router.
>


Curious.

You did include the "25" at the end of the telnet string, right? That's

the check to see if your ISP is ready to accept your mail.

One test could be to add the Gmail account if you have one to Outlook.

It requires specific configuration and generally works where other

things fail.

http://mail.google.com/support/bin/search.py?ctx=en:searchbox&query=outlook

If Gmail configuration succeeds, then we don't have a problem with

Outlook and the issue is at the network level. Possibly wrong

credentials or the authentication box is not checked in account properties.

Leonid S. Knyshov

 
T
#5
I did forget the 25. When I added that the telnet test worked. The Gmail

configuration does not work on that computer either.

"Leonid S. Knyshov // SBS Expert" wrote:


> On 2/27/2010 8:18 AM, Tomj wrote:
> > Thanks. It pinged okay, but the telnet connection did not open either on the
> > computer where I have the problem or on the computer where Outlook works fine.
> > Yes, they are on the same network, sitting side by side. To remove any doubt
> > as to whether or not this affected the situation, I plugged them into the
> > same router.
> >

> Curious.

> You did include the "25" at the end of the telnet string, right? That's
> the check to see if your ISP is ready to accept your mail.

> One test could be to add the Gmail account if you have one to Outlook.
> It requires specific configuration and generally works where other
> things fail.
> http://mail.google.com/support/bin/search.py?ctx=en:searchbox&query=outlook

> If Gmail configuration succeeds, then we don't have a problem with
> Outlook and the issue is at the network level. Possibly wrong
> credentials or the authentication box is not checked in account properties.
> > Leonid S. Knyshov
>

>

>

> >

>

> .
>
 
L

Leonid S. Knyshov // SBS Expert

#6
On 2/27/2010 10:14 AM, Tomj wrote:
> I did forget the 25. When I added that the telnet test worked. The Gmail
> configuration does not work on that computer either.
>


Very strange. Just to confirm, does the port 25 test work from both

computers?

Try creating another Outlook profile from the Mail applet in your

control panel.

Leonid S. Knyshov

 
G

Gordon

#7
"Leonid S. Knyshov // SBS Expert"

<LeonidSKnyshovSBSExpert> wrote in message

news:#lnNJy9tKHA.6140@TK2MSFTNGP05.phx.gbl...
> On 2/27/2010 10:14 AM, Tomj wrote:
> > I did forget the 25. When I added that the telnet test worked. The Gmail
> > configuration does not work on that computer either.
> >

> Very strange. Just to confirm, does the port 25 test work from both
> computers?

> Try creating another Outlook profile from the Mail applet in your control
> panel.


And why would creating a new mail profile cure the fact that GMail doesn't

use port 25?

Is this your "fix" for all Outlook problems? Cos it sure seems to be.
 
L

Leonid S. Knyshov // SBS Expert

#8
On 2/27/2010 10:54 AM, Gordon wrote:

> "Leonid S. Knyshov // SBS Expert"
> <LeonidSKnyshovSBSExpert> wrote in message
> news:#lnNJy9tKHA.6140@TK2MSFTNGP05.phx.gbl...
> > On 2/27/2010 10:14 AM, Tomj wrote:
> >> I did forget the 25. When I added that the telnet test worked. The Gmail
> >> configuration does not work on that computer either.
> >>

> > Very strange. Just to confirm, does the port 25 test work from both
> > computers?
>

>> Try creating another Outlook profile from the Mail applet in your
> > control panel.


> And why would creating a new mail profile cure the fact that GMail
> doesn't use port 25?
> Is this your "fix" for all Outlook problems? Cos it sure seems to be.


I am eliminating possibilities of Outlook client misconfiguration.

Whenever I troubleshoot an Outlook connectivity issue, that is my

reliable test that bypasses whatever other issues might be present. I

can rely on Gmail SMTP server being available without any interference

from the ISP or resident malware and an account can be created for free.

I usually deal with Exchange servers where none of this matters, but the

Gmail test is helpful when working with remote users who are not yet on

the Exchange platform.

Leonid S. Knyshov

 
T
#9
Strangely, no the telnet test did not work in the computer that can send

mail. I received back a connect error 10060.

I did try a new profile back before I did the re-install, but I will try it

again and see. I have to go out for a while, so I will try that when I come

back.

BTW, thanks for the time that you are spending in helping out trying to

resolve this issue.

"Leonid S. Knyshov // SBS Expert" wrote:


> On 2/27/2010 10:14 AM, Tomj wrote:
> > I did forget the 25. When I added that the telnet test worked. The Gmail
> > configuration does not work on that computer either.
> >

> Very strange. Just to confirm, does the port 25 test work from both
> computers?

> Try creating another Outlook profile from the Mail applet in your
> control panel.
> > Leonid S. Knyshov
>

>

>

> >

>

> .
>
 
L

Leonid S. Knyshov // SBS Expert

#10
On 2/27/2010 11:28 AM, Tomj wrote:
> Strangely, no the telnet test did not work in the computer that can send
> mail. I received back a connect error 10060.

> I did try a new profile back before I did the re-install, but I will try it
> again and see. I have to go out for a while, so I will try that when I come
> back.

> BTW, thanks for the time that you are spending in helping out trying to
> resolve this issue.
>


Send me an e-mail through my website.

It would take me 10 minutes to troubleshoot this interactively instead

of all this guess work.

Leonid S. Knyshov

 
T
#11
I don't know how to explain this - the problem has existed all week - I has

tried everything to fix it as I mentioned before. Yesterday I was out for a

good part of the day so I was not able to do anything after our last

discussion. I get back to the computer today, start up Outlook, and it

resolved the problem itself and sent the test email that I have had sitting

in the Outbox for the last few days.

Microsoft works in mysterious ways.

Again, I very much appreciate all your time and effort in assisting me on

this problem.

"Leonid S. Knyshov // SBS Expert" wrote:


> On 2/27/2010 10:54 AM, Gordon wrote:
> > "Leonid S. Knyshov // SBS Expert"
> > <LeonidSKnyshovSBSExpert> wrote in message
> > news:#lnNJy9tKHA.6140@TK2MSFTNGP05.phx.gbl...
> >> On 2/27/2010 10:14 AM, Tomj wrote:
> >>> I did forget the 25. When I added that the telnet test worked. The Gmail
> >>> configuration does not work on that computer either.
> >>
> >> Very strange. Just to confirm, does the port 25 test work from both
> >> computers?
> >
> >> Try creating another Outlook profile from the Mail applet in your
> >> control panel.

> > And why would creating a new mail profile cure the fact that GMail
> > doesn't use port 25?
> > Is this your "fix" for all Outlook problems? Cos it sure seems to be.


> I am eliminating possibilities of Outlook client misconfiguration.
> Whenever I troubleshoot an Outlook connectivity issue, that is my
> reliable test that bypasses whatever other issues might be present. I
> can rely on Gmail SMTP server being available without any interference
> from the ISP or resident malware and an account can be created for free.

> I usually deal with Exchange servers where none of this matters, but the
> Gmail test is helpful when working with remote users who are not yet on
> the Exchange platform.
> > Leonid S. Knyshov
>

>

>

> >

>

> .
>
 
L

Leonid S. Knyshov // SBS Expert

#12
On 2/28/2010 12:57 PM, Tomj wrote:
> I don't know how to explain this - the problem has existed all week - I has
> tried everything to fix it as I mentioned before. Yesterday I was out for a
> good part of the day so I was not able to do anything after our last
> discussion. I get back to the computer today, start up Outlook, and it
> resolved the problem itself and sent the test email that I have had sitting
> in the Outbox for the last few days.

> Microsoft works in mysterious ways.

> Again, I very much appreciate all your time and effort in assisting me on
> this problem.
>


Happy to see a problem get resolved. :)

Leonid S. Knyshov

 

Similar threads