Another little nit.

[Pilli]

I have noticed several times that if I have Pilli_Host running & I am connected to it from pc1 (Alan) that if I am not active on pc1 (screen saver on) and another user connects to Pilli_host my connection from pc1 is broken i.e disconnected. I have now seen it happen on several occaisions as server retains the record of connections. Gary, Clive or GK can connect & almost immediately Alan disconnects with no intervention by Alan. It does not happen everytime.

[10:39:00] ** Alan (IP addy) has connected
[13:38:23] ** gkweb (IP addy) has connected
[13:38:33] <gkweb> toc toc, someone here ?
[13:40:04] ** Alan has disconnected
[14:10:12] <gkweb> bye server :)
[14:10:14] ** gkweb has disconnected

I was in fact out at a clients at this time :)


Edited out the IP's - Pieter

[gkweb]

don't lie me Pilli, you was there and when you saw me you rushed away ;D

[Pilli]

Nah - I was having a serious fight with a wayward wireless router ;D

BTW - I won ;)

[gkweb]

Pilli 1 , router 0 by KO

congratulation ! :D

[Jason_R0]

Interesting, there is 90 seconds between gkweb joining and the disconnect though. Which means that if it did disconnect straight away that is the timeout value, but if you are connected over lan it would of disconnected earlier if it had been due to him joining. I can't see a reason why another client joining would boot someone else, unless there is something wrong with the server machine. Wrong as in ... maybe a firewall/router/operating system option. :)

I will take a look over this just to be sure when I add the other features to chat.

-Jason-

[Pilli]

{QUOTE-> unless there is something wrong with the server machine. Wrong as in ... maybe a firewall/router/operating system option. <-QUOTE}

Yes, Probably the most likely reason as it has never done it while I have been active on the conection. As no other users appear to have done a long term test as yet we probably will not find out easily, unless, of course, you find an error in the code:)
It is also most likely that the client (pc1) using Sygate could be the problem and not the Server, as the server has been 100% reliable when open to any user at any time even after hours with no connections. Server uses Outpost2 as the it's firewall.

[Clive T]

{QUOTE-> Server uses Outpost2 as the it's firewall.
***Report to moderator <-QUOTE}

Don’t think it’s relevant but so do I.