Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Enthusiast Zone > Networking > need help NAT is too restrictive

need help NAT is too restrictive
Thread Tools
Fresh-Faced Recruit
Join Date: Feb 2009
Status: Offline
Reply With Quote
Feb 6, 2009, 09:21 AM
 
Basically, my xbox 360 will not play online games because the NAT is too strict. I've read online that I need to open a couple of ports to play but don't know how to do that. If anyone could give me some help or point me in the right direction I would be very grateful.

-my setup= DSL modem connected to airport, ethernet cable from airport goes to my mini but I connect to the 360 when I want to play.
     
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status: Offline
Reply With Quote
Feb 6, 2009, 10:48 AM
 
Welcome to our forums!

I don't know what "NAT is too restrictive" means, but NAT has nothing to do with a connection problem like this. I don't know how it works with a 360, but you may need to set up port forwarding on the router to forward any packets meant for the 360 to it based on the port number(s), which you mention.

Though somehow I doubt even Microsoft would make it this complicated. But I'm sure someone else who owns a 360 can prove me wrong.

Steve
Celebrating 10 years and 4000 posts on MacNN!
     
Addicted to MacNN
Join Date: Aug 2008
Location: The New Posts Button
Status: Offline
Reply With Quote
Feb 6, 2009, 10:50 AM
 
I've done this on my Time Capsule. His terminology about NAT is accurate as far as the what the Xbox will tell you on a connection check.

I think this is the best explanation you'll find while using an Airport.
     
Moderator
Join Date: Oct 2001
Location: San Jose, CA
Status: Offline
Reply With Quote
Feb 6, 2009, 02:16 PM
 
So Microsoft does make it more complicated than it should be. What a shock!



Anyway, I was confused because NAT stands for network address translation, which simply means that the router translates connections from your "internal" network address, usually 192.168.x.x, into the "external" IP address given to your DSL/cable modem for transmission over the Internet.

Port forwarding forwards incoming data packets to specific machines on your "internal" (LAN) network for particular applications and really has nothing to do with NAT other than knowing which LAN IP address to forward to. For example, if you have a web server on your LAN, any incoming packet labeled with port 80 should be forwarded to that server.

The link to the Apple discussion gives good info.

Steve
(Last edited by ibook_steve; Feb 6, 2009 at 03:47 PM. )
Celebrating 10 years and 4000 posts on MacNN!
     
Addicted to MacNN
Join Date: Aug 2008
Location: The New Posts Button
Status: Offline
Reply With Quote
Feb 6, 2009, 02:19 PM
 
As a note, you'll now you've succeeded on the NXE connection check if it doesn't mention NAT at all.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 09:54 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2