Mads Jakobsen
Comments
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.
@ 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?"
@ 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!"
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.
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.
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.
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.
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?
It was a dublicate? Cool! I'll go and get the solution. Thanks!
As I said, I had the problem before I tried out Hamachi.