Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Help with virtual network

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 2 posts
I am trying to create a network on vmware workstation 10.
My network includes  1 domain server, 1 file server and two client machine. 
I have installed the domain server with actvie directory, DNS and DHCP roles added to it. It is picking up internet connection as network card configuration is Nat (dhcp enabled). 
IP address for Domain server is
Subnet :
default gateway :
DHCP scope is -
Virtual Network configration for cleint machines is VMnet1 where DHCP service is unticked as I want to use my domain server as DHCP server and subnet address is Host virtual adapter name is VMware Network Adapter VMnet1
When I boot up the client machine (windows 7), it is not picking up virtual network settings. I understand it will pick up the internet connection when attached to the domain but it is not even picking up the ip address from the range. Current Ip address for client machine is with subnet mask
Network adapter is Intel ® Pro/1000 MT Network connection which I assume should be VMware Network Adapter VMnet1 as I have chosen virtual network VMnet1 for client network card 
Can someone please tell me what I am doing wrong. I want machine to pick up right Ip address sothat I can join it to the domain. I have checked the firewall on server and client machine and it is off
Thanks for your help in advance

  • 0





  • Banned
  • PipPip
  • 38 posts

Select the network type you want to use — Bridged

Configuring Bridged Networking Options on a Windows Host


You can view and change the settings for bridged networking on your host. These changes affect all virtual machines using bridged networking on the host.

You can decide which network adapters on your host to use for bridged networking. You can map specific network adapters to specific virtual networks (VMnets).

  1. Open a VMware Workstation window.
  2.  Choose Edit > Virtual Network Settings.

    The Virtual Network Editor appears, with the Summary tab active.



  3.  By default, the VMnet0 virtual network is set up in bridged mode and bridges to one of the active Ethernet adapters on the host computer.

    The choice of which adapter it uses is arbitrary. You can restrict the range of choices using options on the Automatic Bridging tab.

    (Also shown are VMnet1, the default virtual network for host-only networking, and VMnet8, the default virtual network for NAT, if they are enabled in VMware Workstation.)



  4.  To exclude one or more physical Ethernet adapters from the list to which VMnet0 may be bridged, click the Automatic Bridging tab. To exclude an Ethernet adapter, click Add to add it to the list of excluded devices.



    In the Choose Network Adapters dialog box, select the listing for the adapter you want to exclude, then click OK.



    To remove an adapter from the list of excluded adapters, select its name in the list, then click Remove.



  5.  To designate a physical Ethernet adapter to be used for bridged networking on virtual switches named VMnet2-VMnet7, click the Host Virtual Network Mapping tab. Choose an adapter from the drop-down list beside the name of the virtual switch you want to use.

    Caution: Be careful when you change the bridged adapter mappings. If you re- assign a physical Ethernet adapter to a different virtual network, any virtual machine using the original network loses its network connectivity via that network. You must then change the setting for each affected virtual machine's network adapter individually. This can be especially troublesome if your host has only one physical Ethernet adapter and you reassign it to a VMnet other than VMnet0; even though the VMnet still appears to be bridged to an automatically chosen adapter, the only adapter it can use has been assigned to another VMnet.



  6.  To make changes to the subnet or the DHCP settings for a virtual network, click the button on the right that corresponds to the virtual network you want to configure, then choose Subnet or DHCP.



  7.  In the Subnet dialog box, you can change the subnet's IP address and the subnet mask.

    The address should specify a valid network address that is suitable for use with the subnet mask.

    The default subnet mask is (a class-C network). Typically, this means you should modify only the third number in the IP address — for example, x in 192.168.x.0 or 172.16.x.0. In general, you should not change the subnet mask. Certain virtual network services may not work as well with a customized subnet mask.

    When you modify the network address or subnet mask, VMware Workstation automatically updates the IP address settings for other components — such as DHCP, NAT and host virtual adapter — on that virtual network to reflect the new settings. The specific settings that are automatically updated include DHCP lease range, DHCP server address, NAT gateway address and host virtual adapter IP address. However, if you have changed any of these settings from its default value — even if you have later changed the setting back to the default — VMware Workstation does not update that setting automatically. It presumes that custom settings are not to be modified.



  8.  In the DHCP settings dialog box, you can change the range of IP addresses provided by the DHCP server on a particular virtual network. You can also set the duration of leases provided to clients on the virtual network.
  9.  When you have made all the changes you want to make on all panels of the VMware Network Configuration dialog box, click OK.

Edited by techmantrey1, 23 November 2014 - 05:36 PM.

  • 0



    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts

Thank you for your help. I chose NAT for clients as well and added router address in server options and everything was working fine. Thanks for help

  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP