Minecraft 1.3 LAN server function fails because host IP bad.

August 3, 2012 at 05:44:28
Specs: Macintosh - Lion, Dual 2+ gig/ 4GB
Minecraft 1.3 LAN server function fails because host IP bad. The host (a laptop) connects to the LAN with a proper 10.0.1.X type address, but this particular laptop uses a 169.* address when it establishes/reports the game (instead of it's 10.0.1.X) and no other computer can connect to it. Other computers DO establish/report the 10.0.1.X address they receive from the wireless router, and they can host just fine- but I really need to get the one laptop to serve as host since it has more horsepower.

See More: Minecraft 1.3 LAN server function fails because host IP bad.

Report •

#1
August 3, 2012 at 07:55:16
post the results of a ipconfig /all from this laptop for review.

a 169x ip means its set to dhcp but is not contacting a dhcp server.
this also means you have not set it with a static ip and you have not forwarded the minecraft port to that static ip in the router.

You must first stay at dhcp and successfully get an assigned ip so you know you have a wifi connection to the router.

Then you do the static and port forwarding.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
August 3, 2012 at 08:30:24
Thanks, I'll do that tonight if I am unable to fix the issue by fiddling with proxy settings. Mysteriously, the Laptop is working FINE with the router as a web-appliance- the router talks to 10.0.1.251 with no issues what so ever- no issues with web access or file sharing within (or outside) the LAN.

To re-iterate- the problem I'm having is that the Laptop, when establishing a service like Web Cam streaming or Minecraft LAN server, for some reason doesn't use the 10.0.1.X address (like all the other laptops doing this do)- and uses the whacky 169.X.X.X address, which the Router doesn't acknowledge or support.

Thanks again for responding! I'll get to the bottom of this!


Report •

#3
August 3, 2012 at 09:49:43
already explained the 169 ip.
you don't have a proxy so playing with proxy settings is pretty senseless.

still waiting on the ipconfig /all post

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
August 3, 2012 at 10:08:24
Understand 169

Will post ipconfig /all results by 6pm EST 8-3-12 (provided son has not run off with laptop). Will update in any case. I may be able to VNC to where ever he is and get it that way.


Report •

#5
August 3, 2012 at 14:12:01
ipconfig, as you are requesting, is a windows command line command.

Closest thing in Unix (Mac) will be ifconfig

Here is the result:


Dem-MacBook-Pro:~ ddvw$ ifconfig
...
... [I deleted the data on the inactive devices]
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1b:63:cd:09:94
inet6 fe80::21b:63ff:fecd:994%en1 prefixlen 64 scopeid 0x6
inet 10.0.1.251 netmask 0xffffff00 broadcast 10.0.1.255
media: autoselect
status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::21b:63ff:fe96:71a6%utun0 prefixlen 64 scopeid 0x7
inet6 fd00:6587:52d7:10c5:21b:63ff:fe96:71a6 prefixlen 64
Dem-MacBook-Pro:~ ddvw$


Report •

#6
August 3, 2012 at 14:21:41
Here is the subsequent record in the Console that identifies the 169* IP within my LAN the laptop chooses when I enable the LAN server on the laptop. None of the other machines do this- they use the IP address assigned by the Router (which this laptop is using to send this correspondence. Strange, Huh?


8/3/12 5:18:26.485 PM [0x0-0x158158].com.Mojang Specifications.Minecraft.Minecraft: Started on 169.254.235.191:59351


Report •

#7
August 3, 2012 at 14:40:07
minecraft uses port 25565 by default not 59351.

please post the entire ifconfig.

I suspect you associated the minecraft server with a disabled/unconnected device which resulted in the 169x ip.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#8
August 3, 2012 at 16:10:02
The whole shooting match. Now the whole world knows. Still-- I really appreciate the help. I'm a pretty senior EE, and normally can figure these things out, but this one has me stumped!

Last login: Fri Aug 3 18:57:35 on console
Dem-MacBook-Pro:~ ddvw$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fd0d:9a6f:30a8:d8c1:21b:63ff:fe96:71a6 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether 00:1b:63:96:71:a6
media: autoselect
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:1c:b3:ff:fe:86:42:f2
inet 169.254.208.252 netmask 0xffff0000 broadcast 169.254.255.255
media: autoselect <full-duplex>
status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1b:63:cd:09:94
inet6 fe80::21b:63ff:fecd:994%en1 prefixlen 64 scopeid 0x6
inet 10.0.1.6 netmask 0xffffff00 broadcast 10.0.1.255
media: autoselect
status: active
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::21b:63ff:fe96:71a6%utun0 prefixlen 64 scopeid 0x7
inet6 fd00:6587:52d7:10c5:21b:63ff:fe96:71a6 prefixlen 64

That's it.


Report •

#9
August 4, 2012 at 14:11:16
Have you tried setting server-ip=10.0.1.6 in the server.properties file? Currently it is binding to the firewire interface, which is why it is using the odd IP address. You might also check your network settings to see that the firewire network interface is turned off. It's a bit unlear; it shows the status as inactive but the interface as UP.

Report •

#10
August 10, 2012 at 04:23:34
ijack- excellent observation about the Firewire interface binding. I did find in network preferences that there was a "Firewire" channel established (don't know when or how this happened, since I've never plugged anything but a fire wire drive in). I've removed that, but still seem to be binding to that interface.

That is really the heart of this problem, not Minecraft per-se. This is what I need help with. I plan to restart, and do a few more "voodoo" tricks, but right now it still seems to want to glom onto the Firewire interface.

I can't coerce the server ip because I'm not using the normal mine craft server- I'm using a single player configuration, where I publish the game to the Local Area Network (which is like a server, but limited only to other computers on the LAN). There is an "options.txt" file buried within ~/LIbrary/Application Support/Minecraft but it has no server configuration. Here it is in it's entirety:


music:1.0
sound:1.0
invertYMouse:false
mouseSensitivity:0.5
fov:0.0
gamma:1.0
viewDistance:1
guiScale:0
particles:0
bobView:true
anaglyph3d:false
advancedOpengl:true
fpsLimit:1
difficulty:2
fancyGraphics:false
ao:true
clouds:true
skin:Default
lastServer:
lang:en_US
chatVisibility:0
chatColors:true
chatLinks:true
chatLinksPrompt:true
chatOpacity:1.0
serverTextures:true
snooperEnabled:true
fullscreen:false
enableVsync:false
key_key.attack:-100
key_key.use:-99
key_key.forward:17
key_key.left:30
key_key.back:31
key_key.right:32
key_key.jump:57
key_key.sneak:42
key_key.drop:16
key_key.inventory:18
key_key.chat:20
key_key.playerlist:15
key_key.pickItem:-98
key_key.command:53

Thanks for any further assistance.


Report •

Ask Question