UNSOLVED

fidotas

updated

19 years ago

F

fidotas

2 Posts

0

4319

August 7th, 2007 21:00

Troubleshooting software update tasks?

Hey All,
 
I've created a new installation of DELL ITA 8.1 (on a PE1950 running W2K3 SP2 32-bit edition) and imported the latest SUU 5.2.1 CD's into the software repository and I'm attempting to deploy some of the system bundles, but I'm having some issues.
 
I can successfully deploy software tasks to PowerEdge 2650 servers running Windows 2003 or Windows 2000 (32 bit editions) that reside in the same subnet (but a different AD domain) as the ITA server.
 
Attempts to deploy software tasks to PowerEdge 1855/1955 servers running Windows 2003 (64 bit edition) that reside in a different subnet (but the same AD domain) from the ITA server fail with the error "Device validation command failed with error message: Unable to connect to the remote device. If a firewall is configured, refer to the IT Assistant readme.txt for additional information."
 
Yes there is a firewall between the subnets, but there is an exception allowing all traffic from the ITA server in both directions.
 
I can successfully run all ITA troubleshooting tests against both sets of servers (same subnet and different subnet in the same building). I can connect to CIFS shares on any server from the ITA server console. I can connect to any server using the Computer Management MMC from the ITA server console (which should show that RPC is working). I can successfully execute a "win32_process" WBEM call using wbemtest.exe from the ITA server console to any of the client servers (i.e. I can launch and see ping in the task list on the remote server) which shows that WMI should be working.
 
So I'm stumped. Where can I go from here to try to track down why I can't deploy software tasks to my remote servers? I can't seem to find any text log files on the client or the ITA server to examine.
 
Any help would be greatly appreciated.
 
Regards,
Daniel Muller
  • fidotas

    2 Posts

    127

    0

    Posted August 7th, 2007 22:00

    Ah, please disregard. This was a firewall issue.