Matrix user forums

Hey Ben,

I am seeking your asistance with a problem on VNET. basically i can not get the two instances to connect to the server and get an error whilst attempting RS232 simulation as per your previosly posted examples.

I go thru the sequecne of creating the node and network on flowcode V4 instance one and it responds with "you are the owner of VNET network". I am following your instructions as posted on the forum. This indicates that the server is running on the PC. I turned off the server and proved that i could not create a node.

The next step to expose the RS232 ports via the manage nodes function. this works!

I then go to instance two of flowcode 4 on the same machine and attempt to join and get the following error."join VNET request fail"

below is the debug from the flow server app. I figured out how to get it into debug mode by adding /d on the end of the command line.
[*]do you have any info on the Flowserver app? I am missing the specific help file for the flowserver application. Not sure if its a Windows 7 issue, however I cant find it on the FC4 CD either, perhaps not looking in the right place.
[*]can you tell me what the ping function does... it did not seem to do anything

Server: LABPC, @Address: 192.168.1.20 is running on port 4360

Server: LABPC, @Address: 192.168.1.20 is running on port 4360

MSG: 4, FROM: 192.168.1.20, CURRENT: 1, TOTAL: 1, BODY: network.node1
MSG: 10, FROM: 192.168.1.20, CURRENT: 1, TOTAL: 1, BODY: network.node1,RS232(0):6,
Server: LABPC, @Address: 192.168.1.20 is running on port 4360

MSG: 2, FROM: 192.168.1.20, CURRENT: 1, TOTAL: 1, BODY:
MSG: 6, FROM: 192.168.1.20, CURRENT: 1, TOTAL: 1, BODY: network.node1

configuration as follows

2 x instance of FC4 professional
Windows 7 machine
ip addr 192.168.1.20 port 4360 on all instance including server application... server is operating on same machine

My intended purpose for VNET is a simulation of a multi node can network, however I thought i would start with sometinh simple such as your demo on RS232 - attached for your reference.

Any suggestions will be greatfully recieved

all the best

pete

Hello,

There is a more detailed guide on setting everything up available from here.

http://www.matrixmultimedia.com/mmforum ... =26&t=6649

In the mean time I'll try and find out what those messages on the Vnet server mean.

thanks Ben,

i went thru this today...thats where I got the test routines and your word doc...

I have a feeling it something to do with my environment...

The comms shold be limited to the loacl machine should it not... and not require a port to be opened on my router firewall?

best

Pete

Hello Pete,

Hm im not too sure about that the communications probably uses the loopback on a local machine so I think even local ports may need to be opened on the firewall to allow the software to see the server correctly. Worth a quick go anyway to see if it resolves the problem.

Hi Ben,

Will check the router...it's odd that client can see the server app and does display the node details from the first instance of FC4. it just wil not connect... Maybe it's a different class of traffic?

Also turned off the firewall on the local machine..no change..Move it to another machine with same behavior, it was on the same subnet..


Odd huh

Best

Pete

Hello,

Have you made sure that:

-the vnet server program is running
-the modules are connected up in the "view diagram" box and you have clicked "save"
-the two flowcodes loaded up use different usernames (eg Node1 and Node2)
-the ip/port of the two flowcodes is the same and the ip of the machine you are using
-that flowcode has access through your firewall

Hi David,

If you look at my earlier post it shows that server is running and ip and port numbers are correct

I turned off the local machine firewall...

No change!

Does the traffic go via the router?

Can you look at the debug trace pls, really interested in the error messages..

Thanks

Pete

When we looked into this, we found we could replicate your problem when the "instances" of the Flowcode programs have the same name. Unfortunately, the error message produced in this situation is not as helpful as it could be. Is this definitely not the problem?

If the problem persists, then there must be some application on your PC (e.g. firewall) that is preventing the messages from being transmitted.

Thanks steve,

To confirm your point re "instances" you are referring to the client name and network?....or the actual instance of the application....if it's the application (flow code programmes) you are referring to then where do you change the name?

I suspected the firewall initially and definitely turned it off, both windows and McAffee.

Thanks

Best regards

Pete

When joining, the "Vnet name" needs to be the same, but the "Client name" needs to be unique between Flowcode instances. I believe the name of the actual Flowcode program does not matter.

Ok, thanks fot the clarification. I have followed the instructions and have entered different client names with the same VNET..

I have tried this on a different machine windows Vista, and Windows 7 with the same result..

The only thing now that is common is the router

Not sure what's left...

Also any luck with the error messages...do you have any documentation that outlines what they mean?

Best

Pete

Hello Pete, those are not error messages, they are just showing what "messages" are being sent to the VNET server module. When you are successful you get additional lines showing a connection and the comms between the two modules.

For example this is a successful vnet i just did on my computer right now:

Gentlemen,

Can you confirm by the messages that the server is communicating with the client?

Given the configuration of the server and the clients on the same machine does the communication go via the ip port to the router and return or go via the ip software stack on the local machine?

Thanks in advance

Pete

Hello Pete,

Have you tried booting your computer up in safe mode and seeing if you can do the VNET comms in safe mode?

Hello Pete,

The communications will go via the local loopback adapter rather then out to a router if your using the Vnet on a single PC. The Vnet server application listens to requests from both the loopback adapter and from the connection to the router.

Thank you for the response.. Will try the safe mode option.

Best regards

Pete