Change IP Address of host adapter / vmnet1

[timofcourse]

I have a guest Windows Server that need to run on Fusion 3.0 with a static address of 10.10.2.2, subnet 255.255.255.0 and have the ability to address it via that address from the host.

Ive been mucking around with the /Library/Application Support/VMWare Fusion/vmnet1/dhcpd.conf and have successfully gotten Fusion to statically assign this IP using the following settings:

subnet 10.10.2.0 netmask 255.255.254.0 {

range 10.10.2.100 10.10.2.254;

option broadcast-address 10.10.3.255;

option domain-name-servers 10.10.2.1;

option domain-name localdomain;

default-lease-time 1800; # default is 30 minutes

max-lease-time 7200; # default is 2 hours

}

host vmnet1 {

hardware ethernet 00:50:56:C0:00:01;

fixed-address 10.10.2.1;

option domain-name-servers 0.0.0.0;

option domain-name "";

}

host WindowsVM {

hardware ethernet 00:0c:29:3a:fc:eb;

fixed-address 10.10.2.2;

}

The only problem is that I cant access the guest from the host once I change those settings. I think it has to do with the actual vmnet1 interface still being assigned to an IP of 192.168.85.1, whereas it should be 10.10.2.1 in order to connect to it (I think). Only problem is, I cant figure out how to change the IP address of that interface (assuming that is the problem).

Any suggestions??

Thanks a bunch!

[WoodyZ]

Just curious but didn't you see that what you're trying to modify is between...

###### VMNET DHCP Configuration. Start of "DO NOT MODIFY SECTION" #####

# Modification Instructions: This section of the configuration file contains

# information generated by the configuration program. Do not modify this

# section.

And...

####### VMNET DHCP Configuration. End of "DO NOT MODIFY SECTION" #######

So what do you not understand about the "DO NOT MODIFY SECTION"?

Anyway aside from the fact that you're not supposed to directly modify the section you are, you also have a couple of errors.

option broadcast-address 10.10.3.255;

Should be...

option broadcast-address 10.10.2.255;

And...

host WindowsVM {

hardware ethernet 00:0c:29:3a:fc:eb;

fixed-address 10.10.2.2;

}

Should not be there at all as that has nothing to do with the Guest in this case use scenerio.

If you want to modify the VMware Virtual Network under Fusion 3 and specifically vmnet1 I'd suggest you use the scripts in tokamak300-20091029.zip from .

Refrences:

Note that the VMware Virtual Network has changed between versions 2 and 3 and much of what has been written prior to version 3 is not directly applicable to version 3 and Dave has not finished the scripts for version 3 yet but at least the basic functionality seem to be working in them.

Anyway using the scripts from tokamak300-20091029.zip I was able to easily change vmnet1 from the assigned default to the 10.10.2.0 Subnet and I manually configured the Guest to use 10.10.2.2 while the Host's vmnet1 Virtual Network Adapter is using 10.10.2.1. The Scope of the DHCP Server IP Address Pool however is using 10.10.2.128 - 10.10.2.254 not 10.10.2.100 - 10.10.2.254 as you had tried to modify it to and if that is okay then you should be set however if you need the Base Address of the Scope of the DHCP Server IP Address Pool to be 10.10.2.100 then I'm not sure how you'll be able to modify that as I'm not sure if the scripts will allow that to be adjusted and if you try to do it manually as you've already tried it will just be reset unless you can find out how to generate and modify the "answer VNET_1_DHCP_CFG_HASH" value in the networking file as I believe that's what's being checked and if it doesn't match it replaces the previous settings.

[timofcourse]

I found numerous websites that descibed editing that file as the only way to change the IP range Fusion DHCP gives out, since I couldnt find any documentation of official tools to configure networking as there are in Workstation. I made a backup, tested it out and it did what I expected it would do. No harm, no foul.

I tried with both broadcast-address IP's and neither fixed my issue, but thanks for the heads up on which one should be used.

Adding the "host WindowsVM {" section statically assigns the server without me having to statically assign it within the guest itself. Again, found this through several sites and it does what I want it to do.

I found the 2.0 version of Tokamak's tools here on VMWare's website, but found many other sites mentioning it wasnt compatible with 3.0 and didnt want to hose my network connections testing to see if it would.

Anyway, I managed to find nearly ever link you posted... except for that whitepaper. While its a bit dated, its exactly what I needed to figured out what files control the adapter settings. As soon as I updated the locations and networking files so that the vmnet1 adapter used 10.10.2.* settings, everything worked like a charm!

On a side-note... how do you create code-blocks in these forums like you did above?

Thanks a bunch!

[WoodyZ]

I found numerous websites that descibed editing that file as the only way to change the IP range Fusion DHCP gives out, since I couldnt find any documentation of official tools to configure networking as there are in Workstation. I made a backup, tested it out and it did what I expected it would do. No harm, no foul.

Editing that file in Fusion 3 is different then prior versions and from your OP you didn't mention editing anything but the vmnet1 dhcpd.conf file and if you edit it in of an by itself it will be replaced with the original setting when the Virtual Network is restarted and based on what you said in the OP is was logical to assume what I did and make the statements I did.

I tried with both broadcast-address IP's and neither fixed my issue, but thanks for the heads up on which one should be used.

Adding the "host WindowsVM {" section statically assigns the server without me having to statically assign it within the guest itself. Again, found this through several sites and it does what I want it to do.

I found the 2.0 version of Tokamak's tools here on VMWare's website, but found many other sites mentioning it wasnt compatible with 3.0 and didnt want to hose my network connections testing to see if it would.

That is why I posted a direct link to the one for Fusion 3 however it's not complete yet.

Anyway, I managed to find nearly ever link you posted... except for that whitepaper. While its a bit dated, its exactly what I needed to figured out what files control the adapter settings. As soon as I updated the locations and networking files so that the vmnet1 adapter used 10.10.2.* settings, everything worked like a charm!

As long as you finally got what you wanted that's good but again from your OP you were not getting there (or why would you even post).. :smileyhappy:

On a side-note... how do you create code-blocks in these forums like you did above?

I use the Plain Text editor not the Rich Text editor and have a look at: Plain Text Markup Help

Thanks a bunch!

Your welcome. :smileyhappy: