Halo 2 Matchmaking over WinGate

[GoldElite382]

My network connection has 5+ computers connected to a hub connected to a WinGate NAT to share our internet connection, all of which have static IPs.
I recently got an XBox 360, which has its IP dynamically assigned by WinGate's DHCP (but it's always assigned to x.x.0.1), and have used the ENS to forward all incoming connections (from the internet) on both TCP and UDP ports 1-65535 to the console.
The computers can access the internet just fine and the XBox can access XBox Live (1 months free gold subscription) just fine, but Halo 2s matchmaking system hangs and joining a party always fails with "We are having network problems".
I have connected the console directly to our modem and everything works fine, so it must be a problem with WinGate. The trouble is, the console registers the NAT as 'open', and every port is being forwarded (all outbound connections are 'allowed') -- I have absolutely no idea what could be wrong.

Any suggestions on what I could do? Other LAN users of the internet complain when they can't use it, and connecting the XBox directly is the only way Halo 2's matchmaking system works currently. Any help will be greatly appreciated. =)
[WinGate 6.1.2 #1094, Windows 98SE]

[jamesc]

When you did the Port Redirection in ENS, did you use the option "Do not translate Source IP"? If you did not, enable it as a test and try again.

[GoldElite382]

Just tried that, but it's not working either. =(

I don't know if any of this helps, but the XBox now has a static IP address, x.x.0.1 (The DHCP is configured to assign addresses x.x.0.2-x.x.255.254).
I was able to join one of my clan members parties, but could not communicate with my headset, even though I could hear the group just fine. This sounds very much like the problems reported with moderate/strict NATs over XBox Live, but the console itself reports an open configuration... =S
At the very least, the standard Live ports (88 and 3074) seem to be forwarding properly (or so GateKeeper tells me). With the exception of the latest dashboard update (I needed to connect directly to get that, too), the Live service itself seems to be running fine.

[jamesc]

I think it may be a good idea to create a support ticket for this; I would like to review your WinGate settings because NAT should allow your XBox 360 to have complete connectivity.
http://support.qbik.com/index.php?_a=tickets&_m=submit

1. WinGate Registry.
GateKeeper --> Options menu --> Advanced --> Save Registry

2. WinGate Config Report
GateKeeper --> Options menu --> Advanced --> Save Config Report

3. ipconfig/all from the WinGate Server
(Windows) Start menu --> Run --> cmd --> ipconfig/all >> C:\ipa.txt

4. IP Address, Subnet Mask, Default Gateway and DNS address of the XBox.

5. Elaboration on this comment, and any links regarding and port numbers:
This sounds very much like the problems reported with moderate/strict NATs over XBox Live, but the console itself reports an open configuration... =S

[GoldElite382]

Right, I have created a ticket, and posted the details of steps 1-4 with it.
As for elaborating the comment, I mean that moderate and strict NATs generally have problems communicating with each other -- Can't join certain parties (a problem I've had), and can't hear other players (As far as I can tell, I can hear them, but they can't hear me, so I'm not quite so sure about that one). Here's an official link for that

The ports XBox Live needs as standard are UDP 88 & 3074, and TCP 3074. Again, an official link.
And finally, an unofficial source that says Halo 2 needs more ports than standard Live (Although surely not more than 65535?! =P)

Hope this helps a little more