Problem recieving IP address in time for login Scripts to run

[Guest]

Network Stats - Class B net, Windows 2000 Server hosting DHCP/ Windows XP Pro
SP2 Clients 1000mb nic PC's and Win2k Pro SP4 with 10/100 nic PC's/ Internal
Firewall Turned Off on XP machines

I have recieved a batch of Compaq & Gateway machines that have built in 1GB
nic's and the switches I have are Cisco 100mb full, I turn on my machines and
if I don't give the machine about 30 seconds from the time of the CTRL ALT
DEL screen to the time I login the machine won't process login scripts
because it doesn't recieve an IP address quick enough. I have tried forcing
the NIC to 100mb full and setting the Switch to 100mb full but that didn't
fix it, I disabled the GIG NIC and placed a PCI NIC a 3com 3c905 and set to
auto and 100full without problems but when I switch back the problem returns,
I have had this happen on all of the PC's although its sporadic as it only
happens 1/3 times from the time of reboot or shutdown and bringing the
machine back up. The cables are Cat5-E and I am seeing this occur on several
different switches accross the net and I have the most recent drivers and
have the bios flashed the the newest version. I know I can set the timeout
longer via this technet article
http://support.microsoft.com/default.aspx?scid=kb;en-us;840669
but this delays logins considerably and I can also set the ports on the
switches to PORTFAST instead of SPANTREE but I don't want to loose my network
if one of the NIC's go into LOOP mode. Is there anything else I can try?

Thanks sorry for the long post.

 

[Guest]

Hi -

Run the Group Policy Editor (gpedit.msc) and browse to Computer
Configuration --> Administrative Templates --> System --> Logon and set the
policy that says "Always wait for the network at computer startup and logon".


This can also be set as a domain policy if you prefer.

Good luck -

 

[Guest]

Is there any settings that would speed up the negotiation for getting an IP
address?