No remote access to Linux using ping or SSH, but Samba works
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.
No remote access to Linux using ping or SSH, but Samba works
Hi,
I have an openSUSE 10.2 (x64) installation and I want to access this machine from a Windows Vista client (x64 as well) in the same private LAN (subnet mask 255.255.255.0) using DHCP (router).
I can reach (ping) the Windows client and other network devices from within the Linux machine. But I cannot ping the Linux machine from the Windows client (using the IP address) nor can I connect to it using SSH or telnet via PuTTY. Pinging other network devices from the Windows client works fine.
Currently, the only way I can access the Linux machine from the Windows client is by using SMB/Samba (even using name resolution)!
This admittedly sounds like a firewall problem. But SUSE firewall is disabled and no additional firewall software is installed (at least none that I am aware of). Using nmap or netsat -ltnu confirms that ports 22 (SSH) and 23 (telnet) are indeed open and listening.
Disabling the firewall on the Windows client did have no effect.
I should add that the Linux machine runs inside a virtual machine on the Windows host using VMWare Workstation 6.0 (with bridged networking). I do not believe that this contributes to the problem because I have successfully worked with similar environments in the past.
I would appreciate any suggestions on where I might start looking for a solution.
Stupid but simple question: is sshd installed and running on the linux system? If it is, can you login locally and try connecting to ssh via a loopback device (in other words, typing ssh username@127.0.0.1 or ssh username@localhost)?
Hi there...
I think you can start trying to see where connection get lost... vmware gives your virtual opensuse an ip address, from the host (win box) you can ping the guest (suse)?
Maybe it can be an issue between the host machine nic and the virtual nic, windows is redirecting outside packets to virtual machine??
It can be a start
the virtual machine gets its own IP address from the DHCP server (which is a router on my network). I confirmed with ifconfig that the (virtual) ethernet device (eth0) has a valid IP address from the DHCP server's IP pool. Unfortunately, I am unable to ping the virtual machine from the windows host using that address. But connecting to the samba shares using that IP address works fine.
Try see if firewall on suse are really off. type in a root terminal --> # iptables -F ..this kills all firewall rules.
Also you can see the rules for ping replies: # cat /proc/sys/net/ipv4/icmp_echo_ignore_all this command must reply 0.
there is other for broadcast: cat /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts ...0 means ok.. 1 means don't reply.
try set both icmp as 0 for sure. After this you can be sure the guest suse is opened. Afterwards try to see vmware host setup in Edit > Virtual Network Settings. I cannot mind other things about suse... about windows cannot even imagine.. sorry
I found out that the problems are most likely due to caching issues either with the Windows client or (more likely) with the router (DHCP server).
I assigned a new IP pool to the DHCP server to enforce new IP addresses for all network clients. This solved the problem. Ping, SSH, HTTP, SMB ... all is working fine now.
Thanks to all those who helped in finding a solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.