Re: HELP- Intermittent Connection Problems....Blamed on XP!!??


Well, your expertise is 1,000 times greater than mine and I really do
appreciate your help!!

I'll do my research and keep my fingers crossed....although I haven't
ever done any diagnostic work in this area, I'm pretty comfortable
with pc maintenance and have fixed quite a few problems in the
past...many that I've created myself!!!!

Again, thnx for your help and patience!!!!!!!!!


On Sat, 26 Aug 2006 16:23:02 -0700, paulibus
<paulibus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hey Phil,

I tried to ping both 68.69.60.129 and 68.69.56.1. I was timed out on the
first address probably because this address doesn't accept pings for security
reasons. I was successful with the 2nd address. Note, I did not receive an
error message.

Error code 65 can be caused by Internet Connection Sharing. See this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q316414

This error can also be caused by 3rd party firewall software. If you think
that may be the case, try uninstalling and reinstalling. If you are using a
3rd party firewall, turn on the Windows firewall before uninstalling. Check
this out:
http://www.practicallynetworked.com/sharing/troubleshoot/removefirewall.htm

I hope this solves it, because we are at the limit of my expertise.

Good luck,

P.

"phil6666" wrote:


OK.....one day later, I lose my internet connection about an hour
after boot-up.

As you suggested, here's the PING results:


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : kntnny.adelphia.net
IP Address. . . . . . . . . . . . : 68.69.60.129
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 68.69.56.1

C:\Documents and Settings\Phil>ping 127.0.0.1

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

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

C:\Documents and Settings\Phil>ping 68.69.60.129

Pinging 68.69.60.129 with 32 bytes of data:

PING: transmit failed, error code 65.
PING: transmit failed, error code 65.
PING: transmit failed, error code 65.
PING: transmit failed, error code 65.

Ping statistics for 68.69.60.129:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings\Phil>ping 68.69.56.1

Pinging 68.69.56.1 with 32 bytes of data:

PING: transmit failed, error code 65.
PING: transmit failed, error code 65.
PING: transmit failed, error code 65.
PING: transmit failed, error code 65.

Ping statistics for 68.69.56.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


SOOOOO, does this mean something to you?????




On Fri, 25 Aug 2006 15:35:02 -0700, paulibus
<paulibus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

It is possible that the problem is at your end. But if you cannot stay
connected via their service, you might as well be using Netzero, and save
some money.

I don't think we can fix this via a help forum, but here is something you
can do. The next time you are connected to the internet:

1 Click Start.
2 Click Run.
3 Type in cmd and click the OK button.
4 On the resulting screen type in "ipconfig" and press Enter; don't use
quotes.
5 Look for the first entries for "IP Address" and "Default Gateway".
6 Write down he numbers next to these entries. They will be in the form
000.000.000.000.

Then the next time you lose the connection:
1 Follow steps 1-3 above.
2 On the resulting screen type "ping 127.0.0.1" without the quotes.
3 Note the result.
4 Then type "ping" with the IP address you previoulsy recorded and note the
result.
5 Then type "ping" with the Default Gateway address.

I'm hoping that 1 of these will respond with a "timed out" message. Then
you will have something to work with. After that you can repost the question
to this forum or the Windows Networking and the Web forum, with the results
of your tests: "I recieved a timed out message when I tried to ping...".

Also try if you can to ioslate the problem. Hook another computer up and/or
bring yours to, and connect from another location. See if the problem
persists. If it does it is your computer, if not it is something beyond it.

Good luck,

Paul



.

Relevant Pages

  • Re: Winsock provider catalog
    ... PING: transmit failed, error code 65. ... info Using home Internet connection ... info Network connection: Name=Local Area Connection 3, ...
    (microsoft.public.windowsxp.general)
  • RE: Winsock provider catalog (summary of previous post)
    ... info Using home Internet connection ... info Network connection: Name=Local Area Connection 3, ... PING: transmit failed, error code 65. ...
    (microsoft.public.windowsxp.general)
  • Re: Winsock provider catalog
    ... PING: transmit failed, error code 65. ... info Using home Internet connection ... info Network connection: Name=Local Area Connection 3, ...
    (microsoft.public.windowsxp.general)
  • Re: HELP- Intermittent Connection Problems....Blamed on XP!!??
    ... Right now my connection is rock-solid, so I repeated the "ping test" ... Ethernet adapter Local Area Connection: ... Ping statistics for 127.0.0.1: ... transmit failed, error code 65. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Ping over direct connection
    ... Consultancy, training and development services. ... jcavo wrote: ... When both my CE5.0 device and my PC are connected to the LAN, they can ping ... error code 11010". ...
    (microsoft.public.windowsce.platbuilder)