I had a network using ASL 3.xx with everything on proxy, which means that all my client boxes accessed everything, including ASL Webadmin, using the proxy. I had never bothered to set up the computers to not use the proxy for local connections because I hadn't thought about it.
Well, when I wanted to install a new ASL 5 box, I downloaded latest.iso, popped the CD in a new machine, and fired it up. Got a working command prompt, and was able to ping the ASL box from the LAN, but try as I might I couldn't log in to WebAdmin. I must've reinstalled both v4 and v5 CDs four or five times, and always the same problem (I never said I was quick, did I? [;)])
Anyhow, three agonizing hours later it dawned on me that the machines were looking for a proxy server and the newly-minted ASL box wouldn't have had the proxy enabled just yet. Told my client to go straight on ports 80 and 443 and everything was happy!
This is not a bug or a problem with ASL, it's entirely an issue of operator error. . .submitted in the hopes that I can be a warning to others!
Cheers,
Dan
This thread was automatically locked due to age.
