The Meaning of Life, the Universe, and Everything.
Join Date:
1/15/2014
Posts:
76
Member Details
Hi all,
I am setting up two minecraft servers to run at the same time on the same computer. One is a test server (for now).
I know how to use the server.properties file to change the default port so both servers can run simultaneously, and the second server is now bound to TCP 25566 instead of the default (TCP 25565).
Why can't the minecraft client detect the new server on the non-default port? Why is there no mechanism in the client to specify the port number to use when defining a server under either "Direct Connect" or "Add Server"? Is there something I'm missing?
The Meaning of Life, the Universe, and Everything.
Join Date:
1/15/2014
Posts:
76
Member Details
Never mind. I figured it out by quessing (because I couldn't find it in any FAQ anywhere).
For those of you who don't know, you specify the port when you put the server address in. IE, launch the client, go to multiplayer, go to "Add Server", put the name in, but when you put the address, put "<ip address>:<port>"
Its not in any of the documentation that I could find, but it worked. Crazy, I have no idea why I was inspired to try this. No person who is more familiar with routing than with web applications is ever going to figure this out on their own - it is NOT intuitive.
For anyone on Team Minecraft who reads this, I STRONGLY advise you to ensure that this is documented, AND the client should be updated to reflect it (like a tooltip when the mouse is over the field, or something). It will help prevent user frustration.
1) the client doesn't detect servers. This is not an Open to Lan game that has multicast announcements.
2) Anyone who knows enough about ports to change their server port probably knows enough to know to add :port to the resource locator
it's just like the good ole days of http://userserver:8080
The Meaning of Life, the Universe, and Everything.
Join Date:
1/15/2014
Posts:
76
Member Details
@Gerbil
2) Anyone who knows enough about ports to change their server port probably knows enough to know to add :port to the resource locator
FYI, I believe you have it wrong. The more a person knows about IP addresses and TCP/UDP ports the LESS likely that they are going to think to put a :port in the server field, because the server field is not a resource locator - it's a server field. If the instructions had said to put "minecraft://server-ip" in the server field, an IP-aware person might have figured out to put the ":port" on the end, but there isn't a core router by Cicso, Netgear, Juniper or Extreme or any other network hardware company where you configure it's services using IP:port. Besides which, the more familiar with network nomenclature a person is, the older they are likely to be, and using resource locators for absolutely everything is a relatively new thing. ;-)
So, for anyone out there on the Minecraft development team, please include a section somewhere in the instructions that CLEARLY spells this out for people. Maybe add it to the server set-up guide also.
I'm afraid I have to disagreed with you.
I started my career at a networking company. Coded networking protocols for bridges and switches, ethernet and token ring, configured networking boxes, managed some unix workstations, mostly SunOS and Solaris.
I'm older and it's obvious, because how else would you specify it given a single text box?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I am setting up two minecraft servers to run at the same time on the same computer. One is a test server (for now).
I know how to use the server.properties file to change the default port so both servers can run simultaneously, and the second server is now bound to TCP 25566 instead of the default (TCP 25565).
Why can't the minecraft client detect the new server on the non-default port? Why is there no mechanism in the client to specify the port number to use when defining a server under either "Direct Connect" or "Add Server"? Is there something I'm missing?
Thanks, I appreciate any help you can provide.
For those of you who don't know, you specify the port when you put the server address in. IE, launch the client, go to multiplayer, go to "Add Server", put the name in, but when you put the address, put "<ip address>:<port>"
Its not in any of the documentation that I could find, but it worked. Crazy, I have no idea why I was inspired to try this. No person who is more familiar with routing than with web applications is ever going to figure this out on their own - it is NOT intuitive.
For anyone on Team Minecraft who reads this, I STRONGLY advise you to ensure that this is documented, AND the client should be updated to reflect it (like a tooltip when the mouse is over the field, or something). It will help prevent user frustration.
Happy Crafting!
2) Anyone who knows enough about ports to change their server port probably knows enough to know to add :port to the resource locator
it's just like the good ole days of http://userserver:8080
2) Anyone who knows enough about ports to change their server port probably knows enough to know to add :port to the resource locator
FYI, I believe you have it wrong. The more a person knows about IP addresses and TCP/UDP ports the LESS likely that they are going to think to put a :port in the server field, because the server field is not a resource locator - it's a server field. If the instructions had said to put "minecraft://server-ip" in the server field, an IP-aware person might have figured out to put the ":port" on the end, but there isn't a core router by Cicso, Netgear, Juniper or Extreme or any other network hardware company where you configure it's services using IP:port. Besides which, the more familiar with network nomenclature a person is, the older they are likely to be, and using resource locators for absolutely everything is a relatively new thing. ;-)
So, for anyone out there on the Minecraft development team, please include a section somewhere in the instructions that CLEARLY spells this out for people. Maybe add it to the server set-up guide also.
I started my career at a networking company. Coded networking protocols for bridges and switches, ethernet and token ring, configured networking boxes, managed some unix workstations, mostly SunOS and Solaris.
I'm older and it's obvious, because how else would you specify it given a single text box?