Elaborating on what has already been said:
RS232 cannot be used for multi-node networks because only one driver at a time can be active on one wire. A single transmitter can talk to many receivers but if two transmitters try to operate at the same time the data will be corrupted.
RS232 or any other serial method, does not have a sudden cut-off at a set speed or cable length. The signal gradually degrades until it is no longer usable. Faster data and longer cables make the problem worse. In addition, if more loads are placed on the lines, their current consumption and load capacitance will reduce the data integrity.
RS485 is designed to be multi-node. Transmitted and received data share the same wires but the rule that only one transmitter can be active at any time still applies. This is why RS485 interface devices have enable pins so they can disconnect from the lines when not using them.
RS485 ideally is chained from one starting point "the master" and up to 32 slaves. The single terminating resistor goes across the wires at the most distant node from the master.
In an RS485 system, for data safety, 'failsafe' pull-up and pull-down resistors should each be fitted between one of the data wires and one of the supply or ground points, preferably but not essentially at the master end. This is to ensure that in the event that no transmitters are active, the lines cannot float but instead assume a known level. The values should be chosen so that the minimum differential voltage to establish a logic output is present across the wires. Typically 0.2V or more.
If you use a star topology instead of a chain, you cannot add the necessary termination resistors at the end of each line because the transmitters will not be able to adequately drive the low resistance that will result from them all being in parallel.
As previously mentioned, the results you see may indicate it is safe to use other interfaces, protocols and speeds but beware that operating outside of recomended specifications may lead to problems, in particular due to unpredicatable and intermittent data transfers.
Brian.