Project

General

Profile

Actions

Network Configuration » History » Revision 3

« Previous | Revision 3/21 (diff) | Next »
Jim Pulokas, 05/12/2010 01:28 PM


Network Configuration

At NRAMM, our microscope, Leginon processing server, Database server, and Webserver are all within the same firewall. We Highly recommend it. If you absolutely can not do it in the same way, here are some information, however, be warned that we might not be able to help you if you are stuck.
  1. Ports used by Leginon
  2. Leginon bulletin board thread on Network problem - Leginon not seeing tecnai host.
  3. An example of working port-forwarding configuration
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. 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.
  3. 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
  4. 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
  5. Try test1.py and test2.py as described in bulletin board post above

< Possible Computer Set-up Configurations | Where to register and download Leginon >


Updated by Jim Pulokas over 14 years ago · 3 revisions