Posts: 68
Joined: 6.Nov.2001
From: Southampton, Hampshire, UK
Status: offline
Hi,
I've recently changed from ISA 2000 to ISA 2004 and I have a few issues.
I've recreated the rules for XBox live under ISA 2004 and my XBox can connect to live and download content but I'm having problems when it comes to gaming.
Prior to moving to ISA 2004 voice chat and gaming both worked on my 360 so this appears to be an ISA 2004 problem.
The only thing I have found is that during the 360's network test it reports a strict NAT connection (which it says may cause problems) but the only way I can think of to get around this in ISA 2004 (and its not very practical in my employment) is to add another NIC & subnet as a DMZ and set ISA to route to that address range rather than use NAT
Has anyone else encountered/resolved this issue or have any comments?
I had this problem using a draytek vigor 2600 - i opened up the ports :
tcp 88 tcp 3074 udp 3074
directed at the IP of my xbox.
This didnt help.
I then used a port redirection of the same ports - to the same ports and this allowed the xbox live test to detect an 'open' nat which seemed to solve all my gaming problems.
Maybe with ISA you could create 3 server publishing rules , or even web listeners?
XBox is a Home-User toy. ISA is a commercial grade firewall product. The two difrerent "worlds" were never meant to work together.
Anyway, the only thing you can do and maintain any sense of security at all would be to create a rule for the XBox that allows everything but limits the Source to only the XBox. This is the way it would be done:
1. Undo *everything* you did to this point in your attempts. There is no such thing as "forwarding ports", so I have no idea what you did there,...but undo all of it. ISA must be returned to its "unmolested" state and start fresh.
2. Statically assign the TCP/IP specs of the XBox. Do not leave them on DHCP or Automatic. In a simple single subnet LAN the ISA would be the XBox's default gateway.
3. On the ISA create a Computer Object called "XBox" and add the XBox (by IP#) to the object. If you think you may have other devices in the same situation as the XBox then you can use a Computer Set Object instead.
4. Create an Access Rule: Name: "Set My XBox Free" <or whatever name you like> Source: "XBox" <the Computer Object from above> Destin: "External" Protocol: "All outbound IP Traffic" Users: "All Users"
5. Set this new Access Rule above (higher in the list) any more restictive rules
If it does not work now,...then it just is not going to work at all.