My first guess would be that a socket server can't listen on a port without an IP associated with it. If your network connection is DHCP then the server can't listen. It you have a hard IP, then it can.
-- Open WebMail Project (http://openwebmail.org) ---------- Original Message ----------- From: Miguel Manso <mma...@gmail.com> To: gambas-user@lists.sourceforge.net Sent: Thu, 21 Sep 2017 19:41:38 +0100 Subject: [Gambas-user] SocketServer issue > Hi guys, > > I've an application that starts a SocketServer on port 8088. All works ok > when I've the network cable inserted on the machine. > > If I boot the machine without the network cable inserted, the SocketServer > doesn't listen on port 8088 and it doesn't raise the _Error event. > > This happens on a particular machine. On a different one, it behaves ok > when it starts with no network cable on it. > > The postgres server (port 5432) starts ok in both machines. > > Any clue why this is happening? > > Thanks. > > -- > Miguel Manso > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Gambas-user mailing list > Gambas-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-user ------- End of Original Message ------- ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user