| Kerio Control on VMware and NICs problem? [message #105439] |
Tue, 13 August 2013 14:30  |
Maurice69
Messages: 2
Registered: August 2013
|
|
|
|
Since I want to install a new SBS2011 server on a virtual environment (no migration but new installation) I'm trying to install/configure Kerio Control on VMware ESXi 5.1.
This is the situation at the moment:
This is the situation I want to create so that Server1 (DC and Exchange) won't byte the new virtual SBS2011 Server (and the other way around):
I installed the OVF file but I'm a but confused with the mentioned NICs in Kerio. The MAC adresses of the NICs B and D are not the MAC adresses from the NICs A and C that are fysical in the VMware server?
but how can I tell Kerio Control to use NIC2 for internet and NIC3 for Trusted Internal network and do I need a NIC4 for the use of the virual network with IP range 192.168.2.x ?
Anyone any tips, hints or clues? 
|
|
|
|
|
|
| Re: Kerio Control on VMware and NICs problem? [message #105447 is a reply to message #105440] |
Tue, 13 August 2013 16:30  |
Maurice69
Messages: 2
Registered: August 2013
|
|
|
|
Hi Pavel,
I allready appoligized on the bogus topic and I also reported myself at te moderator. It is a stupid rule that you cant post links until the fifth post.
Can you please help me with my topic? I guess it helps lots of people who are using VMware and Kerio Control since I could find very less on the internet about this combination.
I was a die hard Winroute user until I switched jobs. Now I'm trying to get the new version back into business so please help me out a little or point me to the information that will be helpfull?
|
|
|
|
| Re: Kerio Control on VMware and NICs problem? [message #105465 is a reply to message #105439] |
Wed, 14 August 2013 05:37 |
silars
Messages: 285
Registered: March 2012
|
|
|
|
VMware assigns a different MAC per vNIC. The physical MAC will be different. They must do this to expose each VM. Otherwise, you would have to use some sort of NAT. That is also an option.
I'd suggest to use a vSwitch per NIC. Name the vSwitch intelligently to denote its use. Then, assign each of the Control NICs to the vSwitch by name.
Should be fairly intuitive at this point.
I use ESXi 5.1 and have 3 different NICs. One for each SP, and one for internal use. Not much different than yours.
You will likely want to leave the Admin vSwitch connected internally only. Ideally, you'd VLAN it the internal network.
|
|
|
|
Members
Search
Help
Register
Login
Home
