2

The company I'm working for bought another company that's got its own domain. We've connected these together and noticed that both domains have got their own WDS server.

Let's call our primary WDS server WDS1, and the existing one of the domain of the bought company WDS2.

What I'm trying to do now is to boot into WDS1 from the other location. However, only WDS2 is recognized by the PXE boot options. So I'm guessing I have to change the DNS entry or something? Where do I start? I've noticed the old WDS server in the other domain's DNS. I'm not sure if PXE boot is DHCP related and not specifically DNS related?

Wesley
  • 32,690
  • 9
  • 82
  • 117
Kenny Bones
  • 119
  • 2
  • 3
  • 14

1 Answers1

2

Ultimately your PXE clients need to be told where to find WDS1 as WDS2 is still responding to their requests.

The PXE client will acquire an address from a DHCP server and then locate the PXE server, both of which are performed using UDP broadcasts. If the two servers are separated by a router (or on different segments) then the broadcasts won't be reaching WDS1, so I am assuming that your two WDS servers are on different network segments.

That I know of, there are two possibilities for configuring which server the clients use for deployment: using DHCP options and using IP helper addresses.

  • DHCP options 66 and 67 can be configured to direct the client to the correct server.
  • IP helper addresses are used to forward UDP broadcasts onto an address on a different network segment.

See the following article from the Microsoft KB which explains the difference between the two in quite some detail: http://support.microsoft.com/kb/926172

This one should also help you on your way: Managing Network Boot Programs (Microsoft TechNet)

Which option is better for you could probably be answered with a bit more detail about the network infrastructure that lies under your two organisations and their WDS servers, for example what address ranges are being used, routing mechanisms in place, how many DHCP servers and where they are placed, operating system versions, etc.

john
  • 1,995
  • 2
  • 17
  • 30
  • Check the 66 and 67 options on the address for the WDS2 server and find out where and if it's getting it's bootstrap file from. If you can't find it there it may be set to broadcast as a PXE service in your routing. – Split71 May 07 '12 at 13:13
  • @Split71 As outlined in john's answer, 66 and 67 don't have to be defined if you use a helper address. – MDMarra May 07 '12 at 19:07
  • @MDMArra Apologies, I edited my answer to be more detailed. I didn't mention IP helper before Split71 commented. – john May 07 '12 at 19:16
  • Just a thought, isn't it possible to just copy the contents of the entire Image folder to the other domain? – Kenny Bones May 10 '12 at 09:49
  • Yes it probably is a viable alternative, but that wasn't requested, and the OP might be wishing to consolidate for ease of maintenance. – john May 10 '12 at 16:12
  • Just for the record, I only set option 66 and 67 in the DHCP. Option 66 was set to the IP address of the new server. And 67 was set to \boot\x86\wdsnbp.com. This worked immediatly. But because of the increased network traffic, I had to copy the deployment share to the local server instead. – Kenny Bones May 11 '12 at 07:44