Updating via a proxy server

[Hammy]

Hi,

I am having problems getting software using TU to connect out via our internal proxy(MS-ISA) server, and despite what configuration I set in TU it insists on attempting direct connections. If I route the destination direct out to the Internet (and permit the necessary FW access) then the software update works fine, but I wish our user(s) to update via our web-proxy which support FTP.

The situation is further complicated by our proxy chaining to an upstream proxy over which we have no(very little) control.

Questions:

1. I've read that TU 2.0 handles proxy access - how, as a end user (client side), can I determine which version of TU I am using. Is TU 2.0 server or clinet - or both ?

2. Has anyone any idea why TU is makeing direct connectiosn destpite the proxy settings both in the TU configuartion and the client's Internet Connections.

Any help on on tracing/fixing this problem would be much appreciated.

--
TIA
HammY

[Mark]

Hi Hammy,

The first thing we need to do is determine which version of TrueUpdate you are using to design your update.

Note: If you are only working with the TrueUpdate runtime, i.e. you are using an update created by another company, and are having problems please contact them directly, as they have designed your update and will have information on how to fix the issues.

In TrueUpdate 1.0 there were two design-time executables:


Client Configuration Utility - CLientConfig.exe
Server File Editor - ServerFileEdit.exe


Whereas TrueUpdate 2.0 has only one design-time executable: TU20Design.exe.

The will also be installed, by default, to different location on your hard drive:


C:\Program Files\TrueUpdate 1.0
C:\Program Files\TrueUpdate 2.0


Once you have figured out what version you are using please let us know.