Thanks Frank for responding.
I was able to resolve the issue by enabling the "Host-only" adapter for the
network 2 and explicitly enabling it within the VM. In my first attempt, I
changed the Adapter 1 setting from NAT to "Host Only Adapter" which was
giving me issues. So far after this change it looks to be stable and i
don't have any connectivity issues.
Thanks again!
Thanks,
Rakesh T
On Fri, Aug 28, 2020 at 2:43 PM Frank Gordon <frankagordon@xxxxxxxxx> wrote:
Hello,
I've never seen anything like this before.
The MAC address is being reported as the IP address.
Are you using a dynamic IP address or are you hardcoding an IP address?
What does the configuration file for the network interface look like?
What is the output "journalctl -xe"
My guess is that the "lease" on the IP address runs out ...
Regards,
Frank
On Fri, Aug 28, 2020 at 4:40 AM Rakesh T <aryan.goti@xxxxxxxxx> wrote:
Missed to ask the actual question ..:).. Has anyone experienced this
problem before / have sme solution to this?
Thanks,
Rakesh T
On Fri, Aug 28, 2020 at 9:00 AM Rakesh T <aryan.goti@xxxxxxxxx> wrote:
Hi All,
I have a Oracle VM developer machine (running OEL7.6) running on top of
Windows 10. In an attempt to establish connection with the VM server using
putty from my desktop, I changed the "Adapter 1" network settings to host
only adapter and after starting the machine I was able to get an IP address
in eth0, and thereby I was able to establish connection using putty. But
after say a few minutes (3 to 4 minutes) I am losing the connection with
the VM server, and when I check the eth0 configuration, I see some strange
address i.e. "08:00:27:ec:1d:e8" getting reported.
After changing adapter 1 to host only adapter.
=================================
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.56.101 netmask 255.255.255.0 broadcast
192.168.56.255<<<<<<<<<<<<<<<<<<<<<<<<< IP address reflecting
ether 08:00:27:ec:1d:e8 txqueuelen 1000 (Ethernet)
RX packets 17 bytes 2352 (2.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 3503 (3.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
After few minutes
====================
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 08:00:27:ec:1d:e8 txqueuelen 1000
(Ethernet)<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
RX packets 681 bytes 61970 (60.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 405 bytes 75946 (74.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@localhost ~]# service network restart
Restarting network (via systemctl): Job for network.service failed
because the control process exited with error code. See "systemctl status
network.service" and "journalctl -xe" for details.
[FAILED]
[root@localhost ~]#
Thanks,
Rakesh T
--
+353-86-0695383
