Error 1379 occurred at Open Application Reference

[hamenarin]

I have a VI server running in a executable made in LV8.0. When I try to Open Application Reference in a client in LV8.0, I get the error 1379: LabVIEW:  The user failed a security authentication check.
I worked a long time with the same server in an executable of LV6, and I can call it from the same LV8.0 I was using to test my new server. It works fine.
Somebody knows if I have to allow access to the RT application, or something like that?
I'm using Windows 2000 NT Professional, SP4.

Thanks,
Henrique

[AESulzer]

Henrique,

Does the problem computer happen to have two network cards? This is the only instance where I recall error 1379 ever coming up. If so, try disabling the network card that you are not using to see if this fixes the problem.

Kind Regards,

[hamenarin]

Thanks, Mr Sulzer.

No, my computer does not have two boards. And the error doesn't appear when running the app from the run-time version 6. I don't have any idea where the problem could be.

Regards, Henrique

[liu]

I got the same error message --1379, I have 2 network cards on each of my 2 computers.I connect them with the same ethernet sw.

Anybody can give me some ideas?

Thanks

Lisha

[Scott Stewart]

I'm stuck on this 1379 problem using LV8.0. Was there ever any resolution or a fix for this?

Thanks,

Scott

[NJKirchner]

I'm getting the same error w/ 8.2.1

I am on a laptop, on home network, VPN to corporate network, attempting to access PC on corporate network.

the NI security is wide open on the PC I'm attempting to open.

I have also tried to use the Logos.ini trick in the c:\windows directory and used both mac addresses of my wireless adapter and the VPN as suggested by an NI AE

still .... No Dice

~,~

Norm

[JMota]

Same thing here. We are trying to talk to a LV 8.2.1 run-time engine and we are getting the same error. In our case we are not going through any VPNs or anything like that.

Have you tried downgrading the remote machine to use the LV 8.2 run-time engine? That's the next thing we are going to try to see if that fixes the problem.

JMota

[FredM]

I have a laptop and am using a call routine to the remote application that works very nicely inside the Boeing Firewall. Outside it, I have access to my EMail and the company data bases, but get the access error when attempting the labview 8.2 call. Bout ready to build a seperate data transfer file rather than trying to use the buggy built ins.

[jlokanis]

Swap your network cables.  LabVIEW VI Server binds itself to the first network card it sees and will not talk to your second card.  So, make sure the the remote machine you are talking to can be reached via the first network card listed by Windows.

This is definily a bug in VI Server but I don' think NI has any plans to fix it.

-John

[Jaggs1]

We had the same problem!  The solution was to install NI Device Drivers (3 CDs) on the server computer.  It solved the problem.  We were using LabVIEW 8.5.  The device drivers may contain some NI security libraryfiles.