Jump to content
Forums

[Update error] Could not connect to the update server.


StrykerGaming

Recommended Posts

I'm receiving this message when I try connecting to the game server. I've tried sending this error per the reporting system but it fails to send.

 

<< Dns Query >>
Update Server
(1)
Name : updater.nclauncher.ncsoft.com
Address : 192.9.115.0
(2)
Name : updater.nclauncher.ncsoft.com
Address : 128.11.115.0
(3)
Name : updater.nclauncher.ncsoft.com
Address : 64.13.115.0


Repository Server
(1)
Name : live.patcher.bladeandsoul.com
Address : 96.15.115.0
(2)
Name : live.patcher.bladeandsoul.com
Address : 144.17.115.0
(3)
Name : live.patcher.bladeandsoul.com
Address : 192.19.115.0


<< FileInfoFile Hash Value >>
File Name    : FileInfoMap_BnS_29.dat.zip
Hash Value    : a6bb6a0ba2f8a618c37cb261b59d3e3c1062d300
File Name    : FileInfoMap_BnS_29.dat
Hash Value    : 4135e4eec68b15a2fc51defe184135ec0b75ef80

<< Error Message >>
[Update error] Could not connect to the update server.
 Please restart the launcher. If this problem persists, please contact Customer Support at http://us.ncsoft.com/en/support/.
E02009
CUS_C5_/17231940

 

Furthermore, when I try pinging the server, I get nothing, it times out completely as if the server does not exist. I'm playing from the Philippines. I did not have this problem yesterday; however, today I am. This morning I was able to connect to the server for 20 minutes when I was disconnected and unable to connect after that.

 

I do not know if this is my ISP's issue or an issue between the server and my ISP. If anyone can give me help in trying to figure out what's going on and how to resolve or get it resolved, I would greatly appreciate it. Thanks!

Link to comment
Share on other sites

Bump for support as it is happening again! Tracert run to show issue.

 


Tracing route to bladeandsoul-www-1920946662.us-west-2.elb.amazonaws.com [52.36.
160.79]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  <hidden>
  2    39 ms    45 ms    38 ms  <hidden>
  3    41 ms    38 ms    39 ms  <hidden>
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    65 ms    69 ms    66 ms  120.28.1.82
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9   456 ms   487 ms   513 ms  52.95.52.120
 10   199 ms   198 ms   199 ms  52.95.52.129
 11   199 ms   199 ms   199 ms  54.239.41.193
 12   202 ms   200 ms   200 ms  205.251.232.147
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 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.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...