PAULDCLARK
Well Known Member
Got a bizarre issue. I have a couple of new Windows 2003 SP2 Std edition servers for use on a multifoundation tech upgrade project (Oracle 9.02 to 10g, 8.95 to 8.95, WS5 to WS6 etc), to be used as testbed jas gen servers.
I am experiencing server package build problems with these machines regardless of the SP and host in use, so I know the issue doesn't lie at the Enterprise Server end.
They will happily build a package with just Specs, whether full or update packages, and will initilaise the package at the server end run paktotam etc and complete normally. But whenever I introduce BSFNs its a completely different story. The server package initilises, creates the folder structure, it even creates a STS and TXT file, and transfers up 1 or 2 BSFN .C and .H files and then stops dead in its tracks. The ent server appears to send a message to the build machine, and it doesn't seem to get there. All network config, anti-virus, firewalls, drivers, updates etc etc all seem to be fine. I've even configured HOSTS files, but nothing seems to have helped at all.
I must have build hundreds of client machines over the years, and never seen anything like it. The Server support team think that the machines are fine, and everything I've suggested checks out.
Anyone got any ideas of where else I should look? The machines are HP servers with a teamed adpater which is forced to 100Mbps, full duplex...
Thanks
P
I am experiencing server package build problems with these machines regardless of the SP and host in use, so I know the issue doesn't lie at the Enterprise Server end.
They will happily build a package with just Specs, whether full or update packages, and will initilaise the package at the server end run paktotam etc and complete normally. But whenever I introduce BSFNs its a completely different story. The server package initilises, creates the folder structure, it even creates a STS and TXT file, and transfers up 1 or 2 BSFN .C and .H files and then stops dead in its tracks. The ent server appears to send a message to the build machine, and it doesn't seem to get there. All network config, anti-virus, firewalls, drivers, updates etc etc all seem to be fine. I've even configured HOSTS files, but nothing seems to have helped at all.
I must have build hundreds of client machines over the years, and never seen anything like it. The Server support team think that the machines are fine, and everything I've suggested checks out.
Anyone got any ideas of where else I should look? The machines are HP servers with a teamed adpater which is forced to 100Mbps, full duplex...
Thanks
P