I've set up an older notebook as a server, connected via WiFi, will be called "server" in this text. Then I have my normal work notebook, called "notebook" in this text.
Both the server and the notebook are connected to the router. The server has additionally a no-ip.org domain.
server ip: 192.168.1.14, notebook ip: 192.168.1.4, router ip: 192.168.1.1
Now just after rebooting and after resetting the wifi connection, I can ping and ssh the server from the notebook.
After some time though something strange happens...
I can't connect to the server from my notebook through 192.168.1.14, all I get is "ssh: connect to host 192.168.1.14 port 22: No route to host".
But if I ssh to the server from my notebook via the no-ip.org domain, it works perfect.
I can then ping 192.168.1.1 from both the server and the notebook, but I can neither ping 192.168.1.4 from the server nor 192.168.1.14 from the notebook...
What might the reason for this strange behaviour be?
It's sometimes possible to "unlock" the server by visiting 192.168.1.14:631 (the CUPS web interface), then ssh works again for some time.
Where's the problem? SSH config? Server config? Router config?
More info: Usually the browser doesn't say "Network problem" as it does usually when trying to access a website that doesn't exist, but it says "Connection terminated by server". Sometimes it also says "Couldn't connect to the server". The first of which contrasts to the "No route to host" error I get when trying to connect via ssh.
Because I totally killed the configuration and was unable to access the installation on the server I reinstalled it yesterday but still have the same problem.
Also it seems that the problem is somewhat related to me connecting. There seems to be some kind of idletime limit, and after that limit is reached without me interacting (no matter if I'm connected anymore) the server stops reacting on any tries to connect locally for some time.
Last edited by zilti (2012-11-13 20:21:39)
I'm able to reconnect locally again for some time after connecting over the no-ip.org domain and doing a "ip link set eth0 down && ip link set eth0 up". Still not the slightest Idea about what might be the reason for this behaviour.
It may have something to do with the router. Have you tried to connect the server and notebook directly?
What you are you do not see, what you see is your shadow.
https://bbs.archlinux.org/viewtopic.php?id=154670 Here's a better description and newer thread
Closed. Continued in the thread linked from post #5
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
You assume people are rational and influenced by evidence. You must not work with the public much. -- Trilby
How to Ask Questions the Smart Way