Just installed Win7 on my nieces laptop today. I had EasyTether running fine on it, so I switched to Wireless Tether, and I got horrible results. And now I can't even get EasyTether to work lol. Anyways, wtf is going on here with my Wireless Tether?!?! I have the phone literally within 2 feet of the laptop, and signal level is around -78db. And when I surf from the phone itself, it's snappy and quick. Anything in particular I should check here?
Code:
C:\Users\Kayla>ping google.com -t
Pinging google.com [72.14.204.104] with 32 bytes of data:
Reply from 72.14.204.104: bytes=32 time=1447ms TTL=50
Request timed out.
Request timed out.
Reply from 72.14.204.104: bytes=32 time=147ms TTL=50
Reply from 72.14.204.104: bytes=32 time=111ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=105ms TTL=50
Request timed out.
Request timed out.
Reply from 72.14.204.104: bytes=32 time=573ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=107ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=174ms TTL=50
Reply from 72.14.204.104: bytes=32 time=103ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=134ms TTL=50
Reply from 72.14.204.104: bytes=32 time=82ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=1012ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=161ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=125ms TTL=50
Reply from 72.14.204.104: bytes=32 time=110ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=134ms TTL=50
Reply from 72.14.204.104: bytes=32 time=103ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=100ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Reply from 72.14.204.104: bytes=32 time=2140ms TTL=50
Reply from 72.14.204.104: bytes=32 time=927ms TTL=50
Request timed out.
Reply from 72.14.204.104: bytes=32 time=586ms TTL=50
Ping statistics for 72.14.204.104:
Packets: Sent = 37, Received = 20, Lost = 17 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 2140ms, Average = 419ms
Code:
C:\Users\Kayla>tracert google.com
Tracing route to google.com [72.14.204.104]
over a maximum of 30 hops:
1 49 ms * 10 ms 192.168.2.254
2 * 497 ms 79 ms 64.sub-66-174-121.myvzw.com [66.174.121.64]
3 * * * Request timed out.
4 2380 ms * * 177.sub-69-83-15.myvzw.com [69.83.15.177]
5 1554 ms 1570 ms * 18.sub-69-83-14.myvzw.com [69.83.14.18]
6 1524 ms 1690 ms 1990 ms 132.sub-66-174-18.myvzw.com [66.174.18.132]
7 * 1586 ms * 131.sub-66-174-18.myvzw.com [66.174.18.131]
8 * 1112 ms 1214 ms 253.sub-69-83-3.myvzw.com [69.83.3.253]
9 * * 1499 ms ge5-0-3d0.cir1.nyc-ny.us.xo.net [209.220.16.13]
10 1513 ms 1899 ms * 209.220.16.110.ptr.us.xo.net [209.220.16.110]
11 * 2172 ms 2033 ms 209.85.252.215
12 2263 ms * 2237 ms 209.85.249.11
13 1832 ms * 1124 ms 66.249.94.46
14 * 1183 ms 1314 ms iad04s01-in-f104.1e100.net [72.14.204.104]
Trace complete.