Q. How to correct aberrations remotely using CEOS Rpc gateway?

[utkarshp1161]

Steps for Running CEOS RPC Gateway and Client Notebook

a) Start the CEOS RPC Gateway on the Microscope PC

• Navigate to:
  C:\Program Files\CEOS-RPC-Gateway

• Confirm the port it is running on:

  • Open PowerShell and run:

    netstat -a -b

  • Look for the CEOS RPC Gateway entry in the output to identify the active port.

(Example output screenshot for reference below)

---

b) Run the Aberration Correction Notebook on the Client Side

• Open the following Jupyter Notebook on the client machine (can also do microscope PC):
  Aberration Correction Notebook

[utkarshp1161]

Q. How to handle the case for port mapping --> ISAAC hpc purposes?

• netsh interface portproxy add v4tov4 listenport=9092 listenaddress=0.0.0.0 connectport=7072 connectaddress=0.0.0.0
• netsh interface portproxy show all
• netsh interface portproxy reset ------> to reset

[utkarshp1161]

Q. How to debug inbound rules in firewall?

• Check the inbound rules :
  - has already existing ones-- for which you didnt create a rule yet
  - Has also ones you create rule for

[utkarshp1161]

fyi: to connect through isaac hpc-- need to map 7072 to 9092

• Didnt work:
  • netsh interface portproxy add v4tov4 listenport=9092 listenaddress=0.0.0.0 connectport=7072 connectaddress=0.0.0.0
• Worked
  • netsh interface portproxy add v4tov4 listenport=9092 listenaddress=0.0.0.0 connectport=7072 connectaddress=127.0.0.1

Elaborated answer:
When configuring netsh portproxy, 127.0.0.1 and 0.0.0.0 behave differently.
If you set listenaddress=127.0.0.1, Windows will only accept connections from the same machine. Remote clients or containers cannot connect because 127.0.0.1 is limited to local loopback.
Using listenaddress=0.0.0.0 binds the proxy to all interfaces (local, LAN, VPN), allowing both local and remote access.
On the other hand, connectaddress must be a specific IP. For SSH tunnels, the service is usually exposed on the loopback interface, so connectaddress=127.0.0.1 is required.
In summary:

Use listenaddress=0.0.0.0 to accept connections from anywhere.

Use connectaddress=127.0.0.1 to forward traffic to the local tunnel.

connectaddress=0.0.0.0 is invalid since it is not a real destination.