As stated in the subject, my friends and I are unable to connect to LAN games on Spring RTS. Here are the steps I've followed in order:
1. Downloaded and ran the latest version of springls (stand alone) 0.37.
2. Logged in using localhost.
3. Hosted a new game (no password, port 8452, no NAT traversal).
3. Started the game, which loaded perfectly.
4. My friend started up his Spring client, and connected using the local IP address.
5. He joined my game, and hit start.
6. It then says "Connecting to server" or something similar with a timer.
7. The timer counts up to 30 seconds, then closes and nothing happens.
We both have the latest lobby version, and the same map and game modes. The above has been repeated multiple times to no avail. Please help. (Will review suggestions tomorrow or when I have the time. Thanks in advance.)
Unable to connect to LAN games.
Moderator: Moderators
Re: Unable to connect to LAN games.
connect to the " local IP address." (whatever it is). i guess thats the problem, connect to the ip of your lan-interface and it should work...2. Logged in using localhost.
from infolog.txt:
[f=0000000] Warning: Opening socket on loopback address. Other users will not be able to connect!
[f=0000000] Binding UDP socket to IP (v4) 127.0.0.1 port 8452
[f=0000000] [UDPListener] successfully bound socket on port 8452
-
- Posts: 3
- Joined: 28 Oct 2012, 09:04
Re: Unable to connect to LAN games.
Ah, okay. So you're saying whoever is hosting the game should not login using localhost, but use the actual IP instead. I'll try that and see if it works.
-
- Posts: 3
- Joined: 28 Oct 2012, 09:04
Re: Unable to connect to LAN games.
Well, I logged in using the host IP and the infolog changed.
It doesn't show the loopback error anymore:
I do appreciate the help though.
It doesn't show the loopback error anymore:
Unfortunately I wasn't able to test and see if it works properly now since everybody left.[f=0000000] Connecting to local server
[f=0000000] Binding UDP socket to IP (v4) 192.168.1.2 port 8452
[f=0000000] [UDPListener] successfully bound socket on port 8452
I do appreciate the help though.