Error Number: 0x800CCC19
L Beck
Pavilion, 5 months old. Lately it's been almost impossible to send email.
I get the error:
A time-out occurred while communicating with the server. Subject 'testing',
Account: 'syringa.net', Server: 'syringa.net', Protocol: SMTP, Port: 25,
Secure(SSL): NoError Number: 0x800CCC19
I've deleted and recreated the email account - no joy. I've deleted the
Outbox folder to let O.E. recreate it - no joy.
I know there's nothing wrong at the server end because I help manage that
server and it doesn't happen on computers running something other than
Windows XP. The only thing I've not tried is restoring to a previous time -
this started about 2 weeks ago.
Any other suggestions?
Frank Saunders, MS-MVP IE/OE
--
Frank Saunders, MS-MVP IE/OE
http:www.fjsmjs.com
"L Beck" <lmac2...@syringa.net> wrote in message
news:uorLwxQF...@TK2MSFTNGP09.phx.gbl...
L Beck
Anything else will cause "unable to locate server" errors.
If I just leave my mail open and let it keep trying to send it, eventually
it will go. But if other customers were having this same problem our phones
would be ringing off the hook.
Any other ideas?
"Frank Saunders, MS-MVP IE/OE" <franks...@mvps.org> wrote in message
news:uusAkTWF...@tk2msftngp13.phx.gbl...
Jim Carlock
not being delivered to my machine.
Provide us with a TRACERT to the system. Perhaps that'll help determine
where the packets are taking their most time. I'm getting some extra time
occuring while going through the final portions of sprintlink.net but it
doesn't look too bad, so I'm thinking there's either a time-out occuring
because packets are slow leaving your system or slow coming back through to
you:
8 20 ms 31 ms 20 ms sl-bb23-atl-10-2.sprintlink.net
[144.232.8.209]
9 40 ms 20 ms 30 ms sl-bb21-atl-8-0.sprintlink.net
[144.232.12.25]
10 50 ms 40 ms 50 ms sl-bb21-chi-11-0.sprintlink.net
[144.232.18.33]
11 40 ms 50 ms 50 ms sl-bb22-chi-15-0.sprintlink.net
[144.232.26.97]
12 80 ms 90 ms 90 ms sl-bb20-sea-8-2.sprintlink.net
[144.232.18.49]
13 81 ms 90 ms 90 ms sl-gw10-sea-0-0.sprintlink.net
[144.232.6.110]
14 100 ms 100 ms 100 ms sl-triad1-4-0.sprintlink.net
[144.224.113.122]
15 110 ms 100 ms 100 ms 65.171.136.10
Trace complete.
--
Jim Carlock
http://www.microcosmotalk.com
Post your messages to the newsgroup for all to witness!
"L Beck" <lmac2...@syringa.net> wrote in message
news:uorLwxQF...@TK2MSFTNGP09.phx.gbl...
L Beck
"Jim Carlock" <anonymous@localhost> wrote in message
news:u8yOHrWF...@TK2MSFTNGP10.phx.gbl...
Jim Carlock
C:\>tracert syringa.net
You should be able to use the mouse and hightlight the information displayed
there, press the Enter key (to send the info to the clip board), then paste
the information into a reply.
L Beck
Tracing route to syringa.net [65.171.136.10]
1 1 ms <1 ms <1 ms 192.168.0.1
2 * 126 ms 15 ms 65.171.136.10
"Jim Carlock" <anonymous@localhost> wrote in message
news:u8yOHrWF...@TK2MSFTNGP10.phx.gbl...
Jim Carlock
>
>Tracing route to syringa.net [65.171.136.10]
>1 1 ms <1 ms <1 ms 192.168.0.1
>2 * 126 ms 15 ms 65.171.136.10
It looks like something is dropping packets for you on the way out to
syringa.net.
It's only taking one hop but the times are not consistent and the *
indicates that there was a timeout. It looks like there might be something
that's not quite right on your end of the network. I'm trying to think of
what might be causing that, but I'm coming up at the short end of the stick.
Something isn't quite right on the server. If the server is a local machine
that you've set up, there should be no packet loss at all. The times should
all indicate <1ms unless you've got a huge network with a bunch of routers,
but I don't see any routers. I'm going to assume that the 192.168.0.1 is
perhaps a DSL modem *(?) and that your connecting to your server (ip
65.171.136.10) in some manner that I can't see.
How exactly is your network set up?
Jim Carlock
Have you tried to connect without the Secure Password Authentication?
L Beck
computers (192.168.0.1). The mail server (65.171.136.10) is the ISP located
across town.
It was about 2 weeks ago that this problem first developed. We've had this
wireless internet for about 6 weeks. However, we've only had the router for
about 3 weeks. Could there be something in connection with the router that
could be causing this? It happens on both computers that go through that
router.
"Jim Carlock" <anonymous@localhost> wrote in message
news:OXrEjXaF...@TK2MSFTNGP09.phx.gbl...
Jim Carlock
126ms, the third seem to have made the connection 15 ms in a very
appropriate manner.
Do you have a server that is set up as a domain?
--
Jim Carlock
http://www.microcosmotalk.com
Post your messages to the newsgroup for all to witness!
"L Beck" <lmac2...@syringa.net> wrote in message
news:uUTbpcbF...@TK2MSFTNGP10.phx.gbl...
Jim Carlock
through it, it replies with a 571 Not a relay.
I'm thinking this message means that you either need a password login to get
through it or you have to be part of the domain that it's working on.
Which in turn might mean that all that it needs is to have the Relay portion
of it turned on, that is if your home PCs are not part of the domain, ie
they run on their own domain or are part of a workgroup.
Just taking a wild stab here.
Jim Carlock
C:\>telnet 65.171.136.10 25
HELP
HELO syringa.net
mail from:webm...@syringa.net
rcpt to:webm...@syringa.net
DATA<press the enter key>
SUBJECT:test test test
This is a test. Testing.
1 2 3 Testing.
Testing 1 2 3 Testing.
<enter to create a blank line>
.
<enter to create a blank line>
<NOTE: In the rcpt to: you can enter your own email address--
You'll get a response of 571 Not a relay or 250 OK>
I just went through that and used the rcpt to:parameters above and the mail
parameters above and the server look like it took the message and sent it.
You might want to have someone check the webm...@syringa.net email account
for email.
The <blank line><period><blank line> is the end of message indicator. You'll
get a lot of 250 OK prompts and if a line contains an error you'll get a 500
syntax error (or something similar).
Let me know how that goes for you.
Jim Carlock
the response I gave about the domain is applicable.
I was able to connect and it looked like the messages were sent.
I think it was initially seeing that I was not part of the domain, and the
relay would make sense in that the server won't send email from another
domain and it was determining that I was in another domain by default.
The SMTP operations seem to be working from this end. So that leaves how
your connecting as the problem.
whoever
> If you received two emails on the webmaster account from me, I'm not
> so sure the response I gave about the domain is applicable.
>
> I was able to connect and it looked like the messages were sent.
>
> I think it was initially seeing that I was not part of the domain, and
> the relay would make sense in that the server won't send email from
> another domain and it was determining that I was in another domain by
> default.
Domains have nothing to do with it - any machine in the world can be part
of any TCP/IP "domain", if the owner of the name server wants them to be.
But any well configured SMTP server can tell an "inside" machine from an
"outside" machine, and "outside" machines are only allowed send mail to
addresses that the SMTP server hosts (this can be one or thousands of
domains). "inside" machines can send mail to any address (the SMTP server
will act as a relay for inside machines, not for outside machines).
"Inside" machines are usually recognized by their IP address (which is not
the same as their domain) though sometimes a server will be configured to
accept usernames and passwords from users on "outside" machines so that
they can use that server as a "relay".
> The SMTP operations seem to be working from this end. So that leaves
> how your connecting as the problem.
As the original poster never received an error message from the server ("A
time-out occurred while communicating with the server") that was always
likely to be the case, assuming the server was actually listening on port
25. As the OP said that other people use the server without problems, it is
safe to assume that it does indeed listen on port 25.
whoever
> I can connect to the syringa.net server, but when I go to try to send
> email through it, it replies with a 571 Not a relay.
Which is the way any well configured mail server should respon, unless you
try to send a message to a syringa.net address.
> I'm thinking this message means that you either need a password login
> to get through it or you have to be part of the domain that it's
> working on.
>
> Which in turn might mean that all that it needs is to have the Relay
> portion of it turned on, that is if your home PCs are not part of the
> domain, ie they run on their own domain or are part of a workgroup.
I think your grasp of mail relaying, and domains (two entirely separate
topics) is a bit weak. Neither of them have anything to do with dropped
packets. Given that the original traceroute originated on a 192.168 IP
address, it is likely that the mail server recognized it as a local device,
and would relay for that device, but as the original poster never got as
far as a relaying error message, that's an irrelevancy.
whoever
> I have a wireless (microwave) internet connection through a router
> with 2 computers (192.168.0.1). The mail server (65.171.136.10) is
> the ISP located across town.
Note that syringa.net resolves to 2 addresses, 65.171.136.10 and
65.171.136.5. You should ping both addresses to see if there is a
difference.
(Try ping -n 100 65.171.136.10 to get a better picture of the
steadiness of the link).
> It was about 2 weeks ago that this problem first developed. We've had
> this wireless internet for about 6 weeks. However, we've only had the
> router for about 3 weeks. Could there be something in connection with
> the router that could be causing this? It happens on both computers
> that go through that router.
You're using "non-routable" addresses, 192.168.*. Do you have a NAT device
in there that's providing address translation, or are you expecting the
router to do that for you?
(If you don't know what NAT is, then the router probably is the problem).
Robert Aldwinckle
> steadiness of the link).
Since a router is involved perhaps the ping test
described here would also be appropriate?
<title>KB314825 - How to Troubleshoot Black Hole Router Issues</title>
---
"whoever" <nos...@nospam.invalid> wrote in message
news:Xns9375D32AC51...@207.46.248.16...