My skill level in this area amounts to "gormlessly follow the how-to guides", so if that's you too, this might be just what you've been looking for!
Ever since installing Hardy I've been having no success mounting network shares at bootup correctly.
When upgrading from Gutsy the existing fstab entries suddenly created weird permissions problems, where the drives would appear on the desktop, but their contents could not be displayed, or could but I was locked out of opening most of the contents.
The solution has finally been FOUND. I didn't do this work (its in a bug report and elsewhere in the forums) but because I've seen so many people hunting for the answer I though reposting it might help somewhere.
Most how-to guides you see here or elsewhere on the web (in my case the old "Unofficial Guide to Dapper") explain how to edit fstab and make an entry similar to this (in this case to mount a drive called "fred" located on a server at 192.168.0.100):-
//192.168.0.100/fred /media/fred smbfs credentials=/root/.smbcredentials,dmask=777,fmask=777 0 0
The WORKING equivalent under Hardy is this:-
//192.168.0.100/fred /media/fred cifs credentials=/root/.smbcredentials,rw,nounix,iocharset=utf8,file_mode =0777,dir_mode=0777 0 0
The key changes are the use of the built-in cifs instead of the now-depreciated smbfs, and the apparently-essential "nounix" switch.
Follow the rest of the normal instructions for creating the local mount folder (in this example "mkdir /media/fred"), creating the credentials file etc in exactly the traditional way.