Network Configuration¶

At NRAMM, our microscope, Leginon processing server, Database server, and Webserver are all within the same and reliable firewall provided by its gateway. We turn off the Windows firewall on the scope PC in this case. The assumption used in this configuration is that computers within the bound of the gateway is safe. This allows all computers in the lab access to the data collected.

Some of the FEI microscopes come with a "support PC" which acts as gateway to the scope PC and prevents the latter direct internet access. The easiest set up is then put the Leginon system within that local network. This has the drawback that Leginon web viewing as well as the data collected are only accessible in the local network (typically in the same room).

You can either by-pass the support PC, putting the trust on the building (or your lab) network gateway

or do port-forwarding on the support PC.

Here is an example provided by a user

Here are some extra information if you know how and want to further configure, however, be warned that we might not be able to help you if you are stuck since we have no experience in doing so.

1. Ports used by Leginon
2. Leginon bulletin board thread on Network problem - Leginon not seeing tecnai host.

Troubleshooting network between main leginon processing server and TEM host:

1. Try to ping TEM host from Leginon host using host name (not IP). If host name does not work, then you need to configure either your DNS server or your /etc/hosts file to know the host name to IP mapping.
2. Pay attention to whether you need to use the fully qualified name, for example "myhost.scripps.edu" rather than just "myhost". If that is the case, then you must also use the fully qualified name in Leginon when connecting to clients.
3. Try to ping Leginon host from TEM host. Again, you may need to adjust host name mapping. On Windows, there is "/etc/hosts" but it is located in a strange place: C:\Windows\System32\Drivers\etc\hosts. The first part of that may be slightly different depending on version of Windows.
4. Start Leginon Client (launcher.py) on TEM host, then try to telnet to it from Leginon processing server
   "telnet temhost 55555" (replace with your hostname)
   If the connection is refused, then you have a firewall blocking connections on TEM host
5. Try the opposite, running launcher.py on Leginon processing server, and telnet from TEM host. If that fails, then you have a firewall on Leginon processing host that is blocking incoming connections to port 55555
6. Try test1.py and test2.py as described in bulletin board post above

---

< Select Linux distribution to use | Where to register and download Leginon >

---