Question : FreeNAS 0.69 Accessing Drive Data on Rebuilt Server

I had a a FreeNAS 0.69 RC1 Server which I used a few large drives to store data (shocker, I know).  Using the Samba share feature I was able to use AD to connect to my Domain and make these shares available to the other users via drive mapping logon scripts.  I was also able to use the types of shares in the Domain DFS without a problem.
Not understanding UNIX\Linux access permissions I kept my configurations in terms I understood.  I shared out a specific directory and then I opened to the child directories and set the permissions on them.  This allowed me to restrict/allow as needed.

...Then we bought a house in another town.  My FreeNAS boot partition got corrupted and a reinstall didn't work as I'd expected.  My answer to this was to rebuild the box as ver0.69 and reattach the drive.  Simple, right?

Wrong.  After adding the disks (as UFS EPT), creating Mount Points, Connecting to AD and creating Shares IF I am able to connect to a share (and that seems hit or miss) I ALWAYS seem to get "Access Denied" when trying to drill-down to child containers.

Two questions:

1) Why is setup so different now when it was BLISSFULLY simple with the RC1?

2) How can I reset the File & Folder permissions on EVERYTHING so that I can AT LEAST access the data that is already on the FreeNAS disks (..eh,..formatting the drives is a joke I've ALREADY heard one too many times, thank you  :o Z  )?

I'm trying to locate a specific backup job but, not being able to access any container other than the root of a share, I can't browse the child containers in order to look for it.

Answer : FreeNAS 0.69 Accessing Drive Data on Rebuilt Server

chmod -R perm dir