Quick and dirty way for alternate failover server?

I link my Windows home PCs (7 and some XP) to a separate file server box via a persistent network mapping. There's a separate mirroring server in place on the network too.

If one server goes down, theres an undignified scramble to remap drives so that work can recommence - but is there a quick way to have Windows 7 pick up the job of determining primary and secondary availability to speed this?

I know I could probably do something involved and complex via a virtual server and clustering but I'd prefer something simple and client-side if possible !


--
Martin

In an ideal world, I would agree.

I would have a series of file servers, maintaining synchronisation, and then a cluster process switching servers in and out as required to a single virtual IP address which Windows could point to.

However, I've got a simple home network and no real interest or budget in doing this. We have two servers that sync/mirror to each other and I'm seeking a simpler client-side solution. Ideally, at login Windows would identify whether the primary server is active and attach drives to this one, switching to the secondary if not.

I don't think this would be too difficult using a login script but wondered whether there was a more elegant way in Windows.

That's fine thanks. I'll probably go with a variety of a login net batch.

Cheers

Martin