Try this on one of them, they may be 'too quick' for XP
How to disable the Media Sensing feature for TCP/IP in Windows
Anyone come accross this one ?
Brand new kit - build image all fine - will it install the MSI's from it's linked GPO ? No.
The PC boots up fine - XP [ SP3 on a 2003 server ]
PC boots, [ very quickly ] you get a flash on applying network settings then the normal logon screen - logon fine no problems.
Stick an old PC on [ same GPO ] and re-deploy the MSIs and they re-deploy no problem on the old kit, on the new kit [ now on third PC out of 25 ] they won't !!
The PCs are in the same GPO - the only thing I can think of is the new ones are having the names of the old ones but they have new SIDs because of the sysprep on the build.
So I am at a complete loss as to why they won't install any MSIs, and I have moved the PC into different GPOs with different MSIs etc and still they won't install !! I have forced policy updates, I have tried everything but still nothing - what have I missed ?
might even be switch related had a few hp switches/dell pcs that until i flash the switch or knock the pcs back to 1/.2 duplex they do this as mentioned above the pc seems to be ready before the network
the below reg file also often helps as it makes the pc wait longer before going on
Windows Registry Editor Version 5.00
Code:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "GpNetworkStartTimeoutPolicyValue"=dword:0000003c
Are you getting any errors in the event logs? Gb NICs sometimes cause odd issues as well.
Are they Nvidia network connections by chance?
did you delete the computer accounts before you added the new one to the domain I had a problem like this a few weeks ago when a pc went bad I replaced the pc but called it the same name ended up removing from domain, deleteing the computer account and re joining the domain worked a treat
I had a similar problem a few weeks back with some Stone ITX boxes. In the event viewer it talked about enrolment failing which stopped GPOs applying. In the end it turned out to be a network card setting on the PC and in a minute I'll remember which one!
Turn your network card speed down to 100 not 1000
Sometimes this is caused by auto-negotiation on switches and Nics especially when STP is enabled this can cause this type of error as we found out to our dismay one day a few years ago.
STP if not set up correctly can take up to 30 secs to negotiate with the switch and in that time DHCP can fail to give address and therefore the workstation can not proceed to do anything in relation to the domain as the workstation is deemed to quick for the network.
This was resolved by using the port fast facility on our Cisco switches.
I hope this makes sense.
Last edited by bossman; 13th July 2009 at 04:14 PM. Reason: Brain not engaged at the time
I have only ever had to set some of the ports to 100 meg [ gigabit everywhere ] on some split ports I have setup and a few NAS boxes that get duplex mismatches when going in on gigabit switches.
Its a good thing to check out but would be very unlikely to affect only the new pcs. That issue with stp affected us to but on all stations till portfast was enabled.
It is usually caused by XPs shoddy handling of nics with bad drivers and slow dhcp servers.
We found that just like mattx our older workstations worked no problem and that older laptops built ok from the same OU but not the new workstations which kinda threw us until I went through the switch logs for that room.
As I have already said as soon as port fast was enabled on the switch (which I thought had been done) it has been fine.
There are currently 1 users browsing this thread. (0 members and 1 guests)