Can't ping between RHEL and Window VMs

[awsmike]

RE: so make sure ICMP is enabled in the Windows firewall. Note: disabling the firewall does not enable ICMP.

I enabled it and still nothing, same message when I ping: connect: Network is unreachable

I'm able to ping between the Window Guest VMs and now to the Linux VM from Windows but still can't from Linux to Windows...

[Perryg]

Well I am like the last housekeeper I talked to. Said I don't do Windows and neither do I so you will need to see what Windows VBox folks have to say. I can tell you that it is a configuration issue and not VBox. I would post this in the Windows guest section for better visibility and you can point back to this post if you like.

[awsmike]

I feel that the issue is within Linux... specifically the 'internal network' adapter. The reason I state this is because once I added that adapter then I lose connectivity to everything.

For example, without Internal Network using only NAT I can ping 8.8.8.8 and use the Internet. I add Internal Network and I lose Internet and cannot ping 8.8.8.8 or my Windows VM - 100.0.0.1. They both give me the same error: connect: Network is unreachable. I don't see how fixing an issue within Windows, where it works fine between Windows VMs, could affect the connectivity within Linux.

Basically if we can get NAT + Internal Network to connect to the Internet, I feel my other issue (pinging to Windows VM) will resolve itself. This may be a separate topic at this point, but that makes sense to me...

[Perryg]

OK so post some diagnostic information. Not ping lets look at the configuration of one windows guest and the Linux guest.

• ifconfig -a from the Linux guest
  ipconfig /all from the Windows guest

Also from the hosts terminal

• VBoxManage showvminfo <guests name>

Replace the <guests name> with each of the above guests.

[awsmike]

Cool, thank you!

I'm attaching due to the size of the content requested...

Thanks

[Perryg]

Code: Select all

NIC 1:           MAC: 08002799C8CE, Attachment: NAT, Cable connected: on, Trace:
 off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Prom
isc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2:           MAC: 080027C97E51, Attachment: NAT, Cable connected: on, Trace:
 off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Prom
isc Policy: deny, Bandwidth group: none
NIC 2 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 3:           MAC: 080027777E99, Attachment: Internal Network 'intnet', Cable
 connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps,
Boot priority: 0, Promisc Policy: deny, Bandwidth group: none

Code: Select all

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter #2
   Physical Address. . . . . . . . . : 08-00-27-C9-7E-51
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5d5d:f1cd:ee7f:82df%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.0.134(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 0.0.0.0
   DHCPv6 IAID . . . . . . . . . . . : 470286375
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-7A-34-54-08-00-27-99-C8-CE
   DNS Servers . . . . . . . . . . . : 10.0.0.134
   NetBIOS over Tcpip. . . . . . . . : Enabled

You have three adapters in the Windows guest and only should have two. Remove the adapter in the guest settings that is associated to ethernet 2

It also looks like you are trying to use a different scheme for the VBox NAT which should be 10.0.1.* and 10.0.2.*. You must set the guest to use DHCP for the VBox NAT adapters.

Remember I said to remove the VBox NAT adapters from the guests until you got this working then you could add the VBox NAT back in? It makes it a lot easier to troubleshoot. VBox NAT is only for you to be able to reach the Internet and nothing else.

[awsmike]

Yes, I put the NAT back in Linux earlier to troubleshoot, was doing several trials between your posts...

OK, so I have removed all NAT's from both Windows and Linux. Now I cannot communicate to and from both. I'm attaching the information you requested again, including the ping results, now that the NAT is removed and we have only "Internal Network" between them.

Thanks!

[Perryg]

Windows:
IPv4 Address. . . . . . . . . . . : 100.0.0.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0

Linux:
inet 100.0.0.2 netmask 255.255.255.255 broadcast 100.0.0.2

The subnet Mask is wrong. They must be the same.

[awsmike]

Not sure why it changed, was the same before.... but still nothing, I gave the Windows the same subnet mask as Linux (255.255.255.255), and all I get is:

Code: Select all

C:\Users\Administrator>ping 100.0.0.2

Pinging 100.0.0.2 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 100.0.0.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

From Linux, same error message:

Code: Select all

$ ping 100.0.0.1
connect: Network is unreachable

[Perryg]

Why not give the two a subnet that works? 255.255.255.0 or 255.0.0.0
Using subnet mask 255.255.255.255 you have only one available address and it would be 100.0.0.2

[awsmike]

Ok, quick update.... so I kept playing with the subnet masks, and once I added both to 255.255.255.0, then they were both able to ping each other!

Now, the other problem, I added NAT back to Linux, and I can't connect to the internet. If I disconnect Internal Network and just leave NAT, I can connect.

Should I create a new topic in the board for that issue or can we carry on here?

Thanks!

[Perryg]

First stop experimenting. It will only make this harder. Remember I said to add NAT after it worked and to be sure to leave the guest set to DHCP so it would get the proper address?

Look at the configuration of the guest and make sure it is set to DHCP on the VBox NAT adapter and that it gets an address of 10.0.2.* or 10.0.1.*

Be sure you leave the intnet configuration alone.

[awsmike]

Yup, the pinging between them worked, that's when I brought NAT back in the picture, but I didn't configure the DHCP so I'll work on that at some point today, have to run off now, but I do appreciate all your help! I will update at some point today the status. Thanks!