Why I can't connect to server...

#1 Wonderful...

#2 Because Garage Game's master server either isn't running or isn't reachable? It happens from time to time. Try again a bit later on.

#3 I'm confused, you say "Internet not connected" down when you list your system specs. So of course you can't run a dedicated server and expect to see it on the master server list...

You could direct connect to it however through a lan.

#4 Ah I missed that. He probably doesn't realise that the dedicated server connects to GG's master server and registers itself. So when you query servers as a client, it receives a list of registered dedicated servers from GG's master server.

Isn't there a way to connect to a dedicated server without using GG's master server?

#5 Yes, but you need to know the ip of the dedicated server.

However, if his server isn't connected to the internet than thats useless unless the client trying to connect to his server is on a local lan.

#6 What if he's running the server and client on the same PC like I do? Can't he somehow ignore the master server and specify localhost as the server the client should connect to? I really need to look into this for my own use.

#7 Yes, just enter the localhost ip. I forget what that is.

#8 Does that help at all Rem?

#9 Even without the masterserver the Join Game window should show the servers running on the same LAN as the client PC. Even without TCP as Torque supports IPX.

#10 Hi all.

Thank for help.
I using 'connect("IP");' and all worked.

Thank again.

#11 Hello!

I read this thread, and I still meet problems.

A few questions then, if some of you can help me.
I try to set up a local server (offline). THe mission loads, and then I get the following message, like Rem Jenus:
"
>Bad master server address: 2:master.garagegames.com:28002
>No master servers found
"

1. At that time does this mean the server is running or that it failed?

I wanted to have both client and servers on the same machine, so
from the client side now, I tried to type:

connect("127.0.0.1"); in the console

and

connect("10.1.1.8"); (the ip I used at that time)

each time it ended in failure
("Connect Challenge Request: 1")
("Connect Challenge Request: 2")
("Connect Challenge Request: 3")
("Connect Challenge Request: 4")
("Connect Challenge Request: 5")

then fail.

So, my question is:
2.is this really possible to run both client and server on the same machine?
has someone done this and what is the procedure?

Thank you for having read this, and I wish someone can help me

Cheers,

Laurent

#12 Yes, it is possible the run a client and a dedicated server on the same machine. I do this. To do that, I do the following:

First of all, start a dedicated server using this syntax in your shortcut:
torque.exe -dedicated -mission fps/data/missions/whatever.mis

After that, I start Torque over the normal shortcut. In the console I type this:
connect("192.168.1.1"); //for example

and hit enter. After that, you will be connect to your dedicated server. The mission will be automaticly loaded.

That's all! :)

#13 actualy I had an almost identicle problem last night.... I was running a dedicated server on the same machine that I was tyring to run the client on..... I tried tons of things and got console messages identicle to what your getting...... my solution was do download torque 1.1.2 (I was still using 1.1.1), and just transfer my game over to the new release..... after that it worked fine :)

#14 Thank you both for your quick reply!

to Marco:
I tried again. unsuccessfully...

This time, I tried with the release version 1.1.1, (without any of my changes inside)
I tried to run the dedicated server on waterWorld.mis and test1.mis.
in both cases, the servers runs, but the client cannot connect.

Then I tried with the release version of Realmwars, and it worked.
Does this mean there is a problem with the demo given with release 1.1.1?

to Eric:
thanks for the tip, I will try and see if it works (though I am reluctant to merge with the 1.1.2...)
Anyway, it might mean the version 1.1.1 is bugging.
or it might mean I screwed up with it somewhere (which is far more likely :D)

Thank you anyway for your posts.

Cheers,

Laurent

#15 There was a problem with the version 1.1.1 I think. I did exactly the same with both 1.1.2 and the 1.1.1.
and the former worked perfectly. Thanks!

Laurent

#16 no problem, just glad I could help.... your problem sounded identicle to mine from your post :)