VBox network mode to test Win 2008 server? - dns

I have 2 machines running on my VirtualBox, one is a Windows XP client the second one is a 2008 Server with DHCP and DNS installed and configured.
now i want to test my server setup with my client machine, i tried all the network mode in VirtualBox but none of them worked
NAT mode get dhcp setting from VirtualBox itself i think
Bridged mode get dhcp from my router
...
any idea what should i do ?

My first guess would be to configure both virtual machines to have a single virtual network adapter that is configured as "internal network" and set a static IP address on both virtual machines. That will effectively isolate both guests to their own private network for testing.

I suggest to you to set network adapters on both virtual machines in "Bridge Mode".
On Windows Server 2008 you must choose type: Intel PRO/1000 MT Server (82545EM)
In this way, your virtual machine will get an IP address on the same LAN of your host machine, and the three machines can communicate

Related

how to ping the ip of linux running under vmware from window(host) of that same PC

I have window 7, and install Enterprises LINUX in vmware workstation, I have assign static IP I eth0 and eth1, and both are pinging from root as well as oracle user, but I cannot able to ping either of them from window of that same machine. Please help to advise how can i ping those static IP from my window 7 which is a host.
The answer depends on your VMWare networking setup for that virtual machine.
If the virtual machine is connected via a bridge or via a host-only network, you can just ping the VM's address.
If you're using NAT, then it's a problem since the VM has a private IP that's not seen by the host. The opposite ping should however work (if VMWare's NAT is smart enough) - you should be able to ping the host from the VM.

VirtualBox Linux does not return ping and host machine cannot access apache on that guest

I have a Windows7 as host and Debian as guest via VirtualBox. everything worked just fine until I did apt-get update on my guest machine and I think it scrambled some settings (not sure though...).
My current VB network settings are:
Adapter 1: Bridged Adapter
Adapter 2: Host-only adapter
My guest machine works fine, has internet connection and I can access it files via My Computer > Network, yet I cannot ping the guest machine nor access its apache webserver, any ideas?
Glad to hear it dude. :)
1 network adapter usually enough for 'normal' purpose. I use more than 1 network adapter when I want to simulate more complicated computer network plan, like I want to have experiment with proxy, router, dns etc. Just make sure you understand the networking mode that you want to use.
Thanks to #yogipriyo, removed the second adapter and selected only 1 bridged adapter and it works.

How to share folders b/n VirtualBox and Win 7 using NAT adapter and Samba

When I had my Adapter set to Host Only I followed this tutorial and was able to view the folder # \samba\share\ only buy typing \\192.168.55.444 in my windows start up. So, this means I could share this folder without any problem between two machines. But, now that I have switched to NAT adapter, and my ifconfig eth0 shows this as the host address 10.0.2.15 I am unable to access my samba shared folder no matter how I try to access it.
You can have two network adapters configured and use them at the same time. Use the Host-only as well as the NAT adapter. In the Virtualbox settings page just add another network adapter.
In your VirtualBox GUI click on your VM.
- then click Settings (Ctrl+S)
- click Network
- click Advanced
- click Port Forwarding
Configure port forwarding on ports 139 and 445
This port forwarding setup will work only if you don't have samba on your HOST machine, otherwise those port are reserved so virtualbox can not take them over to forward to your guest machine.
Better solution to share files between Host and Guest machine is to install and configure VirtualBox Guest Additions.
What OS do you have installed on yor VM ¿? ... The only way (for me to know) for get in work the share over NAT it's with the VBox Guest Additions...
It is not very difficult to install the guest additions; assuming you have an *buntu OS Family, mint or even debian linux, you can try this tutorials...
DEBIAN
*BUNTU
Then you can test the connection again ...

accessing a website hosted in a virtualbox from host

I have Windows 2008 Server installed in a VirtualBox and I'd like to be able to access the default website (localhost) from the host OS (Windows 7).
In IIS, I have set a hostname for the default website, which I've named 'webserver'.
THen I've added the following line to my hosts file (dns)
127.0.0.1 webserver
Now, if I browse to http://webserver in the guest OS, it works just fine.
But how do I access it from the host OS ?
If your virtual machine is connected to the internet, it's basically using your physical PC as a router. That is, the host OS is assigning some private address (e.g. 192.168.X.X).
You need to put that in your browser to access the virtual server from the host OS. I've never used Windows Server, but under Windows you'd find your IP by typing
ipconfig
at the command prompt.
Go your Virtual Machine's network settings in Virtualbox.
Set the network card not as attached through NAT, but through BRIDGED ADAPTER.
If you have multiple adapters on your host machine, select the main one, the one you're using to obtain an IP from your router.
Now your guest virtual machine is on the same network as your host's.
Hence you can simply access the webserver through the Virtual Machine's computer name. Ex. http://virtserv
(Mind well: not the virtual machine's name in Virtualbox, but the COMPUTER NAME in the guest windows installation).
As far as I know the default IP address for virtual box if using NAT is 10.0.2.15, but still you can verify that using ipconfig.
Nat enables you to access your virtual box guest OS even if your host OS is not connected to a router/access point.
You can map a port from your host OS to the guest OS as follows.
Got to your vbox guest OS's settings
Click on the network Tab
Make sure attached to is set to NAT
Click on advanced then port forwarding
Then you will see a screen where you can map host ports to guest ports
All you have to do is use the IP address of the host operating system. In the host operating system open the command prompt and type ipconfig. Find the IPv4 address: E.G.
IPv4Address........ : 10.1.1.100--If there are multiple then try them all
Go into the Virtual Machine OS and open a browser. Type the url:
http://10.1.1.100/optionalPathInfo
This will open the host IIS site from the VM browser.

Web Access to Virtual Machine

Is their a way to access a web server such as windows server 2003 installed on a virtual box such as vmware from the host machine?
If VMware is set to use bridged networking, then each guest OS effectively has its own IP address, like brien said, you just point your browser to that address.
If you configure your virtual machine to use bridged networking, instead of NAT, it will have its own IP address "beside" the host machine, instead of a local IP address "behind" it. Then you can connect to the virtual machine, using that IP number.
(Disclaimer: I've used VMware workstation for several years, but not their server products.)
Yes, you should just be able to point to the IP address of the VM.
How is your VM networking configured?
I am doing this all over the place, just make sure that the vm has an ip configured.
i believe vmware (workstation?) also has built in a virtual network client (VNC) that you can connect to - enable it by going to the configuration properties of the vm, and in the last tab there is a checkbox for it.
IP address should do it.
I faced the same issue. You have to set your networkconnection to "bridged mode" in your VM. Then you have to find out the IP of your Webserver.
Sometimes Webservers have a redirect to a specific URL. In this case you can edit your host-file in C:/Windows/System32/drivers/etc/hosts and add your IP with the redirected URL like this:
192.168.0.37 some.url-you.need
Then your Host can go to the Webserver. Even participants of your Ethernet can access the Webserver.

Resources