can you configure the MS dhcp server (on server 2003) to give out domain controller information?
We have users across an MPLS network complaining about horrible slow logins. When I trapped packets I found they were connecting to a server on the other side of the WAN for DC services. When I asked the server guys why, they said they had no control over it, that there was one DC in the local office and one in the HQ office and the workstations just randomly "found" one to use...
I don't claim to be a windows server expert. I've done tons of Linux and Netware, and enough DHCP to know that the right DHCP server can give out some pretty specialized information, including options for IP phones and lots of other stuff.
Is it possible for DHCP to tell the user what DC to use? If it gave out a primary and a 'backkup' in case the primary is down, would it be possible to force the workstation to try the local one first?
Just trying to stop the "network's slow" complaints...
We have users across an MPLS network complaining about horrible slow logins. When I trapped packets I found they were connecting to a server on the other side of the WAN for DC services. When I asked the server guys why, they said they had no control over it, that there was one DC in the local office and one in the HQ office and the workstations just randomly "found" one to use...
I don't claim to be a windows server expert. I've done tons of Linux and Netware, and enough DHCP to know that the right DHCP server can give out some pretty specialized information, including options for IP phones and lots of other stuff.
Is it possible for DHCP to tell the user what DC to use? If it gave out a primary and a 'backkup' in case the primary is down, would it be possible to force the workstation to try the local one first?
Just trying to stop the "network's slow" complaints...