NetworkConsultant01
asked on
How do I bind a VMware guest to a Windows 2008 Server physical NIC
I have VMware Server 1.0.6 installed on Windows Server 2008, I have a Linux guest installed and functional.
The server is a Dell PowerEdge 2650 with 2 onboard Broadcom gigabit NICs. One has a static IP address for our LAN the other for our DMZ. I need to bind the LInux guest to the DMZ NIC so then assign a local IP address that virual server.
Can anyone walk me through how to do this?
The server is a Dell PowerEdge 2650 with 2 onboard Broadcom gigabit NICs. One has a static IP address for our LAN the other for our DMZ. I need to bind the LInux guest to the DMZ NIC so then assign a local IP address that virual server.
Can anyone walk me through how to do this?
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Again, Bear with me because I haven't tried this on Server 2008, but if you go to the properties of NIC #2 you should see VMWare Bridge Protocol (Or something of the sort). Make sure that is enabled, and then see if it shows up in the Host Virtual Network Mapping menu.
ASKER
It is installed and enabled, it looks to be configured the same as the primary NIC.
Is it available in any of the other VMNets? For example 1 or 3?
ASKER
Negative.
This is a little bit of a long shot, but try closing out of vmware server, and restarting the vmware registration service and then going back in and seeing if its available in vmnet2
ASKER
That did it, so now I assign the 2nd NIC to a different VMnet but the OK button is grayed out. Do I also need to disable automatic briding or assign an IP to it from there?
I think if it is greyed out that must mean it is already set. If you close out of the window and go back in, is the 2nd NIC card anywhere?
And you'll set the IP from within the linux image. Edit /etc/network/interfaces with the following syntax:
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.100
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
And you'll set the IP from within the linux image. Edit /etc/network/interfaces with the following syntax:
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.100
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
If the 2nd NIC card isn't in there, try stopping your images and then seeing if you can click the OK button
ASKER
Do I assign an IP address to the physical NIC in Windows or the bound one in VMware?
You can actually turn off TCP/IP in windows for that NIC or else it will cause a hostname conflict. The VMWare Bridge Protocol brings the TCP/IP over to the guest client. Then once you are in the guest, you can set the manual IP in there.
ASKER
I have tried stopping images, restarting VMware, restarted the server, and last night upgraded to 2.0 RC1 none of which have resolved my issue. 2.0 seems to have made things more confusing so I will probably go back to 1.0.6 until I get ESXi for free.
However, until then I still can't bind the 2nd NIC to anywhere. In fact when I change anythin in virtual network settings I can't click OK. For example if I uncheck automatically bind or mess with NAT/DHCP I can't click OK
However, until then I still can't bind the 2nd NIC to anywhere. In fact when I change anythin in virtual network settings I can't click OK. For example if I uncheck automatically bind or mess with NAT/DHCP I can't click OK
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Posted question http://communities.vmware.com/thread/158031
ASKER
From that post "Just like on Vista hosts, for Win2008 you must run the Virtual Network Editor as Administrator. "
...
...
Ohhh, Sorry I couldn't help you with that, Like I said I haven't used Server 2008. So is the problem resolved?
ASKER
Well yes/no, I got it assigned to VMnet2 but since I upgraded to 2.0 I don't have custom anymore. I have NAT, bridged, and HostOnly.
ASKER
OK I think I have it configured correctly finally.
- I assigned the 2nd physical NIC to VMnet2 and assigned that to the guest
Below is my /etc/sysconfig/network-scr
DEVICE=eth0
BOOTPOTO=
IPADDR=10.0.0.200
NETMASK 255.0.0.0
USERCTL=yes
IPV6INIT=no
PEERDNS=yes
ONBOOT=yes
My /etc/resolve.conf has 4.2.2.1 and 4.2.2.2
I have restarted networking and brought the NIC up and down, I can't ping google, it says unknown host.
I have stuck my Windows laptop in the DMZ and assigned myself a static IP in the same manner and I can get out. So either I am not configuring CentOS correctly or the VMnet2 isn't working.
- I assigned the 2nd physical NIC to VMnet2 and assigned that to the guest
Below is my /etc/sysconfig/network-scr
DEVICE=eth0
BOOTPOTO=
IPADDR=10.0.0.200
NETMASK 255.0.0.0
USERCTL=yes
IPV6INIT=no
PEERDNS=yes
ONBOOT=yes
My /etc/resolve.conf has 4.2.2.1 and 4.2.2.2
I have restarted networking and brought the NIC up and down, I can't ping google, it says unknown host.
I have stuck my Windows laptop in the DMZ and assigned myself a static IP in the same manner and I can get out. So either I am not configuring CentOS correctly or the VMnet2 isn't working.
Hmm try keeping it on vmnet2 and not setting a static ip and see if you can get through the internet, and then we can see if it was your syntax while setting a static ip
ASKER
I accomplished this setup in VMware ESXi, I am going to give you the points as I assume it would have worked the way you described.
VMware
VMware, a software company founded in 1998, was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies. VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture. Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.
39K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER