Home » Kerio User Forums » Kerio Control » Kerio Control on VMware and NICs problem?

Messages: 2
Karma: 0
Send a private message to this user
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? Smile
Pavel Dobry (Kerio)

Messages: 2057
Karma: 251
Send a private message to this user
Please do not create bogus topics in this forum and do not try to cheat forum rules.

Regarding your questions I recommend to contact any of Kerio partners or our technical support.

Messages: 2
Karma: 0
Send a private message to this user
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?

Messages: 285
Karma: 59
Send a private message to this user
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.
Previous Topic: Kerio Problem
Next Topic: Other action for users with exceeds quota
Goto Forum:

Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Wed Nov 21 17:18:19 CET 2018

Total time taken to generate the page: 0.93165 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.