![]() ![]() For those hosts/clients to access the webapp via hostname:8888 will depend on client hosts files, local DNS, or even mDNS services possibly provided on your DHCP server.Check my response above for a way to combat that lag. Hosts on your LAN should now be able to connect to the IP of your VM on port 8888. If you come up with anything other than your current address followed by the hostname, you need to modify the /etc/hosts file to add the correct information. grep /etc/hosts or grep /etc/hosts should find the line you need. You should have a line in /etc/hosts with the address followed by the hostname. In that same terminal, typing ifconfig eth0 | awk '/Bcast/' will show the address. From the open terminal, type hostname then hit enter. To find the IP address of the VM: Open a terminal/console window from the Ubuntu desktop (ctrl-alt-T), we use hostname, ifconfig, and grep /etc/hosts commands to put the pieces together and find your address. If your web server and application are not dependent on the IP it was first configured/installed on, and you have a DHCP server on your LAN, the only other piece of information you should need to connect to the VM is the IP address that was assigned to it via DHCP. This configuration is not usable outside the VM at all. Also verify your connectivity to hostname:8888 (assuming hostname was not added to the loopback/localhost address in the /etc/hosts file) and ip-address:8888.ĮDIT: Based on the /etc/hosts details posted, you are binding your VM and therefore the webapp to the loopback network. Verify your connectivity to localhost:8888. ![]() Shutting down the VM and changing the VM network adapter1 setting to "bridged" will allow your host (and any host on your local network) to communicate with that VM without any special routes added or hoops to jump through. Long story short, windows will not route to an address it is providing NAT for, without jumping through more hoops first. This will give the VM an IP address of 10.0.2.15/24 and a default route of 10.0.2.2 (which should be your host). In the latter case, a dependency on hostname resolving to ip.ad.dr.ess on your network is introduced.īy default, when you create a VM in VirtualBox, network adapter 1 is set to NAT. Outside that VM you will have to use ip.ad.dr.ess:8888 or hostname:8888. The localhost:8888 URL is only a valid URL inside your VM. # The following lines are desirable for IPv6 capable hosts TX packets:1566 errors:0 dropped:0 overruns:0 carrier:0 RX packets:1566 errors:0 dropped:0 overruns:0 frame:0 ![]() TX packets:3587 errors:0 dropped:0 overruns:0 carrier:0 RX packets:7431 errors:0 dropped:0 overruns:0 frame:0 ![]() UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 I tried VBoxManage modifyvm "VM name" -natdnshostresolver1 on but it did not have an impact.Įth0 Link encap:Ethernet HWaddr 08:00:27:d0:fc:0e I cannot see the app from the host at the same URL. I can see the app at localhost:8888 via a browser from within the VM. ![]()
0 Comments
Leave a Reply. |