Printable View
Made a ticket about getting disconnected daily, sometimes twice a day. They fed me the generic sticky and closed my ticket.
I ran a pathping before, came out clean. I would like to run it again because i am not 100% sure i had the right ip for datacenter Zalera.
Also, for security reasons i forward all inbound ports to an unused ip. I would like to know if this security measure conflicts with the game.
Just, please, don't be completely useless ok?
Just in case they ask.....
-=-=-=-=-=-=- FFXIV Information -=-=-=-=-=-=-
MyDocument C:\Users\User\Documents
FINAL FANTASY XIV - A Realm Reborn C:\Program Files (x86)\SquareEnix
FINAL FANTASY XIV - A Realm Reborn Language 1 Region 2
ProxyEnable 0
ProxyServer unspecified
ProxyOverride *.local;192.168.*.*
-=-=-=-=-=-=- System Information -=-=-=-=-=-=-
SYSTEM_OS Windows 8.1 64 bits (6.2, version 9200) (9600.winblue_r9.150322-1500)
SYSTEM_CPU AMD A8-6500 APU with Radeon(tm) HD Graphics (4 CPUs), ~3.5GHz
SYSTEM_CORE_NUM SYSTEM_CORE_LOGIC 4 SYSTEM_CORE_PHYSICS 2
SYSTEM_BIOS BIOS Date: 12/26/13 16:59:57 Ver: 04.06.05
SYSTEM_LANGUAGE français (Paramètres régionaux*: français)
SYSTEM_MEMORY 6091.668MB
SYSTEM_VIRTUAL_MEMORY 2047.875MB
SYSTEM_PAGE_FILE 7115.668MB
SYSTEM_STORAGE C:\ SYSTEM_HARDDISK_DRIVE SYSTEM_TOTALDISC_SPACE 931.168GB SYSTEM_FREEDISC_SPACE 699.027GB
SYSTEM_DIRECTX_VERSION DirectX 11
SYSTEM_GRAPHICS NVIDIA GeForce GTX 650
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY1
SYSTEM_GRAPHICS_CHIP GeForce GTX 650
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 1987.684 MB
SYSTEM_GRAPHICS_SHARED_VRAM 2048.309 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1600 x 900 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
SYSTEM_GRAPHICS_DRIVER_VERSION 9.18.0013.5012
SYSTEM_GRAPHICS_DRIVER_DATE 2015-04-08 20:58:18
SYSTEM_GRAPHICS_DRIVER_LANGUAGE Anglais
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_GRAPHICS NVIDIA GeForce GTX 650
SYSTEM_GRAPHICS_DEVICE \\.\DISPLAY2
SYSTEM_GRAPHICS_CHIP GeForce GTX 650
SYSTEM_GRAPHICS_MAKER NVIDIA
SYSTEM_GRAPHICS_VRAM 1987.684 MB
SYSTEM_GRAPHICS_SHARED_VRAM 2048.309 MB
SYSTEM_GRAPHICS_DAC Integrated RAMDAC
SYSTEM_GRAPHICS_DISPLAY_MODE 1360 x 768 (32 bit) (60Hz)
SYSTEM_GRAPHICS_DRIVER nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
SYSTEM_GRAPHICS_DRIVER_VERSION 9.18.0013.5012
SYSTEM_GRAPHICS_DRIVER_DATE 2015-04-08 20:58:18
SYSTEM_GRAPHICS_DRIVER_LANGUAGE Anglais
3.0
SYSTEM_GRAPHICS_PIXEL_SHADER 3.0
SYSTEM_GRAPHICS_VERTEX_TEXTURE SYSTEM_SUPPORT
SYSTEM_SOUND 8020919-4 (NVIDIA High Definition Audio)
SYSTEM_SOUND_DEVICE_ID {1DCE4065-F1A8-4078-B7F3-B9C486F08B6B}
SYSTEM_SOUND_DEVICE_NAME nvhda64v.sys
SYSTEM_SOUND_DRIVER_VERSION 1.03.0033.0000
SYSTEM_SOUND_DRIVER_LANGUAGE Anglais
SYSTEM_SOUND_DRIVER_DATE 2015-04-08 20:58:18
SYSTEM_INPUT {6F1D2B60-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Souris
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 3 SYSTEM_GAMEPAD_BUTTON 8 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {6F1D2B61-D5A0-11CF-BFC7444553540000}
SYSTEM_INPUT_NAME Clavier
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 128 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {627B1FC0-99A4-11E4-8001444553540000}
SYSTEM_INPUT_NAME 2.4G RF Keyboard & Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {628001C0-99A4-11E4-8002444553540000}
SYSTEM_INPUT_NAME 2.4G RF Keyboard & Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {B1A90170-78E3-11E4-8002444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 3 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {628001C0-99A4-11E4-8003444553540000}
SYSTEM_INPUT_NAME 2.4G RF Keyboard & Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {B1ACF910-78E3-11E4-8003444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 19 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {B1ACF910-78E3-11E4-8004444553540000}
SYSTEM_INPUT_NAME USB Keyboard
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {628001C0-99A4-11E4-8004444553540000}
SYSTEM_INPUT_NAME 2.4G RF Keyboard & Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 0 SYSTEM_GAMEPAD_FOV 0
SYSTEM_INPUT {628001C0-99A4-11E4-8005444553540000}
SYSTEM_INPUT_NAME 2.4G RF Keyboard & Mouse
SYSTEM_INPUT_REMARKS SYSTEM_GAMEPAD_AXIS 0 SYSTEM_GAMEPAD_BUTTON 573 SYSTEM_GAMEPAD_FOV 0
-=-=-=-=-=-=- Application Information -=-=-=-=-=-=-
Technical Support - Mozilla Firefox
-=-=-=-=-=-=- Install Information -=-=-=-=-=-=-
Adobe Flash Player 17 NPAPI
Battle.net
Diablo III
FileZilla Client 3.10.3
Gnaural ver. 1.0.20110606
Malwarebytes Anti-Malware version 2.0.4.1028
Mozilla Firefox 37.0.2 (x86 en-US)
Mozilla Maintenance Service
Origin
Steam
Torchlight II
Age of Wonders III
Joe Dever's Lone Wolf HD Remastered
FINAL FANTASY VII
Sid Meier's Civilization V
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.50727
MSXML 4.0 SP3 Parser
Motorola Device Manager
FINAL FANTASY XIV - A Realm Reborn
AMD OverDrive
Synctunes Desktop
Mumble 1.2.8
Microsoft Visual C++ 2005 Redistributable
ImpôtRapide 2014
Apple Software Update
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.21005
Realtek Ethernet Controller Driver
Motorola Device Software Update
OpenOffice 4.1.1
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
Google Update Helper
Catalyst Control Center InstallProxy
Apple Application Support (32 bits)
RssBandit
The Sims™ 3
Dragon Age™ : Inquisition
Microsoft WSE 3.0 Runtime
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
-=-=-=-=-=-=- Proccess Information -=-=-=-=-=-=-
C:\Program Files (x86)\Motorola Mobility\Motorola Device Manager\MotoHelperAgent.exe 00000514
C:\Program Files (x86)\Mozilla Firefox\firefox.exe 00000744
C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\boot\ffxivsysinfo.exe 00000570
wait...what? Think the word for that is "overkill"? Not to mention the potential to knacker things up on a large scale.Quote:
Also, for security reasons i forward all inbound ports to an unused ip.
A decent firewall/AV solution, and a router with decent NAT is pretty much all you need if you use a little common sense when browsing the internet (in other words, don't click on pop-up ads or strange things from places like Facebook). The key is to not open the outbound session to malicious content in the first place.
Disable the port forwards, as well ads UPNP on the router (has been known to cause issues in the past). Setup your firewall/antivirus and such properly (add the appropriate exceptions for the game's executables and/or IP addresses/DNS names). That should address any localized issues. Port forwarding should NOT be needed in a typical home environment--that is more for dealing with more advanced security schemes typically found in places like work and universities. After that, if there are still connectivity problems you may need to investigate routing issues.
And BTW, pathping will mask some details that may be more helpful in narrowing down where congestion may be creeping into play and causing issues. More standard tools along the lines of tracert and ping will provide a range of values so you can better gauge the typical and min/max response times for hops. That kind of information will better help you identify/capture things like intermittent spikes and such that may interfere with the game's data streams. FFXIV runs on roughly a 300ms boundary and not 2000 (the limit most tools use to flag a time-out/retrans condition).
Thanks for the reply.
I'm a bit (very) paranoid. If it actually works with the port forwarding i'd like to keep using it.
I got an ip for zalera server but the pathping doesn't work. (with/without router) I called my isp about it and even though they told me the support service only covered true/false connection status, they helped me with the problem. Turns out my server doesn't return pings.
The guy also told me my router was ancient. I think it's over 5 years old. I'm using a non wifi router i had before, to see if it helps at all.
I'm sure they mean well but i usually got disconnected at a random point during the whole day. I feel that's a bit too long for me to play without a router. Also i did read the exact same thing before sending my ticket. It seems a bit lazy on their part to just copy paste a generic walkthrough. I asked in the ticket for an address to pathping and if my port forwarding would interfere with the game. They completely did not answer my questions.
If you weren't getting a ping response from the IP, then you very likely had the wrong IP. If you got it from the ARRStatus page (which still shows 199.91.189.57), that IP was taken out of the pool with the infrastructure changes back around the first of April. Need to get the actual IP your client is using when logged fully into the game. You can get that from either Resource Monitor (resmon from the search/run box) or by running netstat in a CMD prompt window.
As for the copy/pasta responses, it is actually fairly common practice to do so as a first response. There unfortunately is a large percentage of people that don't go through the FAQ's that often cover the more common issues, so it isn't that uncommon to get a form-letter style reply if your support request initially looks like those same more common issues. A long time ago, whenever you called in to TWC, the menus always made you walk through the process of resetting your network devices before you talked to anyone...was very annoying. After a lot of complaints, they eventually added an option for you to tell the robot that you had already reset everything and was still having connectivity issues, and then it would move on to the options that actually get someone on the phone. These tactics are far more common fair than many may realize. With SE's support ticket system, you may get a follow up email from an actual person a few days later if it is determined to be worthy of further review and someone has been assigned to review the ticket further.
A decent firewall and a router's NAT is going to provide you basically the same level of protection as what you are trying to do by shunting everything to a fake port (unless you set up one IP as a DMZ of course). Essentially, they are doing the same thing. Your private IP's can't be routed across the internet, only your public IP can be routed to directly from the internet. You need rules specifically set to forward unsolicited inbound traffic to the IP's on your private network--otherwise they will simply get dropped.
If you initiate an outbound session first, then traffic can flow back along the same path though...which is a function of the Network Address Translation's design (NAT). So, if your client reaches out to say 199.91.189.31 and sets up the session with SE on port 54992, then NAT on the router will direct traffic coming back from 199.91.189.31:54992 to come back to that system, but not traffic from any other IP on port 54992 so long as that session remains established. It will also not allow any port traffic on 54992 to go to any other system either, it will only route it back down the path it initially took as an outbound connection. If your firewall/antivirus is not set to block the communications from that connection or the program requesting the connection, then everything goes through without a hitch. If you set a port forwarding rule to send all port 54992 traffic to a specific system, than ALL traffic coming in with that port ID is forwarded to that system--regardless of how/where the connection originated. If there is no firewall rule to block unsolicited traffic, than those packets get to your system and leave you open to attack across that port from any IP in the world.
Another problem with blocking the ports by default is you may not capture all the port ID's that need to be opened for any given service, regardless of where it originated. So if you have something trying to legitimately use say port 55924 and your rule is causing that traffic to go to a dead IP, your system may still reach out to the server just fine...but the inbound traffic may get forwarded to the dead IP and you never complete the acknowledgment, which will eventually cause a dropped session. Remember that port forwarding is a hard and fast rule...point of origin does not matter. With NAT and a stateful inspection firewall, you basically have a sort of automated port flow control--you initiate the outbound connection and they work together to keep only the traffic from that source coming back in.
Additionally, many locally installed firewalls will also provide the extra layer of protection that decides if a program is allowed to reach out to the internet in the first place (by default, usually all programs are blocked unless you allow a default list like Microsoft products and other known safe programs). Many of these types of firewall's will also ask you if you want to allow a new program to access the internet, and if you don't set the option to remember your response then it will continue to ask you every time it tries to open a new session with the internet. So the combination of the two (firewall and router) is typically plenty strong enough in most cases, and more or less idiot proof to some degree.
The age of the router may be a cause for concern. After a while, the capacitors start to dry out and voltage regulation can get skewed...which may cause other components to wear down faster or cause some odd anomalies with the device. Not uncommon for some brands to need to be replaced annually or at best every 3 years or so in some regions/implementations. Sometimes it actually isn't the router having issues, but the power supply (so many come with a DC adapter these days, and they tend to overheat easily). Commercial routers can be less susceptible to these issues for various reasons (better components, better cooling solutions, etc.). But not uncommon for the home-use market to get a bit unreliable after about a 3 year period or less in some cases.
So yeah.. it sounds like you potentially have some problems in your localized topology. May need to simplify your network environment a bit to see if things behave better. Possibly even trying a direct connect to the modem for a short while. That's usually a quick and dirty fix to rule out a flakey/ill-configured router. Just make sure to have something installed on the system for security first though--Anti-Virus and Firewall, even if it is just the Windows Firewall (but make sure they are set to allow the FFXIV executables to access the internet though).