[SOLVED] Private Server unreachable from Workstation
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been developing a website on my private server with laptop workstation access through the router. I had access to the server with PuTTY and, with the browser, Webmin and the website.
Then, since last week, I know not why, attempts to access the server with:
PuTTY generates the error msg
"Network error: Connection timed out."
Browser generates the error msg
"This site can’t be reached
192.168.0.13 took too long to respond.
Search Google for 192 168 10000
ERR_CONNECTION_TIMED_OUT"
terminal command nmap used to generate:
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
10000/tcp open snet-sensor-mgmt
Now, nmap generates:
Starting Nmap 7.01 (...) at ....
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 0.52 seconds
iptables lists:
targets="ACCEPT", sources and destinations="anywhere" for:
Ok. I'm now well beyond my very limited understanding of Linux and server networking, but I'm suspecting that ports 22, 80 and 10000 are down for 192.168.0.13??
Can anyone suggest what I need to do, to restore my workstation access to the server??
Server Distribution:
Linux version 4.4.0-72-generic (buildd@lcy01-17) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu~16.04.4) ) #930UbuntuSMP Fri Mar 31 14:07:41 UTC 2017
Laptop is functioning and connects to internet.
Nmap is running on server. Server is unreachable from laptop.
I don't know whether SSH is running. How do I determine that?
Although the internet is unable to access the server, the server does ping google.com.
inet 192.168.0.11/24 brd 192.168.0.255 scope global eno1
Your IP address is no longer 192.168.0.13. If you do not know how your system is configured then by default it is using DHCP which means your router is assigning a dynamic IP address. Most of the time a device will automatically acquire the same address as before but it is not guaranteed .
You can either configure your router to automatically assign the server the same address or configure the server to use a static IP address. The later might be slightly easier if you have never messed with the router.
inet 192.168.0.11/24 brd 192.168.0.255 scope global eno1
Your IP address is no longer 192.168.0.13. If you do not know how your system is configured then by default it is using DHCP which means your router is assigning a dynamic IP address. Most of the time a device will automatically acquire the same address as before but it is not guaranteed .
You can either configure your router to automatically assign the server the same address or configure the server to use a static IP address. The later might be slightly easier if you have never messed with the router.
Thank you for the quick analysis.
I would like to keep the 192.168.0.13 for now, which I think means that I need to configure the router to reserve IP address 192.168.0.13. Is that correct? If so, then are there also server settings that need to be changed?
The obvious one that you identified to be the router automatically changing the IP address. I configured the router to reserve the IP address but that didn't immediately solve the server access problem ...
And, a not so obvious one that, unfortunately, was the cable plugged into a dead router port. It took quite awhile but when, in desperation, I plugged the cable into a different router port, the workstation accessed the server and the problem was solved ... who would have thought?
You, very quickly, put me onto the track that solved this problem. Thank You
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.