Hi, I've been trying to get networking up and running on CentOS 7 in a VMWare (5.5) VM. From inside the machine (connected to console (GNOME desktop)) it looks like network is up. From outside I can't reach it.
From outside, same subnet:
outside_machine$ ssh -vvvv root@10.14.6.60 OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /login/sg219898/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 10.14.6.60 [10.14.6.60] port 22. debug1: connect to address 10.14.6.60 port 22: Connection timed out ssh: connect to host 10.14.6.60 port 22: Connection timed out (255)outside_machine$
From inside:
http://picpaste.com/Untitled-wOeTEcEu.png http://picpaste.com/Untitled2-5zi3Dj7x.png
* I shutdown NetworkManager based on someone's recommendation. * domainname/nisdomainname/hostname -y etc were showing no domainname so I set them using domainname xxx.com * from inside the machine I'm able to successfully ssh to vplab60/vplab60.xxx.com/localhost/ip-addres
Any help is appreciated.ThanksKashyap ------------------------------------------------------------------------------------------------------------------- Sponsored links: Rock Hard Erections. All New Formula Attacks the Root. Fast. www.capitolbird.org/pharma.html
On 5 March 2015 at 23:02, Kashyap Bhatt thekashyap1@yahoo.co.in wrote:
Hi, I've been trying to get networking up and running on CentOS 7 in a VMWare (5.5) VM. From inside the machine (connected to console (GNOME desktop)) it looks like network is up. From outside I can't reach it. From outside, same subnet:
outside_machine$ ssh -vvvv root@10.14.6.60 OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /login/sg219898/.ssh/config debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 10.14.6.60 [10.14.6.60] port 22. debug1: connect to address 10.14.6.60 port 22: Connection timed out ssh: connect to host 10.14.6.60 port 22: Connection timed out (255)outside_machine$
From inside: http://picpaste.com/Untitled-wOeTEcEu.png http://picpaste.com/Untitled2-5zi3Dj7x.png
- I shutdown NetworkManager based on someone's recommendation.
- domainname/nisdomainname/hostname -y etc were showing no domainname so I
set them using domainname xxx.com
- from inside the machine I'm able to successfully ssh to vplab60/
vplab60.xxx.com/localhost/ip-addres
Sounds like firewall is blocking port 22. Have you checked that?
Any help is appreciated.ThanksKashyap
Sponsored links: Rock Hard Erections. All New Formula Attacks the Root. Fast. www.capitolbird.org/pharma.html _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 3/5/2015 8:02 PM, Kashyap Bhatt wrote:
- I shutdown NetworkManager based on someone's recommendation.
I wouldn't, I would learn how to use it.
My guess is, the CentOS firewall is active, and you need to add a rule to allow inbound tcp/22 for ssh.
On Thu, Mar 5, 2015 at 10:02 PM, Kashyap Bhatt thekashyap1@yahoo.co.in wrote:
Hi, I've been trying to get networking up and running on CentOS 7 in a VMWare (5.5) VM. From inside the machine (connected to console (GNOME desktop)) it looks like network is up. From outside I can't reach it.
Are you sure the vmware NIC is configured as bridged, not NAT on the host side?
Are you sure the vmware NIC is configured as bridged, not NAT on the host side?
Not really. Does it help if I say I'm using the same Network Adapter configuration with which another VM in same subnet works fine? I've added a screen shot if that helps, though I think it shows the guest config and not host which you questioned.PicPaste - Untitled3-cJQlcohB.png
| | | | | | | | | | | PicPaste - Untitled3-cJQlcohB.png PicPaste is a login free service for uploading pictures | | | | View on picpaste.com | Preview by Yahoo | | | | |
Firewall1. ssh was kind of an example to show that I'm unable to "see" this machine from outside. Same is true for ping or host.2. I don't know how to specifically add rule to allow ssh/22 through my firewall so before spending more time on that, I just shut firewall down (systemctl stop firewalld). Same result, ssh/ping time out. Would it make sense to start the firewalld and add rule to allow ssh through it?
On 6 March 2015 at 02:15, Kashyap Bhatt thekashyap1@yahoo.co.in wrote:
Are you sure the vmware NIC is configured as bridged, not NAT on the
host side? Not really. Does it help if I say I'm using the same Network Adapter configuration with which another VM in same subnet works fine? I've added a screen shot if that helps, though I think it shows the guest config and not host which you questioned.PicPaste - Untitled3-cJQlcohB.png
| | | | | | | | | | | PicPaste - Untitled3-cJQlcohB.png PicPaste is a login free service for uploading pictures | | | | View on picpaste.com | Preview by Yahoo | | | | |
Firewall1. ssh was kind of an example to show that I'm unable to "see"
this machine from outside. Same is true for ping or host.2. I don't know how to specifically add rule to allow ssh/22 through my firewall so before spending more time on that, I just shut firewall down (systemctl stop firewalld). Same result, ssh/ping time out. Would it make sense to start the firewalld and add rule to allow ssh through it?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Since you are not able to communicate to the CentOS 7 vm from the host are you at least able to ping the gateway from the from the guest, which is in this case the CentOS 7 VM?
Are you sure the vmware NIC is configured as bridged, not NAT on the
host side? Not really. Does it help if I say I'm using the same Network Adapter configuration with which another VM in same subnet works fine? I've added a screen shot if that helps, though I think it shows the guest config and not host which you questioned.PicPaste - Untitled3-cJQlcohB.png
Firewall1. ssh was kind of an example to show that I'm unable to "see"
this machine from outside. Same is true for ping or host.2. I don't know how to specifically add rule to allow ssh/22 through my firewall so before spending more time on that, I just shut firewall down (systemctl stop firewalld). Same result, ssh/ping time out. Would it make sense to start the firewalld and add rule to allow ssh through it?
Since you are not able to communicate to the CentOS 7 vm from the host are you at least able to ping the gateway from the from the guest, which is in this case the CentOS 7 VM?
So it was a stupid mistake, I had selected the wrong VLAN while creating the VM. Compared the network config with a VM on same ESXi host that was working.
-
Earl A Ramirez -
Erick Ocrospoma -
John R Pierce -
Kashyap Bhatt -
Les Mikesell