Page 1 of 1

problem running SCPT

PostPosted: Tue Apr 13, 2004 7:37 pm
by IwantTOplay
when i'm hosting the game, and my friends try to join, they receive a message saying "the game is no longer available" .
:cry:


they can see my game but just can't join.

any ideas why?

PostPosted: Wed Apr 14, 2004 1:39 pm
by poseyjmac
its related to a firewall/NAT most definately.

PostPosted: Wed Apr 14, 2004 3:19 pm
by IwantTOplay
how do i fix it?

PostPosted: Fri Apr 16, 2004 1:15 pm
by poseyjmac
make sure the correct ports are forwarded on the router of the server. and make sure the correct ports are routed in GIT.

PostPosted: Fri Apr 16, 2004 7:01 pm
by IwantTOplay
they are all done correctly but i still can't find the problem. :cry:

PostPosted: Wed Apr 21, 2004 3:06 pm
by Ice_
Got the same problem and I've found the source of the problem. When you are about to connect, your game suddenly tries to connect to 192.168.0.1 even if the server ip is 222.222.222.222. This problems occur if the server has NAT activated (internet sharing). When you are internet sharing under Windows 2000/XP you get the IP 192.168.0.1 (bingo) and your internet ip 222.222.222.222. I dont know where the problem is, if it's in GIT or the game. But I have reasons to believe that GIT takes the wrong ip number, I could be wrong but thats what I think.

To fix this, remove NAT.

EDIT: oooh, I got it to work, right click the application and go into advanced configuration. On the far right almost at the bottom, check "Alter source IP (for NAT)"

In from hostname: 192.168.0.1
To hostname: his IP (in my case, 222.222.222.222)

GOOD LUCK :D

Thx for a great program GIT crew ;)

PostPosted: Wed Apr 28, 2004 12:55 pm
by IwantTOplay
Ice_ wrote:In from hostname: 192.168.0.1
To hostname: his IP (in my case, 222.222.222.222)


are you saying that both sides (the host and teh client) have to set the external ip address to teh host's ip address?

PostPosted: Mon May 03, 2004 9:04 am
by Ice_
I dont really know, I did in my case changed this setting on both the server and the client. This fixed it. I think the clients only need it though.