Link to home
Start Free TrialLog in
Avatar of Lourens van Dyk
Lourens van DykFlag for South Africa

asked on

Unable to connect to internet via domain controller in Virtual Machine

To whom it may concern

I have recently taken over a school setup from a former IT company.  The school has a server with Windows 2008 R2.  This machine is configured in a workgroup with 2x network cards.  
I guess this is to split the Computer lab from the schools admin side.  The configuration is as follows for the server:
 
LAN adapter 1 IP address settings (Computer Lab):
IP = 192.168.0.11
Subnet Mask = 255.255.255.0
No gateway
Primary DNS = 192.168.0.1

LAN adapter 2 IP address settings (Internet):
IP = 192.168.1.11
Subnet Mask = 255.255.255.0
Gateway = 192.168.1.1
Primary DNS = 196.22.218.248
Secondary DNS = 209.203.10.208

They have a broadband wireless ISP.  Their Mikrotik CPE gateway = 192.168.1.1 and the ISP Suggested DNS Servers = 196.22.218.248 and 209.203.10.208.
LAN Adaper 2 is directly connected to a switch in schools admin side and is then connected to the mikrotik CPE. I can connect to internet via the physical server machine or VM Host.  But now according to their setup, I need to start VM Player to start the actually domain controller.  The Virtual machine mounts the 2x network adapters but is configured with the IP address setup as follows:

LAN adapter 1 IP address settings (Computer Lab):
IP = 192.168.0.1
Subnet Mask = 255.255.255.0
No Gateway
Primary DNS = 192.168.0.1

LAN Adapter 2 IP address settings (Internet):
IP = 192.168.1.6
Subnet Mask = 255.255.255.0
Gateway = 192.168.1.1
DNS = 192.168.1.6

In the DNS Console, I have configured on the Interfaces tab = all adapters (192.168.0.1, 192.168.1.6). On the forwarders tab = 196.22.218.248 and 209.203.10.208 and tik the use root hints.
I am not able to browse internet.  I cannot ping 192.168.1.1 from within my virtual machine.  All My network adapters for the virtual machine connects with the setting:
Bridged: Connected directly to the physical network
I am not sure if this is correct.  Also installed on the virtual machine is Symantec Endpoint Protection and the Manager console.  And also Microsoft Forefront TMG management which acts as the internet proxy for the computer lab PC’s connecting on the 192.168.0.x range.

Please help and advice me what settings need to be changed and if configuration has to be done in Forefront, VM Player or Symantec Endpoint Protection to allow the Domain Controller to connect to internet and that computer lab PC’s can connect to internet.

Kind Regards
ASKER CERTIFIED SOLUTION
Avatar of Chretien TALOM
Chretien TALOM
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Why are you using VMware Player? They have a server that runs a domain controller inside of VMware Player?

Are they using ESXi possibly?
Avatar of Lourens van Dyk

ASKER

Hello xKincaidx

The setup of their LAN is not originally my intend.  I took the setup over from an IT Company.  So the VM Player with the DC inside VM Player was already installed.  The setup needs to be transferred to ESXi, but that is a migration for another day.
Ok chtalom

I have bridged the LAN adapter as you suggested.  I just want to make some screen shots so that you can just check if it is configured correctly.  I can now browse internet from within the VM and also ping the gateway 192.168.1.1.  Only problem that I have is that I cannot browse www.google.co.za, but if I use the ip address 74.125.233.63 in the browser, then I am able to open the google web page.  So I figure that it is a problem on the Microsoft Forefront TMG.  Do you perhaps know where I can configure the setting to allow www.google.co.za and to check whether the web page is blocked on Forefront.

Kind Regards
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.