7 replies to this topic

[Zxen]

The client patches and starts up fine, but whenever I try to log in, it stalls for about ten seconds and tells me "Failed to connect to server." Windows 7 64-bit, Comcast internet.

I've disabled both my antivirus and firewall to rule them out, and the problem persists. I have UAC disabled, and the client is set to run as administrator. I have no problems getting to the Ragnarok website or the patch FTP server: or, for that matter, any other website or connecting to any other game.

It's been about two hours now, and I've tried everything I can think of and everything that's been suggested thus far. Any suggestions would be appreciated: I'm at a loss.

Tracert:

  1	 1 ms	 1 ms	 1 ms  <snipped for privacy, router IP>
  2	41 ms	31 ms	48 ms  <snipped for privacy, external IP>
  3	14 ms	14 ms	24 ms  te-0-0-0-6-sur02.saltlakecity.ut.utah.comcast.ne
t [68.87.220.109]
  4	17 ms	36 ms	23 ms  te-0-6-0-0-ar02.sandy.ut.utah.comcast.net [68.86
.180.85]
  5	19 ms	19 ms	23 ms  te-0-1-0-0-ar03.saltlakecity.ut.utah.comcast.net
[68.86.180.121]
  6	36 ms	34 ms	27 ms  pos-0-2-0-0-cr01.denver.co.ibone.comcast.net [68
.86.90.225]
  7	46 ms	32 ms	29 ms  xe-2-1-2-0-pe01.910fifteenth.co.ibone.comcast.ne
t [68.86.82.22]
  8	24 ms	23 ms	31 ms  173.167.58.162
  9	54 ms	47 ms	50 ms  if-7-2-2-0.tcore1.PDI-PaloAlto.as6453.net [66.19
8.127.69]
10	51 ms	43 ms	49 ms  if-2-2.tcore2.PDI-PaloAlto.as6453.net [66.198.12
7.2]
11	54 ms	48 ms	53 ms  if-11-0-0-3262.core3.SQN-SanJose.as6453.net [66.
198.144.62]
12	76 ms	78 ms	72 ms  Vlan57.icore1.SQN-SanJose.as6453.net [209.58.116
.133]
13	76 ms   106 ms	69 ms  Vlan507.icore1.SQN-SanJose.as6453.net [209.58.11
6.22]
14	58 ms	63 ms	63 ms  ae-6.r20.snjsca04.us.bb.gin.ntt.net [129.250.5.1
2]
15	80 ms	76 ms	71 ms  ae-4.r21.lsanca03.us.bb.gin.ntt.net [129.250.6.1
0]
16	72 ms	72 ms	75 ms  ae-2.r05.lsanca03.us.bb.gin.ntt.net [129.250.5.8
6]
17	70 ms	77 ms	77 ms  xe-0-0-0-15.r05.lsanca03.us.ce.gin.ntt.net [198.
172.90.170]
18	82 ms	74 ms	71 ms  204.2.170.50
19	82 ms	89 ms	72 ms  events.gravityus.com [128.241.93.53]

[Calebob]

Are you opening the shortcut or the actual file? Make sure to go to Computer-> C drive -> Program files (x86) -> Gravity -> Ragnarok Online. Then select the server you'd like to play. Classic Ragnarok, Ragnarok, or Sakray. Make sure you run as Adim to properly patch.

Also there are a couple ports that need to be opened, if not you will not be able to access the server.

Edited by Calebob, 27 January 2013 - 01:04 PM.

[Axylus]

Are you a new player?

Test whether you can open a connection to the IRO log-in server using telnet:

• If you're using Windows Vista or later, then install the Telnet client.
• Open Command Prompt.
• Enter "telnet 128.241.92.162 6900".
• If the window turns blank, then you have successfully connected to the server.

Edited by Axylus, 14 June 2013 - 08:56 AM.

[Zxen]

Are you opening the shortcut or the actual file? Make sure to go to Computer-> C drive -> Program files (x86) -> Gravity -> Ragnarok Online. Then select the server you'd like to play. Classic Ragnarok, Ragnarok, or Sakray. Make sure you run as Adim to properly patch.

Also there are a couple ports that need to be opened, if not you will not be able to access the server.

I am opening the actual file, and in my original post I said I'm running as administrator.

Are you a new player?

Test whether you can open a connection to the IRO log-in server using telnet:

• If you're using Windows Vista or later, then install the telnet client.
• Open Command Prompt (which is located in the Accessories folder of the start menu).
• Enter "telnet premium-login.1.online.ragnarok.warpportal.net 6900".
• If the window turns blank, then you have successfully connected to the server.

Yup, first time player. The telnet fails. Oh, and I've already swapped out my DNS servers for Google Public DNS, so Comcast failing to resolve the domain is ruled out...can't imagine why it'd be doing that. Any resolution?

Edited by Zxen, 27 January 2013 - 04:05 PM.

[Axylus]

Yup, first time player. The telnet fails. Oh, and I've already swapped out my DNS servers for Google Public DNS, so Comcast failing to resolve the domain is ruled out...can't imagine why it'd be doing that. Any resolution?

Your DNS server definitely isn't at fault because the client doesn't use DNS to connect to the log-in server.

The most likely cause of the problem is that your router is blocking outgoing connections on TCP port 6900, which is one of the two ports that RO uses (the other is outgoing TCP port 4500).

Are you trying to connect from a campus network? Campus networks are infamous for blocking access to all but the most commonly used ports.

Edited by Axylus, 10 April 2013 - 11:58 PM.

[Zxen]

Your DNS server definitely isn't at fault because the client doesn't use DNS to connect to the log-in server.

The most likely cause of the problem is that your router is blocking outgoing connections on TCP port 6900, which is one of the two ports that RO uses (the other is outgoing TCP port 4500).

Are you trying to connect from a campus network? They are infamous for blocking all but the most commonly used ports.

Home router here -- I'll check my ports. Thank you!

[Rueghn]

I am having the same issue.

Rebooted a few times, checked ports, properly forwarded. Ran telnet, got blank screen so I am connecting. I run the client, both from desktop shortcut or from the exe file in my install folder, Launcher says "Failed to connect to patch server."

Anti Virus is Avast, I've disabled security and attempted connection. Still having issue.

Worked fine until right now.

[Axylus]

I am having the same issue.

Rebooted a few times, checked ports, properly forwarded. Ran telnet, got blank screen so I am connecting. I run the client, both from desktop shortcut or from the exe file in my install folder, Launcher says "Failed to connect to patch server."

Anti Virus is Avast, I've disabled security and attempted connection. Still having issue.

Worked fine until right now.

It's not the same problem.

Please test whether you can access the update server using both Internet Explorer and another web browser (or FTP client).