snap 4500 - strange behaviour

[villa411]

Hello All,

getting strange a few strange errors on a 4500. Running last version of OS 4. The server will not allow the administrator of AD to access the shares. The AD admin account is listed on all the shares inside the snap. The snap is using the AD admin account to verify AD users - new users can access the shares just not the AD admin account. I removed the AD admin account from one of the shares and now i cannot add it back again as it will not show up in the list of users without access to the share. I have rebooted the snap a few times, checked the ip address etc - swapped cables, flushed dns on the servers etc. When i try and access a share all i get is 'not accessible - you might not have permission to use this network resource'

any help massivly appreciated .

[villa411]

Update - Discovered the problem. For some strange reason the snap will not update its user list from AD. Tried - removing it from domain, remove users, reboot , add to domain, old user list still appears. Reboot, remove from domain, add to workgroup, rename, reboot, remove users, shares, reboot, add to domain, old user list reappears. Gave up.
Would love to ssh into box and delete user list but no idea where it is stored.

Worst problem, will allow users to access shares and data but not administrator.
How to get data off when users dont have access to all data and cant change this setting... bloody snap crud.

Going to wipe back to default and put 4 * 750gb drives in it. Going to do the same to another 4500 that i have as well.

Gloss of snap servers worn of significantly.

[blue68f100]

You can ssh into the shell, but I do not recall off the top of my head where the list is stored. A clean install will work, though wipping every thing. If you do not do a clean install you will have the same problem and possiable the same as the old HD's. Make sure you disable the AV and Snap Shots or you will be setting your self up for more work.

Sorry I have limited knowledge on AD since my unit is for home use.

I did notice the same problem with the admin accessing shares. I just added my user ID in to the shares. It seams to be a permission problem with a user that have admin rights vs the admin or root ID. The default share gives every one full access. So I allways add a new share with limited access. And it use to be if you had root access you could roam (snoop) anywhere on the share. The reason I make a user share and put all into it. This also makes backup a little easier since I need to BU only 1 share. I do the same for FTP only users to isolate them from other areas.

Keep us posted as to progress. We are still learing these GOS units and from users who do not want to pay for support.