Hi there,
I have a strange 10053 communication problem. I setup a logger that reports via Callback option to my Loggernet Server and uploads data every day. I can also download remotely any data via this GPRS connection. To do so I put the Loggernet Server computer into a so-called DMZ* (all traffic is redirectioned to this computer) and made some holes into the computer firewall.
So fare everything is fine, but when I try to upload data onto my CR850 the communication link breaks and all (I really mean all) communication from my computer to the Internet is broken. I have to restart the computer to reestablish the communication.
The logfile indicates something like "F","unexpected socket error","10053","software caused connection abort".
I've already tried some things: uninstall antivirus software, tear down the complete windows firewall (by deactivating it)...
What else? Does anyone have a good idea what else can I try?
By the way the OS of the Logger is version 25. Not sure if it is a bug ar a known problem.
* I know that this is not a true DMZ, but in my router it is called DMZ...
Does anyone have a solution for this problem or an idea what could be the reason. I am really stucked...
I was hoping the Loggernet Expert might reply but a laymans explanation of the error message is the Loggernet has been told that by the underlying Windows API that the socket has been closed and it cannot use it any longer. Normally Loggernet will just return to listening for another connection.
This can be caused by a number of problems ranging from firewall issues, network card driver issues, timeouts in routers, a timeout in the logger or something in the path between the logger and PC causing the connection to reset.
If you are really losing all connection to the internet at this point I would suggest the problem is in the configuration of the PC, as Loggernet is only using the standard Windows TCP/IP API calls. It does not do anything at a lower level that would break the whole API or the underlying drivers.
However, that aside, I should explain that on GPRS systems you do occasionally see this error as the connections out through the cellphone network are not totally reliable. If you are getting this repeatedly to the point that no traffic flows in one particular mode of operation then can I suggest you check the following:
a) the power supply to the loggers/modem is good - as long periods online could cause the voltage to drop to a critical point.
b) that you are using the latest operating system in the logger (from the support section of this website).
c) you have tried increasing the extra response time parameter in Loggernet by a second or two (do not make it tens of seconds).
If you have tried the above can you please confirm the problem only occurs when sending files to the logger. Also please let us know the size of the files and how you are sending them (via Loggernet, ftp or how?).
Hi Andrew,
thanks for the reply. Actually I did not test the behaviour with a logger in the field. Right now I am testing a CR850 with the latest operation system (version 25) in our lab. The powersupply is ensured with a plug, so voltage drop is not an issue.
I also tried the last suggestion you gave me setting some extra response time, but did not help. I still have the same behaviour:
The logger establishs a TCP connection via Modem to the Loggernet server and drops data there, but when I try to upload files (actually a new *.cr8 program version) the communication link breaks and I loose all internet/network connection of the PC and have to restart the computer to reestablish internet/network connection.
The filesize is about 9kB, so it is really a small file.
Thanks in advance for any suggestion that could help. I will now have a look into Windows TCP settings. The computer OS is Windows XP.
BR,
Ponce
What version of Loggernet are you using and are you using an IPPort or the PakbusTCPServer to control and maintain the incoming connection?
Solved it! Fiddling around at all levels of TCP/IP connectivity I forgot to update the driver of the LAN adapter. Seems that the driver was too old. The computer is relatively new, but the driver dated from 2010...
@Andrew: Your hint with regards to the network card adapter gave me the right track! Thx!
* Last updated by: Ponce on 3/27/2013 @ 10:13 AM *