TS2 Server Error

[cosmicShame]

09-01-04 22:37:06,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception1 EIdSocketError.Socket Error # 101
Network is unreachable.
09-01-04 22:37:22,ERROR,All,TTSUDPSender.Execute, SID: 1 Exception2 EIdSocketError.Socket Error # 101
Network is unreachable.


Also, no one was able to connect to the server until I killed it and started it back up.

What's the cause of this ?

[BaNDiT2477]

two things pop into my head:

firewall

or

the default prot that TS use was already in use and when u restarted it found a new one. Is your TS up now and if so what port is it using? if it's not the default port then that's probably. it if it is the default prot the i am not sure

[Dummer Sack]

Another possibility: Do you assign the IP via DHCP? If yes, change it to manual configuration. Maybe the lease on the IP address did expire.

[cosmicShame]

- no firewall
- no port in use probs, bear in mind that the server was up and running for a few days
- no dhcp, this is a production server with a static ip address.

We've been having problems with people hacking in. I think that it's possible that this is a result of some DoS attack. We've had people come on to the server as SA and take it over. I was forced to kill the PID and start with a fresh DB.

I'm not sure if these 2 instances are related. I was wondering if it was possible to send garbled data to TS and have it get messed up like that ?

Also, is there any way to have the server log all ipaddress that connect to it ?

[BaNDiT2477]

TS already logs all ip's...well at least 2.0.19.40 which i am running and selling does.

never had a problem with anyone hacking TS so cant help you

[cosmicShame]

Hmmmn, that activity isn't logged in my server.log is it somewhere else ?

[Dummer Sack]

Activity is not logged by default. You have to activate it.

For server 2.0.19.40 add in the server.ini the following line to the [log] section:
access=1

However I recommend to upgrade to server 2.0.19.46 (from the Developer Releases Forum) which has much more extensive logging options.
To activate logging in server 2.0.19.46 add the following to the [log] section of the server.ini:
access_u=1 (logs unregistred users)
access_r=1 (logs reistred users)
sa=1 (loggs logins to the Web Interface and the TCPQueryPort)

All will be logged in the server.log.

[cosmicShame]

wow, awesome thanx.