When the server is started but has no network connection, a client (end user) will get some kind of "network problem" message and will contact the service desk or the system administrator. And if you have a system administrator who disables (or forgets to enable) the network connection for a network server it's the moment to look for someone else
Roel De Nijs wrote:When the server is started but has no network connection, a client (end user) will get some kind of "network problem" message and will contact the service desk or the system administrator.
This is what happens in your server if you unplug the network connection on your computer before starting the server?
Sean Keane wrote:What would the expected behaviour of the server be when there is no network connection available on the machine and the user attempts to start the server?
Well, in this case, the server will start normally, but in thesis, it will only be possible to connect to it from the same machine. For instance, if I start my server without network connections, it will start normally, but, since there are no network connections available, no other computers will be able to connect to it. Now, if the client looks for a server and there is no network connections available, you are gonna get a RemoteException. You can then handle it like this: