Unable to access the host from the outside network

[Wielbert]

Hi Team,

We have installed Ubuntu 12.04 on the virtual box and the guest being Windows 7. We have installed an application called SQL-LEDGER and when we type 'localhost/sql-ledger/login.pl' we are able to view the app successfully. We have assigned a static IP 192.168.2.*. We access the the app by typing '192.168.2.16/sql-ledger/login.pl' and we are able to access it successfully. We have used the same address to access it on the the guest windows 7 machine and sevral pc connected to the same network. We are having a problem accessing this from morning. We have no port forwarding on the router and the firewall is configured to allow the connection. Interestingly, we are unable to locate the IP address '192.168.2.* on the router list. The ping results are 'DESTINATION HOST UNREACHABLE'

We have being using the 'bridged-network' from the beginning. Is there something that needs to be changed. We are facing this issues from the last hours.

Many thanks in advance.

Regards,
Wielbert Collinson

[mpack]

First guess is that the static address you assigned now conflicts with something else on the network. Why didn't you just keep it simple and allow the guest to be assigned an IP address dynamically (DHCP)?

Guesswork aside, it seems clear that the guest is running fine and you have a network configuration problem.

[Wielbert]

Considering your first solution we have tried NAT, Host over Network and Bridged Adapter. We are unable to resolve the IP address from the guest account.

Any changes in apache related to this issue. Just a thought We got a prompt to install a new version to install VB. Will re-installation work?

Any suggestions is much appreciated.

Regards,
Wielbert Collinson

[noteirak]

'DESTINATION HOST UNREACHABLE' is a very specific error that means exactly what it means : the host couldn't be reached.
This implies two things :
- the host used to be reachable (you've validated this) via a very well known path, but is not anymore, hence the "unreachable"
- the path did not timeout since then, and your network hardware still remembers that path but there is something preventing the path from being used.

This indicates an issue at networking level, not Virtualbox. Nothing changed *at all* in your network infrastructure since? Is 192.168.2.0/24 actually known by your network equipement?

[Wielbert]

We have some comfiguration changes in apache. We have created a no-ip account and a host and we had to forward the port because 80 and 8080 is blocked. Hence it used 9001. However, we have reverted the changes to port 80 and deleted the port forwarding rule and we are having problems since then. I think its a small configuration issue that needs to be sorted. The resolution is right in front of us... we have to just figure it out.... 192.168.2.0/24 is recognized by the network..

Regards,
Wielbert Collinson

[Wielbert]

Hi

I have used the following suggestion in one your post

viewtopic.php?f=3&t=55496

sudo ifconfig -a
sudo route
cat /etc/resolv.conf

I am not able to add screenshots and word documents to the forum

We have a wireless usb connected to the PC 802.11n USB Wireless LAN Card.

Host IP : 192.168.2.20
Guest IP : 192.168.2.33

localhost/sql-ledger/login.pl & 192.168.2.20/sql-ledger/login.pl - works fine in VB with Ubuntu installed.

192.168.2.20/sql-ledger/login.pl - Used to work from 2 weeks and sudenly stopped .

We have set the port forward and changed the firewall rules.

[Wielbert]

More Screenshots

[noteirak]

Thank you for the screenshots, but they do not show me anything useful, sadly.
In one of them, you can pind your .20, is that the IP you couldn't reach before?

The best would be to give us the VM Log file and the guest settings as a zip attachment. See Minimum information needed for assistance.

Also, provide the following output from the host :

Code: Select all

ipconfig /all
route print
netstat -an
nslookup 8.8.8.8
nslookup google-public-dns-a.google.com

And in the guest :

Code: Select all

sudo ifconfig -a
sudo ip addr
sudo route
sudo netstat -lnp
nslookup 8.8.8.8
nslookup google-public-dns-a.google.com

[Wielbert]

1. The version of VirtualBox you are using, and whether you have installed the Guest Additions (in the guest).

Version 4.2.14r86644 | No added guest

2. Host & Guest make and version including 32 or 64 bit, and the amount of memory available to both.

Host : Ubuntu 12.04.02 64 Bit | Guest : Windows 7 64 Bit

Storage for host : Virtual size : 8 gb | Actual size 4.86 gb ------- Memory for Guest [8192MB RAM] Page File /; 4552MB | 1076MB Available

3. Guest log file (as an attachment) See your VirtualBox users guide for how to locate this if using CLI or right click the guest in the VirtualBox main manager and select show log. Then choose save.

The same has been added.

Currently, we are unable to access the internet from the Virtual Box. We receive the message "waiting for n/w configuration : waiting up to 60 seconds for n/w configuration".. While executing ifconfig we see it says " UP BROADCAST RUNNING MULTICAST". We tried to run a command .. i dont recall but we got a message "error fetching interface information : device not found". We have modified the file 70-persistant .net.rules and have save it with a different name 70-persistant .net.rules.save

Regards,
Wielbert Collinson

[Perryg]

Regarding the screen shots. I see that you are trying to use the host-only adapter in your local LAN. Simply a recipe for disaster. The host-only adapter is a modified loopback device and not designed to work this way. Not to mention that the address range and the DHCP server range are not even in the same subnet.

[noteirak]

I second what Perry said on this : your host-only interface (which is what you are using) must not be on the same subnet as your regular LAN, you must use another LAN.
But Host-Only is not meant to be used to go "out". Use bridged or NAT for that, unless you have advanced networking knowledge.

In your host, I see that you don't have a proper IP address (using the 169.254.x.x range):

Code: Select all

Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 08-00-27-00-6C-2E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f519:4b26:96a8:b91e%25(Preferred) 
   Autoconfiguration IPv4 Address. . : 169.254.185.30(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.0.0

But in the guest, I see that you're using your regular LAN subnet:

Code: Select all

eth0      Link encap:Ethernet  HWaddr 08:00:27:25:8f:f8  
          inet addr:192.168.2.20  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1

a Host-Only interface is like a hardware switch with no connection to any other network. This means three things :
- You cannot "just" go out to your regular physical LAN
- You need to give IPs in the same subnet to the host and the guest
- You must not use the same subnet as your regular LAN, or the host will simply not know where to send packets...

Your issue is simply a wrong networking configuration, like expected. Make sure you configure it properly.

[Wielbert]

Good News : 192.168.2.20 works fine. Troubleshooting steps :

VM Settings

1. Name : 802.11n USB Wireless LAN Card
2. Select Cable Connected
3. Adapter Type : Intel PRO/1000 MT Desktop (82540EM)

VM Preferences

1. Host Only Network Details.

1. IP Address : 192.168.2.34
2. IPv4 Network Mask : 255.255.255.0
3. DHCP Server : Enable Server

Bad News : Sudo ufw Disable and the program works fine . If you enable firewall it doesn't work.

Please note that the same settings were applied when we first used the system. Disabling FW is an temporary option but not a permanant fix.

So far it looks good. Any other suggestions apart from disabling FW would be helpful.

Regards,
Wielbert Collinson

[noteirak]

Doesn't really make sense to me... why do you talk about your wifi interface if you're using host-only? Did you use bridging? In which case, your host-only would be useless..
I am not convinced your networking is correct, and you might encounter issues later. But if it works fine for you right now, good enough I guess

[Wielbert]

We have been using bridged adapter from day1. We have never changed to NAT or any other interfaces. These were always the settings as mentioned in my earlier post and reverted back to the original. We are using VB for the first time and did not document the steps hence, we were finding it tough about what settings we were using. Since, we reverted back to the original it looks fine. However, the question still remains ..Why after disabling FW works and when you enable it does not? If we have to disable FW and you think its a permanent solution.. we would go with your suggestion .. Many Thanks

[noteirak]

You did not post the guest settings earlier, so I cannot really tell what config you're using right now.
If you do, it would make sense to me and I could advise you properly.