cRIO discovery VISTA

[andre.buurman@carya]

I have problems discovering a cRIO device under VISTA Ultimate. It had an IP address which was unreachable from my PC, so I went ahead and reset the IP address to 0.0.0.0.
Sofar so good. Only the device was not discoverable by MAX in VISTA. After installing the cRIO drivers on a laptop with LV 8.5 and MAX I could discover the cRIO device and assign a new IP. The new IP was in the local subnet of the VISTA machine, but still MAX wasn't able to find it automatically by refresh. Only when I create a new remote device and entered the new IP address it showed up in MAX under VISTA and I was able to program it from LV.

The question: Are there VISTA settings that interfere with cRIO discovery under VISTA?

VISTA had no service pack installed.


Message Edited by andre.buurman@carya on 06-23-2008 06:30 PM

[Riconquistiamola]

André,

It is likely the Vista protection settings (firewall, user account control, parental controls, etc.) are preventing cRIO discovery through MAX. I was able to find at least one Vista/MAX Remote Systems KB similar to your issue.

Why Does Expanding or Refreshing Remote Systems in MAX Take a Long Time with Vista Parental Controls...

Can you confirm MAX is on the allowed list of these programs? Cheers.

[andre.buurman@carya]

Thanks, but non of these apply to me. My firewall is turned off and I don't have parental controls enable on any user account. I am local administrator.

Could VMware virtual interfaces interfere with the device discovery?

[Riconquistiamola]

André,

I've had success with VMWare, so I hesitate to attribute the problem to them. As a proof-of-concept of sorts, can you hook up the cRIO to the PC with a crossover cable? I would also be interested in the output of RT Ping Controllers to see if it is a problem specific to MAX.

[andre.buurman@carya]

I have narrowed it down to VMware server.

Version listing:
VMware server 1.0.4
LV 8.5.1
cRIO 2.4.1
VISTA Ultimate (no SP)

Actions performed:
I have reset the IP address of the cRIO prior to testing.
1. Disabled VMware virtual adapters.
Result:
cRIO show up in MAX without IP address


2. Enabled VMware virtual adapters above and rebooted
Result:
cRIO didn't show up in MAX


3. Disabled VMware virtual adapters
cRIO discoverd again in MAx and with RT controller ping


Message Edited by andre.buurman@carya on 06-25-2008 07:35 AM

It doesn't seem limited to cRIO, a collegue of mine had to same issues with VMware server 2.x and a cFP system under VISTA Home Premium. Disabling VMware adapters proved  to be the solution.


Message Edited by andre.buurman@carya on 06-25-2008 07:37 AM

[Riconquistiamola]

André,

Great catch! I am using Windows XP with VMWare Player, so it is possible this problem does not exist with my current combination.

I've put this test on my to-do list and I'll let you know if it looks like a LabVIEW bug.

Cheers and thanks for bringing this to our attention.

[Riconquistiamola · Accepted solution]

Hello all,

This behaviour is indeed a CAR. This was reported to R&D (# 119890) for further investigation.

Cheers.

[FSguigui]

Hello,

i have problem with my connection between my PC(Vista) and ethernet from Compact Rio.

I've turn off windows defender, windows adorn fire and i'm in administrator's session...

but MAX doesn't recognize the Compact Rio.

I've done manipulations about IP adress but no result..

My colleague has Xp and it's ok...

I've tried with wireless but no result again..

What do you make inactive again with Vista?

Regards

CHAUVEL Guillaume

ISAT Student

France

[andre.buurman@carya]

If your problem is not with the versions of the software listed in this thread in combination with VMWare Server, you should create a new thread. When creating a new thread also add LV, MAX and cRIO versions and supply information regarding network details, eg. direct cable connection, via switch, etc.

[FSguigui]

Excuse me but i don't understand the meaning of "thread"...

It's a connexion?

Regards,

Guillaume