Forum Settings
       
This Forum is Read Only

Error (40000)3Follow

#1 Oct 16 2010 at 6:27 PM Rating: Good
Scholar
16 posts
I keep getting an "Error (40000)3" error, then it goes to a lobby timeout error. This has happened like 5 times today. I've never had this issue before. I have to restart the game to make it work. I can only play for about 10 minutes before this happens.

Anyone else have this problem? Or am I just screwed with how bad this game is and all its bugs?
#2 Oct 16 2010 at 6:39 PM Rating: Good
**
472 posts
I have seen that exact error, but it was a never persistent error that would happen all of the time.
#3 Oct 19 2010 at 7:50 PM Rating: Decent
Scholar
16 posts
It's happening all the time...wtf is the problem?
#4 Oct 19 2010 at 8:44 PM Rating: Decent
Scholar
*
191 posts
So this is a recent problem then?
As in, it just started today or a couple days ago?

I've occasionally seen this. Usually happens when SE is messing with the servers especially
in the days before maint or a patch.
____________________________
FFXI:
Elvaan/Cerberus/Rank10 x 3/Sky/Sea
Blm80/Bst80/Rdm75/Blu75/Whm75/Rng75
WW100+3/Cook100+2/CC94+2/Alchemy87+2/Fishing61/Rest60
Owner Star Nursuries

FFXIV:
Elezen LvL37/Bodhum
Con24/Thau18/Weav24/Carp17/Gold21/Smith17/Alchem17/Leather17/Bot9/Min6
#5 Oct 19 2010 at 8:49 PM Rating: Decent
Scholar
16 posts
It's been happening everyday for me lately. Tonight it happened a minute after I logged in. Right now I've been fine for an hour. Sometimes it'll happen when I login (1-10 minutes), other times it'll happen when I'm doing a leve. It's really random and I have no idea what the problem is. My PC is fine with everything else I do, just FFXIV causes me problems.

I've heard some other people having issues, but nothing that happens as frequently as I have. I know the game is buggy, but this buggy?

As soon as I summited this, it happened again. I've tried switching RAM as well, same issue. I can barely play this game. Starting to look like the biggest waste of $75 ever...

Edited, Oct 19th 2010 10:51pm by IceDogg
#6 Oct 20 2010 at 2:32 PM Rating: Decent
Scholar
16 posts
It keeps happening...played for about an hour, (40000)3 error again. After that I get...

"13001 The lobby server connection has encountered an error.
Error Code: 0
Status: O
TIMEOUT"

That always follows the (40000)3 error. I have to close the game, relaunch, then play it again, until the error happens again, the repeat.

Any help?
#7 Oct 20 2010 at 10:54 PM Rating: Decent
**
529 posts
This has happened to me now 3 times in a row. Makes no sense, I've had no issues like this ever, and its not my internet because it never loses connection to the internet.
____________________________

#8 Oct 22 2010 at 7:52 PM Rating: Decent
Scholar
16 posts
I've got this error twice again today. Thought it was for one area, but it's happening in others now. Happened a few hours in, and just happened again not even 5 minutes into playing the game.

Does anyone know what this error means? How can I fix it? etc? This is really getting on my nerves. On the brink of cancelling.
#9 Oct 22 2010 at 10:37 PM Rating: Decent
Scholar
16 posts
Anyone know what this error means? It says nothing, I've looked it up online on their support side, shows nothing. I wanna fix this...
#10 Oct 23 2010 at 10:16 AM Rating: Decent
2 posts
Same Error I click through the errors and they send me back to the login screen.
#11 Oct 23 2010 at 6:55 PM Rating: Good
I've been dealing with this error for the first time tonight, and it has happened 4 times.

If anyone in my LS is reading this, I'm sorry, but I won't be logging in anymore tonight. Too much hassle. Hopefully I don't have this crap happen in the future, but tonight isn't my night I guess.
____________________________
#12 Oct 23 2010 at 6:57 PM Rating: Default
<<
____________________________


#13 Oct 23 2010 at 7:55 PM Rating: Decent
Scholar
24 posts
Not to say it's never happened to me before, it surely has; but since last update it is ridiculous, to the point that I can't stay in a party and keep failing my leves. disconcerting
#14 Oct 23 2010 at 10:21 PM Rating: Decent
Scholar
16 posts
It's been only happening the last week or two. It's so random that I can't really do anything. I constantly fail leves, have to close/re-open the game. I'm awaiting on an open ticket from support to see if they can help.
#15 Oct 25 2010 at 3:02 PM Rating: Decent
Scholar
16 posts
Dear Customer,

Regarding your request for technical support. Please find your answer below.

If you are receiving the error message "Final Fantasy XIV has stopped running" or experiencing errors installing and/or starting up the game, this may be
due to incompatible hardware or your current drivers for your graphics card, current version of Windows, and current version of DirectX are not up to date.

Unfortunately your graphics card [NVIDIA GeForce 8800 Ultra] is not supported by Square Enix to run Final Fantasy XIV as it is a mobile and/or integrated graphics
card. Please refer to the minimum and recommended system requirements (developed on desktop platforms using dedicated graphics cards) as listed below:

Minimum system requirements
OS - Windows XP SP3, Vista 32/64 SP2, Windows 7 34/64
Processor - Intel Core2 Duo (2.0GHz), AMD Athlon X2 (2.0GHz)
Memory - Windows XP (1.5GB), Windows Vista/7 (2GB)
Storage - Install (15GB), Download (6GB)
Video - NVIDIA GeForce 9600 Series (512MB VRAM or equivalent), ATI Radeon HD 2900 (512MB VRAM or equivalent)
Sound - DirectSound compatible sound card (Direct X9.0c)
Resolution - 1280x720; 32 bit
DirectX - DirectX9.0c

Recommended system requirements
OS - Windows 7 32/64
Processor - Intel Core i7 (2.66GHz) or faster
Memory - 4GB or more
Video - NVIDIA GeForce GTX 460 (768MB VRAM or equivalent)

I got that as a response. Odd how a 8800 Ultra is faster than a 9600. I'm getting sick of this company.
#16 Oct 26 2010 at 1:05 PM Rating: Decent
Scholar
16 posts
I got some help from calling them. They said the "(40000)3" is a general connectivity error. They also said the game is recommended to be run directly from your cable/dsl modem, and not a router, which I thought was odd. They said to do the following port forwarding

tcp = 2580 10010, 40043, 50000-65535

udp = 50000-65535

upnp enabled (router)

I just did all that and will see if it fixes the issue. Just a heads up for anyone who has this problem. Just call them, online support is terrible.
#17 Oct 26 2010 at 1:14 PM Rating: Excellent
Quote:
Unfortunately your graphics card [NVIDIA GeForce 8800 Ultra] is not supported by Square Enix to run Final Fantasy XIV as it is a mobile and/or integrated graphics
card.


Hate to say it, but this probably is your problem here. For the most part (there are some exceptions), laptops cannot handle FFXIV properly. Mobile/integrated graphics cards are insufficient for the game. Even most of the "gaming laptops" aren't going to cut it. Again, there are some exceptions as some of the forum members here have pointed out in the past... but not many.


Although someone mentioned that Error (40000)3 is a general connectivity error, so it sounds like your system specs aren't tied into this particular issue. Port forwarding is needed if you're running through a router. Read this for more info.
#18 Oct 26 2010 at 10:04 PM Rating: Decent
Scholar
16 posts
Osarion, Goblin in Disguise wrote:
Quote:
Unfortunately your graphics card [NVIDIA GeForce 8800 Ultra] is not supported by Square Enix to run Final Fantasy XIV as it is a mobile and/or integrated graphics
card.


Hate to say it, but this probably is your problem here. For the most part (there are some exceptions), laptops cannot handle FFXIV properly. Mobile/integrated graphics cards are insufficient for the game. Even most of the "gaming laptops" aren't going to cut it. Again, there are some exceptions as some of the forum members here have pointed out in the past... but not many.


Although someone mentioned that Error (40000)3 is a general connectivity error, so it sounds like your system specs aren't tied into this particular issue. Port forwarding is needed if you're running through a router. Read this for more info.


I'm using a desktop GeForce 8800 Ultra, it isn't a mobile or integrated graphics card at all. It's still a decent card for it's age.

I just got the error again, so I'm not sure what to do. This game is nothing but trouble lately.
#19 Oct 26 2010 at 10:16 PM Rating: Decent
33 posts
I have been getting this error as well today..

regardless of port forwarding there is something they are doing on their end to cause this.. the mass amount of people across several forums are reporting this problem starting within the last 24 hours..

#20 Oct 26 2010 at 10:32 PM Rating: Decent
Scholar
16 posts
They said the game is meant to be run "directly from your cable/dsl modem to your computer, not with a router" that amazed me. I've never heard of anyone doing something like that. I've been getting it 2-3 times a day the past few weeks. It's hard to barely play.
#21 Oct 26 2010 at 10:45 PM Rating: Good
*
228 posts
IceDogg wrote:
They said the game is meant to be run "directly from your cable/dsl modem to your computer, not with a router" that amazed me. I've never heard of anyone doing something like that. I've been getting it 2-3 times a day the past few weeks. It's hard to barely play.



This was an official response? Was it from CS? I find that.. I'm not even sure what to make of that. Who doesn't have an in-house network these days o.O;

On a side note, I do run a network and haven't had any errors like this as of yet.
____________________________
Quote:
Pikko wrote:
Quote:
sideways wrote: (really Pikko?)

Oh go stuff that thread up your ***. Did you even READ that post?
[...]
I mean, excuuuuse me for trying to make people PLAY NICE.


^ Second best forum mod smack down *ever*.
#22 Oct 27 2010 at 8:42 AM Rating: Decent
Scholar
16 posts
mistrik wrote:
IceDogg wrote:
They said the game is meant to be run "directly from your cable/dsl modem to your computer, not with a router" that amazed me. I've never heard of anyone doing something like that. I've been getting it 2-3 times a day the past few weeks. It's hard to barely play.



This was an official response? Was it from CS? I find that.. I'm not even sure what to make of that. Who doesn't have an in-house network these days o.O;

On a side note, I do run a network and haven't had any errors like this as of yet.


Yes, I got that over the phone from a guy on customer support. That's why he gave me the ports to forward. Since the game wasn't "designed" for routers, I had to do that. I was shocked too, about to laugh or ask stupid questions. Call them yourself and ask.
#23 Oct 27 2010 at 8:57 AM Rating: Decent
38 posts
if its that general error, there is something i have noticed also

If the client crashes and i log back in, i can go through to chracter selection, as soon as i select my character i get this error

What i find though was by now logging out properly, then back in again this seems to reset my character to being available again.
#24 Oct 27 2010 at 9:17 AM Rating: Good
***
1,606 posts
mistrik wrote:
IceDogg wrote:
They said the game is meant to be run "directly from your cable/dsl modem to your computer, not with a router" that amazed me. I've never heard of anyone doing something like that. I've been getting it 2-3 times a day the past few weeks. It's hard to barely play.



This was an official response? Was it from CS? I find that.. I'm not even sure what to make of that. Who doesn't have an in-house network these days o.O;

On a side note, I do run a network and haven't had any errors like this as of yet.

I've spoken with CSRs about games not working correctly and I've been told that and/or told that I should disable my firewall/anti-virus. I always tell them thanks for the suggestion but I'm not comfortable doing any of those.
#25 Oct 29 2010 at 1:42 PM Rating: Decent
Scholar
16 posts
I've put new ram in my system, and changed video cards (9800 GTX+). The 9800 GTX+ is clear supported, and this error still happens. I've done ALL the port forwarding they've recommended.

I also find it funny they told you to disable your firewall/anti-virus. Apparently they want you to disable your router and just connect your computer to the modem directly. If it happens one more time I'm calling them again. This is getting old quick.
#26 Oct 29 2010 at 3:41 PM Rating: Decent
Scholar
16 posts
I just called again. They told me to disable firewall/anti-virus. They said "We don't have a list of all the errors in the game, and what they mean. We're still learning, what you know, we know." That's what he said exactly. He said try connecting straight to my modem without the router. If it still has the same problem, he said I'm pretty much screwed.
#27 Oct 29 2010 at 4:11 PM Rating: Decent
IceDogg wrote:
I just called again. They told me to disable firewall/anti-virus. They said "We don't have a list of all the errors in the game, and what they mean. We're still learning, what you know, we know." That's what he said exactly. He said try connecting straight to my modem without the router. If it still has the same problem, he said I'm pretty much screwed.


Yeah unfortunately the CSR wont have a list of all possible error codes, etc... only the Dev team will have it, and they probably only pass along the most commonly found ones to the CSRs will some trouble shooting tips. A friend of mine has had this problem, and in fact, >>> I <<< used to have this problem. Was running on a Win 7 Platform with an i3 and a GTX460, and was getting that error on Trabia server a lot. I ended up changing servers to Palamecia and got the error less frequently (lead me to believe it was tied in with server load, or corrupted data packets from the server...) After switching to an 5000+ running Win XP and a GTX 460 I stopped having errors all together, and after reupgrading to Win 7, I did some tweaks to the TCP/IP settings and port forwarded my router, and since then have had no issues with (40000)3.

There are a few websites out there that explain helpful tweaks for win 7 tcp/ip settings... if your still having prolems. this may help.
____________________________
Humankind cannot gain anything without first giving something in return. To obtain, something of equal value must be lost.
Data Center: Primal; Server: Ultros; Free Company: The Kraken Club; Grand Company: The Maelstrom; Chocobo: Kweh
#28 Oct 29 2010 at 7:13 PM Rating: Decent
Scholar
16 posts
Whats ports and whatnot dude you use to fix it? I assume it could've been your new pc too. I'm on a different video card and ram, and the same problem exists. I've forwarded all the ports and more that they told me too on my router. It worked for an hour or two directly from the modem. But why buy a new router to play one game? >.<
#29 Oct 29 2010 at 7:34 PM Rating: Decent
IceDogg wrote:
Whats ports and whatnot dude you use to fix it? I assume it could've been your new pc too. I'm on a different video card and ram, and the same problem exists. I've forwarded all the ports and more that they told me too on my router. It worked for an hour or two directly from the modem. But why buy a new router to play one game? >.<


Ok this will take a while but I will edit this post with the info, just letting you know i am working on getting what information I can for you.

EDIT:

My PC:
OS: Windows 7 Professional (32-bit)
CPU: AMD Athlon 64 X2 Dual Core Processor 5000+ 2.60GHz (OC'd to 3.13GHz)
Motherboard: MSI 790XT-G45
RAM: 4GB(3.31GB Usable)
GPU: EVGA NVIDIA GeForce GTX 460 (OC'd)

A couple of preliminary notes:
Windows 7 (64-bit) has compatibility issues with FFXIV. I specifically upgraded from Windows XP to 32-bit Windows 7 for this reason. If your running 64-bit you need to make sure that you are running FFXIV in WoW64 (Windows 32-bit On Windows 64-bit). Typically Windows will do this automatically, assuming it installed correctly. As far as my PC knowledge of the emulation of 32-bit applications on a 64-bit enviroment goes, that is about it. For more information you would have to research that yourself.

As far as TCP/IP tweaks for Windows 7, here is a few suggestions that may alliviate some connectivity issues.

WARNING!!! DO NOT IMPLEMENT ANY OF THE FOLLOWING CHANGES TO YOUR TCP/IP SETTINGS UNLESS YOU KNOW WHAT YOUR DOING! CHANGES TO YOUR REGISTRY MAY CONFLICT WITH OTHER APPLICATIONS YOU USE! I AM NOT RESPONSIBLE IF YOU MESS UP YOUR REGISTRY INFO. LOL.

The following should be executed in elevated command prompt (with admin priviledges).

Disable Windows Scaling heuristics
Windows Vista/7 has the ability to automatically change its own TCP Window auto-tuning behavior to a more conservative state regardless of any user settings. It is possible for Windows to override the autotuninlevel even after an user sets their custom TCP auto-tuning level.

To prevent that behavior and enforce any user-set TCP Window auto-tunning level, you should execute the following command from the following prompt: C:\>

netsh int tcp set heuristics disabled

It should reply: "Ok."

TCP Auto-Tuning
To turn off the default RWIN auto tuning behavior, (in elevated command prompt) type:

netsh int tcp set global autotuninglevel=disabled

The default auto-tuning level is "normal", and the possible settings for the above command are:
disabled: uses a fixed value for the tcp receive window. Limits it to 64KB (limited at 65535).
highlyrestricted: allows the receive window to grow beyond its default value, very conservatively
restricted: somewhat restricted growth of the tcp receive window beyond its default value
normal: default value, allows the receive window to grow to accommodate most conditions
experimental: allows the receive window to grow to accommodate extreme scenarios (not recommended, it can degrade performance in common scenarios, only intended for research purposes. It enables RWIN values of over 16 MB)

Recommended setting: normal (unless you're experiencing problems).

If you're experiencing problems with your NAT router or SPI firewall, try the "restricted", "highlyrestricted", or even "disabled" state.

Notes:
- Reportedly, some older residential NAT routers with a SPI firewall may have problems with enabled tcp auto-tuning in it's "normal" state, resulting in slow speeds, packet loss, reduced network performance in general.
- auto-tuning also causes problems with really old routers that do not support TCP Windows scaling.
- netsh set commands take effect immediately after executing, there is no need to reboot.
- sometimes when using "normal" mode and long lasting connections (p2p software / torrents), tcp windows can get very large and consume too much resources, if you're experiencing problems try a more conservative (restricted) setting.


Compound TCP - Improve throughput
The traditional slow-start and congestion avoidance algorithms in TCP help avoid network congestion by gradually increasing the TCP window at the beginning of transfers until the TCP Receive Window boundary is reached, or packet loss occurs. For broadband internet connections that combine high TCP Window with higher latency (high BDP), these algorithms do not increase the TCP windows fast enough to fully utilize the bandwidth of the connection.

Compound TCP (CTCP) is a newer method, available in Vista and Server 2008 (there is also a hotfix available for XP/2003). CTCP increases the TCP send window more aggressively for broadband connections (with large RWIN and BDP). CTCP attempts to maximize throughput by monitoring delay variations and packet loss. It also ensures that its behavior does not impact other TCP connections negatively.

By default, Vista and Windows 7 have CTCP turned off, it is only on by default under Server 2008. Turning this option on can significantly increase throughput.

To enable CTCP, in elevated command prompt type:

netsh int tcp set global congestionprovider=ctcp

To disable CTCP:

netsh int tcp set global congestionprovider=none

Possible options are: ctcp, none, default (restores the system default value).
Recommended setting: ctcp

It is better to use this newer generation CTCP congestion control algorithm for most broadband connections, it's highly recommended that it be turned on.

ECN Capability
ECN (Explicit Congestion Notification, RFC 3168) is a mechanism that provides routers with an alternate method of communicating network congestion. It is aimed to decrease retransmissions. In essence, ECN assumes that the cause of any packet loss is router congestion. It allows routers experiencing congestion to mark packets and allow clients to automatically lower their transfer rate to prevent further packet loss. Traditionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a bit in the IP header (in the DiffServ field) instead of dropping a packet in order to signal congestion. The receiver echoes the congestion indication to the sender, which must react as though a packet drop were detected.

ECN is disabled by default in Vista and other modern TCP/IP implementations, as it is possible that it may cause problems with some outdated routers that drop packets with the ECN bit set, rather than ignoring the bit. To check whether your router supports ECN, you can use the Microsoft Internet Connectivity Evaluation Tool. The results will be displayed under "Traffic Congestion Test".

To enable ECN, in elevated command prompt type:

netsh int tcp set global ecncapability=enabled

Possible settings are: enabled, disabled, default (restores the state to the system default).
The default state is: disabled
Recommendation: enabled (only for short-lived, interactive connections and HTTP requests with routers that support it, in the presense of congestion/packet loss), disabled otherwise (for pure bulk throughput with large TCP Window, no regular congestion/packet loss, or outdated routers without ECN support).

Notes: ECN is only effective in combination with AQM (Active Queue Management) router policy. It has more noticeable effect on performance with interactive connections and HTTP requests, in the presense of router congestion/packet loss. Its effect on bulk throughput with large TCP Window are less clear.

RSS - Receive-side Scaling
The receive-side scaling setting enables parallelized processing of received packets on multiple processors, while avoiding packet reordering. It avoids packet reordering y separating packets into "flows", and using a single processor for processing all the packets for a given flow. Packets are separated into flows by computing a hash value based on specific fields in each packet, and the resulting hash values are used to select a processor for processing the flow. This approach ensures that all packets belonging to a given TCP connection will be queued to the same processor, in the same order that they were received by the network adapter.

To set RSS:

netsh int tcp set global rss=enabled

Possible rss settings are: disabled, enabled, default (restores rss state to the system default).
Default state is: enabled
Recommended: enabled (if you have 2 or more processor cores and a NIC that can handle RSS)

TCP Chimney Offload
TCP chimney offload enables Windows to offload all TCP processing for a connection to a network adapter. Offloads are initiated on a per-connection basis. Compared to task offload, TCP chimney offload further reduces networking-related CPU overhead, enabling better overall system performance by freeing up CPU time for other tasks.

To set TCP Chimney Offload:

netsh int tcp set global chimney=enabled

Default state: disabled (under Vista), automatic (under Windows 7 and 2008 Server)
Recommended: enabled

The possible states are disabled, enabled, default (Vista), automatic (only Windows 7 and 2008 Server) as follows:

automatic - This default setting is only available under Windows 7 and 2008 Server, it is not available udner Vista. It offloads if the connection is 10 GbE, has a RTT < 20ms, and the connection has exchanged at least 130KB of data. The device driver must also have TCP Chimney enabled.
default - this setting restores chimney offload to the system default. Setting this "default" state under Windows 7 and 2008 Server is possible, but it sets the system to the "automatic" mode described above.
disabled - this setting is maually configured as disabled.
enabled - this setting is manually configured as enabled.

Notes:
Under Windows 7 and Server 2008 the "default" and the additional "automatic" parameter set the system to the same "automatic" state.
For Chimney Offload to work, it needs to be enabled in both the OS and NIC. To enable the "TCP Offloading" setting in your NIC, navigate to the Device Manager, under Network Adapters, in the Advanced tab, and check "Enabled" in the box next to the TCP offload entry.


Direct Cache Access (DCA)
Windows 7 and 2008 Server (but not Vista) add NETDMA 2.0 Direct cache access support. Direct Cache Access (DCA) allows a capable I/O device, such as a network controller, to deliver data directly into a CPU cache. The objective of DCA is to reduce memory latency and the memory bandwidth requirement in high bandwidth (Gigabit) environments. DCA requires support from the I/O device, system chipset, and CPUs.

To enable DCA:

netsh int tcp set global dca=enabled

Available states are: enabled, disabled.
Default state: disabled
Recommended: enabled (provided the CPU/Chipset/NIC support it)

Setting MTU
It is sometimes useful to view and set the MTU value for a specific network interface manually. To view a list of active network interfaces and their MTU values in Vista using netsh, open command prompt as administrator and execute the following command:

netsh interface ipv4 show subinterface

To change the MTU value of a specific network card, type the following in command prompt:

netsh interface ipv4 set subinterface "network interface name" mtu=#### store=persistent

Where "network interface name" is your specific network adapter name as obtained above (or viewable under Network adapters), and mtu=#### is the desired MTU value.

For example, if the name of your network card is "Wireless Network Connection" and you'd like to set its MTU to 1500, you'd have to type:

netsh interface ipv4 set subinterface "Wireless Network Connection" mtu=1500 store=persistent

Note: The maximum MTU value is usually 1500, and up to 1492 for PPPoE connections.

==================
Manually tuning Registry Parameters
==================
Note that for changes to these settings to take effect the computer needs to be rebooted. As always, a registry backup is recommended if making any changes, and some proficiency in using regedit is required.
------------------
NetDMA (TCPA)
NetDMA enables support for advanced direct memory access. In essence, it provides the ability to more efficiently move network data by minimizing CPU usage. NetDMA frees the CPU from handling memory data transfers between network card data buffers and application buffers by using a DMA engine.

Under Windows 7, NetDMA can be set directly using the netsh interface (not available under Vista):

netsh int tcp set global netdma=enabled

Under Vista/2008/7, you can set NetDMA/TCPA using the following Registry parameter:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnableTCPA=1 (DWORD, not in registry by default. Set to 1 to enable, 0 to disable NetDMA)

Recommended setting is 1, a new DWORD value may need to be created if not already present in the registry.

Checksum Offloading (DisableTaskOffload)
This NDIS 5 setting allows for reducing CPU load by offloading some tasks required to maintain the TCP/IP stack to the network card. Theoretically, Widnows should automatically detect capable network hardware.

The tasks offloaded are as follows:
- TCP/IP checksum calculation - each packet sent includes a verification checksum.
- TCP/IP segmentation - also known as "TCP Large Send" where Windows sends a large amount of data to the network card, and the NIC is then responsible for dividing it according to the network MTU. Experimental feature, not enabled by default
- IPSec Encryption cyphers and message digests - provides encryption of packets at the hardware level.

To change the checksum offloading setting in the Windows Registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
DisableTaskOffload=0 (DWORD value, default: not set, recommended: 0=enable offload, 1=disable offload)

DefaultTTL
TTL can be safely left alone in many cases. It is a limit to the time and number of hops/routers a packet will travel before being discarded. A number that's too small risks packets being discarded before reaching their destination. A number that's too large (over 128) will cause delay in when lost IP packets are discarded.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
DefaultTTL=64 (DWORD, set to a decimal value between 32 and 128. Recommended: 64)

TcpMaxDataRetransmissions
Determines how many times unacknowledged data (non-connect segment) is retransmitted before TCP aborts the connection. The retransmission timeout is doubled with each successive retransmission on a connection. It is reset when responses resume.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TCPMaxDataRetransmissions=7 (DWORD, recommended: between 3 and 10, not present in registry by default)

Note: When not present in the registry, the default behavior is 255 retransmissions (5 in documentation).

SynAttackProtect
This undocumented setting provides protection against SYN denial of service (DoS) attacks. When enabled, connections timeout sooner if SYN attack is detected. When set at 1, TCPMaxDataRetransmissions can be lowered further.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
SynAttackProtect=1 (DWORD, recommended: 1, not present in registry by default)

Network Throttling Index
By default, Windows Vista/7 implements a network throttling mechanism to restrict the processing of non-multimedia network traffic to 10 packets per millisecond (a bit over 100 Mbits/second). The idea behind such throttling is that processing of network packets can be a resource-intensive task, and it may need to be throttled to give prioritized CPU access to multimedia programs. In some cases, Gigabit networks for example, it may be benefitial to turn off such throttling.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile
NetworkThrottlingIndex=ffffffff (DWORD, default: 10, recommended: 10 or ffffffff, valid range: 1 through 70 decimal or ffffffff to completely disable throttling)

It is only recommended to change this setting in saturated Gigabit LAN environments, where you do not want to give priority of multimedia playback.

Notes: Setting is available in Windows 7, Vista (SP1), 2008 Server. Default value is 10 under Windows 7, similar behavior if not present in the Registry.

Set DNS and Hosts Priority

As with previous versions of Windows, one can improve DNS and hostname resolution by increasing the priority of of related services, while keeping their order. This is explained in more defail in our Host Resolution article. Lower numbers mean higher process priority. The corresponding registry settings in Vista are as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ServiceProvider
LocalPriority=4 (DWORD, recommended: 4, default: 499) - local names cache
HostsPriority=5 (DWORD, recommended: 5, default: 500) - the HOSTS file
DnsPriority=6 (DWORD, recommended: 6, default: 2000) - DNS
NetbtPriority=7 (DWORD, recommended: 7, default: 2001) - NetBT name resolution, including WINS

TcpTimedWaitDelay (port allocation)
Short lived (ephemeral) TCP/IP ports above 1024 are allocated as needed by the OS. The default Vista values have improved from previous Windows versions, and are usually sufficient under normal load. However, in some instances under heavy load it it may be necessary to adjust the settings below to tweak the availability of user ports requested by an application.

If the default limits are exceeded under heavy loads, the following error may be observed: "address in use: connect exception". By default under Vista (when the values are not presend in the registry), the OS can allocate up to 16384 ephemeral ports above port 1024, and the OS waits for 120 seconds before reclaiming ports after an application closes the TCP connection. This is a considerable improvement over older Windows versions. However, if necessary, the following registry values can be added/edited:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
MaxUserPort=65535 (DWORD, not in the registry by default. Recommended: leave at default, or use a number above 16384 up to 65535 decimal as necessary) - maximum number of ports to use. 1024 is automatically subtracted from entered value to allow for reserved ports under 1024.
TcpTimedWaitDelay=30 (DWORD, not present or 0xffffffff in registry by default. Recommended: 30 decimal, denoting 30 seconds) - time to wait before reclaiming ports, in seconds. Default time before reclaiming ports, if value is at 0xffffffff or not present in the registry is 120 seconds. Just reducing the delay is often sufficient without changing MaxUserPort, as it allows for reusing ports more efficiently.

Ephemeral ports can be checked and changed using netsh as well.

To query the current values, in command prompt, type:
netsh int ipv4 show dynamicportrange tcp (for UDP, use the same command, replacing only "tcp" with "udp" at the end)

To set both the starting, and max user port using netsh, in elevated command prompt run:
netsh int ipv4 set dynamicportrange protocol=tcp start=1025 num=64511 (start=NNN denoting the starting port, and num=NNN denoting the number of ports)

Notes:
By default, dynamic ports are allocated between ports 49152 and 65535 (for a total of 16384 ephemeral ports).
Using netsh allows to set both the starting port and port range. Editing the Registry allows for setting the port range, and the starting port is fixed at 1025. Deleting the MaxUserPort registry entry (or setting it to a value outside the allowed range) causes the OS to revert to using the default values.
Some system processes can install port filters to block certain port ranges. If ephemeral ports run into these filtered port ranges, TCP/IP applications will be unable to bind to any ports.


Disable Nagle's algorithm
The tweak below allows for tweaking or disabling Nagle's alogrithm. Disabling "nagling" allows for very small packets to be transferred immediately without delay. Note that disabling Nagle's algorithm is only recommended for some games, and it may have negative impact on file transfers/throughput. The dafault state (Nagling enabled) improves performance by allowing several small packets to be combined together into a single, larger packet for more efficient transmission. While this improves overall performance and reduces TCP/IP overhead, it may briefly delay transmission of smaller packets. Keep in mind that disabling Nagle's algorithm may have some negative effect on file transfers, and can only help reduce delay in some games. To implement this tweak, in the registry editor (Start>Run>regedit) find:

This setting configures the maximum number of outstanding ACKs in Windows XP/2003/Vista/2008:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}
There will be multiple NIC interfaces listed there, for example: {1660430C-B14A-4AC2-8F83-B653E83E8297}. Find the correct one with your IP address listed. Under this {NIC-id} key, create a new DWORD value:
TcpAckFrequency=1 (DWORD value, 1=disable, 2=default, 2-n=send ACKs if outstanding ACKs before timed interval. Setting not present by default).

For gaming performance, recommended is 1 (disable). For pure throughput and data streaming, you can experiment with values over 2. If you try larger values, just make sure TcpAckFrequency*MTU is less than RWIN, since the sender may stop sending data if RWIN fills witout acknowledgement.

Also, find the following key (if present):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters
Add a new DWORD value:
TCPNoDelay=1 (DWORD value, 0 to enable Nagle's algorithm, 1 to disable, not present by default)

To configure the ACK interval timeout (only has effect if nagling is enabled), find the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{NIC-id}
TcpDelAckTicks=0 (DWORD value, default=2, 0=disable nagling, 1-6=100-600 ms). Note you can also set this to 1 to reduce the nagle effect from the default of 200ms without disabling it.

======================================
======================================

Port Forwarding:
UDP: 55296-55551
TCP: 54992-55551

Edited, Oct 29th 2010 10:29pm by StateAlchemist2
____________________________
Humankind cannot gain anything without first giving something in return. To obtain, something of equal value must be lost.
Data Center: Primal; Server: Ultros; Free Company: The Kraken Club; Grand Company: The Maelstrom; Chocobo: Kweh
#30 Oct 29 2010 at 8:30 PM Rating: Decent
Hope that helps.
____________________________
Humankind cannot gain anything without first giving something in return. To obtain, something of equal value must be lost.
Data Center: Primal; Server: Ultros; Free Company: The Kraken Club; Grand Company: The Maelstrom; Chocobo: Kweh
#31 Oct 30 2010 at 12:14 AM Rating: Default
**
588 posts
As of the last two patches i crash all the time randomly when torrents are running since last patch i crash even when ther eare no torrents going and the torrent program is closed.
____________________________


Cornyboob Funnyname Wutai Phys 50 Conj 49 Weaver 49 LW 34 Alch 28 Pug 22 Archer 20 Glad 19 Thaum 20 GS 11 Bot 9 Miner 8 Shield 44 Maur 3

This forum is read only
This Forum is Read Only!
Recent Visitors: 20 All times are in CST
Anonymous Guests (20)