Comments on: Network ports used by Serendipity products http://blog.serendipity-software.com.au/archives/2006/08/11/network-ports-used-by-serendipity-products/ Musings and happenings Sun, 23 Nov 2008 18:45:45 +0000 http://wordpress.org/?v=2.5.1 By: Olaf http://blog.serendipity-software.com.au/archives/2006/08/11/network-ports-used-by-serendipity-products/#comment-3344 Olaf Mon, 14 Aug 2006 20:35:55 +0000 http://blog.serendipity-software.com.au/archives/2006/08/11/network-ports-used-by-serendipity-products/#comment-3344 If you face problems with dying BM clients, it is always a good idea to set the server/client communication in the /etc/ss.conf to port 9104 or something to become more stable. Believe it works... All commnunication running on port 9100 really has to be avoided wherever possible. Split communication ports wherever possible. It really helps. More than 3 maschines/nodes communicating via the same 9100 port are not an adavantage... Greetings from Duesseldorf If you face problems with dying BM clients,
it is always a good idea to set the server/client communication in the /etc/ss.conf to port 9104 or something to become more stable.
Believe it works…

All commnunication running on port 9100 really has to be avoided wherever possible. Split communication ports wherever possible.
It really helps. More than 3 maschines/nodes communicating via the same 9100 port are not an adavantage…

Greetings from Duesseldorf

]]>