Have you checked that the DHCP server is properly authorised in AD?
Might sound obvious, but the scope isn't out of IP addresses is it?
Look in the event log for errors about the DHCP service, try unauthorising
and authorising the DHCP server again.
Cheers,
Jeremy.
"Ripley" <Ripley[ at ]discussions.microsoft.com> wrote in message
news:53D8EDA9-58F9-40DD-BA47-29D3822E044B[ at ]microsoft.com...
[Quoted Text] >I have a SBS2003 Server with 1 additional Windows 2000 Server.
>
> The SBS2003 runs as my DNS and DHCP server, whilst the Windows 2000 Server
> runs as an additional DNS server.
>
> Over the past few days clients have started to report that they are unable
> to log into the network. When I check on the machines, they have been
> assigned the default windows IP address (169.54 or something), hence their
> inability to access our network which is a 192.168.1 range.
>
> The only way to resolve this is to assign these clients a static IP
> address.
> Once I do this, they can get into our network no worries.
>
> Obviously, this points to the DHCP server and possibly DNS. I have tried
> the
> usual rebooting the server, flushing the DNS, checking the DNS and DHCP
> records, etc. But I can find nothing, and there are no faults being logged
> to
> point me in the right direction.
>
> Any ideas??
|