Jump to content

Recommended Posts

Posted (edited)

I am currently setting up a new server on a site that is shared by two institutions. Team A has a bare metal Server 2012 domain running DHCP, DNS, WDS, WSUS etc. We are setting up a 2012R2 domain on a single VM for Team B.

 

Team B uses the DHCP & DNS from Team A's server. We are trying to get WDS working on Team B's server. However, when we PXE Boot a client it is picking up Team A's WDS/MDT.

 

We have tried adding Server & Scope Options 066 and 067 in DHCP on Team A's server to point to Team B's server IP yet it is still getting WDS/MDT on Team A's server.

 

We have also tried disabling WDS on Team A's server but the client then gets a PXE-E55 error because it is still trying to get to Team A's server.

 

Any ideas as to what we are missing? Is it possible to have 2 different WDS servers on the same network?

Edited by woreilly
Extra info
Posted
Are the effected clients getting the correct IP addresses from the range they should be, it sounds like they are either ignoring the scope options and defaulting to the higher up ones or getting the wrong IP range and therefore getting the scope options from that range.
Posted
Do you have vlans. Are all the affected clients on the same vlan?

 

There are no VLANs. Just two Domains/Servers sharing the same network infrastructure.

 

Are the effected clients getting the correct IP addresses from the range they should be, it sounds like they are either ignoring the scope options and defaulting to the higher up ones or getting the wrong IP range and therefore getting the scope options from that range.

 

There is only one DHCP server (Team A). That one DHCP server has only one scope.

Posted

if both Team A and Team B are both using DHCP servers , how do you stop a team B client getting issued a DHCP address from team A's dhcp server?

it sounds like you need to implement vlans , not only for this task but also for security,

Posted

Can you ping the correct MDT server from a B PC? Or any PC on the scope for that matter. I'm guessing it's on a reachable subnet and has DNS entries for it (and the other servers on that site).

 

I'd definitely look at vlans for the two sites, it makes everything more secure and means you can have each scope set up with their specific MDT server as needed.

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...