OK, here is the problem I am a PC gamer and if anybody here has the games Battlefield: Bad Company 2 or the multiplayer version of the 2010 Medal of Honor game (both made by DICE), then you may have heard of the connection problems and loss of conneciton to game servers problems. One user suggested the following: "Most of you here uses Windows 7 or Vista right? Some of you are on router right? some have direct connection to the Internet? Well, for me I had the Connection Interrupted: The EA servers are currently no available issue for ages since launch date. The updater refuses to start, and even in the multiplayer menu, I couldn't get to the login screen. So, this is what I did to allow me to play multiplayer. For those of you who had done any TCP optimizing to reduce latency for your other games, some of your settings may have conflicted with EA's games. I did that and now I have to revert one of the setting, known only as ECN Capability. See this: SpeedGuide.net :: Windows 7, Vista, 2008 Tweaks Apparently, EA servers were never configured to allow ECN Capability bits so, they will drop any packets if your computer is setting out TCP data packets containing the ECN Capability bit. By the way, on Vista and Window 7 system, the ECN Capability bit is usually set as default. Some of you may have accidentally set it to enabled. To fix it, start up your command prompt with administrator rights. 1) First, enter the following command netsh int tcp show global 2) Then see if your ECN Capability is set to any other thing then default or disabled. 3) Reset it by entering this: netsh int tcp set global ecncapability=default Hopefully, this time you may be able to play. Also, there may be other TCP settings at system level that is preventing connection, so check that website out and see what particular setting will affect the connection. To be sure, restart your system after entering the above commands. Enjoy. " I followed his advice and saw no change, however, the following day (today actually) I booted up my PC and my ethernet adapter wasn't even connecting to my router, giving me an "Unidentified Access" message. While spending ages in the morning before college with no sucess, I tried to see if I could revert my change - no luck. After college, after many reboots and trying to reset IP settings, Stack e.t.c - no luck again. I'm now writing this using a Wireless USB adapter which as a gamer is not a preffered choice of connecting to my router. My router is fine - it's working fine too. Other PC's can connect wired and wirelessly but mine can connect no more via enthenet (Realtek). I need some help here! I tried a system restore aswell - nothing. I don't want to have to install Windows because all my games are from Steam and my internet speed is only 2.46Mbps and I can use up to 100GB per month until my ISP reduce the speed to 1Mbps for 30 days as a consequence. Ask me if I've done anything because I've forgotten some stuff in my post.

More info: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Jonathan Rapley>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : JonRapleyGAMING Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : home Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : 00-24-1D-C6-5A-3D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::31e2:79af:bf60:900c%27(Preferred) Autoconfiguration IPv4 Address. . : 169.xxx.xxx.xx(Preferred) IS THIS A PROBLEM? Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 452994077 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D9-3F-14-00-24-1D-C6-5A-3D DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Wireless LAN adapter Wireless Network Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter Physical Address. . . . . . . . . : 00-1F-1F-51-D7-F1 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : Edimax nLite Wireless USB Adapter THIS IS SO I CAN ACCESS INTERNET WHILE ETHERNET IS DOWN Physical Address. . . . . . . . . : 00-1F-1F-51-D7-F0 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::a105:786f:6847:663f%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.xxx.x.xx(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 19 October 2010 21:13:49 Lease Expires . . . . . . . . . . : 20 October 2010 21:13:49 Default Gateway . . . . . . . . . : 192.xxx.x.xxx DHCP Server . . . . . . . . . . . : 192.xxx.x.xxx DHCPv6 IAID . . . . . . . . . . . : 218111775 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-D9-3F-14-00-24-1D-C6-5A-3D DNS Servers . . . . . . . . . . . : 192.xxx.x.xxx NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.home: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:3849:3183:a96f:2126(Pref erred) Link-local IPv6 Address . . . . . : fe80::3849:3183:a96f:2126%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{B9B40345-4E77-4617-83F8-6506B25EDD39}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{04EC9334-8758-4D8D-8B18-93F37000AE53}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\Jonathan Rapley>

And this Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Jonathan Rapley>netsh int tcp show global Querying active state... TCP Global Parameters ---------------------------------------------- Receive-Side Scaling State : enabled Chimney Offload State : automatic NetDMA State : enabled Direct Cache Acess (DCA) : disabled Receive Window Auto-Tuning Level : normal Add-On Congestion Control Provider : none ECN Capability : disabled RFC 1323 Timestamps : disabled C:\Users\Jonathan Rapley>

After leaving the PC off, unplugging EVERYTHING and re-plugging it back in after a day - IT'S FIXED!!! Thank God :)

Hi, I am glad to know the issue has been resolved. I also noticed the Realtek PCIe GBE Family Controller got an IP Address as “169.xxx.xxx.xx”. 169.xxx.xxx.xx is a APIPA (Automatic Private IP Addressing) address; it indicates that the computer was unable to get a valid IP Address. Commonly, you can try the following: 1. Please ensure that your NIC driver is up-to-date. 2. Upgrade your router’s firmware. 3. Change another network cable. 4. If it is possible, please connect this computer to another network and see how it works. In the future, if you experience any issues regarding our products or if you have any feedbacks, you are also welcome to post a new thread in our forum. Thanks. Have a great day!Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.