Discussion

Here’s a modification that allows you to turn DHCP on or off per vmnet? interface for host-only networks:VMWARE_HOSTONLY_DHCP=yesif [ -f ‘/etc/vmware/vmnet'”$vHubNr”‘/services’ ]; then source ‘/etc/vmware/vmnet'”$vHubNr”‘/services’fivmware_bg_exec ‘Host-only networking on /dev/vmnet'”$vHubNr” \ vmware_start_hostonly “$vHubNr” ‘vmnet'”$vHubNr” \ “$hostaddr” “$netmask” “$VMWARE_HOSTONLY_DHCP”Change the line mentioned in the article to the above lines and then you can create a file or files at /etc/vmware/vmnet?/services with the line VMWARE_HOSTONLY_DHCP=no to turn off DHCP for that vmnet? interface

I have find a solution to disable dhcp server in vmware server 1.0.6 :launch script : /usr/bin/vmware-config.plIn this question :Do you want to be able to use NAT networking in your virtual machines? (yes/no) [yes] no <– ANSWER, VERY IMPORTANT Thanks

I have find a solution to disable dhcp server in vmware server 1.0.6 :launch script : /usr/bin/vmware-config.plIn this question :Do you want to be able to use NAT networking in your virtual machines? (yes/no) [yes] no <– ANSWER, VERY IMPORTANT Thanks

I have had similar problems with 1.0.6if you don’t turn off your vmware server all that often, you can kill the process from consolefirst you will need to find the process, you can do that in most Linux GUI’s with a process monitor, then look for vmnet-dhcpd. Then kill the process called vmnet-dhcpd.With no GUI, and using the console, or through ssh etc. type in ‘ps aux | grep vmnet-dhcpd’, the process id will then be shown, then type ‘kill ####’ and the dhcp daemon will be killed. The process id is the first number after the name of the user who started up the daemon, in my case, root.eg.xpclientx2:/mnt/VMs # ps aux | grep vmnet-dhcpdroot 12208 0.0 0.0 1828 308 ? Ss 07:54 0:00 /usr/bin/vmnet-dhcpd -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/run/vmnet-dhcpd-vmnet1.pid vmnet1root 12212 0.0 0.0 3064 712 pts/0 R+ 07:55 0:00 grep vmnet-dhcpdxpclientx2:/mnt/VMs # kill 12208It’s only a band-aid approach, but the good thing is, it won’t matter what version it is, or if they modify the scripts again in future, as long as the dhcp daemon is seperate.

One thing I did to remove DHCP from a single vmnet was to edit /etc/vmnet<#>/dhcp/dhcp.conf (in my network it was vi /etc/vmnet8/dhcp/dhcp.conf) and remark out all of the lines. Then I ran # /usr/lib/vmware/net-services.sh restart and it appears to disable the DHCP since it doesn't know what network to serve IPs for.

In vmware-server 201, they finally gave us a choice!I think if we change the statement like "answer VNET_1_DHCP" in /etc/vmware/locations from "yes" to "no", it seems to no longer start the daemon. Code near /usr/lib/vmware/net-services.sh:700, where I used to disable the start by hand, seems to support this new config.Sure makes THAT easy for me.