Hello, when I connect to my brothers game through our adHoc network we created, and create a game on my brothers machine through single player and click connect as LAN while in game on his machine so I can join it, the message says: Connected as 0.0.0.0:12345 on his chat log, his actual IPV4 is not 0.0.0.0:12345 at all, ipconfig reads it as a proper IPV4 address which is running me into a weird problem when trying to connect to his game.
The adHoc has so far allowed us to find each others games successfully, unlike trying to find each others games on our normal network which are not successful, so heres the problem we're running into:
When I see his games on the multiplayer dashboard from my own computer, his shows up but reads this as the details - 169.255.133.133:0.0.0.0:12345 (I modified the IP as to not display the actual IP for forum use).
I know that it's supposed to only say his IPV4... it's only supposed to be like '169.255.133.133:12345' but that isn't working, I only get the really long IP which I bolded instead.
When I try and connect to it I get an error that it can't find that address to connect to. When I enter his IPV4, or the 0.0.0.0:12345 which was given when the LAN was created on his chatlog, the game seems to think that his IPV4 and the chatlog addresses do not exist.
Just as a FYI -
1. This issue does not relate to Minecraftserver.exe as we are NOT using this program (we use the in-game LAN), and do not wish to use Minecraftserver.exe unless it's a last resort.
2. We are both running Java 1.7, and the latest version of Minecraft 1.6.2, and we both have a retail license each for online use so we are not sharing one license.
3. I want to overcome this error, so before dismissing my error in the comments below, please try and help me address a solution to this one certain error prior to offering alternative solutions. THANK YOU!
Has anyone else seen this sort of problem before? How do I fix this?
Make sure that both computers see the ad-hoc network they're connected to as a home network.
Hi, Tedster. I left the info out that the AdHoc is a home network, we can both see each others computers on it, and network discovery/file sharing is also enabled on both.
Your solution hasn't fixed the issue. Will have to find other ways to fix this -.-
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The adHoc has so far allowed us to find each others games successfully, unlike trying to find each others games on our normal network which are not successful, so heres the problem we're running into:
When I see his games on the multiplayer dashboard from my own computer, his shows up but reads this as the details -
169.255.133.133:0.0.0.0:12345 (I modified the IP as to not display the actual IP for forum use).
I know that it's supposed to only say his IPV4... it's only supposed to be like '169.255.133.133:12345' but that isn't working, I only get the really long IP which I bolded instead.
When I try and connect to it I get an error that it can't find that address to connect to. When I enter his IPV4, or the 0.0.0.0:12345 which was given when the LAN was created on his chatlog, the game seems to think that his IPV4 and the chatlog addresses do not exist.
Just as a FYI -
1. This issue does not relate to Minecraftserver.exe as we are NOT using this program (we use the in-game LAN), and do not wish to use Minecraftserver.exe unless it's a last resort.
2. We are both running Java 1.7, and the latest version of Minecraft 1.6.2, and we both have a retail license each for online use so we are not sharing one license.
3. I want to overcome this error, so before dismissing my error in the comments below, please try and help me address a solution to this one certain error prior to offering alternative solutions. THANK YOU!
Has anyone else seen this sort of problem before? How do I fix this?
Hi, Tedster. I left the info out that the AdHoc is a home network, we can both see each others computers on it, and network discovery/file sharing is also enabled on both.
Your solution hasn't fixed the issue. Will have to find other ways to fix this -.-