Windows Server 2016 AD/DHCP/DNS Environment IP Issue

[hoaxy32]

Hey guys,

having a bit of an issue with my Windows Server 2016 AD/DHCP/DNS environment, specifically with issuing an IP address to clients and I'd like some advice or maybe someone knows a fix.

Currently, this Windows Server 2016 box runs Active Directory, DHCP and DNS requests to 17 Windows 10-based workstations and the issue comes when our users boot the systems for the first time that day and the server not issuing a valid IP but if that same user does a system reboot then the server will issue a valid IP. It first started a few weeks after this new server was installed, then only one or two systems would not be able to connect but over time it has become more and more systems, then we have to do a quick restart then it would be able to connect.

 

Any thoughts are most appreciated,

Thanks.

[Husky]

Is it a flat network or is it segmented? (i.e. VLANs, are you using VLAN tagging?)

 

It might also be an issue with Windows 10's "Fast Startup". Try disabling it under Power Options in the Control Panel and see if that solves the issue with that workstation.

[hoaxy32]

 

 

 

 

34 minutes ago, Husky said:

Is it a flat network or is it segmented? (i.e. VLANs, are you using VLAN tagging?)

 

It might also be an issue with Windows 10's "Fast Startup". Try disabling it under Power Options in the Control Panel and see if that solves the issue with that workstation.

It's a flat network, no VLAN's.

 

That's a good point, I haven't checked the fast startup on the affected machines. Will give that a shot, thank you!

[hyperlynx256]

I was just about to say that. We had a couple of workstations do just that. and that was the solution for both workstations. 

[hoaxy32]

On 8/3/2019 at 7:06 AM, deltaop582 said:

I was just about to say that. We had a couple of workstations do just that. and that was the solution for both workstations. 

Yeah and funny enough looks like it has fixed the issue here also. Thumbs up to Husky.