I made a request to 2k for all of this BS, and this is my reply:
Thank you for contacting 2K sports.
We have been investigating server issues with NBA 2K13. These issues have been resolved.
If you are experiencing any further connection issues for NBA 2K13, please refer to the following troubleshooting guide:
Check all the physical devices on your network to ensure they are plugged in and powered on.
Perform a connection test on each device connected to the network.
For Xbox 360, refer to the following website
http://support.xbox.com/en-US/xbox-360/networking/connectivity-solutions
For Playstation 3, refer to the following website http://manuals.playstation.net/document/en/ps3/current/settings/connecttest.html
For PC, refer to the following website
http://www.microsoft.com/windows/using/tools/igd/default.mspx
For Wii U, refer to the following website
http://www.nintendo.com/consumer/systems/wiiu/en_na/internet.jsp
Understanding NAT Types:
NAT Types:
Open
Moderate
Strict
Open NATs can connect to any of the three types. --> Probably the least common type
Moderate can only connect to open and moderate. --> Probably the most common type
Strict can ONLY connect to open.
Strict NATs are a difficult problem with peer-to-peer games. Since most people don't have open NATs, the player with a strict NAT won't be able to find many joinable games.
Also, if the player with a strict NAT does manage to join a game, if another player with a moderate NAT joins later, the player with the strict NAT gets kicked out.
The problem is even worse since it is sometimes difficult for software (i.e. Games for Windows Live) to detect which NAT type it is running behind, and can often report that the player has a moderate NAT when they actually have a strict NAT.
Another problem is that sometimes the ISP (Internet Service Provider) is also NAT'd which often means even if you have a direct connection to the internet (without a router/firewall), the ISP still acts as a strict NAT.
Port Forwarding:
The following Ports need to be open on your router to connect to the NBA 2k13 online servers:
TCP 80, UDP 88, UDP 3074, TCP 3074, UDP 53, TCP 53, UDP 3064, TCP 1795, TCP 1745, UDP 1795, UDP 1745
If you need assistance with opening these ports, please refer to the following website for more information (you will need to know your router brand and model, as the website guides are based on specific routers)
http://portforward.com/english/routers/port_forwarding/routerindex.htm
Here are some additional tips that have helped many players improve their connectivity:
1. Make sure your router's firmware is upgraded the latest version (very important).
Unplug your router for 10 minutes and plug it back in. Some older routers degrade in performance over time until it is rebooted, similar to a PC.
Disable any firewall or other network filtering for the game.
Enable uPnP (universal plug and play) on your router.
If you don't care about security, enable DMZ (de-militarized zone) on your router for your PC's address. This turns off all of your router's firewall features for that specific PC.
Get a router that has the "Xbox LIVE compatible" or "Certified for Windows Vista" logo.
Contact your ISP and ask them what your DNS setting should be.
Direct Connection/Power Cycle:
If you are still having issues connecting to the online servers after trying the above steps, try connecting your broadband modem directly to the console or PC on which you are playing this game. At this point, please disconnect your Broadband modem from power for Five (5) minutes. After this time has elapsed, plug the modem back into power and allow the normal power-up cycle to finish.
If this final step does not resolve your issue, please plug a PC directly into your modem and provide us screen shots from the following locations:
www.speedtest.net
www.whatsmyip.org
http://www.pingtest.net/
ipconfig (Windows + R > type "cmd" without quotes > hit okay > type "ipconfig" without quotes > press ENTER )
The Router's port configuration screen
Please provide these screencaps to your reply so we can look into this further.
Regards,
Andre C
** Usually shutting off the system and turning it on will fix the problem... for about 5 minutes.