Someone with an Archer C2 please do me a favor
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Someone with an Archer C2 please do me a favor
Posts: 10
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-01-10
Someone with an Archer C2 please do me a favor
2016-01-11 02:10:00
Tags:
Model :
Hardware Version : Not Clear
Firmware Version :
ISP :
Please, do a direct LAN ping to your Archer C2 for ~20 seconds and paste the results here.
It'd be better to do that by wired connection, but a wifi connection is fine too.
Thanks.
Hardware Version : Not Clear
Firmware Version :
ISP :
Please, do a direct LAN ping to your Archer C2 for ~20 seconds and paste the results here.
It'd be better to do that by wired connection, but a wifi connection is fine too.
Thanks.
#1
Options
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thread Manage
6 Reply
Posts: 7
Helpful: 1
Solutions: 0
Stories: 0
Registered: 2016-02-06
Re:Someone with an Archer C2 please do me a favor
2016-02-08 20:16:30
I did a ping /t and I got the following serponses but repeating..
C:\Windows\System32>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.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:\Windows\System32>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#2
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 10
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-01-10
Re:Someone with an Archer C2 please do me a favor
2016-02-10 12:19:06
kornm wrote
I did a ping /t and I got the following serponses but repeating..
C:\Windows\System32>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Thank you.
Is this a wired connection?
What's the firmware version of your C2?
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#3
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 9
Helpful: 3
Solutions: 0
Stories: 0
Registered: 2016-02-12
Re:Someone with an Archer C2 please do me a favor
2016-02-16 14:05:49
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.855 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.124 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=7.582 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.265 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.811 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=4.852 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=3.925 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.787 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.542 ms
Request timeout for icmp_seq 9
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=6.788 ms
Request timeout for icmp_seq 11
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=18.197 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=7.540 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=19.262 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.097 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.486 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=3.551 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=5.808 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=7.194 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=3.656 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3.161 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=4.178 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=5.537 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=5.434 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=61.339 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=53.259 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=108.453 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=39.403 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=3.473 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=4.772 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=4.706 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=5.432 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=4.107 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=9.548 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=4.719 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=3.589 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=7.134 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=35.983 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=22.109 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=90.021 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=20.543 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2.262 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=6.113 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=4.939 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=3.816 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=3.595 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=7.123 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=7.064 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=7.028 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=2.829 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=11.378 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=2.734 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=62.126 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=0.980 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=3.327 ms
This is a Macbook Pro 2011 on 5Ghz wifi
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.855 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.124 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=7.582 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.265 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.811 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=4.852 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=3.925 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.787 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.542 ms
Request timeout for icmp_seq 9
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=6.788 ms
Request timeout for icmp_seq 11
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=18.197 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=7.540 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=19.262 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.097 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=2.486 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=3.551 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=5.808 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=7.194 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=3.656 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3.161 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=4.178 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=5.537 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=5.434 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=61.339 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=53.259 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=108.453 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=39.403 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=3.473 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=4.772 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=4.706 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=5.432 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=4.107 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=9.548 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=4.719 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=3.589 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=7.134 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=35.983 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=22.109 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=90.021 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=20.543 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2.262 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=6.113 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=4.939 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=3.816 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=3.595 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=7.123 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=7.064 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=7.028 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=2.829 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=11.378 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=2.734 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=62.126 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=0.980 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=3.327 ms
This is a Macbook Pro 2011 on 5Ghz wifi
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#4
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 9
Helpful: 3
Solutions: 0
Stories: 0
Registered: 2016-02-12
Re:Someone with an Archer C2 please do me a favor
2016-02-16 14:06:45
Latest firmware
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#5
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 10
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-01-10
Re:Someone with an Archer C2 please do me a favor
2016-02-16 22:15:07
Is your C2 v1.0 or v1.1? You can see it at the back of the router.Pedro_NZ wrote
Latest firmware
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#6
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 9
Helpful: 3
Solutions: 0
Stories: 0
Registered: 2016-02-12
Re:Someone with an Archer C2 please do me a favor
2016-02-17 17:42:21
File:
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
0
We appreciate your feedback. Feel free to let us know more. Log in to submit feedback.
#7
Options
- Copy Link
- Report Inappropriate Content
Thread Manage
Posts: 10
Helpful: 0
Solutions: 0
Stories: 0
Registered: 2016-01-10
Information
Helpful: 0
Views: 571
Replies: 6
Voters 0
No one has voted for it yet.
Tags
Report Inappropriate Content
Transfer Module
New message