https://communities.vmware.com/t5/VMware-Workstation-Pro/Briged-VM-network-not-working-DHCP/m-p/2990153#M183037 <P>you don't describe your environment very well. If you have a server bridged to the same subnet as your router, you will have 2 DHCP servers, not good.<BR /><BR />What is the subnet of your router?<BR />What is the result of ipconfig/all on the host, the server VM and the client VM(s). Or ip addr if a linux client?<BR />What are the settings in your Virtual Network Editor?<BR /><BR />If you really want to use the DHCP server in your VM server, you will&nbsp; have to isolate it from the router, maybe with NAT. I have Windows and Linux servers as Domain controllers and I give all machines static IP's. That is the way we roll in our Domains, as well. Dynamic IP addresses come back to bite you very often.</P> Sun, 08 Oct 2023 18:04:21 GMT louyo 2023-10-08T18:04:21Z https://communities.vmware.com/t5/VMware-Workstation-Pro/Briged-VM-network-not-working-DHCP/m-p/2990085#M183028 <P>Hi,<BR /><BR />1/ I have a Windows server with DHCP service activated, bridge mode : works fine, internet connection. I gave the server a fixed IP address.</P><P>2/ But my Client VM does not get IP from the DHCP, I get an APIPA address</P><P>I deleted VMnet0 to recreate a bridge card, didn't help.<BR />If I give the client a static IP adress it works fine. If I try to get my IP from my physical router: it also works.</P><P>Thanks for yourself</P><P>1 -&nbsp;<BR />Ethernet Adapter Ethernet0:<BR />DNS Suffix for this Connection:<BR />Description: Intel(R) Gigabit Network Connection<BR />Physical Address: 00-0C-29-......<BR />DHCP Enabled: No<BR />No Automatic Configuration: Yes<BR />IPv4 Address: 192.168.0.100 (Preferred) (IP I assigned)<BR />Subnet Mask: 255.255.255.0<BR />Default Gateway: 192.168.0.1<BR />DNS Servers: 8.8.4.4, 1.1.1.1</P><P>2/<BR />Ethernet Adapter Ethernet0:<BR />DNS Suffix for this Connection:<BR />Description: Intel(R) Gigabit Network Connection<BR />Physical Address: 00-0C-29-.....<BR />Autoconfiguration IPv4 Address: 169.254.30.3 (Preferred)<BR />Subnet Mask: 255.255.0.0<BR />Default Gateway:<BR />DHCPv6 IAID: 201329...<BR />DHCPv6 Client DUID: 00-01-00-01-2C-B1-F3-xx..<BR />DNS Servers: fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1, fec0:0:0:ffff::3%1<BR />NetBIOS over Tcpip: Enabled</P> Sat, 07 Oct 2023 12:31:13 GMT https://communities.vmware.com/t5/VMware-Workstation-Pro/Briged-VM-network-not-working-DHCP/m-p/2990085#M183028 frenchienewbie 2023-10-07T12:31:13Z https://communities.vmware.com/t5/VMware-Workstation-Pro/Briged-VM-network-not-working-DHCP/m-p/2990153#M183037 <P>you don't describe your environment very well. If you have a server bridged to the same subnet as your router, you will have 2 DHCP servers, not good.<BR /><BR />What is the subnet of your router?<BR />What is the result of ipconfig/all on the host, the server VM and the client VM(s). Or ip addr if a linux client?<BR />What are the settings in your Virtual Network Editor?<BR /><BR />If you really want to use the DHCP server in your VM server, you will&nbsp; have to isolate it from the router, maybe with NAT. I have Windows and Linux servers as Domain controllers and I give all machines static IP's. That is the way we roll in our Domains, as well. Dynamic IP addresses come back to bite you very often.</P> Sun, 08 Oct 2023 18:04:21 GMT https://communities.vmware.com/t5/VMware-Workstation-Pro/Briged-VM-network-not-working-DHCP/m-p/2990153#M183037 louyo 2023-10-08T18:04:21Z