package loss and general failures


hi, yesterday connection started acting out of nowhere. have no idea problem might be. this:

request timed out.
request timed out.
reply 173.194.66.101: bytes=32 time=29ms ttl=48
reply 173.194.66.101: bytes=32 time=60ms ttl=48
reply 173.194.66.101: bytes=32 time=58ms ttl=48
reply 173.194.66.101: bytes=32 time=49ms ttl=48
reply 173.194.66.101: bytes=32 time=70ms ttl=48
reply 173.194.66.101: bytes=32 time=50ms ttl=48
reply 173.194.66.101: bytes=32 time=32ms ttl=48
reply 173.194.66.101: bytes=32 time=51ms ttl=48
reply 173.194.66.101: bytes=32 time=57ms ttl=48
reply 173.194.66.101: bytes=32 time=73ms ttl=48
reply 173.194.66.101: bytes=32 time=49ms ttl=48
reply 173.194.66.101: bytes=32 time=44ms ttl=48
reply 173.194.66.101: bytes=32 time=41ms ttl=48
reply 173.194.66.101: bytes=32 time=25ms ttl=48
reply 173.194.66.101: bytes=32 time=50ms ttl=48
reply 173.194.66.101: bytes=32 time=42ms ttl=48
reply 173.194.66.101: bytes=32 time=59ms ttl=48
reply 173.194.66.101: bytes=32 time=65ms ttl=48
reply 173.194.66.101: bytes=32 time=42ms ttl=48
reply 173.194.66.101: bytes=32 time=53ms ttl=48
reply 173.194.66.101: bytes=32 time=36ms ttl=48
request timed out.
request timed out.
request timed out.
request timed out.
request timed out.
request timed out.
request timed out.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
request timed out.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 192.168.10.34: destination host unreachable.
reply 173.194.66.101: bytes=32 time=2972ms ttl=48
reply 173.194.66.101: bytes=32 time=25ms ttl=48
reply 173.194.66.101: bytes=32 time=26ms ttl=48
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=24ms ttl=48
request timed out.
reply 173.194.66.101: bytes=32 time=24ms ttl=48
reply 173.194.66.101: bytes=32 time=24ms ttl=48
reply 173.194.66.101: bytes=32 time=24ms ttl=48
reply 173.194.66.101: bytes=32 time=1118ms ttl=48
reply 173.194.66.101: bytes=32 time=24ms ttl=48
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=24ms ttl=48
reply 173.194.66.101: bytes=32 time=250ms ttl=48
reply 173.194.66.101: bytes=32 time=52ms ttl=48
request timed out.
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=925ms ttl=48
reply 173.194.66.101: bytes=32 time=26ms ttl=48
reply 173.194.66.101: bytes=32 time=25ms ttl=48
reply 173.194.66.101: bytes=32 time=23ms ttl=48
reply 173.194.66.101: bytes=32 time=72ms ttl=48

this related network devices between source , destination computers. btw, devices in between , how's connectivity establish here?

arnav sharma | http://arnavsharma.net/ please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client