Eh...I guessed everything was fine since I was able to connect to www.timedesk.net (and to put my hands on user_id 3😊).
You mean hostname when say servername, right? Setting both the hostname and the address to the ip-address isn't considered the way to go (but can be a workaround when DNS isn't properly configured).
As of now your ip-address appears in my browser's address field because you have the hostname set to the ip...
Actually (as you may have noticed in the thread you found) I had a similar problem myself some time ago. I am behind a IP-Masquerading firewall and, with kernel 2.2.x, hosts on one network segment cannot connect to other hosts on the same segment unless you fool around a lot. Adding entries in /etc/hosts also does the trick.
It was to avoid this kind of network jungle that I suggested that you get things started on localhost first, following the book...
