01-18-2012 09:17 PM
I have a situation where I need to have the computer running Diadem to be connected to two different networks. I have two NIC's installed in the machine, NIC A and NIC B, we will call them. The reason for this, is that I am using Diadem to access an AOP server on an AVL PUMA machine. If I connect PUMA to the LAN, PUMA occasionally crashes, probably something to do with the IP address. So, PUMA needs to be on a network that does not have a router. My diadem computer needs to communicate with PUMA, and with the local shared drives on our company network.
Anyway, I have the company LAN hooked up on NIC A, and the PUMA network hooked up on NIC B. Diadem fails to connect when both networks are connected, but connects to the data store no problem when only the PUMA network is hooked up. Any ideas how to fix this? It seems diadem is looking at NIC A instead of NIC B, like it should be.
For reference, when both NIC's are hooked up, I can access share drives, and ping computers on both separate networks, without a problem, so it's not a connection issue.
Any help would be appreciated.
-Russ
Solved! Go to Solution.
01-19-2012 06:07 AM
I assume poth NIC have different IP range.
- Did you use IP instead of server name.
- Do you use RPC or CORBA to access the PUMA server?
- Which DIAdem version.
Can you create a logfile when the connection fails?
Greetings
Andreas
01-19-2012 07:48 AM - edited 01-19-2012 07:51 AM
01-19-2012 07:52 AM