Author Topic: Can't connect to LAN game (Read 1239 times)

Evar678 · March 04, 2013, 01:36:02 PM

Ok, so. I need to film something from a different point of view, and so I started a LAN game up. I have two blockland keys, so I started another instance of blockland on the other key. I then tried to join the LAN game, but on the host instance, I get the message: "Blockhead has left the game". I checked the console, and saw:

Code: [Select]

Got Connect challenge Request from 169.254.186.167:36200
Got connect request from 169.254.186.167:36200
    lane name = Blockhead
AUTHCHECK: Blockhead = internet client -> LAN game, rejecting
Issuing Disconnect packet.
CDROP: 97869 169.254.186.167:26200

Any help?

Ad Bot · Advertisement

Zeblote · March 04, 2013, 02:01:34 PM

Did you use 2 different blockland installations?

Evar678 · March 04, 2013, 04:00:09 PM

Quote from: Zeblote on March 04, 2013, 02:01:34 PM

Did you use 2 different blockland installations?

Yes.

Dglider · March 05, 2013, 02:13:40 AM

Wild stab - Are the LAN names the same for both of your installations?

If that doesn't work, block blockland from connecting to the internet with your firewall, or just disconnect your computer, while you're filming. Then it can't do the auth check at all.

Greek2me · March 05, 2013, 02:19:16 AM

Quote from: Evar678 on March 04, 2013, 04:00:09 PM

Yes.

Are you 100% positive that you used separate installations? That's normally the cause of this.

Evar678 · March 05, 2013, 01:44:26 PM

Quote from: Greek2me on March 05, 2013, 02:19:16 AM

Are you 100% positive that you used separate installations? That's normally the cause of this.

100%

Quote from: Dglider on March 05, 2013, 02:13:40 AM

Wild stab - Are the LAN names the same for both of your installations?

If that doesn't work, block blockland from connecting to the internet with your firewall, or just disconnect your computer, while you're filming. Then it can't do the auth check at all.

No, one LAN name is Evar678, the other one is Blockhead
The only reason I was doing this on LAN instead of my dedi was because I didn't have internet access at the time. I also tried this with my wireless adapter disabled, same issue.

DaSord213 · March 06, 2013, 12:42:09 PM

Just start a second instance of blockland using the same installation as your evar one. It should work fine.

Badspot · March 06, 2013, 03:22:07 PM

The client.isLan() function is apparently using some old code that does not recognize the 169.254.*.* block. I have fixed this for the next update.