Version Update failed

[Hyan]

Okaaayyy so I moved to a new apartment and now it won't let me update the game anymore. I get a

11000 Version Update Failed error

every time I try to start the updater. This happens on two different connections so I'm not sure if it's related to it. Torrents download fine, internet works fine, but this error keeps popping up.

I wonder if my internet settings are blocking it or something?

[Xanthe]

Beta 3 is over. The update servers are probably offline until Open Beta starts.

[Hyan]

This happened while Beta 3 was still ongoing.. so I'm not entirely convinced about it :X

[Ratatapa]

I was able to update on another PC today

[Gokulo]

I have tried running the client at random times after P3 ended and sometimes it would go through and sometimes it would give this error. I guess they're just playing with servers when beta is offline

[Buddy]

So there is not an actual update yet other than the one's that were needed for P3?

[Hyan]

I'm just wondering if there are settings I need to enable or something. Phpp DHCP Idk something like that?

[Xanthe]

It wouldn't hurt enabling uPnP on your PC and router if you haven't already. That handles all of the ports business more simply than setting up port forwarding rules.

[Hyan]

I think it is enabled on my PC... but is there something I have to do to my router as well?

[Metafox]

I believe some routers have some kind of security features that will limit peer-to-peer connections like that. I know my mother's router had an issue where torrent downloads were very slow, but upon disabling the feature, the torrents worked as normal. My own router doesn't have anything like that so I can't give you specific examples. I'm sure you've tried already, but try looking around in your router for any extra security features.

[Hyan]

Yeah, it's odd, that normal torrent downloads work fine (although some files are slow even with lots of seeders and dl'ers) but XIV's just refuses to load.

Just gonna utorrent the OB if it comes down to it.

[Xanthe]

Most newer routers have a setting for uPnP (Universal Plug and Play). It should be grouped with other port-related settings, or possibly with QoS (Quality of Service). If all else fails, you can forward TCP and UDP ports 50000-65000 to the PC you're downloading to. The most likely reason your other torrents work fine while FFXIV fails is you have a specific port set in your torrent client and are forwarding that on your router, but FFXIV pick a random port in the range I mentioned above.

[Hyan]

I can't access my new router's settings, fml.

Hm. Would it help if I changed the port from XIV config?

...

Well, I changed 55296 to 55551 and it connects now. Magic and miracles.

[Cooleko]

who is your provider? some are still throttling torrents and closing ports. you have to regularly switch ports if you experience the isp cutting you off.

[Hyan]

Nah it's fine now, I doubt my provider cares :D

[Buddy]

I don't know if this has been said, as I looked for another new thread but I was able to download 2 updates/patches today. One was dated from 8.27.2010 and the other is today 8.30.2010. If this is old news please disregard.

[Ratatapa]

It's been said first was the Boot and the 2nd was the version update client

[Fayttt]

Getting this version update failed too now. Forwarded ports 50000-65000 on my router on both UDP and TCP and tried opening beta config and setting port to 55551 instead of 55296 and still not working. I've got no idea how to enable uPNP on my PC though; maybe that's it? I'm on win 7.
Edit: Oh, is this uPNP thing the uPNP port mapping in the config? If so, I've got it set to automatic so I assume it should work.
I never had to mess with ports and all this before but I'm kind of shitting bricks about having to re download the entire client again if this update keeps failing.

[Hyan]

Free translation to finglish

control panel > web and internet > web and sharing center > additional settings > searching web turned on. (For uPNP)

Something like that.

[Fayttt]

Found it, turned it on, still not working.
This is dumb.