BSFA: Grovelling apologies

OK, we cocked up: the BSFA web site disappearing into the void was down to us disposing of an old domain that we thought was redundant: it turns out that www.bsfa.co.uk (and a couple of other websites) were CNAMEd to a subdomain of it.

Mea maxima culpa.

We’ve actioned fixes from both ends (reinstating the domain, and arranging with the ISP responsible for the bsfa.co.uk domain to point the web site at a more sensible place for the future). Sadly, neither of these will happen instantly, so if anyone needs access to the BSFA website urgently in the interim, you can reach it at bsfa.site.ramtops.org.

ETA: corrected link. Also, someone with posting rights in bsfa_news might want to put a note in there.

dear lazyweb

Has anyone out there any idea what could fsck routing in XP Pro such that it’ll see the LAN fine, but won’t route through its gateway? It’s running under VMware with bridged networking, but so are five other VMs (W2K, W2K/AS and XP pro, variously) all of which will happily route anywhere.

IP and routing settings look fine; it’s most odd. And irritating.

( working XP Pro VM )

( broken XP Pro VM )

The only difference there that I can see (apart from the IP address) is that the virtual ethernet device is 0x2 on the working box, 0x10003 on the broken one. I don’t have any idea how the interface numbers are assigned (by XP? by VMware?), let alone if they make any difference.

(10.0.0.1 is our dual WAN router, sitting outside the Sonicwall, if anyone is curious)