# Cannot connect to remote pvserver from macOS client
**URL:** https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452
**Category:** ParaView Support
**Created:** [June 21, 2021, 1:54am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452 "2021-06-21T01:54:30Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 21, 2021, 1:54am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/1 "2021-06-21T01:54:30Z")
I am connecting to a remote pvserver running on a Linux cluster node via an SSH tunnel. I have built paraview 5.9.1 from source on the cluster node.
I can successfully create the tunnel, start pvserver on the node, and connect from a Windows 10 Paraview 5.9.1 client, but I cannot connect from a macOS 11.4 (Big Sur) Paraview 5.9.1 client. When attempting to connect from macOS, I get the error:
```auto
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 781
vtkSocketCommunicator (0x600003c3aeb0): Could not receive tag. 1010580540
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 535
vtkSocketCommunicator (0x600003c3aeb0): Endian handshake failed.
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/Remoting/Core/vtkTCPNetworkAccessManager.cxx, line 333
vtkTCPNetworkAccessManager (0x600001b44900):
**********************************************************************
Connection failed during handshake. vtkSocketCommunicator::GetVersion()
returns different values on the two connecting processes
(Current value: 100).
**********************************************************************
```
What causes this error code? Is there a way to workaround this issue?
Thanks,
Ben
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 21, 2021, 7:14am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/2 "2021-06-21T07:14:22Z")
Are you enterely sure these are the same version of ParaView ?
> I have built paraview 5.9.1 from source on the cluster node.
Which option did you enable ?
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 22, 2021, 2:34am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/3 "2021-06-22T02:34:31Z")
Yes, I am certain they are the same version of ParaView. I built the server ParaView with the options:
`-DCMAKE_BUILD_TYPE=RelWithDebInfo -DPARAVIEW_USE_MPI=ON -DPARAVIEW_USE_QT=OFF -DCMAKE_INSTALL_PREFIX=/avatar/bwibking/paraview_install -DCMAKE_CXX_COMPILER=g++ -DCMAKE_C_COMPILER=gcc -DPARAVIEW_USE_PYTHON=ON -DVTK_OPENGL_HAS_EGL=ON`
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 22, 2021, 7:59am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/4 "2021-06-22T07:59:27Z")
Strange bug. Did you encounter this @cory.quammen ?
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [June 22, 2021, 4:22pm UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/5 "2021-06-22T16:22:39Z")
By any chance is the Mac an M1 chip?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [June 22, 2021, 7:55pm UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/6 "2021-06-22T19:55:02Z")
I was able to do a reverse connection from 5.9.1 osmesa version to my Mac 5.9.1 client, not using a tunnel.
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 23, 2021, 12:47am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/7 "2021-06-23T00:47:09Z")
No, it’s an Intel MacBook Pro.
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 23, 2021, 6:44am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/8 "2021-06-23T06:44:09Z")
I installed the pre-compiled binary from ParaView-5.9.1-osmesa-MPI-Linux-Python3.8-64bit.tar.gz on my cluster and tried to connect, but I get the same error:
```auto
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 781
vtkSocketCommunicator (0x6000035c2130): Could not receive tag. 1010580540
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 535
vtkSocketCommunicator (0x6000035c2130): Endian handshake failed.
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/Remoting/Core/vtkTCPNetworkAccessManager.cxx, line 333
vtkTCPNetworkAccessManager (0x6000012f7b80):
**********************************************************************
Connection failed during handshake. vtkSocketCommunicator::GetVersion()
returns different values on the two connecting processes
(Current value: 100).
**********************************************************************
```
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 23, 2021, 6:47am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/9 "2021-06-23T06:47:16Z")
On the server side, it says:
`channel 3: open failed: connect failed: Name or service not known`
Could this be a hostname resolution issue, or other issue with the tunnel?
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 23, 2021, 6:53am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/10 "2021-06-23T06:53:26Z")
Arg, this was very annoying. It works _only_ if I set up the tunnel using the fully-qualified domain name of the cluster node.
It would be nice if ParaView gave a more sensible error message in this case. I don’t understand why the tunnel needs to be set up this way, or why pvserver cares about the FQDN, though.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 23, 2021, 7:12am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/11 "2021-06-23T07:12:14Z")
Most definitelly:
[https://gitlab.kitware.com/paraview/paraview/-/issues/18171](https://gitlab.kitware.com/paraview/paraview/-/issues/18171)
---
### Author:  [@BenWibking](https://discourse.paraview.org/u/BenWibking)
#### Post date: [June 23, 2021, 7:17am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/12 "2021-06-23T07:17:05Z")
That’s good to know this is being tracked in the case of an actual version mismatch. Do you know why setting up a tunnel using a different hostname than the one printed to stdout by pvserver causes a version mismatch error?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [June 23, 2021, 7:17am UTC](https://discourse.paraview.org/t/cannot-connect-to-remote-pvserver-from-macos-client/7452/13 "2021-06-23T07:17:58Z")
I’m afraid not, this would require much deeper investigation.