Not getting a DHCP address before group policies run.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We are currently having a problem from time to time where we start our
computers and it appears the machine does not get a DHCP address before the
group policies are applied. When this happens, our network drives do not map
to the machine. The only resolution we currently have is to log the user off
and have them log back in. Has anyone heard of anything like this before?
We originally thought it was a network card problem, until we started using a
different card this week.

Any helpful info would be appreciated.
 
In
RF1908 said:
We are currently having a problem from time to time where we start our
computers and it appears the machine does not get a DHCP address
before the group policies are applied. When this happens, our
network drives do not map to the machine. The only resolution we
currently have is to log the user off and have them log back in. Has
anyone heard of anything like this before? We originally thought it
was a network card problem, until we started using a different card
this week.

Any helpful info would be appreciated.
Click to expand...

Are you sure that's the issue? (check your event logs). Are you using
wireless, or wired Ethernet?
Have you tried enabling "always wait for network" via group policy?

(Computer Configuration-->Administrative Templates-->System-->Logon....
"Always wait for network at computer startup and logon" to ENABLED.)
 
It happens with wired or wireless. We have enabled "always wait for network"
via group policy. There is nothing in the event logs that show what is
happening.
 
In
RF1908 said:
It happens with wired or wireless. We have enabled "always wait for
network" via group policy. There is nothing in the event logs that
show what is happening.
Click to expand...

This is very odd. Event logs ought to show you something. And your computer
ought to be getting an IP address long before someone logs in - in fact, if
it didn't, it couldn't contact the server at all.

You might post in microsoft.public.windows.group_policy.
 
Back
Top