Hi Fergy,
You have been fantastic at responding back to me, so many thanks to you , but incase you have
or anyone has misunderstood my posts, please let me explain again.
So starting from the original issue i had.
---------------------------------------------------------------------------------------------------------
Problem:
Computer A - Control terminal with Windows / Nware kiosk software on V-Lan A
to talk back to :
Nion n6unit - on V-Lan B network.
To get kiosk Nware to work over a different vlan ( NOT Kiosk2Go i am talking about here )
As the computer A nware - kiosk discovery was not seeing the multicast sent from the nion n6 unit.
Which , I get, it did not go across the vlans. All good. This was a network limit anyway.
So....
To modify the Pandad CFG.XML / run the pandad.exe
mod the remote link to discover the nion across the vlan. Changing the remote link ip to set to the nion n6 static ip address.
in this case it was:
ip 192.168.50.110,
it could be discovered via the kiosk software ( again NOT talking about the Kiosk2Go here )
But.....
All this was dropped anyway, as V-Lan A and V-Lan B were merged into 1 V-Lan for me.
So I stopped pursuing this . Which made my life easier !
---------------------------------------------------------------------------------------------------------
Obviously .....
if over 1 vlan then the discovery automatically picks up the nware kiosk software.( again NOT K2G I am talking about )
So my issues were no longer a problem.
I do understand the nware kiosk software does NOT work over port 80 and it purely for the web generated pages or K2G ( Kisok2Go )
that does run on ports 80
The K2G pages i have created, run on chromium browsers on small 7 inch panels and I have never had an issue with these .
In summary.......
I have understood the K2G since it first come out many years ago , Then again the info here will help others understand these amazing
systems just that little bit better.
NOTHING has yet topped the NION DSP systems in the world !