Jump to content

Recommended Posts

Posted

Hi.

 

I’m moving my server to a new office that has its own internet and ports round the office.

I’ve got the settings from doing an ipconfig.

 

What do I need to update on my server to get it to work?

I’ve got the physical machine connecting fine but my hyperV DC won’t connect.

 

I’m confused on where I need to update the gateway settings or in the hyperV virtual switch?

 

Any help much appreciated.

 

 

Thankyou.

Posted

Yes there are basic switches.

 

The issue is the domain controller was setup on a 192 network with a bt router on same ip range, subnet mask and gateway

Now the offices own internet is on a 10.4 up range.

 

I have my NIC on the phisical machine getting dhcp off the offices wall port. In hyperV I have a virtual switch that uses that network card but of course it won’t work as the Virtual domain controllers ip settings are on a different subnet.

Posted
Is there multiple ports on the host , if so couldn’t you use a bridge port ? Or setup Up routing and remote access on the DC to do NAT between the two networks
  • Thanks 1
Posted

Thanks for your reply. There is a second port on the host. I guess I could’ve used that.

In the end have got a spare edge router I’m going to put in and configure it for the ip range.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...