Okay. Ran it. Passed it (failed while GPGnet was open, closed GPGnet, passed).

So, since nothing has changed on MY end between when I WAS able to play and now that I CAN'T stay connected for > 5 minutes, will someone at GPG finally acknowledge that there are serious problems with the viability of the network code when it comes to resiliency?

I've never had so much trouble connecting to another player/game. Even connecting DOS DOOM over BNC networking with IPX/SPX was easier and more reliable than this. Damn

I agree 100%

Generated: 5/5/2007 8:41:36 PM (5/5/2007 10:41:36 AM UTC)
Hostname: home
adapter: Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC - Packet Scheduler Miniport
adapter: D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.B) #2 - Packet Scheduler Miniport
addresses: 192.168.0.4
gateway: 192.168.0.1
adapter: MS TCP Loopback interface

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: SUCCESS - NAT check, port 6112
success
Test 11: FAILED - Direct UDP (port 9103)
failed - exception caught (Only one usage of each socket address (protocol/network address/port) is normally permitted)
Test 12: FAILED - NAT check, port 9103
failed - exception caught (Only one usage of each socket address (protocol/network address/port) is normally permitted)
Test 13: SUCCESS - Direct UDP (port 30350)
success
Test 14: SUCCESS - NAT check, port 30350
success
Test 15: SUCCESS - Direct UDP (port 30351)
success
Test 16: SUCCESS - NAT check, port 30351
success

2 tests failed



anyone who can help will become a god to me

i dont know what to do
=[
regards viperj

If you are in this boat:

1. You've forwarded all the ports for SupCom and confirmed Nattrace they all work
2. You've reinstalled .Net 2.0 and updated it
3. ...but GPGnet still says "1 Code: 1 Could not connect to GPGnet: Supreme Commander. Please check your internet connection and try again."

then try this:
run GPGnet and during the Login process, open task manager and right click on the "GPG.Multiplayer.Client.exe". Select "Set Affinity..." and untick the checkboxes so only one CPU is selected.

This workaround would only apply to Dual Core or Hyperthreaded CPUs (most of them these days).

this has to be done before each login process...but at least it works.[/list]

how would you go about forwarding a port

andre thanks figured itoout

Tried almost everything..even with DMZ, the 2 tests(5&6) still fail!

Btw I am using is a Linksys WRT54Gv5 Router.

NATTrace report (v1.01)

Generated: 5/11/2007 4:41:25 AM (5/10/2007 8:41:25 PM UTC)
Hostname: innovations
adapter: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller - Packet Scheduler Miniport
adapter: Linksys Wireless-G USB Network Adapter #3 - Packet Scheduler Miniport
addresses: 192.168.1.101
gateway: 192.168.1.1
adapter: MS TCP Loopback interface

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: FAILED - Direct TCP to fixed IP
failed - exception caught (Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
Test 6: FAILED - Direct TCP (web) to named host
failed - exception caught (Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
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: SUCCESS - NAT check, port 6112
success
Test 11: SUCCESS - Direct UDP (port 9103)
success
Test 12: SUCCESS - NAT check, port 9103
success
Test 13: SUCCESS - Direct UDP (port 30350)
success
Test 14: SUCCESS - NAT check, port 30350
success
Test 15: SUCCESS - Direct UDP (port 30351)
success
Test 16: SUCCESS - NAT check, port 30351
success

2 tests failed

Out of the 100 game I have attempted to join in the past week, 0 have launched correctly. I run NATTrace with 100% pass rate on all ports, and am using a Siemens Speedstream 4100 in bridge mode and a D-Link DI-514 router, setup to forward all the ports in question correctly. I have completely uninstalled and subsequently reinstalled .NET framework 2.0 (which I believe was unnessecary, but I'm running out of options)

78/100 = kicked by host because I report 'nil' to one or more players
5/100 = game cancelled while joining.
17/100 = timed out while joining game.

S.O.S.

Does anyone else have a similar problem?

hi,

nattrace says

test 10 nat 6112 nat failed

port send package to 10003 instead of 6112

anwone smart nows how to say to your comp he has to send it to 6112??

every port is open everyone says ok exxept the gameport

tryed to switch to port 6113 but giving same results

hope anyone nows what to do

Read others with the same situation, my NAT results are saying that I'm sending out info on different ports than they should be. Haven't found a concrete resolution...anyone have input?

Here's my report....
****

NATTrace report (v1.01)

Generated: 5/23/2007 7:05:39 PM (5/24/2007 2:05:39 AM UTC)
Hostname: magaera
adapter: Intel(R) PRO/1000 PM Network Connection - Packet Scheduler Miniport
addresses: 192.168.1.101
gateway: 192.168.1.1
adapter: MS TCP Loopback interface

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 12026 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 12028 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 12017 instead)
Test 15: SUCCESS - Direct UDP (port 30351)
success



Now, my roommate is having the exact same test result, using the same port variations as mine. We're on the same router, we use a Linksys WRT54GL. Thoughts?

Is this thread dead? Is GPG still working on something, or is it "sorry to all you SpeedTouch users, we won't fix it since we've written in the readme.txt that we don't support Symmetrical NAT and Speedtouch is eurotrash anyways"? It's really frustrating to wait for a patch this long and this still hasn't been fixed. I had high hopes for SC to be the next Total Annihilation. At least I can still play TA...

And to think I've recommended SC to a few collegues, who have a SpeedTouch as well... Not much hope we will ever play together online.

Any updates on Nattrace yet? If I get 100% OK on NetTrace, and cannot play through GPGNet, NetTrace obviously isn't doing the same thing as GPGNet? NowakPL's tool gets some errors...

Not to try to bash you here MadAndy, just trying to keep hope alive.

Guys,

I had these problems but managed to fix them. I cant be bothered to wtite down everything I did (just finished posting on another thread and time is now pressing) PM me if you see me in chat and I'll do what I can to help.

Skynet

Yeah, well after the most recent patch, it seems that all the @#^@ network issues like every other player being 'nil' and most games unjoinable magically returned. Awesome. I am behind a single router to a modem configured in full bridge mode, (IE no NAT whatsoever) My firewall has appropriate exceptions, and all the static ports in question are open (have also tried disabling firewall and connecting directly to the modem.

Note: Some games do, on rare occasion work, which proof enough that it's not my end, (NATTrace passes 100%) I would really appreciate an explaination, if not a fix.

Thanks,
--Meteor

P.S. I check this thread frequently, dead though it may seem -- feel free to direct any questions to me, I'll answer to the best of my ability.

Unfortunately, this is no proof the problem is not at your end. Mine is in DMZ mode and I still cannot connect to other symnat routers. When I had everything set up correctly, I could join 95% of the online games except for my friend's, who is behind symnat too.

At a given time (not after patch changes), I could join only 20%, and there were lots of nil pingers, thus unplayable.

I changed nothing, and tried the other day. I'm back to 95%. Seems like a modem reset, somehow? After the latest patch, things seem unchanged. I can still play most of the games.

Yea, you're right,

I don't have enough information to say, for certain, that the problem isn't on my end, merely that I have done everything I know how to, eleminating possibilities. For the love of numbers, I don't know what % are joinable, merely that it is small (a lot less than half).

One other recent development which has occurred without any local settings being changed is that, even within the joinable games, I very frequently encounter the "Connection to Host Timed Out." Messege, with available options: Keep trying and Give up. Needless to say, Keep trying hasn't worked yet, so I am completely losing contact with the host (usually with a ping well under 200ms) fairly frequenty in the lobby.

I am using a D-Link DI-514 with appropriate port exceptions made for Supreme Commander to run, and a Speedstream 4100 ADSL modem, set to full bridge mode, so as to circumlocute the above mentioned NAT issue. I am running Sygate Personal Firewall, also with exceptions set and tested. NATTrace passes 100% (still) I have tried assigning manuel local IPs to my computer and router, with no success, and am Currently set to automatic (DHCP). Every other online game I play (Kalonline, StarPorts: GE, GO! Online, Doom 3, MS Flight Simulator X) work without issue.

Thanks again,
--Meteor

I don't know about half of your games, but I know and agree that SupCom cannot have the same connectivity system as Doom 3 in something bigger than a 1vs1 match.

Anyhoo, only way I got mine working(ish), is trying out sticky http://forums.gaspowered.com/viewtopic.php?p=166999 in DMZ mode.

I got some problems now and then, but for most of the time, I can connect to every game I wish (everything except my friend, since he is using the same symnat modem/router like me :/).

Yeah,
Thanks for the suggestion, neilsvk but I can already pass the NATTrace tests, so I'm not sure what I could accomplish by setting up a DMZ to get around the NAT issue.

In any case, I get about 1-2 nils per game lobby I join, and am usually kicked by the host. Interestingly as well, it is usually me, as the error messege the host receives, on average says Meteor (my GPGNet handle) cannot connect with so-and-so, not the other way around. Not to take this personally, but it does get a bit old when I don't know what, if anything I did or am doing to create this problem. Any further light that could be shed on this issue would be greatly appreciated.


Frustrated,
--Meteor

To be honoust, I don't know why turning DMZ on didn't work and by doing the things in the post in addition to it suddenly cleared all problems. I guess there still is a thin security layer around DMZ set up by the manufacturer through which I had to make a hole...? I just know I had the same problems as you. It's not the ideal solution, but at least I can play online.

Unfortunately the GPG side has been pretty quiet about these issues other than stating in the readme.txt that symnat routers don't work so well.

I'd like very much to try that,

However, I understand the workings of a DMZ only in theory, and haven't ever poked around with those settings in particular on my router, thinking that I would need a host (for the DMZ) which I do not have. While there is one other machine on the network, using the same router, I don't have access to it, so that's out. So, unless it's possible for my dinky DI-514 router to provide said DMZ hosting, I think that's out.

If I've gotten something fundemental horribly backwards, please let me know.

I see nil people.

--Meteor

Two computers rule DMZ out, I think so too. On the other hand, if you don't need the 2nd computer when you play SupCom online, you can still do it. I have two connections: the ethernet port direct cable connect and the wireless. I use the wireless for regular use. But in my router, I set the DMZ for the ethernet port. So when I play Supcom, I disable wireless and enable ethernet by using Windows Network Connections...

But do you have a seperate modem and router? You can still try direct connecting your pc to your modem then...? Practically the same thing.

Yeah, I figured that too, and while I have tried playing directly connected to the modem (at the expense of the other user), it's been at least 2-3 patches since then, so I may give that a whirl again.

I just replayed the single-player campaign since I'm pretty much a desease on GPGNet and I must say, having an Asshat AI buzz in every 5 minutes and tell me to check my objectives with no option to turn it off is pretty annoying. Might as well have called it supreme lacky.

Anyway, I'm gonna go direct to the modem this time, using only my soft-firewall on my machine (already configured) and if that doesn't change anything I might poke around at the DMZ settings, also at the expense of the 2nd user in my network.

Again thanks for the continued posts, nielsvk, even after the GPG guys have gone.

Peace,
--Meteor

Yeah, that's really the most frustrating part. They seem really helpful, but with dead ends, they just silence you to death.

Again, good luck. Maybe we'll meet online some day...

Yea, if I ever manage to get this to run, I'll try to play a game or two with ya.
Why is it that there aren't better instructions for this, and yet my #@&^# Pop Tarts have instructions on them!? (Remove Pastery from Pouch.)

Thanks again.

--Meteor

OK I think being blown off have not heard back from THQ about conettion problem , it seems when the got stumped the ignored me on phone and e-mail. here info i have
this is from trace they had me download and run and shows no problem and that when the e-mails and support stopped and will not even call me back. below are trace report and also copy if e-mail < the last they returned that is have sent repeated e-mails and left several messages on tech phone

ANYBODY HAVE A CLUE ? I have un-installed firewalls and disabled window's from booting up and un-installed SC and re-installed around 5 times each time tryed I re-downloaded patch and re-installed them too...

E-mails:
Thank you for contacting THQ Technical Support.

At this point we suggest that you use the network tool (it is from the Supreme Commander developers). You can download this from the following link:

http://cavesvr.caverock.com/~andrew/nattrace/

This is a small program that will test your internet connection to see if it's suitable for playing Supreme Commander. If it finds any problems it will attempt to provide suggestions on what can be done to make things work. It also lets you save a report for sending to others to help with fault assistance. Let us know how this worked out for you.

Note: GPGnet and Supreme Commander require the following ports to be open:

* Ports 30350 and 30351 opened for UDP traffic, to allow for GPGnet logins
* Port 9103 open for UDP traffic, to allow for GPGnet-brokered matchmaking
* Ports 6112 open to UDP traffic, to allow for SupCom gameplay. This port is among the most common ports used by online multiplayer games of all kinds."


Best regards,

THQ Technical Support


--Original Message--
From: bprunty67@hotmail.com
Date: 5/9/2007 3:25:13 PM
To: support@thq.com
Subject: Re: Supreme commander...GPGNET [#3220]


yes , as i had said in last e-mail "Nope same crap" as in did what e-mail said even over wrote the patches i had save to disk. all back ground software including fire wall off and no way to set the conection type with you software for GPNet




--------------------------------------------------------------------------------
From: "support@thq.com" <support@thq.com>
Reply-To: support@thq.com
To: bprunty67@hotmail.com
Subject: Re: Supreme commander...GPGNET [#3220]
Date: Wed, 9 May 2007 19:24:50 +0000 (GMT)


Thank you for contacting THQ Technical Support.

Have you tried connecting in a clean boot state as suggested below?



Best regards,

THQ Technical Support


--Original Message--
From: bprunty67@hotmail.com
Date: 5/9/2007 11:17:46 AM
To: support@thq.com
Subject: Re: Supreme commander...GPGNET [#3220]


nope same crap , no I have no router and conected with Motorola cable modem and no other software has a problem but yours!




--------------------------------------------------------------------------------
From: "support@thq.com" <support@thq.com>
Reply-To: support@thq.com
To: bprunty67@hotmail.com
Subject: Re: Supreme commander...GPGNET [#3220]
Date: Wed, 9 May 2007 17:29:29 +0000 (GMT)


Thank you for contacting THQ Technical Support.

Are you connecting to the Internet through a router? If so, we cannot offer tech support for your router (because of the large number of different router brands and manufacturers'). If you are using a router, try connecting directly to the Internet (directly connected to your modem, not going through a router).

Regarding the patch update issue. You can download the patch update in two parts from the links below:

a: first download/install this patch update:

http://www.fileshack.com/file.x/10225/S ... Patch+3217

b: then download/install the more recent patch update:

http://games.softpedia.com/get/Patch/Su ... atch.shtml

If the suggestions above did not resolve your issue, then try connecting in a clean boot state. The clean boot shuts down any running programs in the background (such as anti-virus/spyware, etc.) that may interfere with the game.

Here's how:

Note: if you have the Vista operating system, then click on the link below for clean boot instructions for this operating system:
http://support.microsoft.com/kb/331796

Prior to installing/playing the game, click on START and then click on RUN, type msconfig in the Open box, and then click OK.

On the General tab, click Selective Startup, and then CLEAR the Process System.ini File, Process WIn.ini File, and Load Startup Items check boxes. Note: You cannot clear the Use Original Boot.ini check box so just keep that the way it is, as well as the Load System Services.

Click on the Services tab, select the "Hide All Microsoft Services", and then click "Disable All".

Click OK, and then click Restart to restart your computer.

After the computer restarts, try installing / playing the game.


When you are done playing the game, return from a clean boot state:

1. Click Start, click Run, type msconfig in the Open box, and then click OK.

2. On the General tab, click Normal Startup - load all device drivers and services.

3. Click OK, and then click Restart when you are prompted to restart your computer.


Best regards,

THQ Technical Support


--Original Message--
From: bprunty67@hotmail.com
Date: 5/8/2007 3:45:39 PM
To: support@thq.com
Subject: Re: Supreme commander...GPGNET [#3220]




6) What to do if you CANNOT connect to GPGNet?

A: If you have firewall software, please make sure you have ports 30350, 30351, 9103 and 6112 open to UDP traffic.

7) What are automatic patch downloads?

A: GPGNet automatically delivers patches of itself and of Supreme Commander to connected players. If patching fails, never seems to end or aborts, make sure you don't have anything in the background that is either updating Windows or using your Internet connection during the patch download and application process.

Yeah did that and turned off fire wall included I WANT A REFUND AT THIS POINT !

If that all the help you can give!




--------------------------------------------------------------------------------
From: "support@thq.com" <support@thq.com>
Reply-To: support@thq.com
To: bprunty67@hotmail.com
Subject: Re: Supreme commander...GPGNET [#3220]
Date: Tue, 8 May 2007 22:23:04 +0000 (GMT)


Thank you for contacting THQ Technical Support.

Please review the information below regarding online/multiplayer tips for this game:

MULTIPLAYER SUPREME COMMANDER

http://info2.thq.com/faq_sc/

LAN and Direct IP Multiplayer Connect:

Players can connect to each other either locally over a Local Area Network (LAN) or remotely via direct IP connection. Both connection types use the TCP/IP protocol. To host or join either type of game, click Multiplayer > LAN/IP.

Host a LAN or Direct IP game:

1) From the Main Menu, click Multiplayer > LAN/IP.
2) Enter your nickname.
3) Click “Host�.
4) Enter the Game Name that you want other players to see.
5) Enter a custom port or leave it set to “Auto� (recommended).
6) Click “Create�.

If you have players joining via Direct IP, you will need tell them your IP address, along with the Port on which the game is running. The game will tell you the current Port number in the chat area of the Game Lobby.

Join a LAN game:

1) From the Main Menu, click Multiplayer > LAN/IP.
2) Enter your nickname.
3) Click on any available games in the highlighted Server List window. Information on that game will be displayed in the Server Information window to the right.
4) Click “Join� to play or “Observe� to just watch the game, if the host has allowed observers. You will then appear in the Game Lobby.

Join via Direct IP:

1) From the Main Menu, click Multiplayer > LAN/IP.
2) Enter your nickname.
3) Click the “IP Address/Hostname� field at the bottom of the window. This area will become highlighted, and a cursor will appear in the field.
4) Enter a valid IP address or Hostname into the “IP Address/Hostname� field.
5) Enter the Port number in the “Port� field.
6) Click “Join� to play or “Observe� to just watch the game, if the host has allowed observers. If the IP/Hostname and Port are valid, you will appear in the Game Lobby.

If you wish to join a LAN game instead, simply click in the “Server List� window to highlight it, choose a server, and press Join/Observe as normal.


GPGNet:

GPGNet is an Internet gaming service provided by Gas Powered Games which allows players to meet up, challenge other players, join games, and compete in a worldwide ranking system, all without paying any special connection charges.

In order to use GPGNet, your computer must have the TCP/IP protocol installed, and must provide TCP/IP support for 32-bit applications.

Product Key Required
• You must have installed Supreme Commander with a valid product key in order to connect to GPGNet and play online. A product key cannot be connected to GPGNet by two PCs at the same time. If upon connection to GPGNet you receive an error message related to your product key, please re-install Supreme Commander and enter a valid product key.

Online Knowledge Base
• GPGNet includes an extensive Knowledge Base with troubleshooting information for both GPGNet and Supreme Commander. You can find the Knowledge Base by opening GPGNet and going to Help > GPGNet Knowledge Base.

.NET 2.0 Framework Required
• GPGNet requires the .NET 2.0 Framework installed in order to function. The necessary files are normally installed along with your installation of Supreme Commander. Some users, however, must install the framework separately. If you receive an error message reading "can't find MultiplayerClient.exe," this is usually caused by a failure to have .NET 2.0 installed. You can locate the files by using Windows Update or by visiting http://www.microsoft.com/net.

Firewall settings
• Open ports 6112 to UDP traffic, and open 9103 to UDP traffic. These are among the most common ports used by online multiplayer games. SupCom cannot be modified to use other ports. Also, open ports 30340 and 30341 to UDP traffic, for GPGNet to function. Make sure that GPGNet and SupCom appear on your Windows Firewall exception list, and the exception lists of other firewall products you are currently running. If you are behind a DMZ, disable all on-access scanners.

Anti-virus software
• Many users of antivirus software (such as Nvidia Access Manager, NOD32, Norton, PandaSoft, etc.) are unable to connect to GPGNet, experience poor performance or game crashes. If you experience trouble, we suggest that users place both SupCom and GPGNet on the exception lists for these software products or otherwise disable them during gameplay.

If you CAN connect to GPGNet, but CANNOT connect to games
• First, please understand that SupCom is a peer-to-peer multiplayer game, meaning that open connections must exist between all the players attempting to play. While common for RTS games, this configuration differs significantly from server-client games such as first-person shooters and MMOs. If you CAN connect to GPGNet, but CANNOT connect to games, this is likely a firewall or antivirus conflict either with your own connection, or your opponent's connection. It is not uncommon for players to be able to connect to server-client games but be unable to connect to peer-to-peer games. Please see the steps above to open your connection to all necessary traffic in order to play.

If you CANNOT connect to GPGNet
• If you have firewall software, please make sure you have ports 30350, 30351, 9103 and 6112 open to UDP traffic.

Automatic patch downloads
• GPGNet automatically delivers patches of itself and of SupCom to connected players. If patching fails, never seems to end or aborts, make sure you don’t have anything in the background that is either updating Windows or using your Internet connection during the patch download and application process.

Routers with Symmetrical NAT
• Certain routers that use symmetrical NAT may not work well with GPGnet and Supreme Commander. These routers are very rare, and most have firmware updates available to fix the problem. If you are using a router with symmetrical NAT, please contact the manufacturer to see if there are firmware updates available.


Best regards,

THQ Technical Support


--Original Message--
From: bprunty67@hotmail.com
Date: 5/3/2007 9:46:38 PM
To: support@thq.com
Subject: Supreme commander...GPGNET


Keep Getting error " 1 core:1 Could not connect to GPGNet: supreme Commander. Please check your internet connection and try again" well my net connection works just fine you software don't ! GPGNet might want to check your internet connection or hire new IT people.


What the heck tryied reload 3 time and no luck Did the support end the minute that i paid for game?
If anybody knows more can you help , I'm betting the users know more than GPGNet does.








| | | | | Inbox

Get the latest updates from MSN
MSN Home | My MSN | Hotmail | Search | Shopping | Money | People & Chat
Feedback | Help
© 2007 Microsoft TERMS OF USE Advertise TRUSTe Approved Privacy Statement GetNetWise Anti-Spam Policy

and here is other e-mail........

From : <THQ@thq.com>
Sent : Friday, May 18, 2007 6:19 PM
To : bprunty67@hotmail.com
Subject : THQ Support - Supreme Commander - Problem connecting online - 1 Core: 1 Could not connect to GPGNet: Supreme Commander...

| | | Inbox


Hello Brian:



I spoke with my Supervisor regarding your call today. He said at this point, your best bet is to check the tech support forums on GPGNet regarding this. We found this link on the GPGNet forum that deals directly with this. You might find some assistance there:



http://garage.gaspowered.com/?q=node/7860







Sincerely,



Peter

THQ Technical Support






NATTrace report (v1.01)

Generated: 5/10/2007 1:22:37 PM (5/10/2007 6:22:37 PM UTC)
Hostname: brian
adapter: Realtek RTL8169/8110 Family Gigabit Ethernet NIC - Packet Scheduler Miniport
addresses: 76.177.226.48
gateway: 76.177.224.1
adapter: MS TCP Loopback interface

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: SUCCESS - NAT check, port 6112
success
Test 11: SUCCESS - Direct UDP (port 9103)
success
Test 12: SUCCESS - NAT check, port 9103
success
Test 13: SUCCESS - Direct UDP (port 30350)
success
Test 14: SUCCESS - NAT check, port 30350
success
Test 15: SUCCESS - Direct UDP (port 30351)
success
Test 16: SUCCESS - NAT check, port 30351
success

0 tests failed