Quote: Originally Posted by
Sonicxtacy02 
i got this installed per your instructions. The funny thing is when i launch the client app it sends a single point to the server.. but subequent points are not sent... the debug says the server isnt pingable... even though the server clearly is because one point has been sent. This happens each time i start the client app... one point uploads.. then nothing. Any ideas?
The way the app works is to try to send data when a network chnge occures i.e. everytime you get a new network connection. It checks to see if the network is an internet connection by trying to connect to
http://www.microsoft.com/. If this passes then it looks to see if you've allowed the server to be pingable. This is set in the ini file. If it is then it trys to ping. If it recieves a response then it trys to send the data if not then it fails.
I think the debug message your seeing is the setting from your ini file as I default it to false.
I think whats happening is the client has sent its message, which the server has recieved (hence the one point) but the the server message sying its recieved the data is not being returned to the client. The client then goes into the no connection mode and waits for the specified retryperiod.
So the question is why does it think its not sent the data when it has.
Does the client say a current time for the server updated label?
Does the client seem to hang for a long time?
try setting your tracking period and retry period smaller. Say 10 secods and 15 seconds. That way you may see more points. It wont have solved your problem but it will narrow it down.
I assume that the server can see the client. By this I mean can it respond. have you got a firewall that will stop it from responding?
Can you send me your debug file to take a look.
I could add some extra debug and send you a special version if you pm me your email address.