TechSpot

NAT Issue - Please Help

By Coeus
May 9, 2009
  1. Hi all.

    I am on a BT Home Hub router (bastard thing) and am having some connection problems. To date I have:

    1. Enabled static IP address.
    2. Disabled Windows firewall
    3. Correctly allowed Sup Comm on my McAffe firewall.
    4. Port-forwarded ports 6112, 9103, 30350 and 30351.
    5. Enabled my IP address as DMZ (kinda negates the need for port forwarding but did it anyway).

    So after all this I ran NATTRACE and get the following results:

    NAT test failed. Your router is correctly passing information to and from the internet, but is NAT translating the port numbers on outgoing UDP packets. When your computer sends a packet to a port number (eg 6112) on the server, it should come from that same port number on your own computer - this is not happening. View the report to see precisely which ports are being NATed.

    NATTrace report (v1.01)

    Tests:
    Test 1: SUCCESS - Connect to fixed IP
    success
    Test 2: SUCCESS - Check NATTrace version
    success
    Test 3: SUCCESS - Perform DNS lookup
    success
    Test 4: SUCCESS - Connect to named host
    success
    Test 5: SUCCESS - Direct TCP to fixed IP
    success
    Test 6: SUCCESS - Direct TCP (web) to named host
    success
    Test 7: SUCCESS - Direct TCP (6112) to named host
    success
    Test 8: SUCCESS - Direct UDP (6112) to fixed IP
    success
    Test 9: SUCCESS - Direct UDP (6112) to named host
    success
    Test 10: FAILED - NAT check, port 6112
    NAT detected (Expected send on port 6112, went on port 60391 instead)
    Test 11: SUCCESS - Direct UDP (port 9103)
    success
    Test 12: FAILED - NAT check, port 9103
    NAT detected (Expected send on port 9103, went on port 60392 instead)
    Test 13: SUCCESS - Direct UDP (port 30350)
    success
    Test 14: FAILED - NAT check, port 30350
    NAT detected (Expected send on port 30350, went on port 60393 instead)
    Test 15: SUCCESS - Direct UDP (port 30351)
    success
    Test 16: FAILED - NAT check, port 30351
    NAT detected (Expected send on port 30351, went on port 60394 instead)

    4 tests failed

    For the life of me I cannot figure out where its going wrong. Any input would be greatly appreciated. Googling it seems there are quite a few suffering from this but have not found a definitive answer yet.

    Best regards,
    Coeus.
     
  2. jobeard

    jobeard TS Ambassador Posts: 9,317   +618

    Nattrace is specific to your gaming environment and implements whatever it pleases,
    so frankly, its value and correctness is in question.

    Item in RED are high risk choices and while this might
    be useful to diagnose your issue, you should reverse these asap.

    New rules are required for the ports shown and getting this correct is
    different for every FW. It is not uncommon to require a separate rule for inbound from outbound (but each can specific TCP+UDP).

    Inbound rules need source-ip=any
    outbound need dest-ip=any
     
  3. Coeus

    Coeus TS Rookie Topic Starter

    Thanks for replying jobeard. I am not too technically literate with computers and am not sure what you mean by 'New rules are required for the ports shown and getting this correct is
    different for every FW. It is not uncommon to require a separate rule for inbound from outbound (but each can specific TCP+UDP).'

    Any chance of a step-by-step guide?

    Best regards,
    Coeus.
     
  4. jobeard

    jobeard TS Ambassador Posts: 9,317   +618

    get the documentation for the McAffe firewall and read-up on creating custom rules.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...