Coding and Dismantling Stuff

Don't thank me, it's what I do.

About the author

Russell is a .Net developer based in Lancashire in the UK.  His day job is as a C# developer for the UK's largest online white-goods retailer, DRL Limited.

His weekend job entails alternately demolishing and constructing various bits of his home, much to the distress of his fiance Kelly, 3-year-old daughter Amelie, and menagerie of pets.


  1. Fix dodgy keywords Google is scraping from my blog
  2. Complete migration of NHaml from Google Code to GitHub
  3. ReTelnet Mock Telnet Server à la Jetty
  4. Learn to use Git
  5. Complete beta release FHEMDotNet
  6. Publish FHEMDotNet on Google Code
  7. Learn NancyFX library
  8. Pull RussPAll/NHaml into NHaml/NHaml
  9. Open Source Blackberry Twitter app
  10. Other stuff

Troubleshooting Remote Access to an FHEM Server

Hi all,

A quick one tonight because I've just spent a good half an hour scratching my head over it!

If you're running an FHEM server, and you'd like to be able to access it via Telnet from a remote box, here are four quick steps you can take to troubleshoot any issues you're having.

  1. Make sure you can connect to the server from the same box it's installed on, this will prove that it's running correctly.
  2. Telnet client settings - If you're using PuTTY to connect to your server, when you're configuring your connection make sure:
    1. In the "Terminal" category, check the box "Implicit CR in every LF"
    2. In the "Session" category, make sure you check the box to close the window "Only on clean exit", this way if there's an error you'll get a message box pop up to tell you, PuTTY won't just shut itself down.
  3. Server firewall settings - I'm using Windows Home Server, so for me the process was:
    1. Remote into the server via Remote Desktop connection
    2. Open Control Panel, then Windows Firewall
    3. If your firewall is Off, you shouldn't have any problems with FHEM (but expect all sorts of unpleasant suprises in the future!)
    4. If your firewall is On, make sure that the box "Don't allow allow exceptions" is not checked.  If you do what I did, and accidentally check it, expect to be kicked out of your remote desktop session and have to plug a keyboard and monitor into your server to fix it.
    5. In the Exceptions tab, add an exception for the port number you've configured your server (the default I believe is 7072) and give it a sensible name, eg FHEM.
  4. FHEM Configuration - Make sure that your FHEM port number is configured as a global port:
    1. In your config file, the command to specify the port number must look like "attr global port xxxx global", without that second "global" keyword the port is only accessible from the localhost.
    2. Because the port is blocked in a Perl Socket module, not in the FHEM application, the FHEM log won't give you any record of failed attempts due to the above problem.

Those things sorted the problem out for me, of course there could be other things to check, for example:

  • A firewall configured on the machine you want to connect from
  • Router and port-forwarding settings may come into play if you're going across networks

Hope that helps someone out there,


Permalink | Comments (0)

Add comment

  Country flag

  • Comment
  • Preview