Network continually stalling

Discussion in 'Computer Information' started by Robert Baer, Oct 27, 2012.

  1. Robert Baer

    Robert Baer Guest

    Have NIC card replacing on-board Ethernet support now; made zero
    difference WRT problems:
    1) Say i attempt to login to my Google e-mail or other account OR change
    pages while browsing (say looking for parts on Mouser website).
    Data transmission and reception STOPS for an indeterminate amount of
    time and may or may not continue for an indeterminate amount of time -
    sometimes "forever".
    2) In NGs, say i click on a posting to view it and not a damn thing
    happens; must then click on a different posting and re-try the one i
    want - doing that almost always selects and shows what i wanted.
    3) In NGs, say i write a response and click on send; sometimes the
    progress bar runs essentially forever. Most of the time closing down the
    browser will fix that, but not always.

    In all cases (AFAIK for NGs), absolutely ZERO packets are sent or
    received.
    Avast! e-mail help suggested the use of one of the tools listed at:
    https://www.google.com/search?q=sof...w.r_cp.r_qf.&cad=b&sei=Gf6KULvuGY62qQHF7YDICQ

    Sorry about the l*o*n*g reference; that is what was given.
    Using a short Google query "software monitors/logs network traffic"
    gives a LOT more "hits", and it might me a "good idea" (according to
    Martha Stewart) to avoid that if possible, as there are no "filters".

    Does anyone KNOW which ones (a) work, (b) does NOT and CANNOT crash
    the computer - most especially does NOT and CANNOT crash the OS?
    Te second part is *VERY* important,as the last time i tried a
    suggested malware "finder", everything was clobbered (would you believe
    a black screen with a license violation message?).
    Robert Baer, Oct 27, 2012
    #1
    1. Advertising

  2. Robert Baer

    Paul Guest

    Robert Baer wrote:
    > Have NIC card replacing on-board Ethernet support now; made zero
    > difference WRT problems:
    > 1) Say i attempt to login to my Google e-mail or other account OR change
    > pages while browsing (say looking for parts on Mouser website).
    > Data transmission and reception STOPS for an indeterminate amount of
    > time and may or may not continue for an indeterminate amount of time -
    > sometimes "forever".
    > 2) In NGs, say i click on a posting to view it and not a damn thing
    > happens; must then click on a different posting and re-try the one i
    > want - doing that almost always selects and shows what i wanted.
    > 3) In NGs, say i write a response and click on send; sometimes the
    > progress bar runs essentially forever. Most of the time closing down the
    > browser will fix that, but not always.
    >
    > In all cases (AFAIK for NGs), absolutely ZERO packets are sent or
    > received.
    > Avast! e-mail help suggested the use of one of the tools listed at:
    > https://www.google.com/search?q=sof...w.r_cp.r_qf.&cad=b&sei=Gf6KULvuGY62qQHF7YDICQ
    >
    >
    > Sorry about the l*o*n*g reference; that is what was given.
    > Using a short Google query "software monitors/logs network traffic"
    > gives a LOT more "hits", and it might me a "good idea" (according to
    > Martha Stewart) to avoid that if possible, as there are no "filters".
    >
    > Does anyone KNOW which ones (a) work, (b) does NOT and CANNOT crash
    > the computer - most especially does NOT and CANNOT crash the OS?
    > Te second part is *VERY* important,as the last time i tried a
    > suggested malware "finder", everything was clobbered (would you believe
    > a black screen with a license violation message?).


    A malware finder which quarantines the malware, can also take important
    system files and put them in the quarantine folder as well. There are
    a few system services in Windows, that if they're disabled, the
    OS will shut down in 60 seconds. So there are some things, a
    modern Windows won't stay up if they're damaged.

    There is no guarantee malware is repairable. While some malware
    is of that variety, it isn't always that way.

    I use this for scans. 237MB CD.

    http://support.kaspersky.com/viruses/rescuedisk/main?qid=208286083

    Don't forget to visit Event Viewer, and look for any error messages
    in there around the time of the incident (when networking stops).

    Paul
    Paul, Oct 27, 2012
    #2
    1. Advertising

  3. Robert Baer

    Izzy Guest

    On 26 Oct 2012, Robert Baer <> posted some
    news:77Iis.3388$:

    > Have NIC card replacing on-board Ethernet support now; made zero
    > difference WRT problems:
    > 1) Say i attempt to login to my Google e-mail or other account OR
    > change pages while browsing (say looking for parts on Mouser website).
    > Data transmission and reception STOPS for an indeterminate amount
    > of
    > time and may or may not continue for an indeterminate amount of time -
    > sometimes "forever".


    Try this:

    Open a command prompt.

    run this command:

    ping accounts.google.com -n 30

    The -n 30 will ping gmail 30 times. You want it to look like this:

    ping accounts.google.com -n 30

    Pinging accounts.l.google.com [74.125.141.84] with 32 bytes of data:

    Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=39ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=44ms TTL=47
    Request timed out.
    Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=47ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=57ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=46ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=54ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=44ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    Reply from 74.125.141.84: bytes=32 time=49ms TTL=47

    Ping statistics for 74.125.141.84:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 57ms, Average = 43ms

    You shouldn't have any requests time out.

    The one "Request timed out." is where I pulled the cable between the
    router and the cable modem, for a sec then plugged it back in.

    See what your network does.

    Then you can try this:

    tracert accounts.google.com -d

    The -d just means don't try to resolve any names to IP addresses.

    P:\>tracert accounts.google.com -d

    Tracing route to accounts.l.google.com [74.125.141.84]
    over a maximum of 30 hops:

    1 1 ms <1 ms <1 ms 176.16.20.1
    2 8 ms 7 ms 7 ms 10.xx.xxx.1x
    3 12 ms 7 ms 11 ms 68.4.14.200
    4 11 ms 15 ms 9 ms 68.4.11.104
    5 9 ms 9 ms 12 ms 68.4.11.94
    6 11 ms 9 ms 9 ms 68.1.1.13
    7 13 ms 18 ms 11 ms 68.105.30.181
    8 18 ms 11 ms 18 ms 64.233.174.238
    9 16 ms 41 ms 15 ms 64.233.174.192
    10 39 ms 40 ms 47 ms 72.14.239.153
    11 40 ms 48 ms 46 ms 64.233.174.125
    12 * * * Request timed out.
    13 41 ms 39 ms 40 ms 74.125.141.84

    Trace complete.

    Line 12 just means whatever is there has extremely high latency or it
    simply doesn't respond to icmp requests. Line 13 responds so this is ok.

    See what you get.



    > 2) In NGs, say i click on a posting to view it and not a damn thing
    > happens; must then click on a different posting and re-try the one i
    > want - doing that almost always selects and shows what i wanted.
    > 3) In NGs, say i write a response and click on send; sometimes the
    > progress bar runs essentially forever. Most of the time closing down
    > the browser will fix that, but not always.


    > In all cases (AFAIK for NGs), absolutely ZERO packets are sent or
    > received.
    > Avast! e-mail help suggested the use of one of the tools listed at:
    > https://www.google.com/search?q=software that monitors/logs network t
    > raffic%3F&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:eek:fficial&client=
    > firefox-a#hl=pl&client=firefox-a&hs=7wy&rls=org.mozilla:en-US%3Aofficia
    > l&sclient=psy-ab&q=software+monitors%2Flogs+network+traffic&oq=software
    > +monitors%2Flogs+network+traffic&gs_l=serp.3...4238.5476.0.5980.4.3.1.0
    > .0.0.66.183.3.3.0...0.0...1c.1.pJ8QTVS1X5A&pbx=1&fp=1&bpcl=35466521&biw
    > =1920&bih=1040&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&cad=b&sei=Gf6KULvuGY62q
    > QHF7YDICQ


    > Sorry about the l*o*n*g reference; that is what was given.
    > Using a short Google query "software monitors/logs network traffic"
    > gives a LOT more "hits", and it might me a "good idea" (according to
    > Martha Stewart) to avoid that if possible, as there are no "filters".
    >
    > Does anyone KNOW which ones (a) work, (b) does NOT and CANNOT crash
    > the computer - most especially does NOT and CANNOT crash the OS?
    > Te second part is *VERY* important,as the last time i tried a
    > suggested malware "finder", everything was clobbered (would you
    > believe a black screen with a license violation message?).
    Izzy, Oct 30, 2012
    #3
  4. Robert Baer

    Robert Baer Guest

    Izzy wrote:
    > On 26 Oct 2012, Robert Baer<> posted some
    > news:77Iis.3388$:
    >
    >> Have NIC card replacing on-board Ethernet support now; made zero
    >> difference WRT problems:
    >> 1) Say i attempt to login to my Google e-mail or other account OR
    >> change pages while browsing (say looking for parts on Mouser website).
    >> Data transmission and reception STOPS for an indeterminate amount
    >> of
    >> time and may or may not continue for an indeterminate amount of time -
    >> sometimes "forever".

    >
    > Try this:
    >
    > Open a command prompt.
    >
    > run this command:
    >
    > ping accounts.google.com -n 30
    >
    > The -n 30 will ping gmail 30 times. You want it to look like this:
    >
    > ping accounts.google.com -n 30
    >
    > Pinging accounts.l.google.com [74.125.141.84] with 32 bytes of data:
    >
    > Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=39ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=44ms TTL=47
    > Request timed out.
    > Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=47ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=57ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=43ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=41ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=46ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=42ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=54ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=40ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=44ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=45ms TTL=47
    > Reply from 74.125.141.84: bytes=32 time=49ms TTL=47
    >
    > Ping statistics for 74.125.141.84:
    > Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
    > Approximate round trip times in milli-seconds:
    > Minimum = 39ms, Maximum = 57ms, Average = 43ms
    >
    > You shouldn't have any requests time out.

    * this always works; never "unlocks" stalled packets (like i try to
    login to gmail account and nada happens).

    >
    > The one "Request timed out." is where I pulled the cable between the
    > router and the cable modem, for a sec then plugged it back in.
    >
    > See what your network does.
    >
    > Then you can try this:
    >
    > tracert accounts.google.com -d
    >
    > The -d just means don't try to resolve any names to IP addresses.
    >
    > P:\>tracert accounts.google.com -d
    >
    > Tracing route to accounts.l.google.com [74.125.141.84]
    > over a maximum of 30 hops:
    >
    > 1 1 ms<1 ms<1 ms 176.16.20.1
    > 2 8 ms 7 ms 7 ms 10.xx.xxx.1x
    > 3 12 ms 7 ms 11 ms 68.4.14.200
    > 4 11 ms 15 ms 9 ms 68.4.11.104
    > 5 9 ms 9 ms 12 ms 68.4.11.94
    > 6 11 ms 9 ms 9 ms 68.1.1.13
    > 7 13 ms 18 ms 11 ms 68.105.30.181
    > 8 18 ms 11 ms 18 ms 64.233.174.238
    > 9 16 ms 41 ms 15 ms 64.233.174.192
    > 10 39 ms 40 ms 47 ms 72.14.239.153
    > 11 40 ms 48 ms 46 ms 64.233.174.125
    > 12 * * * Request timed out.
    > 13 41 ms 39 ms 40 ms 74.125.141.84
    >
    > Trace complete.
    >
    > Line 12 just means whatever is there has extremely high latency or it
    > simply doesn't respond to icmp requests. Line 13 responds so this is ok.
    >
    > See what you get.

    * never see timeout message, BUT one or more lines stop in middle from
    ..3sec to 10sec but "printout" looks good.

    >
    >
    >
    >> 2) In NGs, say i click on a posting to view it and not a damn thing
    >> happens; must then click on a different posting and re-try the one i
    >> want - doing that almost always selects and shows what i wanted.
    >> 3) In NGs, say i write a response and click on send; sometimes the
    >> progress bar runs essentially forever. Most of the time closing down
    >> the browser will fix that, but not always.

    >
    >> In all cases (AFAIK for NGs), absolutely ZERO packets are sent or
    >> received.
    >> Avast! e-mail help suggested the use of one of the tools listed at:
    >> https://www.google.com/search?q=software that monitors/logs network t
    >> raffic%3F&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:eek:fficial&client=
    >> firefox-a#hl=pl&client=firefox-a&hs=7wy&rls=org.mozilla:en-US%3Aofficia
    >> l&sclient=psy-ab&q=software+monitors%2Flogs+network+traffic&oq=software
    >> +monitors%2Flogs+network+traffic&gs_l=serp.3...4238.5476.0.5980.4.3.1.0
    >> .0.0.66.183.3.3.0...0.0...1c.1.pJ8QTVS1X5A&pbx=1&fp=1&bpcl=35466521&biw
    >> =1920&bih=1040&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&cad=b&sei=Gf6KULvuGY62q
    >> QHF7YDICQ

    >
    >> Sorry about the l*o*n*g reference; that is what was given.
    >> Using a short Google query "software monitors/logs network traffic"
    >> gives a LOT more "hits", and it might me a "good idea" (according to
    >> Martha Stewart) to avoid that if possible, as there are no "filters".
    >>
    >> Does anyone KNOW which ones (a) work, (b) does NOT and CANNOT crash
    >> the computer - most especially does NOT and CANNOT crash the OS?
    >> Te second part is *VERY* important,as the last time i tried a
    >> suggested malware "finder", everything was clobbered (would you
    >> believe a black screen with a license violation message?).

    >
    >
    >
    Robert Baer, Oct 31, 2012
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. joe

    stalling - set clock ratio

    joe, Jun 24, 2003, in forum: Computer Support
    Replies:
    0
    Views:
    1,570
  2. Pooh

    Windows XP Pro Shutdown stalling

    Pooh, Jan 4, 2004, in forum: Computer Support
    Replies:
    2
    Views:
    604
    Miggsee
    Jan 4, 2004
  3. woodco

    send/receive stalling

    woodco, May 8, 2004, in forum: Computer Support
    Replies:
    0
    Views:
    433
    woodco
    May 8, 2004
  4. System boot stalling on ESCD

    , Sep 7, 2004, in forum: Computer Support
    Replies:
    2
    Views:
    606
  5. Re: System boot stalling on ESCD

    , Sep 8, 2004, in forum: Computer Support
    Replies:
    0
    Views:
    411
Loading...

Share This Page