Game Development Community

LAN Network problems, IPX?

by Bruce Wallace · in Torque Game Engine · 04/01/2002 (9:19 am) · 10 replies

I was searching around and found an old thread with similar problems but instead of bringing back an old post i'll just link it here.

www.garagegames.com/index.php?sec=mg&mod=forums&page=result.thread&qt=1506

I have been trying to figure this out, but haven't been able to get anywhere with it.


Problem:
Cannot connect to a server on my home LAN(connect() wont work either). In an earlier head version The LAN game would show up and I could join and play in it. After RealmWars was released I tried the same thing and haven't been able to connect. I Just got done making a few console logs wich will follow.

What I am asking for is ideas on how to fix this or why it no longer allows me to connect to LAN hosted servers. It also seems that IPX has something odd going on with it as I never get a response from LAN server ping. But I suspect In the working version the 192 IP is IPX, Just guessing as I only have a vague idea on how the connections are resolved.

First: My network.

ISP->router->10/100 switch/hub->computers used for this test.

Router:
IP: 24.159.129.152
Subnet: 255.255.255.0

Server IP: 192.168.0.116
Subnet: 255.255.255.0

Client IP: 192.168.0.167
Subnet: 255.255.255.0



The first two log snips are from the logs of an earlier head version(about a month old) in wich the LAN connection worked. The second two are from RealmWars demo.


Client:

//-------------------------- 3/1/102 -- 11:50:12 -----
LAN server ping: IP:Broadcast:28000...
LAN server ping: IPX:FFFFFFFF:FFFFFFFFFFFF:28000...
No master servers found in this region, trying IP:63.224.200.48:28002.
Requesting the server list from master server IP:63.224.200.48:28002 (2 tries left)...
Received server list packet 1 of 1 from the master server (1 servers).
Pinging Server IP:192.168.0.116:28000 (3)...
Pinging Server IP:24.159.129.152:64454 (3)...
Pinging Server IP:24.159.129.152:64454 (2)...
Pinging Server IP:24.159.129.152:64454 (1)...
Pinging Server IP:24.159.129.152:64454 (0)...
Ping to server IP:24.159.129.152:64454 timed out.
Querying Server IP:192.168.0.116:28000 (3)...
Server query canceled.
Connect Challenge Request: 1
Got challenge response
Sent connect request
Connection accepted - id 1446 protocol 5


Server:

Received info request from a master server [IP:63.224.200.48:28002].
Got challenge request
Sent challenge response
Connection request from: IP:192.168.0.167:28000
Accepting connect... CLIENT ID = 0
Sending connect accept: 1446
CADD: 1446 IP:192.168.0.167:28000


Client:

//-------------------------- 3/1/102 -- 11:54:24 -----
LAN server ping: IP:Broadcast:28000...
LAN server ping: IPX:FFFFFFFF:FFFFFFFFFFFF:28000...
No master servers found in this region, trying IP:216.116.33.156:28002.
Requesting the server list from master server IP:216.116.33.156:28002 (2 tries left)...
Received server list packet 1 of 1 from the master server (3 servers).
Pinging Server IP:24.159.129.152:64482 (3)...
Pinging Server IP:80.129.44.4:1034 (3)...
Pinging Server IP:24.112.197.55:29000 (3)...
Pinging Server IP:24.159.129.152:64482 (2)...
Pinging Server IP:24.159.129.152:64482 (1)...
Pinging Server IP:24.159.129.152:64482 (0)...
Ping to server IP:24.159.129.152:64482 timed out.
Querying Server IP:24.112.197.55:29000 (3)...
Querying Server IP:80.129.44.4:1034 (3)...
==>connect("24.159.129.152:64482");
Connect Challenge Request: 1
Connect Challenge Request: 2
Connect Challenge Request: 3
Connect Challenge Request: 4
Connect Challenge Request: 5
==>connect("192.168.0.116:28000");
Connect Challenge Request: 1
Connect Challenge Request: 2
Connect Challenge Request: 3
Connect Challenge Request: 4
Connect Challenge Request: 5

Server:

Received info request from a master server [IP:216.116.33.156:28002].
Sending heartbeat to master server [IP:216.116.33.156:28002]
Received info request from a master server [IP:216.116.33.156:28002].
Got challenge request
Sent challenge response
Sent challenge response
Sent challenge response
Sent challenge response
Sent challenge response
Received info request from a master server [IP:216.116.33.156:28002].
Sending heartbeat to master server [IP:216.116.33.156:28002]
Received info request from a master server [IP:216.116.33.156:28002].

Does anyone Know what is going on? How would I test IPX I've tried connect("IPX:FFFFFFFF:FFFFFFFFFFFF:28000"); etc.
I posted in bugs because it worked before and I have no idea where to start.
Any Information is appriciated.

thanks,

Bruce

Edit: fixed url.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque Owner Josh Goldshlag
#1
04/01/2002 (9:30 am)
Are both the server and client running the realm wars version of Torque? Can you try going back to the old version and see if that still works? If it does, at least that rules out possible network hardware changes/problems.

Josh

Torque 3D Owner Bruce Wallace
#2
04/01/2002 (9:33 am)
yes the first two client and server are from a month old head version that I have been working with and it still works with that old head(look at the dates on client logs, they are kinda messed up, but the same). The second two blocks of console logs are from client and server of realmwars.

Edit: I just looked closely at the dates.. I guess thats a bug too heh.

Torque Owner Edward Gardner
#3
04/01/2002 (9:42 am)
include the port in the connect statement, it seems to be required now:

connect("127.0.0.1:28001",$Client::Password,$pref::Player::Name);

-edit-
never mind, I see you ARE including the port, sorry :(

Torque 3D Owner Bruce Wallace
#4
04/02/2002 (5:46 am)
This problem seems to only exist in non dedicated hosts. I can start a dedicated server and join it on the same machine and the rest of the network can join also.

hmm.

Torque 3D Owner Joel Baxter
#5
04/02/2002 (9:01 am)
In older versions of torque, the client initialization would call setNetPort with $Pref::Net::Port as argument. I checked the CVS head version recently, and now it calls setNetPort with an argument of zero, I guess to disable any current port bindings.

From the comment above that line I assume that this was done because singleplayer games don't need to use the network. However, it seems like this change would hose listen servers, because the only other place that setNetPort is called is in the dedicated server initialization (using $Pref::Server::Port).

So, I wouldn't be surprised, given the symptoms you describe, if we need another call to setNetPort somewhere for listen servers. Or actually, it seems like it would be best to just have one call to setNetPort overall, inside createServer, in the block of code that does stuff when the server type is MultiPlayer.

If you try that out, lemme know what happens... I'm moving to a new house right now and I'm not really able to test things that would involve multiple computers. :-)

Torque 3D Owner Bruce Wallace
#6
04/02/2002 (10:26 am)
Thanks alot Joel, replacing 0 with $Pref::Server::Port in the client init.cs allows the game to be found via master server.. still don't think the IPX Broadcast is functioning correctly but this puts the current head and realmwars back to the way they were working before.

Torque 3D Owner Joel Baxter
#7
04/02/2002 (12:18 pm)
Cool.

Have you tried consolidating the setNetPort calls into one call in the multiplayer portion of createServer as mentioned above? Just pick one or the other of the prefs to use for that call, I'd say $Pref::Net::Port. (Don't see why we'd need separate prefs for listen server port and dedicated server port anyway.)

Torque 3D Owner Bruce Wallace
#8
04/04/2002 (9:00 am)
I haven't tried it yet, got sidetracked fixing some issues with the particle editor. I definatly want to look into this further. I'll let you know if I discover anything. And while I am posting here, Does anyone have any Idea of testing the IPX out?

Torque Owner Tim Gift
#9
04/05/2002 (9:15 am)
That client port initialization shouldn't have been changed... I'll look into it.

Torque Owner Tim Gift
#10
04/05/2002 (10:21 am)
Checked in a fix to CVS.