Results 1 to 10 of 28

Hybrid View

  1. #1
    Player
    KisaiTenshi's Avatar
    Join Date
    Sep 2013
    Location
    Gridania
    Posts
    2,775
    Character
    Kisa Kisa
    World
    Excalibur
    Main Class
    White Mage Lv 100
    Quote Originally Posted by Flaeb View Post


    I've done a ton of research on this issue and I am at a lost.
    The problem is not:
    - Avast (free)
    - Internet explorer
    - The Launcher itself

    I installed Windows 10 two days ago, I ran the launcher just fine, it updated FFXIV, and FFXIV DX10 launched just fine.

    This appears to be directly a problem with DNS. I'd suggest you set your DNS to 8.8.8.8 on your Windows PC or router and see if that resolves it. Some ISP's run intercepting DNS (so they can serve custom "not found" pages for whatever the hell reason) so it results in very slow to updates, and that is in fact a change I deliberately make every time it seems like DNS is the culprit.
    (0)

  2. #2
    Player
    dspguy's Avatar
    Join Date
    Aug 2013
    Posts
    1,667
    Character
    Jain Farstrider
    World
    Leviathan
    Main Class
    Marauder Lv 100
    Quote Originally Posted by KisaiTenshi View Post

    This appears to be directly a problem with DNS. I'd suggest you set your DNS to 8.8.8.8 on your Windows PC or router and see if that resolves it.
    That fixed it for me.
    (0)

  3. #3
    Player
    Flaeb's Avatar
    Join Date
    Aug 2013
    Posts
    48
    Character
    Nevva Kenezer
    World
    Balmung
    Main Class
    Black Mage Lv 52
    My DNS is always 8.8.8.8 8.8.4.4. Good thinking though!
    (0)

  4. #4
    Player
    KisaiTenshi's Avatar
    Join Date
    Sep 2013
    Location
    Gridania
    Posts
    2,775
    Character
    Kisa Kisa
    World
    Excalibur
    Main Class
    White Mage Lv 100
    Quote Originally Posted by Flaeb View Post
    My DNS is always 8.8.8.8 8.8.4.4. Good thinking though!
    Interestingly enough, I actually managed to see this error (twice) when I logged out and logged back in later. So this might actually be a DNS cache issue.
    (0)