I'm assuming your home network looks a bit like this:
Your Server / PC <-----> Router <-----> The Rest of the Internet
If so, you need to logon to your router and forward the ports from that to your server. Unfortunately this varies between each router, and each make. Check out portforward.com, or let us know which router you have and someone might beable to help.
everyone lags...the point is how much lag...it could be 0.01-0.2 milliseconds then its not noticable...but anything above that then it becomes noticable, but again that depends on the server...the server has to beable to upload to what 23 people at once...thats 4kbps per person so thats roughly 96kbps but thats only in game...then you have to add more kbps to get them to move...which brings to around 453kbps for 20 people in game at one time, assuming they are lagging the norm of 0.01 - 0.2 milliseconds.
and it depends on if you have a true 10meg broadband connection, which is around 1 meg upload connection....then it gets complicated so it depends on your connection, port forwarding, your clients connections...
and btw it sounds like your clients are timing out..
Hey guys...you'd think this would have covered all the base by now but......anyway here's my situation:
--> my router
-I can host through my game have ppl join and race
-I can run the ded.server (nogfx) app. on my pc, then through the game I can find my "ded.server" and join to myself and race with others joined as well
BUT when I do this:
--> my router
-I run the ded.server (nogfx) app. on my pc#2, I can see my server on lfsworld but not ingame from pc#1, also I can not manually enter the server name & connect...I get the ok button then it hangs (pauses like it's searching) then the ok button returns.
-windows on pc#2 has asked and has been granted access for LFS to be unblocked.
What i don't get is it's the same router & confg. and all that. My next step is to switch the slots the ethernet cables go into...pc#1 is in slot #1 / pc#2 is in slot #2...I'm wondering if the router (SMC) is physically internally wired so that slot #1 is a master.
I'm new to this networking stuff so I'm sure there's something simple I'm just missing. Any help would be great!
You're still port forwarding to the PC1 most likely. You'll have to change that, if you want to use PC2 as a public server.
When you're connecting to the game inside your network, just goto Multiplayer > Join Specific Game, select Local Network, and type in the local address of PC2. No need to go via the in-game list, its much faster, etc.
Heh, its the middle of the afternoon here Yes, I'm supposed to be working... shush (actually I'm just waiting for 3:30pm so I can go and pick up my new car , its been too busy this week, so I deserve a little time to "myself" (i.e. the forums) for a few minutes )
Not quite a conflict, but it looks like you've got the gist of it. Basically you can only port forward a port/range of ports to one PC at once, and you have to port forward the relevant ports from your router to the PC hosting the server.
Fair enough, depending on your home router it may not work though.
wait...I just re-read your post....you mean only i was experiencing the problem of not being able to connect because of the circular conflict and that someone else (not on my pc#1 or #2) would have been fine.
meaning I got it right and don't have to do anything else
Right click and select Extract to folder, or use your favourite unzipping software. Usually you can double click on the file, and follow the extract procedure. DONE
Either create a new, or copy a new setup.cfg file. I suggest copying setup.cfg, and naming it something you'll remember. Change the config as required. Take a look at the configuration sections to learn more. DONE
Start the server. I usually create a batch file containing
lfs.exe /cfg=<PATH TO CFG FILE> DONE
You can edit and use my batch file attached if you dont know how to make one. DONE
Test connecting to the server. If its on the same PC connect to the IP 127.0.0.1. Otherwise type the IP address of the remote server. If its on the same local subnet, then start the LFS client and Click "Multiplayer", then "Join Specific Game", then select local network. DONE
If you cannot connect, and you got the password (if any) correct, then you need to open the ports in your windows firewall (see the firewall section), or your LAN's firewall. If you have a LAN firewall, then talk to your sys/network admin nicely. DONE
Try connecting from outside your network (i.e. from the internet). Either get a friend to help, or ask on the forums. You'll need to remember to tell us what you called the server. DONE
The first problem is a pretty big one; Your instance of LFS cannot bind to the address and port you've given it. What this means is that it cannot listen for incoming connections. This means one of the following:
1. You've told it to bind to an address that isn't available on the machine (i.e. you've filled in the /ip directive. Unless you know what you're doing, leave this blank / commented out)
2. You've got a firewall preventing you from binding to that port
3. You've told it to use a port already in use
You will never beable to connect locally, using your config, because you've told LFS to only listen on 10.29.78.89. Either comment this line out, or try to connect to that IP from the machine instead of 127.0.0.1.
Unless you have multiple IP addresses, and you only want to listen on one, never configure the ip directive. This ensures that it will bind to all addresses on the machine, including localhost.
With regards to the track info not getting to another PC, its possible thats caused by a firewall.
I'm not entirely following you, which maybe a language thing.
Perhaps a simple network diagram might help? I'm slightly confused by the statement "the whole network is using different subnet masks". Does this mean you have a different subnet for each machine (Surely not?!!?!! That would obviously be a bit crazy, but I've seen worse), or the machine you're trying to connect from is on a different subnet (this would be an infrastructure issue, and out of the scope of this thread somewhat).