Executable locks-up network connection

[ntaINC]

I've built an executable that communicates with sensors over our network. The program works fine for a while, any where from a few hours to several days. But eventually the program seems to lock-up the network; we lose communication with our sensors and any mapped drives. I am not very familiar with networks but I can trace the problem to my program because as soon as I stop it, the mapped drives become accessible. Upon restarting my program, the communications with our sensors is as expected. We’ve isolated the components, the logging computer and sensors, from the rest of the network but are still encountering the lock-up. Any insight would be appreciated.

Thanks,

Tessa

[unclebump]

We need to see the code.

[ntaINC]

It's a fairly large program for me. It's written in LV8.2

[Eleno Sandoval]

I would try to solve this problem by first looking at the actual network
traffic using TCPDUMP, or WinDump.

For example to monitor the traffic between two HP pc's at the dos command
line I type:

windump -i 2 host HP1 and HP2

Where the 2 is for the 2nd ethernet interface on the monitoring PC.

You can Google for windump. It's free.

Good luck,

Leno

"ntaINC" <x@no.email> wrote in message
news:1174311612179-493742@exchange.ni.com...
> I've built an executable that communicates with sensors over our network.
> The program works fine for a while, any where from a few hours to several
> days. But eventually the program seems to lock-up the network; we lose
> communication with our sensors and any mapped drives. I am not very
> familiar with networks but I can trace the problem to my program because
> as soon as I stop it, the mapped drives become accessible. Upon restarting
> my program, the communications with our sensors is as expected. We?ve
> isolated the components, the logging computer and sensors, from the rest
> of the network but are still encountering the lock-up. Any insight would
> be appreciated.
>
> &nbsp;
>
> Thanks,
>
> Tessa

[altenbach]

After running the program for a while, open a command prompt and type "netstat". I wonder if there is an increasing number of connections sticking around.

[ntaINC]

After about a minute I got what's shown in the attachment, but I don't know what it means.