Today at work I once again discovered that Microsoft's ISA Server is a genuine piece of crap. A customer was having some troubles using there telebanking software that uses FTP as means to exchange information. It had always been in working order before, but stopped working at a random moment in time. Appearing onsite I discovered that the machine was unable to connect to the FTP site, but checking with a co-worker the FTP site was reachable fine from the office. So it must be a local problem. Main suspects where the ISA server and the not-by-us-managed DSL router. Ofcourse I suspected the ISA server. Stopping the ISA Server service on the dreadful Windows 2000 machine ofcourse made the telebanking software do it's work, but if I would keep it in that state the customer loosed his ''image of security'' and another side-effect was that we had to configure every workstation to no longer use the proxy.

Trying to inject a firewall rule into the ISA server that would allow ALL traffic (that means ALL protocols to ALL destinations from ALL servers from ALL users) ofcourse did not work. So I had to abandon the site with a no longer working telebanking software, thanks Microsoft!

Back at work I continued configuring a stack (250) of Cisco SOHO routers to be deployed for the rollout I discussed yesterday. Using my nice config-generator, tftp and minicom on my fine Linux workstation. Did you ever do 40 routers a day on Windows ? I guess not :) (not counting Cisco Express Configuration Services)

People wondering when the layout will change, just keep looking, it will change in these days whenever I get a creativity impulse and have time to struggle trough the templates and find a nice HTML replacement for it. It actually already is a wonder that I actually update this weblog daily :) Also I'll repost some old blog entries from my old blogging setup ! :)

UPDATE: As you can see the layout has changed a bit, new logo, some other headers, more powered by thingies, GeoURL tags etc...

EVENINGATE: Well just got out of the car fixing the connection to the colosite where my webserver is hosted, seems like one of the 2 mbit links went haywire creating 60% packetloss. Decommisioned the link for now so the link remains stable however a little bit slower. Problemtime approx 45 minutes..