MESA 7i96s and remote access doen't work

Dear all,
Here is my problem. First I tried with a Raspberry PI, then now with a desktop computer. I have installed LinuxCNC on the Raspberry 2.8.  The Raspberry works acceptably over GPIO, only slow on one axis. If I set it to faster it misses step. So I installed a MESA 7i96s board. When I want to use it not on GPIO but on 7i96S it stops.

I tried it yesterday, with a new desktop computer. I installed the new debian and linuxcnc 2.9 recommended here. I would use both remotely, on the Raspberry with VNC, on the desktop I tried VNC, Remote Desktop, X via SSH (I would manage it from a windows laptop).

On the raspberry it works with the GPIO on VNC. As soon as I would use the 7i96S board at that moment the whole thing "freezes" and only by turning off the power supply the system can be restarted.

Yesterday I tried the same with a new desktop computer. The axis simulator works perfectly fine via remote desktop. If I select the 7i96S it also "freezing" and only responds to anything after power off. If I use the desktop's own keyboard, screen and mouse the 7i96S board works fine. If I want to access it remotely it stops immediately.

Does anyone have any experience with this? Has anyone tried this? Or does anyone have any ideas of what else I could try.

Gabor Vid

Sounds like possibly a network setup issue.

Is the 7I96S set for a 10.10.10.10 IP address?

Thank you, for your answer.

I'm not using the address 10.10.10.10. I set it according to the address range used on our LAN. The address of the 7i96s board is: 192.168.3.81. Raspberry PI 192.168.3.80; the desktop computer 192.168.3.82 the laptop 192.168.3.20

The 7i96s board works with a local monitor, mouse, and keyboard from the desktop computer, but the whole thing stops only with remote access. I tried this on the desktop machine with VNC, remote desktop, X-SSH forwarding, all of them gave the same result. The axis simulator works. At the moment, I don't have the opportunity to test whether it works with a local monitor, mouse and keyboard with the Raspberry.

You need a separate NIC for the LAN and for the MESA card.
The MESA card needs to be connected directly to the network card, no switch or anything between the MESA card and computer.
So keep 192.168.3.xxx for your LAN. And choose another network for the MESA card.
And this is a must, make sure the NIC connected to MESA card has a different address.
So say 10.10.10.10 for the MESA card and 10.10.10.11 for the NIC, do not give the MESA card and computer the same address (I see you already know this but just in case someone else reads this). Don't add an entry for DNS nor GATEWAY for that network. Do not give the MESA card and computer the same address. And no USB Network devices for the MESA network.
Also the computer running Linuxcnc must be directly connected to the MESA card.

Thanks for the reply. I can try it on Monday, because I can get another NIC. I will definitely write what the result was.

i'm trying the same thing... physical connection to the mesa on the 10. network.  Axis works great when physically at the computer. TeamViewer will work for desktop sharing as it's using the wifi connection to get to TeamViewer server and back to my remote computer. But Axis will not start over a VNC server connection.     The error mentions   "BadWindow (invalid window parameter)"

I'd like a remote connection to my linux box, but not using a cloud service if possible. 

Is this something that 'should' work,  or using VNC just has too many hoops to jump through?  VNC is not showing a mirror of the desktop, it is showing a new instance of a desktop   (this might be a noob thing, or the root of the problem) 

incidentally attempting to start Glade via VNC a connection crashes the connection immediately. 

thanks!

adding info to this thread as i found a working solution. it should go without saying... don't use this if you can crash or harm someone or something - be physically at the machine...

vncserver is the wrong tool in it's default configuration, it may be able to be configured to do what x11vnc does, but that's beyond my current knowledge.

x11vnc is a tool that works. the default config shows display :0.0 at the IP that is remotely available, through a VNC viewer. (in my case, using RealVNC as a client, example: 192,168.1.99:0 )

note to the next newbie that stumbles upon this: know that the x11 display system renders 'views', knowing which 'view' you want to attach to or create is key to figuring out what is going on. vncviewer created a new view by default, this isn't what we wanted.