Question : Best way to map network drives

I have a windows 2003 small business server setup with about 7 XP pro desktops joined to the domain.  We have data shared on each desktop, which not ideal as it's not centralized and it's not backed up properly.

I want to consolidate all my data on the server and access it from the server via network drives.

My experience with login scripts, network drives, and UNC paths has been somewhat unreliable as it doesn't always work (dropped connections, network drives not mapping, network drives missing, etc...)

Question: What is the best way to provide access to server resources via network RELIABLY? Is there such thing as a redundant network connection (like, a startup script under "startup" AND a login script)?

Answer : Best way to map network drives

When you map a drive manually in Explorer, you can check "Reconnect at logon" (in Vista, it might differ in XP, I can't remember). I would use a singe drive anyways, not more, and create subfolders for different purposes.