We experienced the same problem a few months ago with NETINSTALL and 2x RB333 boards, my supplier was as much use as an "ashtray on a motorbike", and the only real advice I got was from Normis, which, after much to-ing & fro-ing, resulted in him suggesting that the RB's were goosed, and that I should return them to my supplier ~ who at that point, hadn't got any stock, and wasn't expecting any soon
I was TOTALLY convinced that the RB's were fine, and that the issue was with NETINSTALL!!!!!
We tried disabling the firewall & various 'other' services on the XP box we were using, to no avail!!! We built 3 other machines with XP Home, XP Pro, and Vista ~ Still no luck!!
Then, as a final 'stab-in-the-dark' we tried another, older, machine we had lying around (running XP, with all the latest patches), and BINGO it worked ~ it went straight through, programmed the chip, and on reboot the RB333's were perfect!
Totally confused, we then tried the fixed boards back on ALL the other NETINSTALL installations that we had created, and it trashed them again ~ back to the old box in the corner & that worked fine - EVERY TIME!!!!
This was a real issue, and it NEARLY stopped us from using MT in our deployment.
I didn't ever get to the bottom of why this happened (and still does!), I'm just praying our old box in the corner doesn't ever die!!!!
The only thing we know at this point, is that the old XP box is our ONLY machine with an intel network card? (So just maybe...?)
I assume this must me related to the network card, and for some reason the NETINSTALL program doesn't like certain (newer? Non-Intel?) network cards/chips!
If you have an old machine knocking about, I suggest you give it a try, as it took us weeks to sort this out ~ With virtually no help from our supplier or MT.
Hope that helps