Question : Client wont connect to session. error 10030.

I have 300 hp dc7700usdt machines, that have been, and continue to connect to my ghost server when I push out an image via pxe boot. I spent months with the networking team perfecting the network and switch settings to make everything work perfectly.
I just received 140 dc7800 small form machines and they are all on the same network, same switches. Some of them replaced older machines that connected to the server, so they are on known working ethernet ports.
I originally used pc-dos to boot the dc7700s, but just started using winpe. When I created the winpe boot image I added "ja=push". The session name is 'push', by the way, I can send a pxe boot/ghostcast to a dc7700 and it connects and receives the image fine.  i can put a dc7800 on the same port, and send it the same image, (i realize the image may not work due to the machines not being identical and its not a universal image, but it should still send), but it will load into the winpe, and ghost, but then it just says attempting to connect to session 'push'. Then fails after several minutes giving me a 10030 error.
Why does this machine fail and not the older ones? Both boot fine into the pxe/tftp/ winpe no problem.
When I send the ghostcast i do name the session 'push'.

Any ideas?>=

thanks in advance

Answer : Client wont connect to session. error 10030.

turns out the built in intel pro1000 driver for winpe in gss2.5 is no good for the hp dc7800. I downloaded the most up-to-date driver from the hp site and added it to the winpe driver list, AND unchecked the built in intel pro 1000 driver. I created a new winpe boot image, and the ghostcast connected the first time.