I have a Windows 7 host OS, and a linux guest OS.
The linux guest OS doesn't have the following issue with NAT, but with Host-only mode, I have the following issue..
My Host has a 10/8 address.
Looking in Virtualbox settings..network...Host only and resetting my machine I was getting a 192 address.
I went to virtualbox file..preferencesm and see
Virtualbox host only ethernet adaptor #1
and
virtualbox host only ethernet adaptor #2
both had a 192 address,. I changed it to a 10/8 address and reset the machine (right click..reset).
Now
Virtualbox host only ethernet adaptor #1 10.0.0.26
and
virtualbox host only ethernet adaptor #2 10.0.0.25
And my host machine is 10.0.0.10 (WiFi adaptor)
I do ifconfig in the guest but still see the 192 address.
I can ping 10.0.0.26 and 10.0.0.25
A)My IP isn't getting set to 10.0.0.25 or 10.0.0.26, judging by ifconfig results
B)Now when I ping CompB (the host machine) by NetBIOS Name then it pings the IP of 10.0.0.25 (the virtual adaptor) instead of 10.0.0.10
bridging n windows NetBIOS names clash and IP doesn't update
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: bridging n windows NetBIOS names clash and IP doesn't up
10.x addresses are non-routable, intended for NAT. I suggest that you allow IP addresses to be assigned automatically.
Re: bridging n windows NetBIOS names clash and IP doesn't up
@mpack You have not understood my question. I am familiar with networking. All of this is behind a physical NAT Router. No private address is going to be going out to the Internet.
If I do NAT on the virtual machine then I get a virtual NAT Router. I don't want a virtual NAT Router that's why i'm looking at the bridging option in virtualbox.
If I do NAT on the virtual machine then I get a virtual NAT Router. I don't want a virtual NAT Router that's why i'm looking at the bridging option in virtualbox.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: bridging n windows NetBIOS names clash and IP doesn't up
Host-only is not a good protocol for LAN and the like. It is more like a local loopback than a network protocol and usually has issues if you try to use it any other way. Its main use is to allow the host and guest to communicate when no LAN or router is available. Bridged would be more useful if you have a router in your LAN, but you don't say if you have one or not.
Re: bridging n windows NetBIOS names clash and IP doesn't up
I have a physical NAT Router. (I did imply it when I said my host OS has a 10/8 address. And in my reply to the previous post I mentioned a physical NAT router I have).
The Virtual Machine worked partly, behind Virtual NAT.. But it didn't work in so far as what I wanted, because I want to run an SSH server on a VM. And I want that SSH server to see the source IP of any machine on my LAN that connects to it. So, I don't want the virtual NAT.
The Virtual Machine worked partly, behind Virtual NAT.. But it didn't work in so far as what I wanted, because I want to run an SSH server on a VM. And I want that SSH server to see the source IP of any machine on my LAN that connects to it. So, I don't want the virtual NAT.
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: bridging n windows NetBIOS names clash and IP doesn't up
Why not disable the host only adapter in the host machine (from the host OS) and set your guest machine to use bridged mode? Then both host and guest should get 10. addresses from DHCP on your router and no other IP addresses.
Bill
Re: bridging n windows NetBIOS names clash and IP doesn't up
I have two host only adaptors.. Say I disable them on my Host machine.
Say I choose Bridge.
I don't have/want DHCP set on my physical router.
So i'll try what you say but setting IP and gateway statically (if I can.. if my physical router behaves)
Say I choose Bridge.
I don't have/want DHCP set on my physical router.
So i'll try what you say but setting IP and gateway statically (if I can.. if my physical router behaves)