We are trying to establish debug connections to a couple OMAP3530 dev kits running Win CE 6.0.
The 2 kits are connected to 2 different computers with pretty much identical installs of VS2005, Platform Builder and WinCE 6.0 R2. All patches have been applied to both environments, one system has been used to build a kernel while the other has not. Here is what we're seeing:

The system that has been used to create a version of the kernel can connect to a dev platform but only using the remote tools such as Process Veiwer, SPY, Registry Editor, etc.. Live debugging is not possible, when we try to connect to the remote client with VS2005 the connection fails.
KITL was enabled in one of the kernels we have been testing with.
The platfrom manager is configured to use KITL for the transport and startup server.
The Device Tools properties in Vs2005 is setup to use TCPIP connect transport and ActiveSync Startup Provider

The other system can connect to the remote client using VS2005 and perform live debugging but cannot connect using the remote tools such as Process Viewer.

Both systems can connect to the dev platforms using Activesync via USB.
The connections have been configured identically on both systems but nothing seems to make any difference.

I realize the descriptions are a bit vague but we have tried almost every combination of settings trying to get the connectivity to work fully on both systems with no luck.

Any ideas?