Ensign
Join Date: Jul 2012
Posts: 3
# 1 Cant connect
08-28-2014, 04:37 PM
the patcher is stuck at >LOADING PLEASE WAIT<

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms mynetwork.home [192.168.2.1]
2 12 ms 11 ms 12 ms bas2-longueuil15_lo0_SYMP.net.bell.ca [64.230.20
0.33]
3 11 ms 12 ms 12 ms dis2-stlambert20_5-1_100.net.bell.ca [64.230.38.
24]
4 24 ms 56 ms 33 ms agg2-montreal02_7-2-0.net.bell.ca [64.230.32.10]

5 20 ms 20 ms 23 ms core3-montreal02_xe0-8-2-0_core.net.bell.ca [64.
230.170.245]
6 24 ms 24 ms 24 ms newcore2-newyork83_so5-0-0_0 [64.230.187.236]
7 23 ms 24 ms 25 ms bx5-newyork83_pos0-4-0-0.net.bell.ca [64.230.187
.22]
8 22 ms 22 ms 22 ms te0-7-0-16.ccr21.jfk05.atlas.cogentco.com [154.5
4.10.205]
9 25 ms 24 ms 25 ms be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47
.57]
10 28 ms 27 ms 28 ms be2097.ccr22.bos01.atlas.cogentco.com [154.54.30
.118]
11 31 ms 31 ms 30 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
12 39 ms 35 ms 35 ms 38.111.40.114
13 28 ms 30 ms 32 ms patchserver2.crypticstudios.com [208.95.185.41]


Trace complete.

C:\Windows\system32>


contacting nettest server..
Local IP: 174.88.245.75
Ping: 24.8 msec
Port: 80: 586 KB/sec 17 KB/sec 620 KB/sec 500
Port: 80: 584 KB/sec 16 KB/sec 617 KB/sec 500
Port: 443: 1790 KB/sec 49 KB/sec 1892 KB/sec 500
Port: 443: 573 KB/sec 16 KB/sec 605 KB/sec 500
Port: 7255: 1789 KB/sec 50 KB/sec 1890 KB/sec 500
Port: 7255: 575 KB/sec 16 KB/sec 609 KB/sec 500
Port: 7003: 565 KB/sec 16 KB/sec 596 KB/sec 500
Port: 7003: 542 KB/sec 15 KB/sec 573 KB/sec 500
Port: 7202: 539 KB/sec 15 KB/sec 570 KB/sec 500
Port: 7202: 561 KB/sec 16 KB/sec 592 KB/sec 500
Port: 7499: 1785 KB/sec 50 KB/sec 1886 KB/sec 500
Port: 7499: 1875 KB/sec 52 KB/sec 1973 KB/sec 500
Port: 80: 1858 KB/sec 52 KB/sec 1964 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>pathping patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 AURORA.home [192.168.2.15]
1 mynetwork.home [192.168.2.1]
2 bas2-longueuil15_lo0_SYMP.net.bell.ca [64.230.200.33]
3 dis2-stlambert20_5-1_100.net.bell.ca [64.230.38.24]
4 agg2-montreal02_7-2-0.net.bell.ca [64.230.32.10]
5 core3-montreal02_xe0-8-2-0_core.net.bell.ca [64.230.170.245]
6 newcore2-newyork83_so5-0-0_0 [64.230.187.236]
7 bx5-newyork83_pos0-4-0-0.net.bell.ca [64.230.187.22]
8 te0-7-0-16.ccr21.jfk05.atlas.cogentco.com [154.54.10.205]
9 be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47.57]
10 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
11 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 38.111.40.114
13 patchserver2.crypticstudios.com [208.95.185.41]

Computing statistics for 325 seconds...

Last edited by myrrd894; 08-28-2014 at 04:43 PM.
Career Officer
Join Date: Jun 2012
Posts: 2,413
# 2
08-28-2014, 05:40 PM
Quote:
Originally Posted by myrrd894 View Post
...
C:\Windows\system32>pathping patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
0 AURORA.home [192.168.2.15]
1 mynetwork.home [192.168.2.1]
2 bas2-longueuil15_lo0_SYMP.net.bell.ca [64.230.200.33]
3 dis2-stlambert20_5-1_100.net.bell.ca [64.230.38.24]
4 agg2-montreal02_7-2-0.net.bell.ca [64.230.32.10]
5 core3-montreal02_xe0-8-2-0_core.net.bell.ca [64.230.170.245]
6 newcore2-newyork83_so5-0-0_0 [64.230.187.236]
7 bx5-newyork83_pos0-4-0-0.net.bell.ca [64.230.187.22]
8 te0-7-0-16.ccr21.jfk05.atlas.cogentco.com [154.54.10.205]
9 be2063.mpd22.jfk02.atlas.cogentco.com [154.54.47.57]
10 be2097.ccr22.bos01.atlas.cogentco.com [154.54.30.118]
11 te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 38.111.40.114
13 patchserver2.crypticstudios.com [208.95.185.41]

Computing statistics for 325 seconds...
So did you wait 325 seconds for the 'Path Ping' to complete ???

Nothing is particularly wrong with the 'Trace Route' so its not a network latency issue...

The inconsistent results of the 'Net Test' indicates a connection quality issue of some kind that is unrelated to the STO servers, as 'Net Test' talks to its own dedicated diagnostic server, not the STO servers...

So we need the 'Path Ping' complete results to pinpoint the problem....
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 07:15 PM.