Psion workabout communication

[duijv023]

Can NOD32 disturb communication with an Psion workabout (handheld device) without communicaton viral code (of course)?
This device communicates via RS232 on YMODEM protocol in a custom made application.

Communication was broken, no log event found in NOD32 logs.
After exclusion of the target directory in IMON, communication was runnig normally.
Is this a coincidence or does it make sense??

Does anybody know?

[alglove]

Some sort of flow control problem, maybe? Does the problem reappear of you remove the exclusion?

[duijv023]

First result was OK after exclusion of the "application.exe"

But we are not sure about this being the solution. Time will tell

[NOD32 user]

A lot of applications and program controls use network to communicate, usually by binding to 127.0.0.1 or 0.0.0.0 and opening a listening port. Another module or program control in an application is then able to communicate with it, for example the program module that operates the com port may receive it's data and control commands from another part of the same application via a tcp/ip loopback on your loal machine. Of course I do not know about your specific softwrare, and normally it makes no challenge but you can see that if it is doing this then maybe it isn't able to cope with IMON checking it's traffic ...
It's very interesting if you've never done it to use a utility that shows what applications have bindings to what IP's and what ports they have open
HTH