ISA Solution Software & Sites 22 NOV 2007

At last! The solution to my problem has finally been found!! :) <- Huge Grin. As I mentioned earlier today (Post {0410} to be exact), the introduction of the ISA server was causing me a lot of headaches. I had been right in terms of the solution – simply make your application’s download request make use of Internet Explorer’s settings and it ought to work – as long as Internet Explorer is set up to handle the ISA request correctly. So using Dim WbReq As New Net.WebClient
WbReq.Proxy.Credentials = System.Net.CredentialCache.DefaultCredentials

instead of my usual lazy

My.Network.DownloadFile(*parameters*) <- Thanks VS .NET 2005 for making life easy!

would get me my desired results, as long as the system’s stored user names and passwords list contained the correct login details to UCT’s ISA server at

So my solution is simple enough. Change the first instance of the download code to the desired code (funnily enough, once the DefaultCredentials have been set once, it seems that My.Network.DownloadFile works just fine from that point onwards) and then add a information-containing dialog box that automatically opens the control panel’s user management dialog with a call to

Process.Start((System.Environment.GetFolderPath(Environment.SpecialFolder.System) & ”
usrmgr.cpl”).Replace(“”, “”))

Note that in Windows Server 2003 (my main headache), you can actually directly open the key manager dialog by calling:

Process.Start((System.Environment.GetFolderPath(Environment.SpecialFolder.System) & “keymgr.cpl”).Replace(“”, “”))


Okay, so now that the solution has been found, I just need to now go and alter around a half-dozen or so CodeUnit apps :(

Work, work, work. It just never ends :)

Related Posts:

About Craig Lotter

South African software architect and developer at Touchwork. Husband to a cupcake baker and father to two little girls. I don't have time for myself any more.