NAT - DHCP issue

[mihai027]

i always get ip 10.0.2.15 on every machine (xp, 2000 etc) no matter what mac or network card i have set.

there is a workaround to actually use the DHCP ?

[Sasquatch]

With NAT, VB is the DHCP server and it will always give 10.0.2.15 for the first NAT attached NIC. See the manual about this. If you want to use your network DHCP, you have to set up HIF networking, which is also described in the manual. Unless you have specific needs for networking on the Guest, NAT will be enough for internet and some network share browsing. Other machines can't connect to the Guest though.

[mihai027]

With NAT, VB is the DHCP server and it will always give 10.0.2.15 for the first NAT attached NIC. See the manual about this. If you want to use your network DHCP, you have to set up HIF networking, which is also described in the manual. Unless you have specific needs for networking on the Guest, NAT will be enough for internet and some network share browsing. Other machines can't connect to the Guest though.

HIF ? host interface?

maybe i was misunderstood: i want a network with 2-3 vb systems that uses vb dhcp. the problem is that all 2-3 machines have the same ip: 10.0.2.15 give by vb dhcp. it is a bug or what ?

[TerryE]

Yes -- HIF is a standard acronym in the User Guide. The whole point about NAT is that the internal network that the guest sees is isolated from the host side. All machines will have the same IP just the same as most home networks run on 192.168.0.0/255 or 192.168.0.1/255. If you want them to have different IP addresses use a bridged network as Sasquatch says.

[mikeva50]

I'll try to simplify how to do this for you. If you're trying to get your Virtual Machine to pull an IP address supplied by a router to have it visible by all of your other real machines you have to go into the Virtual Machines network settings within virtual box and set the Vitrual Machines network adapter to be attached to the host interface. Then on the same page add a host interface "virtual network adaptor" to the host machine. Make sure you select the new host interface and select OK.

Now on the host machine you need to go into Network Connections and highlight both the virtual network adaptor and your real network adaptor, right click on them and select bridge connections. This will now link your host card "Example: 192.168.1.103" to your virtual host card which will then in turn give an IP address to the Vittual Machines virtual network adaptor "Example: 192.168.1.102"

Hope it helps...

[TerryE]

Thanks Mike, but you don't need to simplify this for us. All you are doing is saying that you are configuring HIF rather than NAT and this is just a RTFM issue.

[mikeva50]

No need to take offence.... were you the one who started this thread? Did you ask the original question in the thread? I've looked at a bunch of your posts and no I definitely don’t need to simplify anything for you. In fact I'm certain that when I have a question you'll have to simplify it for me so don’t get upset with this response. All I'm trying to do is give mihai027 a straight forward answer instead of giving him an answer containing a crap-load of acronyms that he may not understand which will completely waste my time. I know a lot of people that shoot a bunch of technical talk out of their mouth when trying to explain something to a not so technical user in an attempt to prove themselves to others. That is fine because we all like to get into our technical talk with likeminded individuals but when you’re trying to help someone who doesn’t have much knowledge in this area “Hence the reason he’s asking an easy question.” it doesn’t help him at all if you start throwing out acronyms left and right that he won’t know.

Like I said… I wasn’t aiming my post at you or anyone else… Just mihai027

[Sasquatch]

Even if you simplified it, you didn't help him with the question. I already stated that it's explained in the manual, so he should look there anyway.

His real issue is an Internal Network (either separated from the Host or with a Bridge) and setting IP addresses. That is currently not possible that VB distributes IP addresses to the Guests that way. Either his router must provide them with an IP when using a bridge, or he has to set them manually.

[mikeva50]

Did you read my post? I said that "If you're trying to get your Virtual Machine to pull an IP address supplied by a router"... He wants all VM's to have a seperate IP supplied by the router and not the 10.0.2.15 address that NAT gives him. What I posted is the exact answer that he's most likley looking for to setup a bridge and get the VM to pull a router IP. If by chance he read the manual as you told him to then perhaps he solved his own issue.... Without your help... Im sorry but telling somone to "Read the manual" and "Figure it out yourself" isnt helping ither.

[Sasquatch]

You haven't been very helpful with those 4 posts either. Would you pay a bit more respect for those who come here every day and moderate this forum trying to help as many people as possible? Thanks.

[mikeva50]

You're right and I do apologise... I do respect the fact that you have over 2700 posts. On most posts I've looked at you seem to have always posted very helpful comments and I'm sure a lot of people are very thankful for that. I'm also sure the above question was asked 1000 times and eventually it just simply gets annoying answering the same question over and over again. I'll just have to try and refrain from getting defensive over slightly unconstructive criticism. Thanks

[mihai027]

i try one more time ... maybe my english is not so good.

""If you're trying to get your Virtual Machine to pull an IP address supplied by a router"" - NO I DO NOT !

so i have a physical machines with virtual box 2.0.2. In this virtual box i installed 1. windows 2000 and 2. windows xp.

i want to put them in the same network using virtual box dhcp and NAT.

the problem is that virtual box dhcp give me the same ip for both virtual systems:

Code: Select all

1. :
  Physical Address. . . . . . . . . : 12-22-27-3D-91-DC
  Dhcp Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  IP Address. . . . . . . . . . . . : 10.0.2.15
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 10.0.2.2
  DHCP Server . . . . . . . . . . . : 10.0.2.2
  DNS Servers . . . . . . . . . . . : 10.0.2.3

Code: Select all

2.:
 Physical Address. . . . . . . . . : 08-00-27-B8-8D-D1
 Dhcp Enabled. . . . . . . . . . . : Yes
 Autoconfiguration Enabled . . . . : Yes
 IP Address. . . . . . . . . . . . : 10.0.2.15
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . : 10.0.2.2
 DHCP Server . . . . . . . . . . . : 10.0.2.2
 DNS Servers . . . . . . . . . . . : 10.0.2.3

in normal (non virtual) NAT with dhcp ip network must be:

1.: 10.0.2.15 (192.168.0.2 - or whatever)
2.: 10.0.2.16 (192.168.0.3 - or whaterer)

how can i convince dhcp to have different ip's on different machines ?

p.s. vmware do that ....

[TerryE]

I wasn’t aiming my post at you or anyone else… Just mihai027

Mike, you're right: I do owe you an apology. When you are reading dozens of these and firing off answers, then your eye can sometimes miss something. In this case mikeva50 vs mihai027. These might seem v. different but not when vertically aligned a page-up away. I thought your post was from the original poster and I couldn't understand why you were explaining to us some basic stuff in the manual. My bad and my apologies.

mihai027, I tidied your post a little. I think that you misunderstand a fundamental aspect of NAT. Read through the Wiki NAT Article. VMware combines the VBox NAT and internal networking functions, so you cannot assume because VMware does X that you can do the same in VBox. VBox NAT isolates the VMs in a VM host from each other. If you want to interwork between two VMs within the same host, then you need to use HIF (section 6.6 of the User Guide) or Internal Networking (section 6.10 of the User Guide).

[mihai027]

ok, thanks