Dude wrote:Houston, the Eagle has landed!debug3: Trying to reverse map address 192.168.56.1.This is actually normal since the VirtualBox host-only adapter acts on behalf of the client connection. Similarly, with the NAT adapter, the host adapter acts on behalf of the virtual machine.
One thing to remember is that the host-only interface is no good for outgoing connections. Traffic should go out on your VirtualBox NAT interface.
Looking at your previous output:
and on the ill-behaved OL 6.3I see that you have set 192.168.56.1 as the TCP/IP gateway. This is apparently not the case on your OL 5.6 machine.
[root@vblnxsrv02 ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.56.1 0.0.0.0 UG 0 0 0 eth1
So I'm wondering, did you perhaps specify 192.168.56.1 as default gateway in the TCP/IP settings of your OL 6.3 virtual machine? You should not specify any gateway on that 192.168.56.102/103 interface. Just leave it blank. Compare it with the setting of your OL 5.6 machine.
At least this would explain why your OL 6.3 machine cannot reach any DNS name server. It is not going to resolve 192.168.56.1 anyway, but at least it won't delay because it cannot connect to any DNS server.
And btw, 192.168.56.100 - 254 are usually reserved for host-only DHCP. You could try to enable the DHCP server on the host-only adapter in your TCP/IP settings on the VM and enable the DCHP server on the host-only adapter of VirtualBox preferences. You will also see it does not set a gateway.Yes. As mentioned earlier, on this (my office desktop) I have the host-only configured with the DHCP server DIS-abled. Yet my personal laptop, with the exact same version of VBox has it enabled and configured exactly as you say. I just installed that one a couple of weeks ago (new laptop) so I know it is at default settings. The evidence surely says I changed it on the office desktop, but I sure don't remember it.