Can you connect a PC this way?

You can connect either the USB or the Ethernet but not both.  You should be able to connect the computer to the router using an Ethernet cable and all devices be able to access the Intenret.

Thanks, That's the way it's set up now but was trying to connect the one PC directly and still have wireless for the others. I'm having a issue but not sure what this all means and thought the second hop might me a problem with the N600 router. Not sure what  * * * Request timed out means but its from the router right? The problem is what others have posted about with Blizzard but was not sure what all this below means but started thinking that the second and 3rd hop might be from my router and causing a issue.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1 
2 * * * Request timed out.
3 269 ms 47 ms 40 ms ip68-1-11-151.at.at.cox.net [68.1.11.151] 
4 10 ms 7 ms 6 ms 68.1.10.158 
5 274 ms 227 ms 278 ms ip68-1-11-178.at.at.cox.net [68.1.11.178] 
6 28 ms 28 ms 28 ms maribprj01-ae1.0.rd.at.cox.net [68.1.0.41] 
7 235 ms 208 ms 215 ms te2-3.ccr01.atl02.atlas.cogentco.com [154.54.12.149] 
8 185 ms 222 ms 360 ms te0-0-0-1.ccr21.atl01.atlas.cogentco.com [154.54.0.165] 
9 45 ms 46 ms 46 ms te0-1-0-6.ccr21.ord01.atlas.cogentco.com [154.54.29.98] 
10 46 ms 51 ms 55 ms te0-5-0-5.ccr22.ord03.atlas.cogentco.com [154.54.44.162] 
11 62 ms 72 ms 58 ms 192.205.37.173 
12 * * 66 ms cr2.cgcil.ip.att.net [12.122.84.94] 
13 * 64 ms 61 ms gar3.cgcil.ip.att.net [12.122.132.213] 
14 99 ms 71 ms 65 ms 12.122.251.50 
15 * 64 ms 62 ms 63.240.130.214 
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Don't think it would have made a difference unless you could get a different IP on the USB,,

The 2nd hop appears to simply not be configured to respond to ICMP traffic however the data you have suggests a problem between and including the router and our CMTS.  Can you try again without the router and post your results?

Hello, Chris here is the info I just ran. The first traceroute is thru the router, the second is with the PC connected to the modem directly, and the last is a pathping. Thanks, Jason

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 238 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 9 ms 8 ms ip68-1-11-151.at.at.cox.net [68.1.11.151]
4 10 ms 11 ms 9 ms 68.1.10.158
5 11 ms 10 ms 9 ms ip68-1-11-178.at.at.cox.net [68.1.11.178]
6 31 ms 31 ms 39 ms maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
7 187 ms 220 ms 222 ms te2-3.ccr01.atl02.atlas.cogentco.com [154.54.12.149]
8 32 ms 31 ms 32 ms te0-0-0-1.ccr21.atl01.atlas.cogentco.com [154.54.0.165]
9 53 ms 49 ms 51 ms te0-1-0-6.ccr21.ord01.atlas.cogentco.com [154.54.29.98]
10 49 ms 49 ms 47 ms te0-5-0-5.ccr22.ord03.atlas.cogentco.com [154.54.44.162]
11 63 ms 66 ms 64 ms 192.205.37.173
12 * 68 ms 67 ms cr1.cgcil.ip.att.net [12.122.84.54]
13 62 ms * 66 ms gar2.clboh.ip.att.net [12.122.133.197]
14 66 ms 66 ms 66 ms 12.122.251.50
15 69 ms 66 ms 64 ms 63.240.130.214
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 9 ms 9 ms 27 ms Fubarrd-PC [0.0.0.0]
2 11 ms 7 ms 7 ms ip68-1-11-170.at.at.cox.net [68.1.11.170]
3 9 ms 9 ms 11 ms 68.1.10.158
4 32 ms 9 ms 11 ms ip68-1-11-178.at.at.cox.net [68.1.11.178]
5 32 ms 118 ms 32 ms maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
6 111 ms 213 ms 212 ms te2-3.ccr01.atl02.atlas.cogentco.com [154.54.12.149]
7 31 ms 31 ms 32 ms te0-4-0-7.ccr21.atl01.atlas.cogentco.com [154.54.88.201]
8 67 ms 65 ms 63 ms te0-7-0-32.ccr21.ord01.atlas.cogentco.com [154.54.29.94]
9 67 ms 63 ms 75 ms te0-1-0-3.ccr22.ord03.atlas.cogentco.com [154.54.1.2]
10 * * 73 ms att.ord03.atlas.cogentco.com [154.54.12.86]
11 76 ms 76 ms 75 ms cr1.cgcil.ip.att.net [12.122.84.54]
12 76 ms 75 ms 90 ms gar2.clboh.ip.att.net [12.122.133.197]
13 * * 74 ms 12.122.251.22
14 75 ms 78 ms 75 ms 63.240.130.210
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Fubarrd-PC.pn.at.cox.net [70.191.235.116]
1 Fubarrd-PC [0.0.0.0]
2 ip68-1-11-170.at.at.cox.net [68.1.11.170]
3 68.1.10.158
4 ip68-1-11-178.at.at.cox.net [68.1.11.178]
5 maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
6 te2-3.ccr01.atl02.atlas.cogentco.com [154.54.12.149]
7 te0-4-0-7.ccr21.atl01.atlas.cogentco.com [154.54.88.201]
8 te0-7-0-32.ccr21.ord01.atlas.cogentco.com [154.54.29.94]
9 te0-5-0-5.ccr22.ord03.atlas.cogentco.com [154.54.44.162]
10 att.ord03.atlas.cogentco.com [154.54.12.86]
11 * cr2.cgcil.ip.att.net [12.122.84.94]
12 gar3.cgcil.ip.att.net [12.122.132.213]
13 12.122.251.50
14 63.240.130.210
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Fubarrd-PC.pn.at.cox.net [70.191.235.116]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% Fubarrd-PC [0.0.0.0]
0/ 100 = 0% |
2 25ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-170.at.at.cox.net [68.1.11.170]
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% 68.1.10.158
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-178.at.at.cox.net [68.1.11.178]
0/ 100 = 0% |
5 45ms 0/ 100 = 0% 0/ 100 = 0% maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
0/ 100 = 0% |
6 96ms 1/ 100 = 1% 1/ 100 = 1% te2-3.ccr01.atl02.atlas.cogentco.com [154.54.12.149]
0/ 100 = 0% |
7 34ms 0/ 100 = 0% 0/ 100 = 0% te0-4-0-7.ccr21.atl01.atlas.cogentco.com [154.54.88.201]
0/ 100 = 0% |
8 65ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-32.ccr21.ord01.atlas.cogentco.com [154.54.29.94]
0/ 100 = 0% |
9 66ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-5.ccr22.ord03.atlas.cogentco.com [154.54.44.162]
7/ 100 = 7% |
10 81ms 7/ 100 = 7% 0/ 100 = 0% att.ord03.atlas.cogentco.com [154.54.12.86]
93/ 100 = 93% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.

Those all look just fine except for this one which is particularly telling:

jas89tta said:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 238 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.

238 ms from your PC to your router seems a bit high.  I would start looking at that link for potential problems.