Well I guess I got my terms mixed up a bit and you are right I am describing "Host Interface networking".
My intent was to describe a network setup that I knew worked. I struggled with the NAT network option and never got it to work. However since I knew I would be running a couple of server OSs as guest vm's I needed the two communication of "Host Interface networking". - is your actual (i.e. physical) network also using 192.168.x.x ip addresses Yes my actual physical NIC is using 192.168.0.1. - suggestion for a good dhcp server ? 1. Because my host OS is XP I use the internet connection sharing option. This option causes XP to act as a dhcp server, Go to this link for more info on ICS: http://www.practicallynetworked.com/sharing/xp_ics/ 2. If you are using a router it should have a built in SHCP server. 3. DHCP Server Software for XP: http://tftpd32.jounin.net/ http://www.billiter.com/ http://www.magikinfo.com/dhcp.htm Thanks, Fred Cunningham -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cédric Paternotte Sent: Sunday, March 11, 2007 8:27 AM To: VirtualBox end user list Subject: Re: [vbox-users] Internal networking on windows Hi Fred, Thanks for your reply. Although I'm not exactly sure we're speaking of the same feature. In your explanation you're bridging your host physical nic with the vm's virtual nic. Is that right ? Isn't that supposed to be the "Host Interface networking" mode ? The mode in which the host physical nic is playing an actual role ? Because it doesn't seem to be the case of the "Internal network" mode (described in §5.3.4). >From what I understood from the documention (provided I got it right), there's no physical nic involved in the process. No virtual nic are needed for the vms either. Actually one could setup an "internal network" on a host with no network card at all, since the internal network is emulated by VirtualBox. The only thing the vms should see being the other vms running on the same host (the host itself and the outside world being invisible to them). I'm going to try your suggestion anyway as it may be the only working alternative. Just a few questions though : - is your actual (i.e. physical) network also using 192.168.x.x ip adresses ? - I guess the bridge must be made of the host nic and all concurrent vm's nics - suggestion for a good dhcp server ? Thanks, Cedric On 3/10/07, Fred Cunningham <[EMAIL PROTECTED]> wrote: > > > > > I have "Internal networking" functioning with Windows XP SP2 using a Network > Bridge with a static IP of 192.168.0.1. > > The only thing that trouble with was getting my host NIC to be in the > Promiscuous mode because it did not automatically do so. > > > > This is for Windows, and it worked for me: > http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q302348&ID=KB;EN-US; Q302348 > > I ran the netsh command after setting up the bridge. The steps from that > article are copied below: > > 1. At a command prompt, type netsh bridge show adapter. > > 2. Locate the identification number of the NIC that is not responding. > > 3. If the NIC is not in Compatibility mode, you can change it manually if > you type the following command, where 1 is the number of the NIC that is > displayed in the first step: > > netsh bridge set adapter 1 forcecompatmode=enable > > 4. Run the netsh bridge show adapter command again to verify that the > ForceCompatabilityMode? field for the NIC is displayed as Enabled. > > > > I have the Network card within the VM set to "Obtain an IP address > automatically", of course this means that the XP host system has a DHCP > server to provide IP address to the installed VM's. > > > > I have Windows 98, Windows 2000 PRO, Windows Server 2003 and SUSE 10.2 > installed as VM's and I am able to communicate with them all over the > internal network. > > > > > > I hope this helps. > > > > > > Fred Cunningham > > > > > > > > ________________________________ > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Cédric Paternotte > Sent: Saturday, March 10, 2007 3:41 AM > To: [email protected] > Subject: [vbox-users] Internal networking on windows > > > > > -- repost from forum -- > > Hi, > > I'm trying to get "Internal networking" to work between two XP virtual > machines on a same host but had no luck so far. > I'm sure I'm missing something stupid but I just don't see what. Some > insights would be great > > My configuration is > > Host system : > - Windows XP, wireless card, static ip 10.0.0.10, mask 255.255.255.0, > gateway 10.0.0.254 > > VM1 ("XP1") : > - Windows XP, static ip 192.168.0.1, mask 255.255.255.0, no gateway > > VM2 ("XP2") : > - Windows XP, static ip 192.168.0.2, mask 255.255.255.0, no gateway > > > Following the docs, this is how I tried to set up the internal network > (named "faraday") : > > > VBoxManage modifyvm XP1 -nic1 intnet > > > VBoxManage modifyvm XP1 -intnet1 faraday > > > VBoxManage modifyvm XP2 -nic1 intnet > > > VBoxManage modifyvm XP2 -intnet1 faraday > > So the two vms should now be able to ping themselves, right ? At least > that's what I understood. > > The doc makes it clear (at least to me) that VirtualBox takes care of the > wiring between the two vms and that no changes need > to be appliedto the host network configuration (no extra virtual nic > needed). > Using the same network id ("faraday") should be enough to make it happen. > > Obviously it doesn't, the vms don't see each other (no ping response). > > What am I missing ?? > > I also tried to use ips from the same subnet as the host (10.0.0.x) for the > vms but didn't get better results. > > Thanks, > > Cedric > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
