We help IT Professionals succeed at work.

Setup vmware server on network

Premiernc
Premiernc asked
on
MS server 2003 host
VMWare server 2
linux based ABACA product virtual machine
Need to be able to see the ABACA vmachine on the local network or whatever it takes to be able to work with it. Newbie to Virtual stuff and the adaptors and bridging throw me for a loop. This is a live situation and need some help fast. Thanks a million
Comment
Watch Question

Author

Commented:
Current netwok setup


Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.230.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.64.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.6.150
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.6.1

I can ping these addresses. It seems as if the linux machine is not listening for an IP address etc. It says it is at 169.254.1.5:8000, this is for the web console for the Abaca product. Is this an issue with the machine and not the VMware setup?

Commented:
In the properties for the virtual machine, set the network interface to use bridging, this will allow it to "piggy back" on the physical machine network card.  The virtual machine can then communicate on the same LAN as the physical machine as if it had it's own physical NIC.

Author

Commented:
The virtual machine should have an address on the 192.168.230.0 subnet, is that correct? I can ping the 192.168.230.1 address from the host machine command prompt.

Commented:
Yes, that is correct.

Author

Commented:
Maybe I am confusing the guest operating system and its settings with the virtual machine settings. Shouldn't the linux guest operating system have an IP on the virtual machine network?

Commented:
Only if you do not want the guest virtual machine to talk to anything outside of the virtual machine network.
If you want to be connected to the physical LAN, you need to bridge the interface and use an IP from the physical LAN network.

Author

Commented:
So, I am correct in understanding the this could be the linux OS not using DHCP corectly and it is assigning itself the 169.254.x.x address. So it may not be my VMWare setup, but the linux guest OS.

Commented:
Yes, if you are using DHCP and get a 169.254.x.x address, then the guest virtual machine is not seeing the DHCP server.

Author

Commented:
Which settings do I actually change so the virtual adaptors are on the same main subnet as the host?

Commented:
If the guest OS is Linux, you may need to restart the machine to get it working once you change the NIC to Bridged.
do an /sbin/ifconfig -a in the Linux shell prompt and see if an extra network card shows up besides the one with the 169 IP.

Commented:
Subnet and physical network are two different things.  But setting the virtual interface to be bridged with the physical machine NIC should set everything up correctly.

Author

Commented:
One small problem, We are unable access the linux OS because the username and password are incorrect. Tech support for the ABACA product say we need to access it through the web interface, unfortunately that is unacessible at 169.254.x.x. I tried to attach a screen shot of the adaptors.
1.bmp

Commented:
So VMNet0 is your bridged network.  Set your Linux box to use this and then reboot and see if it grabs an IP.

Author

Commented:
I added the other screen shot. It seems everything is setup correctly on my end. What should I see with and IPCONFIG as far as the linux IP goes, should I see the IP number?
2.bmp

Commented:
Once it gets an IP from DHCP you should see that yes.  
ipconfig will show currently active interfaces, ipconfig /a will show any that are currently disabled as well.

Author

Commented:
Basically, this is a virtual spam detection setup. Will I be able to port forward 25 to this address even though its not on the same subnet(192.168.6.0) These are my concerns with not quite understanding how VMWare works. if it can sit in the middle between my firewall and the mail server without any problems then I am ok with that. At this point, it looks like the linux is not grabbing an IP from the VMware. So I can throw this back in their laps. Thanks for all your help.

Commented:
You can assign multiple interfaces to the virtual machine, and put one in each required network.
The virtual guests only have access to the physical networks that the host machine is connected to.
So if you can be in both 192.168.6.0 and 192.168.200.0 with your host PC, you can have two interfaces in your guest VM that correspond to that.
Basically, the VM cannot do anything the physical PC cannot do.

Author

Commented:
The tech support says that the VMware setup looks right but also that the Linux is setup to grab DHCP. Any reason you can think of that the linux would not be getting an address from the VMware?

Commented:
It does get the address from VMware, it gets it from the DHCP server on your local network.  The same place your PC would get it.
Do you have a DHCP server?

Author

Commented:
Another note. In the Status box of the VMware virtual machine where it has powered on state etc, it says under IP Addresses, not available. Is tha indicative of anything in particular?

Commented:
That should read "does not" get the address from VMware.

Commented:
Not availble means it could not contact a DHCP server.

Author

Commented:
It appears to have a static ip of 169.254.x.x. Is there a setting in VMware that I can check to make sure a DHCP server is available?
Commented:
No, it has nothing to do with VMware.  The DHCP server is on your network.
Let me try my best to explain VMware Virtual Networking for you in addition to mattvmotas comments.
By default, when you install VMware Server, 10 Virtual Switches are installed (VMnet 0 through VMnet9). By default, VMnet0 is used for Bridged Networking (A Virtual Machine using this Networking Setup can use the physical Host's Subnet and fetches an IP Address from the DHCP Server present in the physical environment)
Vmnet1 is for Host-only Networking when you do not want the Virtual Machine to be seen by other physical Machines in your Network.
VMnet8 is for NAT Networking. This would be used when you want the Virtual Machine to use the physical Host's IP Address for Network Communication and not its own IP Address.
When you use NAT or Host-only type of Networking, a Virtual DHCP Server is installed by default.
However this DHCP Server cannot lease you IP Addresses if your VM is set to use Bridged Networking.

Author

Commented:
Thank you mattvmotas for some good help. Everything worked once I jogged the bridged settings on and off a few times. It works exactly as you stated. Great work.

Author

Commented:
Just needed some jogging of the settings. The whole setup worked like the answer said it should.Thanks