12-16-2009 05:11 AM
We are trying to integrate a .Net (2.0 C#) assembly with
LabVIEW application (8.6). When we are in development environment than everything works
fine. But after compilation we are not able to have the assembly working
properly:
1. The assembly is a small TCP server which is using sockets and custom communication protocol.
2. 2. After compilation I’m able to connect to the
application (assembly) only from the same computer but when I’m trying to
connect from a remote PC (on the same LAN) than a client returns 10060 socket
error ("A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection failed
because connected host has failed to respond").
What can it be? .Net security settings? LabVIEW’s side
effect?
Thanks,
Alexander
12-17-2009 12:34 AM
12-17-2009 12:59 AM
tried the same application on both PCs - local and remote. The situation is as
I explained in my first post - it is working (able to connect) only when both
applications are on the same local PC.
server application is in LabVIEW development environment. But when it is in
run-time there is no connect from remote.
12-17-2009 04:58 AM
i have used LV8.5.1 (8.5 has some problems with .NET) to connect to a hardware running linux in it and havent faced any problem as such (both development version as well the exe).
Just a question. Are you using a set of dll's (.NET) to connect? If yes can you check whether the dll is not causing any problem due to registration issues (may be the the "constructor node" )
Guru