Googlejuice a month later

I have a few entries in my back log, will get them out of the door this week end.

I’ve seen that very few people did stay subscribed to my blog, I hope they will come back soon!

But anyway, before going to bed, here is my google juice:


18 December 2003

31 January 2004





1 and 2




2 (with the new blog!)

Longhorn winfs


Hum, somewhere

Longhorn peer2peer



Longhorn SOA


50+ and counting

 This is just to say that googlejuice is long to get, but obviously fast to loose if your web site goes offline. We’ll see if google like me again in a month time!

Tomorrow, toilets, Robert Scoble, blog context switching, remoting from the SOA point of view (followup on previous discussion), and I’ll start a series of articles on the way process a page, not the boring page life cycle thing everybody did, but from the request. Should be good J

As always, please slap me in my comments it motivates me to get a better blog here.


ISA Server 2004

There will be a lot of posts today, I have quite a serious backlog and don’t want to do one of these HUGE posts that only Chris Brumme can successfully write.

Back to the point, the ISA Server 2004 beta, code name stingray, which you can find here, has a brand new UI, and that changes everything. It is more configurable, publishing of servers works much better, etc.

However, if you try to get your ISA Server on a machine with DNS and DHCP (as I do on my internal network, serving my 3 computers, honey’s computer, flat mates computers and even the street computer, there’s a gotcha.

First, head to this article on the ISA Server community site. Thomas describes what needs to be done to get DNS working, and drop a hint on DHCP. You have to allow incoming DHCP (server) protocol using a routing rule on the “All Networks” network set. This is not a feature but a known bug in the beta 2. I hear you saying: But my poor poor Sebastien, you must still be drunk from that night to ask me to allow any DHCP request going through my network? Fear not my friend. First you’re not supposed to put the beta 2 in production. Second, you just have to only allow the DHCP RESPONSE to go through wherever you want to allocate them. Finally, you shouldn’t rely on DHCP addressing to secure your network.

I’m going to see tonight if you can still secure your network to prevent some kind of DHCP request attack by adding a second rule blocking the request on the external Network set.


Back Online - New Server

I’m back online, finally. I announced here that I would bring the blog back online the 3rd of January… So a month later here I am. Sorry for those of you who read this blog for letting you down. DSL takes a lot of time to be activated at my new place. Nice 4 bedroom house by the way.

The tech side of the post now: It is all running on a brand new server, with:

· Windows Server 2003 Standard Edition

· Internet Server and Acceleration 2004 beta 2

· Exchange Server 2003

· IIS 6 with dasBlog 1.5

Very good configuration, RAM usage is about 440mb, but it also have a dns and dhcp server and a few other nifties… Any advice to reduce the memory footprint appreciated :)