Having issues with network adapter eth0

[vjjv]

I am having Virtualbox 4.3.26 in Windows 8.1 host with Oracle Linux VM. This was working fine for 2 months or so and suddenly from yesterday I am having issues.

I am not able to access anything from my VM in my host operating system. I have deployed some apps and I was able to use a browser localhost:8080/... and it worked. I was also able to connect to the database installed in the VM before using the VM's IP. But now I am not able to. I tried restarting the VM couple of times.

I am having the "Bridged Adapter" option for the Network Adapter.

When I run ipconfig, I do not see any IPv$ address at all, so I tried doing

Code: Select all

[]# /sbin/dhclient eth0
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit 

Listening on LPF/eth0/mac
Sending on   LPF/eth0/mac
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 (xid=)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=)
No DHCPOFFERS received.
Trying recorded lease IP
PING *********************** eth0: 56(84) bytes of data.

--- IP ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3001ms
, pipe 3
No working leases in persistent database - sleeping.

Not sure why this is happening. I also tried to activate the eth0 via System->Administration->Network option, but that also failed.

Any suggestions? Thanks.

[Perryg]

Minimal information needed to be able to help

Post the guests log file ( as an attachment )
Post the results of the following as well:

• From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.
  
  Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

Also what changed since the time this worked and now. Something must have caused this and knowing would help.

[vjjv]

Thanks for the response.

I am attaching the VM /var/log/messages that might be relevant. Please let me know if you need more information.

I am also attaching the VM details image.

I am not sure if anything changed, not even Windows Update, but one thing to note is I am using mobile broadband, then switched to another wireless, then to mobile broadband, not sure if that would be an issue. I did not restart my laptop though.

Thanks again.

[Perryg]

Did you read my post and did you not understand it?

[vjjv]

Apologies, I missed the first line of your post.

Both my Host Windows and Guest Linux are 64 bit.

I am attaching the log files as zip. I also looked in the log files, but could not find anything that I could relate to this issue.

Thanks.

[noteirak]

I can't see anything special in the logs.

One note about bridged mode in VirtualBox which might be the cause of your issue: I see from your screenshot and from the logs that you bridged on your Wifi card. It means that all the network traffic from the VM will ONLY go there, and ONLY if the interface in the host is UP & RUNNING, even for LAN access!
Are you sure you still have Wifi signal at that point? If the VM is supposed to use the mobile link instead at that point, then you'll need to change the network config to the proper adapter at runtime.
If you need network access without having to manage the interface configuration, switch to NAT which will use whatever is available, just like a regular process on the host.

[vjjv]

Apologies for the late response.

I tried NAT and it did not work. The VM's IP was 10.*.*.* and when I did ipconfig in my host cmd, I did not see any such IPs.

But as you suggested, I changed the Bridged Adapter to "Internet Sharing Device" and it works now. I guess, I have to live with it.

Thanks again for the help.