09-09-2012 06:55 AM
More often than not, when my son wants to play on Xbox Live, the Xbox won't connect to Xbox Live. It will connect to the network and the internet but not Xbox Live. After running the connection test, the suggestion is to reboot the modem and router. It works after rebooting those two devices. Why does this happen so often?
09-09-2012 09:08 AM
For gaming console like x-box or x-box 360 you need to open some ports on the router because they are defaultly close. On your EA4500 access the device UI then go to Application & Gaming then select Port Range Forwarding. You need to manually enter specific ports for your gmaing console. Here are some tested ports for x-box TCP/UDP: 80,3074,53 & 88. By the way may I know who is your ISP? because DSL internet service provider they usually used modem/router wherein to set it to full bridge
09-10-2012 03:26 AM - edited 09-10-2012 03:27 AM
I did as you suggested and it seems like it worked, although not at first. I hard coded the Xbox with an IP address, subnet mask, gateway and DNS server, then I configured the router to forward requests for those ports to that IP address. As soon as I did that, my wife and son who were surfing, complained that they couldn't connect to the internet anymore on their wireless laptops. I backed out the port forwarding to restore their internet connectivity which worked. Then I figured I'd go with one port at a tiime. I set 3074 to forward to the Xbox and tried logging into Xbox Live. Voila! That worked. Didn't need to power cycle the modem and router. Any idea why their internet connectivity went away with those four ports forwarded? And any idea what port 3074 is for and why that enabled the Xbox Live sign in? Also, do I still need to forward ports 80, 53 and 88?
09-10-2012 05:58 AM
According to wikipedia:http://en.wikipedia.org/wiki/List_of_TCP _and_UDP_port_numbers. 3074 is for Xbox LIVE and/or Games for Windows - LIVE. Now with regrads to those 2 laptop's losing wireless connection, it's probably because of the xbox was eating the packets at that time. It's a good thing that you were able to make it to work in your end though.
11-19-2012 06:52 AM
Hi, I’ve read your post from this link: http://homecommunity.cisco.com/t5/Wireless-Routers
11-19-2012 07:28 AM
I read a couple other threads where users had similar problems. The culprit appears to be port 53 which is for DNS. I'm not sure why Microsoft would recommend forwarding that port.
11-19-2012 09:11 AM
I found something online about PORT 53: http://www.networkworld.com/community/blog/allow-b