ScreamingPict
31-05-2006, 12:13
Hi- I have a problem with my TS server and I wonder if anyone can help? I have googled but failed to find anything useful.
I have a TS server installed on my VIA 533MHz server with 256MB RAM and Win XP Pro. That is a slow machine but it is all that is running on the PC and should be suffcient.
The server comes up and functions well, however after about 1-3 hours all clients on it are disconnected and they cannot reconnect. This happens for both clients outside the NAT'ed gateway and clients on the same subnet.
At this point the server still seems to be running OK- I can still connect to it over the administration web pages and the Windows service is still up- but noone can connect the TS client to it.
The server log shows the server starting up OK and then after 1-3 hours (at the exact time of the disconnections) it shows;
31-05-06 02:32:54,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception1 EIdSocketError.Socket Error # 10065
No route to host.
31-05-06 02:32:55,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception2 EIdSocketError.Socket Error # 10065
No route to host.
The error always appears twice (never once) usually 1-3 seconds apart.
I am running server version 2.0.20.1 (Win32).
I have tried running both the executable version and the Windows service version. I have even set up the service to restart if it dies and yet this still occurs.
The error number above is a winsock error implying that some issue has occurred on the network- but given that this can occur with no clients physically attached to the server I can only think that the connection being dropped is an internal networked connection between different parts of the server.
I have had a look at the windows firewall and allowed both the executable and port 8767 through the firewall but the error still occurs.
If I restart the server (or the service) everything is fine again for another 1-3 hrs.
Has anyone any hints on how I could debug this? I will try turning off the Windows firewall as a next step and post my results here.
Thanks in advance.
--
Pict
I have a TS server installed on my VIA 533MHz server with 256MB RAM and Win XP Pro. That is a slow machine but it is all that is running on the PC and should be suffcient.
The server comes up and functions well, however after about 1-3 hours all clients on it are disconnected and they cannot reconnect. This happens for both clients outside the NAT'ed gateway and clients on the same subnet.
At this point the server still seems to be running OK- I can still connect to it over the administration web pages and the Windows service is still up- but noone can connect the TS client to it.
The server log shows the server starting up OK and then after 1-3 hours (at the exact time of the disconnections) it shows;
31-05-06 02:32:54,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception1 EIdSocketError.Socket Error # 10065
No route to host.
31-05-06 02:32:55,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception2 EIdSocketError.Socket Error # 10065
No route to host.
The error always appears twice (never once) usually 1-3 seconds apart.
I am running server version 2.0.20.1 (Win32).
I have tried running both the executable version and the Windows service version. I have even set up the service to restart if it dies and yet this still occurs.
The error number above is a winsock error implying that some issue has occurred on the network- but given that this can occur with no clients physically attached to the server I can only think that the connection being dropped is an internal networked connection between different parts of the server.
I have had a look at the windows firewall and allowed both the executable and port 8767 through the firewall but the error still occurs.
If I restart the server (or the service) everything is fine again for another 1-3 hrs.
Has anyone any hints on how I could debug this? I will try turning off the Windows firewall as a next step and post my results here.
Thanks in advance.
--
Pict