13 replies to this topic

[Lyrage]

I have this friend of mine that can't patch his iRO client. I tried giving him a copy of my own updated client and he was able to log in just fine. But after this week's maintenance, he still can't patched his client on his own.

At first:

http://i.imgur.com/zIvfZd0.jpg

After 10 minutes of waiting:

http://i.imgur.com/cl9Jqdd.jpg

I hope you can help us.

[DrAzzy]

In IE, attempt to go to ftp://ropatch1.gravityus.com ("success" is getting a list of folders, "failure" is any error message)

If that succeeds, it's almost certainly firewall settings blocking the patcher from connecting.

If that fails, try the same link in Firefox or Chrome (if using chrome, you must go to settings, advanced, and uncheck "Use a web service to help with navigation errors", otherwise it will hide the useful error message and instead show you a useless page designed to "help")

If it works in FF/Chrome, it's an IE settings issue. Check if IE is set to be in offline mode.

If it doesn't work in FF/Chrome, post the error message you get here.

Edited by DrAzzy, 30 May 2013 - 09:09 AM.

[Lyrage]

It works in IE, we even managed to download the patch files manually. However, when my friend pasted the downloaded files to his RO folder, nothing happens. He still can't patch nor log-in.

[Axylus]

That's weird.

[DrAzzy]

If the patcher can't connect to the ftp server, it won't patch with manually downloaded files. I think it needs to see the directory listing, and thus the file sizes, so it can check if the files are the correct ones and finished downloading.

Check your firewall settings.

[Lyrage]

Sorry for the late reply, I went to sleep.

Hmm... He already allowed RO in his firewall, including the inbound and outbound rules. Could this be an ISP problem?

[Lyrage]

Sorry double post.

Edited by Lyrage, 30 May 2013 - 08:18 PM.

[DrAzzy]

Sorry for the late reply, I went to sleep.

Hmm... He already allowed RO in his firewall, including the inbound and outbound rules. Could this be an ISP problem?

No - if he can access it in any browser, that demonstrates that nothing upstream is blocking it. And since it works in IE... (the patcher just calls IE), I don't understand how it could fail to work for the patcher, unless there was a firewall blocking the patcher (as a "program control" measure). I don't know what else it could be at this point.

Edited by DrAzzy, 31 May 2013 - 05:03 AM.

[Lyrage]

Nooooooooooooooo...

We just want to play.

[Axylus]

I could take a look using TeamViewer if your friend wants.

[Lyrage]

Will it be okay if I'll ask him later instead? He's off to church now.

Edited by Lyrage, 31 May 2013 - 08:32 PM.

[Lyrage]

Update! My friend agreed to it.

Shall I PM you the ID and password?

[Axylus]

Update! My friend agreed to it.

Shall I PM you the ID and password?

See the private message that I've just sent you.

[Axylus]

For the record, I investigated the problem using TeamViewer, but unfortunately wasn't able to fix it. This is what I observed:

• The updater always stalled after it issued a PASV command and the server then responded with code 227 ("entering passive mode").
• Strangely, it was possible to access the update server using Internet Explorer and the textual user interface ftp application, but it wasn't possible to access the server using either Chrome or Firefox.
• Disabling Windows Firewall had no effect, and there didn't appear to be any other firewall software installed.
• Changing Internet Explorer's FTP settings had no effect.
• Resetting Internet Explorer's configuration had no effect.
• Disabling Avast! Free Antivirus had no effect.

The following is a log of the updater's FTP session:

USER anonymous
331 Anonymous access allowed, send identity (e-mail name) as password.
PASS IEUser@
230-Welcome to the WarpPortal Ragnarok Online Patch Service
	Directory has 144,298,504,192 bytes of disk space available.
230 User logged in.
CWD /patch
250 CWD command successful.
TYPE A
200 Type set to A.
PASV
227 Entering Passive Mode (128,241,93,38,230,29)
.

Edited by Axylus, 01 June 2013 - 05:09 AM.