Stop DHCP Server on network mode NAT

[Pauli]

Hello,

I try some Windows Server configs and so i have a SBS 2011 server at my Windows 7-64 VirtualBox. To use this server not on my internal network but go to the internet I'm using network mode NAT. This mode have a DHCP server to the virtual network but Windows SBS want to have a DHCP server too.

So is there the possibility to disable this VB DHCP Server for this maschine?

Thanks, Pauli

[Perryg]

You should be able to disable it in the main manager -> preferences -> network

[Technologov]

IMO you should try VBox 'bridged' mode.

I'm not aware of any way to disable DHCP server in vbox NAT. You should disable VBox NAT completely.

[Perryg]

Actually if you really want to make this work you should use the internal network to isolate the Windows domain from the local LAN. Lots easier than trying to set it up with Bridged as this will appear to be multi-homed.

See:
Setup Windows Domain in VirtualBox

[Pauli]

@Perryg post 1: Thank you, but this is only for internal network mode and do nothing change for the NAT mode!

@Technologov: Thank you, but with bridge mode the test domain is connecting to my real domain - not very good!

@Perryg post 2: Thank you - not very nice to setup a separate routing PC to get access to the Internet!

No other idea?

Thanks!

[Technologov]

Write your setup requirements again, so we try to help.

[Perryg]

Not if you want it to work properly. The additional (ICS/pFsense) guest is your router. They have very small footprints if installed properly & the Domain will not appear on the local LAN and there will be no conflicts. It is simply the best way, but you know what you want so I will leave you & Technologov to figure it all out.

[BillG]

I can only agree with Perry. Trying to run a Windows domain behind a NAT router is tricky. You can only make it work if you have full control of the NAT router, so that you can disable its DHCP function and run your own. This is true whether your domain machines are virtual or physical.

You are much better off running your domain on an internal network and run your own NAT device in a vm. People strike this same problem trying to run AD behind ICS. It just won't work.