TS-439 Pro and AD and Folder Browsing

[rosege]

why dont you try the latest firmware? I have installed it on my qnaps that support it and it has been very good

too bad they didnt make it for my 409U

[randomed]

Looking around the forums most people report the iSCSI performance to be worse in the 3.4.x revisions of the firmware vs the 3.3.x line. I will still attempt to try it but I need to find a place to backup everything on the QNAP before we attempt any form of updates. I posted my comment as something to investigate.

[Yuki]

TS-459Pro+
Firmware 3.4.2 Build 0331T
4x2TB Seagate ST32000641AS drives from compatibility list
Network is Windows 2008 R2 Domain with Windows XP and Windpws 7 clients
All gigabit network on HP ProCurve 1810-24 managed switches
Servers: ESXi 4.1 with Windows 2008R2 VMs.

Now the issues:

1) Once QNAP is joined to the domain - we can't login to the shares (QNAP shows up properly in DNS and registers itself as a computer in Active Directory)
2) Once QNAP is joined to the domain - we can't even see the share through browsing by IP address. It will only respond and show shares if access via it's name
3) Slow write performance over cifs/SMB (around 30Mb/s).

This is really frustrating. As a small IT consulting company we have recommended two dozen units of various sizes to our clients. These are advertised as supporting integration with Active Directory, but in reality it doesn't work. We had plans to deploy 8 TS-859U-RP+ for video storage but with slow write speeds and inability to integrate with AD and browse by IP address this is unlikely to happen.

QNAP - please investigate this further.

[QNAPJauss]

Dear Yuki,

I am sorry for the issues you encountered.
But mainly all our customer can use Active Directory integration wihout any problems.
Of course, some may have some issue, but beside identified bugs, it depends on the Network configuration and Active Directory settings.

1) Once QNAP is joined to the domain - we can't login to the shares (QNAP shows up properly in DNS and registers itself as a computer in Active Directory)
2) Once QNAP is joined to the domain - we can't even see the share through browsing by IP address. It will only respond and show shares if access via it's name
3) Slow write performance over cifs/SMB (around 30Mb/s).

1- Do you have any details ? network configuration, specific GPO settings...
By default, domain users do not have access to the shares. You must give some permission.
2- It is the first time i can see this case. Do you have a way to reproduce ? MAybe a Remote connection will help.
Please check your PM, i will manage a remote session to find out the problems.
3- The performance depends a lot on the network environment, and the Models. most of our NAS can reach much faster speed.

Did you contact technical support to fix the issues ?
Maybe if you give us more details we can help here too.

BR,
Jauss

[chckumi]

Hello support team,

we have also problem with write performance around 6MB/s after update to new firmware. Read performance is good around 40MB/s.

We have QNAP TS-859 Pro, firmware 3.4.2, 8x2TB disks, RAID 5

[rubbertail]

Same Problem as Yuki here with a TS-509 Pro, FW 3.4.2.

* Windows 2008R2 SP1 AD controller, forest/domain level 2008R2
* When adding NAS to the domain, both A record in DNS and computer account gets created
* Add Domain Group "Domain Users" to all shares on the NAS as R/W, also press "Submit" there
* See the NAS in Network Environment on all computers - 2 ADCs with WinServer 2008R2 SP1, 2 Clients with Win7 SP1 64bit
* When clicking on the NAS in Network environment, error 0x80070035 Network Path not found
* When trying to access NAS by \\<IP> or \\<FQHN> or \\<IP>\<Share> or \\<FQHN>\<Share> error 0x80004005 Unknown error
* No cached credentials in any system for the NAS
* Domain freshly installed in a test system

As there is LOADS of data on the NAS I cannot re-initialize it easily as I don't know where to put more than 3TB... Is there a way to just re-initialize Samba on the NAS, meaning deleting all the Samba config files and having the default from the Firmware again there, without affecting any of the data on the harddisks?

Thanks
Martin

[QNAPJauss]

Hi,

From what you say it is not related to the configuration file.
Yes, there is a way to restore the default samba configuration, and keep the data.
Would it be possible to connect remotely to verify your issue ?

Thank you,
BR,
Jauss

[rubbertail]

Sorry for the cross-post, but it's important here as there now...

OK, just had a remote session with a QNAP technician.
In smb.conf, there as a line "hostname lookup = yes" - when this was commented out and Samba restarted, it worked.
Don't ask me what that line did in there... personally, I never changed anything on the Linux config file basis. There was a remote session with QNAP before where this might have happened - loads of FW versions before.

However, now it works - thanks to the guys at QNAP. Great service!

Martin