TS-439 Pro and AD and Folder Browsing

[uanmi]

The QNAP guys spent a couple of days connected to my system and this ended last week. Nothing has occurred since then and I have not heard from them. I imagine their trying to solve this asap. I would appreciate hearing from them too.
regards, mark

[kimbilio]

An update... it seems that adding a new A record to the DNS, with a different hostname to the NAS's actual netbios hostname, will work. Clients can now connect to the shares on the nas by using the new hostname I've added to the DNS, and authentication via the AD account works fine. Trying to use the original hostname (which also still resolves fine via the DNS server) fails.

Obviously, the issue still needs fixing, but I can workaround things easier this way than by mapping with an IP address all the time.

Interestingly, I've found a number of results in google that talk about this same sort of problem in a more general sense and not related to qnap devices - clients can't access samba shares via the hostname, only via the ip address. It would seem to be fixable, but requires far more of a grasp on samba configuration than what I posses!

Michael

[WeatherDave]

Interestingly, I've found a number of results in google that talk about this same sort of problem in a more general sense and not related to qnap devices - clients can't access samba shares via the hostname, only via the ip address. It would seem to be fixable, but requires far more of a grasp on samba configuration than what I posses!

We're getting close to picking up a rackmounted QNAP, and I've been digging around some to identify potential issues. Since so many devices use SAMBA, I've been scanning the Samba site. Of particular interest is that with 3.4.3 release, they fixed a number of notable issues with Windows 7 and Server 2008 R2. In particular:

o Fix trust relationships to windows 2008 (2008 r2) (bug #6711).
o Fix Windows 7 share access (which defaults to NTLMv2) (bug #6680).

Perhaps Microsoft's tweaks are impacting the installed protocols that the QNAP device uses? Any idea of what implementation they are running with?

Just a though,

Dave

[kimbilio]

Perhaps Microsoft's tweaks are impacting the installed protocols that the QNAP device uses? Any idea of what implementation they are running with?

From what I can tell, the installed version of samba on firmware 3.2.3 Build 0209T is 3.3.9, so it's a bit behind the current stable release...

Michael

[uanmi]

QNAP technical support created an alias on the QNAP box that is seen by wins. So rather than connecting to \\myQnap I am connecting to the alias \\MyQnap-nas
For whatever reason the WINS authentication works with the alias and not with the registered hostname.

This is very similar to the DNS and WINS alias presented earlier in this thread. I tested that approach as well and it works.

Be aware that the Chinese new year holiday starts now for 2 weeks so tech support might slow down a little.

I have a suspicion that the problem is samba and we need a new firmware with a new version of samba.

regards, Mark

[fugle]

Have the same problem.
This is so lame - since buying my TS-439 some months ago I had a LOT of problems.
After upgrade to fw 3.2.1_Build1231 I had the same problem, after granting every user access to Shared folder I fixed the problem.

Some days ago I upgraded fw to TS-439_3.2.3_Build0209 and now the situation is that only my Windows7 client can connect without user/pw prompt.
My Win2008R2 servers and WinXP clients get the user/pw prompt.

I observed that the process of qnap AD membership didn't create a A-record in AD DNS (Win2008 Domain).
I tried to manually create a A-record for my qnap without any success regarding user/pw prompt.

My domain DNS server don't accept "unsecure" DNS registration and for security I want to stay with this policy.
WINS are not a solution since this service are outdated long ago.

I have other post on the forum with a lot of other problems regarding this product.
This is the first and my last time spending money on a Linux/Samba box.

Fugle.

[fugle]

QNAP technical support created an alias on the QNAP box that is seen by wins. So rather than connecting to \\myQnap I am connecting to the alias \\MyQnap-nas

Can you please give som detailed regarding this "alias", is this a config on the QNap box or DNS/WINS registration ?

fugle

[uanmi]

The QNAP support connected to my QNAP NAS and added an alias in the linux OS. I recommend you contact them and ask for help. They can be found using skype - their id is qnapskype

I'm hoping they will come out with a samba update and fix asap.

regards
Mark

[fugle]

Hehe - never ending story - after a reboot of my QNap my Windows7 client have the same problem.

[jnelson2000]

Still happening. Need this fixed NOW!. Total waste of money with the flakyness.

[QNAPJauss]

Dear jnelson2000 and fugle,

Please, i suggest you to contact our tech support so that they can confirm if it's the same issue or not.

Meanwhile, you can try this
- Connect to the NAS by SSH with the user admin.
- Edit the file /etc/config/smb.conf and add the line :
netbios aliases = nasname-nas
You can add it after "global" :
[global]
netbios aliases = yournasname-nas
Change "yournasname-nas" by a name different then the name of your NAS.

- save the file
- restart samba by : /etc/init.d/smb.sh restart

After that, you should be able to connect using the name you specify in the file "nasname-nas".

Hope this can help you while we try to identify the issue.

Please, can you give feedback and let us know if this way it is working.
Also, contact our technical support so they can check your configuration and environment.
Thank you.

BR,
Jauss

[fugle]

Thank you QNAPJauss.

Working now after putting the netbios alias in smb.conf

Fugle

[jnelson2000]

reying to edit the file logged in as admin and says permission denied.

[gregtnj]

I have had the same issue eg.

net use N: \\NASNAME\SHARE /USER:DomainName\DomainUserName <= Doesn't work.
net use N: \\X.X.X.X\SHARE /USER:DomainName\DomainUserName <= DOES WORK

I have boiled it down to a WINS issue. When I run nblookup (against the local WINS Server) on our network it doesn't contain an entry for NASNAME. A little bit more research shows that the machine that I am running this nblookup on is attempting to do the name resolution via WINS before DNS name resolution. I haven't had a chance to turn off WINS name resolution (As I'm not sure what else it will break). But from past experience on an AD network GET RID of WINS and run pure DNS for your name resolution.

For those running a DHCP Server serving IP info to your desktops, do a test to set it up to NOT advertise WINS server addresses to your clients. I think this is in DHCP server\Scope Options\General tab. Untick Options 44 and 46? Let me know what happens.

For the QNAP development team. I'd lay money that your SAMBA code isn't updating/advertising to the WINS Server correctly

Ill be testing this tomorrow morning when I get into the office and I turn our NAS back on that I accidently turned off instead of restarting.

Greg

[gregtnj]

Changing name resolution did not fix the issue. This what I tested.
- Disabled windows device from using WINS as a name resolution mechanism.
- Stopped DHCP server from advertising WINS server and Node type information to all clients.
- thought that it may have been something to do with the NAS havign port trunked ethernet ports, so untrunked and had only 1 ethernet port on the network.

I've had enough of being the debugger for QNAP for now.