<p dir="ltr">Ok, here is what I see.</p>
<p dir="ltr">Your interface appears to be trying to do a DHCP configure. But, here is your problem... the adapter already had one... and Windows got it. You are in Bridge, not NAT mode, so Linux can not have its own IP, it will get rejected by the host server.</p>
<p dir="ltr">Let me think a sec on this.</p>
<p dir="ltr">Kevin </p>
<div class="gmail_quote">On Feb 4, 2015 12:16 AM, "Michael Torres" <<a href="mailto:matorres124@gmail.com">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>...devserver NetworkManager[561]: <warn> (enp0s3): DHCPv4 request timed out.<br>...devserver NetworkManager[561]: <info> (enp0s3): canceled DHCP transaction, DHCP client pid 2138<br>...devserver NetworkManager[561]: <info> Activation (enp0s3) Stage 4 0f 5 (IPv4 Configure Timeout) scheduled...<br>...devserver NetworkManager[561]: <info> Activation (enp0s3) Stage 4 0f 5 (IPv4 Configure Timeout) started...<br>...devserver NetworkManager[561]: <info> Activation (enp0s3) Stage 4 0f 5 (IPv4 Configure Timeout) complete...<br>...devserver network[1987]: Bringing up interface enp0s3: Error: Timeout 90 sec expired.<br>...devserver network[1987]: [FAILED]<br>...devserver systemd[1]: network.service: control process exoited, code=exited satus=1<br>...devserver systemd[1]: Failed to start LSB: Bring up/down networking.<br>-- Subject: Unit network.service has failed<br>-- Defined-By: systemd<br>-- Support: <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br>--<br>-- Unit network.service has failed<br><br><br></div>This may show the problem, but it shows what I already know. I went to that site "freedesktop" and search for key words that were in this error......, nothing.<br><br></div>So, if this erorrs tells you something that I cannot readily see, I am all ears (or eyes, as this is email...)<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 4, 2015 at 12:00 AM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Bingo, Huston we found the problem.</p>
<p dir="ltr">The old scripts are using systemctl so for backwards compatability. Look in the journal and it should tell you what is wrong.</p>
<p dir="ltr">I think the command off the top of my head is something like</p>
<p dir="ltr">#journalctl --unit=network </p>
<p dir="ltr">Kevin</p>
<div class="gmail_quote">On Feb 3, 2015 11:53 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>OK, when I start/stop the network service, I use the following command....<br><br></div>[root@devserver]# /etc/init.d/network stop<br></div> Stopping network (via systemctrl)<br><div><br><br>[root@devserver]# /etc/init.d/network start<br> Starting network (via systemctrl)<br><br></div><div>Then I run the commands that you gave earlier after starting fails...<br><br><br></div><div>This is the result..<br><br></div><div>network.service loaded failed failed LSB: Bring up/down networking<br></div><div><br><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 11:47 PM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">If your interface has no IP, you can't communicate out to anywhere, and we are back to the conversation about starting and enabling your network service.</p>
<div class="gmail_quote">On Feb 3, 2015 11:45 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">thats the point.... I dont have an IP address...there is nothing that I put to scan it. My NIC was allowing it when I was at Starbucks.. That is why I think its my router, as such isnt the router that assigns IP address to the network when using DHCP?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 11:39 PM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Ok, down to two possibilities. </p>
<p dir="ltr">Nmap is a scanner. It is trying to identify your VM and probe for open ports.</p>
<p dir="ltr">When you scanned by name... it did not understand that name. Your router is external to all of this, and should not be involved at all. </p>
<p dir="ltr">Try nmap by IP address.</p>
<p dir="ltr">If that still results in nothing, add a virtual network via VMware or VBox. Next add a new virtual network adapter to your VM, and connect it to the new network. This should be a private network between host and client. Config your interface in the VM. This will resolve your problem. In this case, your NIC is not allowing traffic to go out, then back in to itself. The traffic is almost certainly not going to your router then back.</p>
<p dir="ltr">HTH<br>
Kevin</p>
<div class="gmail_quote">On Feb 3, 2015 10:41 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>netstat -plant<br><br></div>liastening on ports 25 and 22 both for IPv4 nad IPv6<br><br></div>Result from the nmap(windows version)<br>Starting Nmap 6.47 ( <a href="http://nmap.org" target="_blank">http://nmap.org</a> ) at 2015-02-03 22:36 US Mountain Standard Time<br><br>NSE: Loaded 118 scripts for scanning.<br><br>NSE: Script Pre-scanning.<br><br>NSE: Script Post-scanning.<br><br>Read data files from: C:\Program Files (x86)\Nmap<br><br>Nmap done: 0 IP addresses (0 hosts up) scanned in 4.20 seconds<br><br> Raw packets sent: 0 (0B) | Rcvd: 0 (0B)<br><br>Failed to resolve "devserver".<br><br>WARNING: No targets were specified, so 0 hosts scanned.<br><br></div>I would ahave asusmed the the above results as the dhcp server is not generating a IPv4 address<br><br><br><div><div>so...<br><br><p dir="ltr"> 1) The netstat does not show the binding to port 21... this means SSHD did not start.</p><p>I am guessing port 22 is OK<br></p>
<p dir="ltr"> 2) netstat shows SSHD, but the firewall is not allowing it. Open the firewall</p><p>Firewall is already disabled<br></p>
<p dir="ltr"> 3) netstat shows SSHD, the firewall is open, but you still don't see the port open via nmap.</p>
<p dir="ltr"> 3a) if you see other ports open, I would look at the Windows firewall</p><p>Windows firewall allowed it on a Public network (startbuck), so why not allow it at my home<br></p>
<p dir="ltr"> 3b) If you don't see any ports open, you have two options here.</p>
<p dir="ltr"> 3b1) Make sure your NIC (from the Windows side) is in promiscuous mode.</p><p>dont know how to do that.<br></p>
<p dir="ltr"> 3b2) If it is already in promiscuous mode, then this
may not work in this configuration. In this case, try adding a private
network on a second NIC, and communicate with the VM over that.</p>Ill try to connect to my ethernet adpater and see if that is it, maybe its my wireless adapter....<br><br></div><div>Mike<br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 10:22 PM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Ok, sorry, I misunderstood. </p>
<p dir="ltr">Nmap could be your friend here. Install it on your Windows machine. It will install the graphical tool automatically in Windows. Point this at your VM, and do a "intense scan"</p>
<p dir="ltr">Next, on the Linux VM, do a <br>
# netstat -plant</p>
<p dir="ltr">Zenmap/Nmap will tell you what ports it can see open from its side of the link. The netstat command will tell you which ports are opened by running software.</p>
<p dir="ltr">Lastly, on the Linux VM, do a <br>
# ip tables -L</p>
<p dir="ltr">This will tell you which ports the firewall will allow.</p>
<p dir="ltr">Now, you have a few possibilities:</p>
<p dir="ltr"> 1) The netstat does not show the binding to port 21... this means SSHD did not start.</p>
<p dir="ltr"> 2) netstat shows SSHD, but the firewall is not allowing it. Open the firewall</p>
<p dir="ltr"> 3) netstat shows SSHD, the firewall is open, but you still don't see the port open via nmap.</p>
<p dir="ltr"> 3a) if you see other ports open, I would look at the Windows firewall</p>
<p dir="ltr"> 3b) If you don't see any ports open, you have two options here.</p>
<p dir="ltr"> 3b1) Make sure your NIC (from the Windows side) is in promiscuous mode.</p>
<p dir="ltr"> 3b2) If it is already in promiscuous mode, then this may not work in this configuration. In this case, try adding a private network on a second NIC, and communicate with the VM over that.</p>
<p dir="ltr">Let me how it goes.</p>
<p dir="ltr">Kevin</p>
<div class="gmail_quote">On Feb 3, 2015 9:58 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Well, no, I didnt issue any commands other than /path/to/network/script/network start /path/to/network/script/network stop<br>and the commands to disable firewall/SELINUX<br><br></div>I know I didnt use any systemctrl commands., but I tried to run the commands that you just provided and nothing happened. I should probably say that I know that IPv6 is enalbed and have network connection to the net work and I can ping <a href="http://yahoo.com" target="_blank">yahoo.com</a> etc..... I just cant SSH(putty) to the server.<br><br></div><div>This all leads me to beleive that there is a configuration in my router that is not allowing me to get a IPv4 address. Does the default gateway have to be a certain number? I have manually configured that IP on my router a long time ago, but even then I had Bridged networking working correctly.<br><br></div><div>Mike<br></div><div><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 9:48 PM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Your network is probably not getting started. The enp0p3 is the name of an interface started almost definantly by systemd, not the old RHEL way. This is likely why the networking-scripts didn't work.</p>
<p dir="ltr">When you were at Starbucks, you likely did a systemctl start on the interface. Look in your history for it. If you find it, issue the same command again. If your interface comes up correctly, reissue the command once again, substituting enable for start. This second command is similar to a chkconfig command.</p>
<p dir="ltr">Let me know how that works.</p>
<p dir="ltr">Kevin </p>
<div class="gmail_quote">On Feb 3, 2015 9:13 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>The result of that command is:<br><br></div>0 loaded units listed<br><br><br></div>So I ran a what it suggested: systemctl list-unit-files<br></div><div>majority of everything says "static" but some are "enabled" or "disabled"<br><br></div><div>again, because I cannot copy or capture a screen shot, is there a specific list item that you need to see?"<br></div><div><br></div><br><br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 8:44 PM, Kevin Fries <span dir="ltr"><<a href="mailto:kevin@fries-biro.com" target="_blank">kevin@fries-biro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Do a</p>
<p dir="ltr"># systemctl --failed</p>
<p dir="ltr">And post the results</p>
<p dir="ltr">Kevin</p>
<div class="gmail_quote">On Feb 3, 2015 8:37 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Arrghh....yes its configured. But I am having an issue getting the cat /etc/sysconfig/network-script/ifcfg-enp0s3..........because I cant connect, I cant ssh in to use outty so I can copy using my mouse. I tried taking a screen shot, but VBox for some reason wont display on on the "print screen"command.<br><br></div>is there a particular setting you are looking for? again, the file is configured and it is reading it.<br><br></div>Mike<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 8:15 PM, Stephen M <span dir="ltr"><<a href="mailto:smelheim85@gmail.com" target="_blank">smelheim85@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">I don't remember if this is a problem in centos 7 as it was in 6. But check to make sure the eth0 is configured. But yes a print out of ifconfig inside vox would be great. </p>
<div class="gmail_quote">On Feb 3, 2015 8:07 PM, "Michael Torres" <<a href="mailto:matorres124@gmail.com" target="_blank">matorres124@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Hello all,<br><br></div>I have an problem that I cannot seem to figure out.....<br><br></div>I am trying to use "Bridged" networking in Virtual Box to a CentOS 7 minimum install distro that I want to use for my development server.<br><br></div>I have used Bridged networking in the past and never had any issues but that was with older versions of CentOS<br><br></div>The issue.... DHCP will not assign a IPv4 address to the server.<br><br></div>Here is the weird part... I was at startbucks and actually got it to work! (Please, hold the "Just use it at starbucks then" comments..I know....)<br><br></div>Here is the process I used...<br><br></div>-Installed a fresh CentOS 7 on VBox<br></div>-While on NAT, I performed "yum update" so my server was fresh with the latest<br></div>-Disabled SELinux<br></div>-Disabled the Firewall<br></div>-Shut down server to reconfigure the adapter to "Bridged"<br></div>-used adapter type of "Intel Pro 1000 MT Desktop (82540EM)"<br></div>-set it to "Promiscuous Mode"<br></div>-restart the server<br><br><br></div>Again, at Starbucks it assigned a IP address, so this leads me to believe that the issue is with a configuration on my router.<br><br></div>I am not very good at networking, so any help would be appreciated.<br><br></div>If you need error messages or other output, let me know (and possibly the command as I don't know networking that well other than "ifconfig")<br><div><br><br>Mike<br></div></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div><br></div>
<br>---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br></blockquote></div>