People cannot join to LAN world: Local game hosted on 0.0.0.0

Can you please attach screenshots of the different IPs and open a dos box, type ipconfig /all and attach the result .

I posted screenshots, unfortunately, when i type ipconfig/all in a dos box, it says that it's illegal command. Not sure if we talking about same thing, i googled dos box and this came out: http://www.dosbox.com

well, I meant dos command prompt, I assume you were right, but the command is "ipconfig /all" (with a blank between "ipconfig" and "/all").
Forget this "dosbox".

usage: ipconfig <command> <args>
where <command> is one of waitall, getifaddr, ifcount, getoption, getpacket, getv6packet, set, setverbose

I'm having this issue in Win7 x64. IP says 0.0.0.0:xxxxx when I go to try to open to lan. Other ppl cannot connect, connection says refused. If you guys want, I can get some IP information together when I get home... weve never had problems before.

Having the same problem on my brother's and my computer. He is running Lion and I am running Mountain lion. Both Java 1.6.0_37. When we open to lan it says localhost 0.0.0.0:50322. When the other computer attempts to connect is says connection refused. No connection issues in 1.4.3 .

I can confirm this also happens on Windows 7 x64 with Java 1.7.0_09 (Java 7 Update 9) which is the recommended build. On my iMac running OSX Lion, I can find the world with the auto search but cannot join as it is bound to the wrong port.

Me after I opened the world to LAN:
http://i.imgur.com/oBqrQ.png

ME finding it on the other computer but unable to join:
http://i.imgur.com/gVnoA.png

I think this is a major bug as it renders LAN unplayable, a huge aspect of post-1.3

Same as DrRed, I am having the exact same problem in the screenshots. My java version is 1.7.0_07 though

java -version
java version "1.7.0_07"
Java(TM) SE Runtime Environment (build 1.7.0_07-b10)
Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode)

My husband cannot join my LAN and says connection refused but it is findable. We switched to the Server.exe in the meantime... works fine.

I have the same issue, macbook late 2007 running 10.6.8, it's binding my LAN world to the ip 0.0.0.0:xxxxx. This is REALLY annoying, cause it's impossible to play on LAN worlds now.

I'm getting the same issue on both Windows 7 and Linux. At least Linux is not binding to localhost any longer. But both are binding to 0.0.0.0:<port>, and even though each can see the other, it will not connect.

I have the same issue on a Windows 8 machine and two Windows 7 machines (all x64).

The Win 8 machine is running java 1.7.0_06, and the bug appeared after upgrading from 1.4.3 (I checked before upgrading to 1.4.4 that the Open Lan command showed the correct IP, after 1.4.4 it shows ip 0.0.0.0

Anyone find a workaround for fixing this?

Hi all - on the Mac at least, there is a workaround. Simply find the IP address of the machine hosting the game (it's reported as 0.0.0.0, but that just means the server is listening on any address - use ifconfig in a terminal, or look it up in your network settings).

Then, in the other machines, do a "direct connect", specifying the real IP address of the host along with the port number it reported when starting up.

So, for example, if you open the game to LAN on a machine with IP address 192.168.0.203, Minecraft will report something like this:

0.0.0.0/57323

On the client machines, you can then do a direct connect to 192.168.0.203:57323

I hope this helps everyone else who's stuck with this frustrating bug - my kids were most annoyed until I worked this out!

Thanks Gavin Sallery! Solved the problem for me and my friends. It would have been good though if the problem had been fixed properly in the 1.44 official update.

Thanks - you are a life saver for my kids too!!

Getting the same bug, I want this to be fixed soon as this is how me and my friend play with each other after school every day.

This issue is happening to me, we are running windows 7; needs to be fixed because there are quite a few people who like to play on lan, should be a simple error to fix and be released for 1.4.5

I have the same problem - and I wonder if this is not happening to people? and why / what is difference

• Mac osx

its still there even with the new update ;S we can,t join each other ;(

To confirm, this issue exists on the PC version too. I've had to manually enter the hosts network IP and randomly generated port to continue to play via LAN.

Just to clarify Stefy, the 1.4.4 recommended build is exactly the same as the pre-release, so it could not have been fixed anyway.

Fixed in 1.4.5.

anyone know the eta of 1.4.5? update?

Adam: the pre-release is available now. The automatic update is due on Tuesday. http://mojang.com/2012/11/minecraft-1-4-5-pre-release/

Attempting the pre-release now, hope it works. I thought it was the mods myself and my husband were using. we only used Optifine, Modloader, and TMI. Will these be obsolete now that i am updating to the pre-release?

Yes you will have to get a new copy. OptiFine and Modloader will not update until MCP is released for 1.4.5 but you can expect TMI to update in the next few days.

I tried the pre-release and it is not fixed for me, although I can direct connect with the IP + the port it displays.

MCPatcher 2.4.3_04 runs fine with 1.4.5 and combines the texture pack and mod loading functions

By MCP I am referring to Minecraft Coders' Pack, not MCPatcher. Also, Modloader is an API created by Risugami for Minecraft mods, it is required for mods created with this tool, it is not a third party installer as I assumed you thought.

Yeah, mixed up Modloader with something else. I was refering to Optifine, not MCP.

Any clues on when this will be fixed for good? My husband and I can use Hamachi, but for some reason Hamachi is very bugged for us. We just want to play together, as does everyone who is posting here. Will this be fixed by next week?

I have the 1.4.5 prerelease and it is not fixed for me.

1.4.5 does not fix this for me on the Mac.

It fixes it for me. I am on a Mac.

Ezekial is correct. It does work except it still shows the IP address for me as 0.0.0.0 and the port. The other machine can connect. It just does not show the IP correct.

If it's still not working for you with the 1.4.5 update, here are a couple of things I did (Windows 7 64-bit):

• uninstalled both 32-bit and 64-bit Java

• installed latest version of 32-bit Java (Java 7 update 9)

I can now connect to and host LAN worlds (although starting a LAN world still displays the incorrect 0.0.0.0 IP address).

I don't know if it was getting rid of 64-bit Java or simply updating 32-bit Java that did the trick. Perhaps try simply updating your Java first, to see if that gets you going.

I also have this problem no matter what OS on 1.4.5. It seems the LAN fixes might have accidentally broken something.

I have to retract my comment that it's working now. Still can't connect in 1.4.5. Should this be re-opened, as the fix does not appear to resolve the bug for everyone?

Reopened.

I had the same problem (running windows 7) all through 1.4.5 and now in 1.4.6. So I reported it and was told my report was a dublicate of this old thread. Well, red tape out of the way, I guess it is time for a fix?

So is there a way to fix ? Or do we have to wait until mojang fixes it?

exists when server is windows xp and player tring to join is on windows 8. now i know its not my terrible network or windows 8 start screen overhaul that is the problem.

And a funny thing is, in 1.4.6, if i (mac osX 10.6.8) open a LAN world to another 10.6.8 mac, then it works, but displays opened lan world on 0.0.0.0:<random port>. But, if i open it, and a windows vista tries to connect, then it does not display, but can be connected to by entering my ip:<the random port>

if you say it's fixed...
THAN WHY DOSEN'T IT WORK!
(will just display at 0.0.0.0:<whatever>
seriously! I think the so called "duplicates" are a diffrent bug!

sorry about the nature of my last comment...
i was just agitated.
i DID try using my normal IP but that didn't work...
dono why it works 4 u. maybe it's because i use a network 😞

To Amon Ymus: the case is that some people CAN'T connect. When we describe the problem we include the fact that the IP address is displayed as 0.0.0.0. Because it is. And then we are told that we can just connect because the 0.0.0.0. thing doesn't matter.

Ok, we get it. It doesn't matter. Does something not mattering fix our game? Apparently not.

This is all intended, you are not supposed to directly connect to the person hosting the LAN world, you are supposed to join through the Multiplayer screen which will list any LAN worlds you can join automagically.

We will change the wording to remove the 0.0.0.0 and make it just: 'Game hosted on port: xxxxx'.

Are you SURE that this is resolved? Because there appears to be a whole lot of "Can't connect to LAN worlds" wrapped up with this "Why does it say 0.0.0.0?" issue. I think someone was far too aggressive in marking LAN world connection issues as duplicates of this 0.0.0.0 issue.

NOT RESOLVED.

Please fire this Anon Ymus dude as a moderator, he only seems to want to tell people that they're wrong and it works, and seems to think it's not okay for those of us who have supported this project for over a year now to be angry when WE ARE IGNORED.

IT DOES NOT WORK.

Michael King, it works. It is not supposed to show the IP when you click Open to LAN, just the port number.

As for the Detect LAN worlds list, that works fine too.

Ezekiel: you are missing the point, as people have before you. Ignore the whole IP address issue. Moderators have closed other issues where it has been stated we can not connect at all. Those issues have been marked as duplicates of this one, and people have been directed here for all LAN world connection issues.

Maybe the IP display is working as designed, but the fact is that people can not connect. It's not that we see 0.0.0.0 and are left puzzled as to whether or not to select that connection. It's that when we attempt to connect, we are told "connection refused" or some other message that means we're simply not connected to the LAN world as attempted.

Ok, I agree on that point. This issue is only about what is displayed, right? I will be back in an hour or two (or more) to sort this out.

Temporarily re-opening as community consensus is that connection fails, not just improper display.

Todd: You are typing the real local address of the LAN server, correct? It should look something like these:

192.168.1.x
10.10.1.x

Not these:

0.0.0.0
255.255.255.255

No it doesn't. Why would we claim that it didn't work if it did? Do you think we LIKE to converse with people who pretend they don't understand what we are talking about? Do you think this is our idea of a good time?

It. Is. Not.

Once more. Sometimes the list of open lan-worlds display the worlds we have opened, sometimes not. Whether it display or not, we cannot connect. We get the "connection timed-out" message, which does not help us in any way in determining how to proceed.

So how does the 0.0.0.0 issue fit into this? IT DOES NOT. Declaring that a non-issue is a non-issue is not support. It is a waste of your customers' time.

Minecraft have a problem for some machines to connect over Lan. It is not consistent for all machines, but if two machines cannot connect it is consistent between those two machines in that they can't just connect sometimes or "if you just do blah." If they cannot connect, they cannot connect.

That is the issue.

Firewall?

Also, does a direct connect work?

If those questions were addressed to me:

I am no super-user, and my fire walls are set up like the factory set them up. I know that I have gotten no error message indicating that the firewalls are the problem. That does not mean that I can discount the firewall as the cause of the problem, but it does mean that I have no way of knowing how to proceed. If you honestly believe that some firewalls cause problems for the game, a FAQ on the issue might be in order.

As for a direct connection, is that when you type the local I.P. address and the lan game code number? I have tried that back in the 1.4.6. to no effect, but not recently.

Can you try doing this process on both the client and server computers:
Start > All Programs > Accessories > Command Prompt
Type in the following on client:

ipconfig /all > %userprofile%\Documents\client_ipconfig.txt

And the following on server:

ipconfig /all > %userprofile%\Documents\server_ipconfig.txt

Attach the client_ipconfig.txt and server_ipconfig.txt files to this issue (or use pastebin) located in your documents folder (eg. C:\Users\Hello\Documents, or type in %userprofile%\Documents as the path as you would with %APPDATA%).

GrygrFlzr: for your question about typing the real local address of the server, I wasn't typing an address at all. Someone else in my home starts a world and opens it to LAN. I can see the LAN world in my Multiplayer screen, but clicking it displays a message "Connecting to the server..." that eventually changes to "Failed to connect to the server Connection timed out: connect"

Trying a Direct Connection to the IP address shown in the LAN world selection (a 192.168. address) has the exact same result.

Here are the ipconfig files from two of my computers. The one named "server" can publish lan worlds that show up on the "client" computer, the reverse is not the case. In any event, no lan play is possible.

ok, I figured my problem out, and this may help some of you.

If you use a network (eg you live near Macca's and use that network) than only the computer hooked up to the network emitter can truly publish LAN worlds but only the computers that use the network can actually access it. In some cases, multiplayer will detect the world, in others you will have to use the i.p.v4 (not the i.p. bet the i.p.v4 -this is important)in "direct connect" plus the stuff thats after the colon ( : ). to get the i.p.v4 you just write "ipconfig" in command prompt (cmd) and it should display it.

Mads Jakobsen:
You've already tried connecting from the 'client' to the 'server' via 192.168.0.100:<port>, correct? And that failed?

If you can see the server in your LAN World list but cannot actually connect the problem lies outside of Minecraft itself. It will be network related.

The LAN Server works relatively simple:
1) The 'host' will turn it on and will allow more than a single person on the world and starts listening at a 'random not used port' (the OS decides).
2) A 'client' going into the multiplayer screen will send out a broadcast packet to which the 'host' will reply.
3) The 'client' will connect to the ip the answer came from with the port specified in the message.

So if you can see the world but cannot connect the problem is outside of Minecraft.

From likely to unlikely (and I probably didn't think of all of them, not a network tech 😃):

• A firewall/something on either host or client prevents you from connecting to the port on the host that replied

• You received a broadcast reply from a place you cannot reach

• Something changed the ip the broadcast got from

• The broadcast reply might be altered

Grum, thank you for providing a response. I've looked at a number of tickets about this issue (most of them just closed as resolved, despite folks screaming that it's not), and this is the first response I've seen from Mojang. Note I've said "seen" for those who will jump on me with links to other responses.

When this feature was first added, it worked great in our household. As of 1.4.7, we can no longer see lan games on our network. Nothing on our network has changed, and the computers themselves have had the firewall disabled, etc.

Is it not possible this is a specific Java patch or something specific to Windows 7? I've seen more people with my issue running Windows 7 than anything else.

I'm on Win 7 64-bit, and I usually run Java 1.7.0_03 64 bit (I do some Java build scripting for work, so I also have 1.6.0 installed, this too broke after 1.4.7).

@ Grygrflzr
I just did so, both ways, and it did not work.

@ Grum
While no doubt well-meaning your response is unhelpful for two reasons: It does not actually resolve the issue, but just point the blame elsewhere. But can you? Consider: You don't actually know anything for sure, and can Minecraft really be said to have functional Lan- play when it doesn't function on ordinary machines, with factory settings, without even a meaningful error message?

The second reason being that we have cases where we can see the lan world and cases where we can't. So already when reading your first sentence I went "Well, that doesn't apply to me!"

Occurs on win8 64 bit and xp32 bit as well.

Occurs on win8 64 bit and xp32 bit as well.

The only way I can make the Open to LAN work is using ad-hoc :/

Mads: the problem is in replication of the issue: I've just tested it here @ home from a win7 (64bit, wired through a gbit switch to the modem) to a osx 10.8 machine (wireless to the modem), worked perfectly fine.

You say that 'the first line' doesn't apply to you; you mean with that the LAN world doesn't show up @ your multiplayer screen?
This means that something is eating the broadcast packets OR their reply, this again is 100% outside of Minecrafts control.

I'd love to be able to help more but I'm not really sure how, could you perhaps verify on the host that there is a process listening on the relevant port?

On windows doing: "netstat -ab" gives me:

TCP    0.0.0.0:56171          Grum:0             LISTENING
 [javaw.exe]

This indicates that javaw.exe (minecraft) is indeed listening on the port reported back by 'Open to LAN'.

From another machine I am able to connect to that port without any problem on the network interface within the network. (in this case its 192.168.1.0/255.255.255.0)

@ Grum: I have no idea what "doing: "netstat -ab" means. I do know that if I had known that I had to know, I would not have brought a second Minecraft for Junior and gotten him all excited about playing multiplayer with his daddy.

I do realize that it is a tricky problem for you that this thing only occur to some people, but... first you said that seeing the world on the multi player screen and then not being able to connect was a sign that the problem wasn't Minecraft's fault. Now you are saying that not seeing the world on the multiplayer screen is a sign that the problem isn't Minecraft's fault.

And hey, HEY! Maybe you are right. Maybe the fault lies with reality and not Minecraft. Maybe it is all those firewall, anti-virus, router and OS companies who didn't do their job just right. But are they going to scramble to make Minecraft multi-player work for everybody? No, they are not.

And meanwhile an unknown amount of people are going to get disappointed when trying to use one of Minecraft's central features, and threads like this will continue to build up all over the internet with their endless "It doesn't work" "Sure it does, stop obsessing about 0.0.0.0. lulz!" "But it doesn't work!" "What is your netstat -ab, bro?"

Regarding netstat -ab:
Start Minecraft, Open to LAN.
Click Start > All Programs > Accessories > Command Prompt
Type in the following on the command prompt:

netstat -ab > %userprofile%\Documents\netstat_results.txt

Attach the netstat_results.txt file to this issue (or use pastebin) located in your documents folder (eg. C:\Users\Hello\Documents, or type in %userprofile%\Documents as the path as you would with %APPDATA%).

I just noticed from the server_ipconfig.txt, you are running hamachi, this (horrific) tool overwrites networksettings on a regular basis and has caused a lot of problems before. Could you try closing that tunnel and (lamely but possibly needed) reboot?

Sorry for not being more descriptive with the "netstat -ab", I always forget that such things might not be as straightforward for everyone. GrygrFlzr explained that far better than me 😃

I do realize that it is a tricky problem for you that this thing only occur to some people, but... first you said that seeing the world on the multi player screen and then not being able to connect was a sign that the problem wasn't Minecraft's fault. Now you are saying that not seeing the world on the multiplayer screen is a sign that the problem isn't Minecraft's fault.

And hey, HEY! Maybe you are right. Maybe the fault lies with reality and not Minecraft. Maybe it is all those firewall, anti-virus, router and OS companies who didn't do their job just right. But are they going to scramble to make Minecraft multi-player work for everybody? No, they are not.

The real problem is that these sort of issues are next to impossible to debug remotely, there are so many factors that can cause problems in networking and it can even for someone who knows how it works exactly be quite the challenge to work out what is going wrong where. And we're not even talking about the 'why' after the 'where' has been found 😞

I do not think there is anything on purpose 'messing around with Minecraft' but it could be for example Hamachi taking the broadcast packet (which is needed to see which hosts are 'open' on the same physical network) and 'failing' to do the right thing with it.

The reason I specified further on the 'not seeing the world' is because after I've tested here (on a not so super typical setup) it just worked fine, this leads me to believe Minecraft is not at fault (also, I should add, I've never tested it before on this network as it's just running for ~36hrs now). Again this was not to confuse you but it's just walking down the path of elimination, if it would not have worked here on my network I would have had to figure out if it was either Minecraft being broken or something in my network settings, in this case it worked, so (very likely) something in your network is causing issues.

My money is on Hamachi! 😃

To temporarily close the tunnel:

1. Open start menu

2. Type "view network connections" in the search bar

3. Click View network connections

4. Select Hamachi

5. Click Disable this network device

6. If a prompt appears, click yes (and type your password if requested).

Note this is a temporary solution that will revert upon rebooting the computer. It is recommended that you uninstall Hamachi completely for best performance.

@Grum. I understand you think it's a horrific tool, but Hamachi is often the only way for minecraft players to host multiplayer servers. since portforwarding is a bit difficult. are there any plans for the sake of this bug, that you are ever (so even if it's still years away), going to make an alternative to hamachi for minecraft?

@Maarten Thijs

There is nothing we can do when something like Hamachi sits in between working or not working of Minecraft, you should really complain with Hamachi on that front.

Besides all of that, it's not even sure that in this case Hamachi DOES cause the problem.

Also with sites like portforward.com it shouldn't be too hard to setup portforwards? though it is a bit technical :/

@Maarten Thijs:

but Hamachi is often the only way for minecraft players to host multiplayer servers.

A LAN world is not a multiplayer server.

@Grum @Kumasassa no you guys don't understand, I was not trying to prove you wrong, because I really believe you are right 🙂, I just read that grum thought it was a horrific tool. the only thing I was trying to do with my comment is explain why people use hamachi, nothing more. and I agree for some people it's not to hard to port forward. but hamachi is more user friendly. So yeah, that was really the only reason I posted that comment. So my comment was just a reply to the word horrific. And my question on the end was just out of curiousity.

friends again?

My son only got Hamachi because someone told him it might fix the problem. I removed it, rebooted, and tried again both ways. Nothing changed.

The Netstat ab thing (again done both ways, from computer A to B and reverse) only produces a short text file telling me the action need administrator rights. Whether this relates to the problem, or it just reveal the fundamental truth that I don't know jack about giving DOS prompt commands administrator rights, I know not.

As to whether LAN networks are super fickle and unreliable and really only fit for advanced users, I'll take your word for it. Still, if this is such an obvious fact perhaps you should share your knowledge with your customers BEFORE they buy an extra minecraft for their household in the misguided belief that it will be fun rather than frustrating. I for one have spend a lot of time and energy on this with nothing to show for it.

I can also speak for serious network issues (non-minecraft) caused by Hamachi. Can anyone reproduce this who has never had Hamachi installed?

I have never had hamachi and get the problem too.

As I said, I had the problem before I tried out Hamachi.

I don't run Hamachi.
Open to Lan working up until yesterday. (maybe 3 days, before, as we don't play every day).

On Laptop 1
I see the Lan World,the I select Join Server. Result: Connection Timed Out.
I try Direct Connect using the IPv4:##### shown for the LAN World. Result: Connection Timed Out.

On Laptop 2
I tried Open to LAN on my Laptop instead. (We usually Open to Lan on my son's laptop. I wanted to see what reverse result would be.)

When I Open to Lan, my son doesn't see it on his Laptop, and my World shows as 0.0.0:49387

I typed netstat -ab > %userprofile%\Documents\My Documents\netstat_results.txt at DOS prompt.
When I opened the NetStat_results.txt, I could not see anything related to java in the file. There was a lot in the file, scanned as best I could, then did ctrl f java.

Is there anyway I can get java to listen? : )

I can tell you that my laptop has 32 bit Windows OS, whereas my son's has 64 bit, based on what I saw under Control Panel/Performance Tools. Not sure that is issue, since it worked before.

We both have MC 1.4.7.
My son is finding a lot of coal and iron, and I am jealous because I can't get in. : ) MineCraft is the best, most unique game. Have really enjoyed playing.

I believe I have attached netstat_results.txt and netstat_results2.txt (Ran twice.)
Hope this helps.
Thank you for your time.

Forgot to mention, son has new Asus laptop with Windows 8 OS, 2 GB RAM, and I forgot what processor, video but they meet reqs, I checked. (Currently in use.)

My laptop is HP running Windows 7 Enterprise OS, 2 GB RAM

HOW TO FIX AND IT WORKS

https://www.youtube.com/watch?v=8CaWO_tPVXE

Thank you Stirling. Here's what I forgot. My son's laptop is new. A couple days ago, I noticed that Windows Defender hadn't been activated. So, I activated it. I now believe that is what caused the problem in the first place. I just forgot I did it. So, I followed your instructions on his laptop. I also followed your instructions for my laptop.

Here's an interesting thing. My laptop is my "work" laptop. I.e., I really shouldn't be playing Minecraft on it - or changing the firewall settings. So, after I followed your instructions for my son's laptop and mine, I tested Open to Lan, and it worked!

Then, I went back to my laptop, and undid what I had done to it. I just wanted to see if it would work, since ostensibly, the only laptop that had a change since the last time it worked was my son's laptop. And, guess what? For some reason, I only needed to fix up the firewall problem on my son's laptop. I didn't need to do it on my laptop.

Someday when I have some time, I am going to look into this more. But for right now, I have some coal to mine!

Thanks again!

Resolving as invalid because this comes from non-minecraft problems.

I concur.

@Anon Ymus

I've never installed humici (or however you spell it- IDC ) so i might be able to recreate it.
also, if you use a school/ work network it should work on the regular LAN finder in multiplayer.

Thx, I had time to recreate one more time, because it was bothering me that it didn't make sense that I only needed to Add Program to Firewall for one laptop. And, what I didn't notice, or what didn't register, was that when I undid Add a Program (java), when I started Minecraft, there was a prompt, asking if I wished to "Allow java thru firewall" or some such verbiage. So, I click Yes. I think I need to think more when I am using my laptop. Or maybe write things down. It gets confusing. Like, did I do this on that laptop or on this laptop? Be that as it may, Open to Lan is still working for us, and we are happy about that.

How to fix

https://www.youtube.com/watch?v=8CaWO_tPVXE

The bug is present in 13w06a !

Gavin Sallery: it worked but only for my freids computer(I can conect to him) but the other way around doesn't work. Any suggestions what could I do to fix this?

yea,
1. look at stirling's video: https://www.youtube.com/watch?v=8CaWO_tPVXE

2. portforward your computer: www.portforward.com

this is to Alexandru

Do note that you do not need portforwarding for any LAN games, as it only affects connections from the Internet.

true, i guess.

I still have this problem in 1.5

It's no bug, read the whole comments in this ticket:

Grum (Erik Broes) added a comment - 28/Jan/13 11:23 PM
This is all intended, you are not supposed to directly connect to the person hosting the LAN world, you are supposed to join through the Multiplayer screen which will list any LAN worlds you can join automagically.

We will change the wording to remove the 0.0.0.0 and make it just: 'Game hosted on port: xxxxx'.

I also get this i the newest version of minecraft. Why hasn't this been fixed? if it started in the 1.4.4 pre, why didn't they just undo their mistake? sure you can just launch the server software on your local network, but I'm sure we all liked it when it was simpler...

I have the same problem 0.0.0.0:random port on Windows 7 64bits with 13w17a snapshot on both computer i try to link.

Same problem since 1.4, still in 13w18c.

Same problem in 1.5.2, never been able to see world in multiplayer menu unless on the same pc.

Workaround is in direct connect to enter COMPUTERNAME:port or use ipconfig in cmd.exe to get your local ip and use that with the port