New Look. New CentOS!
Yes, that’s what CentOS 7 says.
Anyway, lately, I installed CentOS 7 over VMware and installation were quite smooth. Immediate after installation, I tried to browse some web, and it was failing.
While doing basic troubleshooting, I noticed there were no IP when I did ifconfig
[[email protected] ~]$ ifconfig ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:0c:29:68:22:e2 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 642 bytes 55820 (54.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 642 bytes 55820 (54.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [[email protected] ~]$
Are you in the same situation like I was?
In this article, I will talk about how to fix if you don’t get the Internet on VMware with CentOS 7.
That leads me to think either network adaptor is not enabled or failed to obtain DHCP IP address.
Quick Solution
- Access terminal/console
- Become a root if you are not already
- Execute “dhclient –v” command
- You will notice it will bound IP address as shown below
[[email protected] network-scripts]# dhclient -v Internet Systems Consortium DHCP Client 4.2.5 Copyright 2004-2013 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens32/00:0c:29:68:22:e2 Sending on LPF/ens32/00:0c:29:68:22:e2 Sending on Socket/fallback DHCPDISCOVER on ens32 to 255.255.255.255 port 67 interval 4 (xid=0x433a9e33) DHCPREQUEST on ens32 to 255.255.255.255 port 67 (xid=0x433a9e33) DHCPOFFER from 172.16.179.254 DHCPACK from 172.16.179.254 (xid=0x433a9e33) bound to 172.16.179.136 -- renewal in 822 seconds. [[email protected] network-scripts]#
5. Boom, that’s all, you should have the Internet now. You will also notice IP when you do ifconfig
[[email protected] network-scripts]# ifconfig ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.16.179.136 netmask 255.255.255.0 broadcast 172.16.179.255 ether 00:0c:29:68:22:e2 txqueuelen 1000 (Ethernet) RX packets 11 bytes 1255 (1.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 23 bytes 3536 (3.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 770 bytes 66956 (65.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 770 bytes 66956 (65.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Add this in auto-startup
You might be interested in putting this in auto-startup, so you don’t have to do this every time you start the CentOS VM.
This is how you can put the script in auto-startup, so it starts automatically after VM is rebooted.
- Go to /etc/init.d
- Create a file with following, I have kept the name as “net-autostart“
#!/bin/bash # Solution for "No Internet Connection from VMware" # ### BEGIN INIT INFO # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 ### END INIT INFO dhclient -v
- Save the file
- Change the file permission as executable
chmod 755 net-autostart
- Add this script for auto-start using chkconfig command
chkconfig --add net-autostart
- Restart VM to test
I hope this helps. Let me know how it goes with you.
If you want to enhance CentOS 7 administration skills, then you may take this course by Cody Ray Miller.
Thank you very much!!! That solved my issue. so easy
Hi Chandan,
I am a beginner to Linux. I am using same Centos7 in Vmware. When I try to ping http://www.google.com, it doesnt not show any results like no packets sent or received.
1. > ifconfig | less
ens33: flags=4163 mtu 1500
inet 10.0.0.8 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 fe80::4f8d:6ecc:f580:5c84 prefixlen 64 scopeid 0x20
inet6 fe80::5f9d:31a2:6a5a:527d prefixlen 64 scopeid 0x20
inet6 fe80::27f3:5ded:c7f8:fb9 prefixlen 64 scopeid 0x20
ether 00:0c:29:2d:61:68 txqueuelen 1000 (Ethernet)
RX packets 8919 bytes 808091 (789.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65 bytes 8927 (8.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
2. [[email protected] ~]# ping http://www.google.com
PING http://www.google.com (172.217.26.164) 56(84) bytes of data.
64 bytes from http://www.google.com (172.217.26.164): icmp_seq=1 ttl=55 time=673 ms
64 bytes from http://www.google.com (172.217.26.164): icmp_seq=2 ttl=55 time=19.8 ms
64 bytes from http://www.google.com (172.217.26.164): icmp_seq=3 ttl=55 time=20.7 ms
64 bytes from http://www.google.com (172.217.26.164): icmp_seq=4 ttl=55 time=18.2 ms
64 bytes from http://www.google.com (172.217.26.164): icmp_seq=5 ttl=55 time=19.1 ms
^Z
[1]+ Stopped ping http://www.google.com
[[email protected] ~]#
3. I have setup VSFTPD server on one virtual machine and normal client in one virutal machine in Vmware box. When I try to connect to server using “ftp”, it says “No Route to host”.
I assume it is interrelated with the network issues in No. 1, 2.
Kindly help. You would be my life saver if you help me with this as I am struggling with this since many days.
Thank you.
Hello Prashant,
Ping to Google looks fine. To see packets received/sent information, you can terminate ping at a particular interval.
Ex: ping –c 5 google.com
Before troubleshooting FTP, you may want to check if both boxes can talk to each other first. Try ping if success then check telnet to ensure it’s not getting blocked due to any reasons.
Hi Chandan,
It worked for me.
Thank you
Great, thanks for confirming Samuel.
Hi Chandan. First off all, sorry for my english.
I faced the same issue on CentOS7 running on VMware, but when I tried to apply your fix under this version, some error is showed, specifically with the command “chkconfig –add net-autostart”. So, I started to looking for other ways to fix it.
I believe that the roots issue starts on the installation. During the installation steps, inside the networks options, the interface is marked in DOWN state, you need to manually change to UP. Whit this, this behavior disappears and is not necessary running a scripts to turns on the interface.
If you don’t notice of this during the installation, like us :), is easy to solve it. Just needs to find the config file of the interface under the folder: /etc/sysconfig/network-scripts/ .For example, ifcfg-ens33
Inside this file, you will find the value ONBOOT=no, just change it to “yes”. And will be solved.
I hope it will be useful,
Regards.
Federico.
Thanks Federico for the feedback. Sure, this will help others.
Thank you so much!!!
Thanks this also worked for me running CentOS 7 (1611) via Windows 10 HyperV
Great, Thanks for letting me know.
Thanks a lot for your post. Its worked for internet connection as well as to establish communication between host and guest machine. I broke my head for this with many IP configurations.
Glad to know Bhaskar.
Very useful, thank you
Your welcome, thanks for visiting.
I modified the connection mode from bridge to NAT, restarted the VM and it works now.
Thanks PasLe Choix for the tricks. Glad it’s working now.
This worked for me two days ago, I didn’t save it to the bash, so when I started my vm today, there is no Internet again.
I then proceed to run the same command again, but this time no more magic.
Why? Can you sort it out? Thank you so much.
thx, nice hack with #dhclient –v 🙂
Yup, that works very well!
Works like a charm!
After trying all the other solutions, this is the only one that actually worked. Thanks.
Glad, it helped. Thanks for the feedback Mike.
Or you can just add autostart to the interface in /etc/sysconfig/network-scripts/ifcfg-
ONBOOT=yes
Thanks, it worked…
Great Aarif, thanks for visiting.
worked for me as well 🙂
thanks!
Great, have fun!
I had the same probnlem when first starting centos 7 on vmware. No network connection.
I found the right solution, instead of scripting around it I just switched on the network interface in the network settings (desktop, upper bar, left of day/time field). Maybe this is intended behaviour to prevent the system from going online before it’s configured correctly.
Thanks for your feedback.
anyway to keep this persistant? I seem to have to do it everytime
Yes, you can by adding a small script to /etc/init.d I have updated the post with the instructions.
Wonderful. It’s work right away
Thanks for your help
Great, I am glad it worked.
Thanks this worked for me like magic. First time on Linux.
I am glad it worked.
This did not work for me, I am still showing no internet.