Jump to content

  • Curse Sites
Become a Premium Member! Help
Latest News Article

Connection refused: connect when connecting to a LAN world


  • Please log in to reply
4 replies to this topic

#1

thebombzen
  • Minecraft: thebombzen

Posted 07 August 2012 - 01:15 AM

Hello, my brother and I both have different minecraft accounts. However, when I try to open a world to LAN, and he tries to connect from a different computer, he gets Connection refused: connect. I am running Fedora 17 Linux, 3.5.0-2.fc17.x86_64, and my JRE version is
java version "1.7.0_05-icedtea"
OpenJDK Runtime Environment (fedora-2.2.1.fc17.9-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
He's running Windows 7.

Is there anything I can do to fix this error? Thanks.

Note: I've also seen this error when both people were running java 6.
Posted Image

Register or log in to remove.

#2

starlinvf
    starlinvf

    Glowstone Miner

  • Members
  • 3169 posts

Posted 07 August 2012 - 03:22 AM

First use netstat -loa after opening the LAN game, and see if the port assigned by the game is actually binding to the private IP4 LAN address.....   it "should", but sometimes it'll attach to the loopback or the IP6 address for unknown reasons.

If that looks ok...   You can also try using "direct connect" with the IP address and port to see if it'll at least go through with that. Other possibilities include the Windows box's firewall overreacting to a java process trying to scan the local network.


A quick test is to run 2 clients on the linux box (using separate logins of course), host a LAN game, then use LAN scan and direct connect IP to see what it does.   If you want to get really creative, forward the TCP on the router to your box and use direct connect to WAN address of the LAN host.

#3

thebombzen
  • Minecraft: thebombzen

Posted 07 August 2012 - 04:18 PM

View Poststarlinvf, on 07 August 2012 - 03:22 AM, said:

First use netstat -loa after opening the LAN game, and see if the port assigned by the game is actually binding to the private IP4 LAN address.....   it "should", but sometimes it'll attach to the loopback or the IP6 address for unknown reasons.

If that looks ok...   You can also try using "direct connect" with the IP address and port to see if it'll at least go through with that. Other possibilities include the Windows box's firewall overreacting to a java process trying to scan the local network.


A quick test is to run 2 clients on the linux box (using separate logins of course), host a LAN game, then use LAN scan and direct connect IP to see what it does.   If you want to get really creative, forward the TCP on the router to your box and use direct connect to WAN address of the LAN host.

I grepped the netstat output and it was indeed binding to ipv6:
[Leo@chessman ~]$ netstat -loa | grep 52138
tcp6	   0	  0 chessman:52138		  [::]:*				  LISTEN	  off (0.00/0/0)
[Leo@chessman ~]$

Is there anything I can do to fix this?
Posted Image

#4

6359_
    6359_

    Zombie Killer

  • Members
  • 170 posts

Posted 07 August 2012 - 04:23 PM

You must allow java on the firewall. ( I did it and it worked)
"Well, This is the part where he kill us!"    "Hello, This is the part where I kill you.   CHAPTER 9 - THE PART WHERE HE KILLS YOU

#5

thebombzen
  • Minecraft: thebombzen

Posted 07 August 2012 - 08:20 PM

View Post6359_, on 07 August 2012 - 04:23 PM, said:

You must allow java on the firewall. ( I did it and it worked)

Could you tell me how you did that? I tried google and poking around system-config-firewall and couldn't find out how.
Posted Image