Re: Error 0x800ccc0e?

YES it was HOSTS that I was thinking of, please see my notes and results
below of the TraceRT, Telnet and Ping tests


BELOW IS MY EMAIL TO TECH SUPPORT

I've a very wierd problem.We currently have several computers sharing a DSL
connection, all of them have access to the internet and four of the five can
access their email. I have already checked all of the obvious problems so
please don't start there. PLEASE have a look at my ping and tracert TEST. I
am able to do a TRACERT test but am not able to ping the server.

We use execulink as our DSL provider but Xcelco has the rest of our DSL
connections and email addresses. THis is because the rest of the company has
Xcelco DSL connections but for some reason with this building we had to go
with execulink. Therefore our typical setup is.

POP3 = mail.xcelco.on.ca
SMTP = execulink.com

The one computer having the problem can send emails but can not recieve
them.



--------------------------------------------------------------------------------

C:\>ping mail.xcelco.on.ca

Pinging mail.xcelco.on.ca [209.167.188.10] with 32 bytes of data:

Reply from 209.167.188.10: bytes=32 time=45ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52

Ping statistics for 209.167.188.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 45ms, Average = 42ms


--------------------------------------------------------------------------------

C:\>tracert mail.xcelco.on.ca

Tracing route to mail.xcelco.on.ca [209.167.188.10]
over a maximum of 30 hops:

1 9 ms 33 ms 36 ms 10.8.0.1
2 10 ms 10 ms 10 ms h.core1.ip.execulink.net [10.1.8.2]
3 11 ms 11 ms 70 ms a.core2.ip.execulink.net [66.203.176.58]
4 12 ms 12 ms 35 ms h66-59-189-217.gtconnect.net [66.59.189.217]
5 15 ms 14 ms 15 ms GE4-1-40.WANA-TOROON.IP.GROUPTELECOM.NET
[66.59.191.73]
6 25 ms 76 ms 28 ms POS9-0.PEERA-CHCGIL.IP.GROUPTELECOM.NET
[66.59.91.82]
7 27 ms 25 ms 25 ms p4-2-0-0.r02.chcgil06.us.bb.verio.net
[129.250.0.97]
8 * 29 ms 26 ms ge-5-2-0.r01.chcgil06.us.bb.verio.net
[129.250..114]
9 30 ms 31 ms 29 ms POS5-2.BR3.CHI2.ALTER.NET [204.255.174.233]
10 31 ms 31 ms 67 ms 0.so-5-2-0.XL1.CHI2.ALTER.NET [152.63.68.2]
11 55 ms 56 ms 56 ms 0.so-1-1-0.XL1.TOR2.ALTER.NET [152.63.3.97]
12 55 ms 79 ms 82 ms POS1-0.XR1.TOR2.ALTER.NET [152.63.2.110]
13 147 ms 172 ms 215 ms 195.ATM9-0-0.GW1.LON1.ALTER.NET
[152.63.131.17]

14 39 ms 39 ms 39 ms xelco5-gw.customer.alter.net [204.92.65.98]
15 44 ms 46 ms 66 ms fors-sarn_ptp-gw.xcelco.on.ca
[216.94.238.218]
16 44 ms 41 ms 40 ms mail.xcelco.on.ca [209.167.188.10]

Trace complete.



--------------------------------------------------------------------------------
C:\>ping mail.xcelco.on.ca

Pinging mail.xcelco.on.ca [209.167.188.10] with 32 bytes of data:

Reply from 209.167.188.10: bytes=32 time=45ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52
Reply from 209.167.188.10: bytes=32 time=42ms TTL=52

Ping statistics for 209.167.188.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 45ms, Average = 42ms


--------------------------------------------------------------------------------

C:\>tracert mail.xcelco.on.ca

Tracing route to mail.xcelco.on.ca [209.167.188.10]
over a maximum of 30 hops:

1 9 ms 33 ms 36 ms 10.8.0.1
2 10 ms 10 ms 10 ms h.core1.ip.execulink.net [10.1.8.2]
3 11 ms 11 ms 70 ms a.core2.ip.execulink.net [66.203.176.58]
4 12 ms 12 ms 35 ms h66-59-189-217.gtconnect.net [66.59.189.217]
5 15 ms 14 ms 15 ms GE4-1-40.WANA-TOROON.IP.GROUPTELECOM.NET
[66.59.191.73]
6 25 ms 76 ms 28 ms POS9-0.PEERA-CHCGIL.IP.GROUPTELECOM.NET
[66.59.91.82]
7 27 ms 25 ms 25 ms p4-2-0-0.r02.chcgil06.us.bb.verio.net
[129.250.0.97]
8 * 29 ms 26 ms ge-5-2-0.r01.chcgil06.us.bb.verio.net
[129.250..114]
9 30 ms 31 ms 29 ms POS5-2.BR3.CHI2.ALTER.NET [204.255.174.233]
10 31 ms 31 ms 67 ms 0.so-5-2-0.XL1.CHI2.ALTER.NET [152.63.68.2]
11 55 ms 56 ms 56 ms 0.so-1-1-0.XL1.TOR2.ALTER.NET [152.63.3.97]
12 55 ms 79 ms 82 ms POS1-0.XR1.TOR2.ALTER.NET [152.63.2.110]
13 147 ms 172 ms 215 ms 195.ATM9-0-0.GW1.LON1.ALTER.NET
[152.63.131.17]

14 39 ms 39 ms 39 ms xelco5-gw.customer.alter.net [204.92.65.98]
15 44 ms 46 ms 66 ms fors-sarn_ptp-gw.xcelco.on.ca
[216.94.238.218]
16 44 ms 41 ms 40 ms mail.xcelco.on.ca [209.167.188.10]

Trace complete.

--------------------------------------------------------------------------------


C:\>telnet mail.xcelco.on.ca
Connecting To mail.xcelco.on.ca...Could not open a connection to host on
port 23
: Connect failed

--------------------------------------------------------------------------------

C:\>telnet mail.xcelco.on.ca 110
Connecting To mail.xcelco.on.ca...Could not open a connection to host on
port 11
0 : Connect failed


--------------------------------------------------------------------------------

C:\>telnet mail.xcelco.on.ca 25
Connecting To mail.xcelco.on.ca...Could not open a connection to host on
port 25
: Connect failed

C:\>



.

Relevant Pages

  • Re: Sysclean
    ... connection specific dns:- ... ping yahoo.com> ping cannot find host name ... ... > | then try to connect to internet, the ie6sp1 still fail to display. ...
    (microsoft.public.windowsxp.general)
  • Re: pppd/chat dialup
    ... OK - first obvious change is that the same host gave you a completely ... >not able to ping when connected using pppd/chat. ... What my thoughts are is that your 'pppd/chat' connection is actually ...
    (comp.os.linux.misc)
  • self ping...HELP!
    ... Desktop is host Host CAN ... ping client client can ... >Also what type of connection do you have and are you on ...
    (microsoft.public.windowsxp.network_web)
  • Shared Connection Difficulty, DNS?
    ... I have a host computer and 2 client computers. ... The client can ping 66.94.231.98 ... When a new dial up connection is established on the ...
    (microsoft.public.windowsxp.network_web)
  • VPN Drop
    ... I'm trying to connect to another company's ISA trough VPN ... PPTP and the connection results in a total success. ... ping, tracert, etc but as soon as the duration reaches 2 ...
    (microsoft.public.isaserver)