Results 1 to 8 of 8

Hybrid View

  1. #1
    Moderator Dynratygus's Avatar
    Join Date
    Oct 2018
    Posts
    2,853
    Good evening and thank you for posting in the Final Fantasy XIV Technical Support Forums.

    How long have you been having this issue? Are you connected directly to the router? Also what have you tried so far to alleviate the errors?

    Hope to see you online !
    (0)

  2. #2
    Player
    Vicvictorw's Avatar
    Join Date
    May 2019
    Posts
    10
    Character
    Vivivachi Wawavachi
    World
    Famfrit
    Main Class
    White Mage Lv 70
    Quote Originally Posted by Dynratygus View Post
    Good evening and thank you for posting in the Final Fantasy XIV Technical Support Forums.

    How long have you been having this issue? Are you connected directly to the router? Also what have you tried so far to alleviate the errors?

    Hope to see you online !
    Hello!

    The issue has been observed for less than a week, as my server transfer is very recent. Before the transfer, this was not a problem at all.

    I am directly connected to my router, and I can't tell if anything I do makes a difference due to the random nature of the disconnects- they don't seem to be prompted by any nearby entities or matter whether I'm in an instance. I have not made any major adjustments to my configurations to try and troubleshoot.
    (0)

  3. #3
    Moderator Einmimiria's Avatar
    Join Date
    Nov 2017
    Posts
    2,510
    Thank you for the reply Vicvictorw.

    Is it always that hop that has a failed ping? Or do any others do the same thing?

    It looks like you have some instability along your route (some hops spike in latency then return to normal). Unfortunately, there isn't much that can be done about this. I do have some suggestions on how to strengthen your home network:

    1) Use a wired connection as opposed to wireless.

    2) Make sure your anti-virus/firewall has the appropriate exceptions for Final Fantasy XIV.

    3) Check the following Port Ranges on your router/modem to ensure that they have been opened:
    ▼TCP
    54992 through 54994,
    55006 through 55007,
    55021 through 55040
    Your ISP can open these ports for you.

    4) The game will use the Internet Explorer web browser to connect to the internet. Open Internet Explorer, then open the "Tools" setting, go to "Internet Options" and adjust the following settings:
    - Under the "General" tab, please delete ALL browser history.
    - Under the "Security" tab, please move the slider to the lowest possible settings or no higher than "Medium"
    - Under the "Privacy" tab, click “Advanced” and select ‘Accept’ under both First Party and Third Party Cookies.
    - Under the "Advanced" tab, please make sure that "Allow software to run or install even if signature is invalid" is CHECKED.
    - Make sure that all SSL and TLS (EXCEPT SSL 3.0) are CHECKED. [SSL 3.0 should be UNCHECKED]
    - Hit "Apply" to save the settings, and then "OK, to close the Internet Options menu.
    - Right-Click on the FFXIV launcher icon and select "Properties"
    - Go to the "Compatibility" tab, and change the compatibility mode to "Windows 7"
    - Hit "Apply", then "OK" to save the changes.
    - Please RESTART your PC now. Once your PC has been restarted, Right-Click the FFXIV launcher icon once more and select "Run as Administrator"

    We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!
    (0)

  4. #4
    Player
    Vicvictorw's Avatar
    Join Date
    May 2019
    Posts
    10
    Character
    Vivivachi Wawavachi
    World
    Famfrit
    Main Class
    White Mage Lv 70
    So my router's configuration isn't as straightforward as simply allowing incoming ports- hopefully I've configured this correctly referencing my NETSTAT information:
    https://i.imgur.com/x6Dobec.png

    Will implement the rest of these suggestions (I'm already on a wired connection) and will report back.

    The tracert, if a ping does fail, it is always on that specific node. It is not consistent.

    Code:
    Tracing route to 204.2.229.10 over a maximum of 30 hops
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2    19 ms    15 ms    16 ms  cpe-174-106-144-1.ec.res.rr.com [174.106.144.1]
      3    22 ms    31 ms    37 ms  cpe-174-111-064-212.triad.res.rr.com [174.111.64.212]
      4    22 ms    24 ms    23 ms  cpe-024-025-055-122.ec.res.rr.com [24.25.55.122]
      5    31 ms    23 ms    30 ms  gig5-0-0.chrlncsa-rtr1.carolina.rr.com [24.93.64.20]
      6    34 ms    31 ms    37 ms  bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
      7    50 ms    37 ms    28 ms  66.109.5.117
      8    30 ms    32 ms   149 ms  38.142.221.105
      9    32 ms    32 ms    32 ms  ae-58.r06.asbnva02.us.bb.gin.ntt.net [129.250.8.121]
     10    32 ms    64 ms    41 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
     11   103 ms   104 ms    97 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
     12   101 ms    98 ms   104 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
     13   104 ms   105 ms   168 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
     14   101 ms   104 ms   106 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
     15   100 ms   101 ms   104 ms  204.2.229.234
     16   104 ms    98 ms   102 ms  204.2.229.10
    
    Trace complete.
    
     
    
    Tracing route to 204.2.229.10 over a maximum of 30 hops
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2    10 ms    15 ms    16 ms  cpe-174-106-144-1.ec.res.rr.com [174.106.144.1]
      3    25 ms    31 ms    25 ms  cpe-174-111-064-212.triad.res.rr.com [174.111.64.212]
      4    28 ms    17 ms    20 ms  cpe-024-025-055-122.ec.res.rr.com [24.25.55.122]
      5    24 ms    39 ms    30 ms  gig5-0-0.chrlncsa-rtr1.carolina.rr.com [24.93.64.20]
      6    26 ms    39 ms    42 ms  bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
      7    30 ms    33 ms    28 ms  66.109.5.117
      8    33 ms    39 ms    29 ms  38.142.221.105
      9    29 ms    29 ms    28 ms  ae-58.r06.asbnva02.us.bb.gin.ntt.net [129.250.8.121]
     10    31 ms    32 ms    34 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
     11   101 ms    98 ms   102 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
     12   105 ms   103 ms    99 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
     13   146 ms   105 ms   105 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
     14   105 ms    98 ms   101 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
     15   106 ms    98 ms    99 ms  204.2.229.234
     16   101 ms   102 ms    99 ms  204.2.229.10
    
    Trace complete.
    
     
    
    Tracing route to 204.2.229.10 over a maximum of 30 hops
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2    69 ms    15 ms    13 ms  cpe-174-106-144-1.ec.res.rr.com [174.106.144.1]
      3    38 ms    31 ms    29 ms  cpe-174-111-064-212.triad.res.rr.com [174.111.64.212]
      4    16 ms    22 ms    23 ms  cpe-024-025-055-122.ec.res.rr.com [24.25.55.122]
      5    27 ms    23 ms    31 ms  gig5-0-0.chrlncsa-rtr1.carolina.rr.com [24.93.64.20]
      6    35 ms    29 ms    30 ms  bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
      7    32 ms    26 ms    30 ms  66.109.5.117
      8    29 ms    33 ms    29 ms  38.142.221.105
      9    30 ms    31 ms    28 ms  ae-58.r06.asbnva02.us.bb.gin.ntt.net [129.250.8.121]
     10    35 ms    32 ms    28 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
     11    98 ms   107 ms    98 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
     12   104 ms    98 ms   104 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
     13   105 ms   106 ms   131 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
     14   103 ms   103 ms   103 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
     15   127 ms   104 ms   107 ms  204.2.229.234
     16   104 ms    98 ms    99 ms  204.2.229.10
    
    Trace complete.
    
     
    
    Tracing route to 204.2.229.10 over a maximum of 30 hops
    
      1    <1 ms    <1 ms    <1 ms  192.168.0.1
      2    16 ms    13 ms    17 ms  cpe-174-106-144-1.ec.res.rr.com [174.106.144.1]
      3    27 ms    30 ms    32 ms  cpe-174-111-064-212.triad.res.rr.com [174.111.64.212]
      4    23 ms    32 ms    33 ms  cpe-024-025-055-122.ec.res.rr.com [24.25.55.122]
      5    27 ms    30 ms    21 ms  gig5-0-0.chrlncsa-rtr1.carolina.rr.com [24.93.64.20]
      6    47 ms    32 ms    38 ms  bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
      7    44 ms     *       34 ms  66.109.5.117
      8    28 ms    26 ms    34 ms  38.142.221.105
      9    27 ms    39 ms    35 ms  ae-58.r06.asbnva02.us.bb.gin.ntt.net [129.250.8.121]
     10    31 ms    25 ms    32 ms  ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
     11    98 ms   100 ms   102 ms  ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
     12   100 ms   107 ms   100 ms  ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
     13   108 ms   102 ms   100 ms  ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11]
     14   103 ms   108 ms   110 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
     15   101 ms   101 ms    99 ms  204.2.229.234
     16   102 ms   106 ms   102 ms  204.2.229.10
    
    Trace complete.
    (0)
    Last edited by Vicvictorw; 05-11-2019 at 08:17 AM.