not aquiring ip address quick enough

[Guest]

I work in the government and we have multiple machines on our vast domain.
This is Win2000 server with winxp machines. These machines all have SP2 on
them.... Some machines out of the blue cannot log onto the domain right away
at startup..... they have to wait about 30 seconds for dhcp to finally kick
in..... then they can log in.

If you log in locally you will see that the only reason the domain is not
available is because they still have no ip address.... it just sits there at
that "aquiring network address" screen..... finally it works and all is well
....... that is of course until the next reboot.....???????????

Why does this happen to only a few, and how can I prohibit this in the future?

Thanks everyone!!!!

 

[Richard G. Harper]

I would look at network congestion in the area where the "few machines" are,
or problems with their physical network connection.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Guest]

I have monitor reports in front of me.. and all is well ... I have moved
another pc to that workstation just to check....

I was able to disable nic card and renable ... I immediatly recieved my ip
address... only took about about a half second...

this is not the case with the few machines I am speaking of..... I have
about 4000 ghosted new e-6000 gateways... and there aren't any physical
difference's between them...

We are using 100fx

????????????

I would look at network congestion in the area where the "few machines" are,
or problems with their physical network connection.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

I work in the government and we have multiple machines on our vast domain.
This is Win2000 server with winxp machines. These machines all have SP2 on
them.... Some machines out of the blue cannot log onto the domain right
away
at startup..... they have to wait about 30 seconds for dhcp to finally
kick
in..... then they can log in.

If you log in locally you will see that the only reason the domain is not
available is because they still have no ip address.... it just sits there
at
that "aquiring network address" screen..... finally it works and all is
well
...... that is of course until the next reboot.....???????????

Why does this happen to only a few, and how can I prohibit this in the
future?

Thanks everyone!!!!