TS-439 Pro and AD and Folder Browsing

[uanmi]

QNAP TS439 Pro
Firmware: 3.2.0 build 1212T
Connected to Active Directory using Administrator account

Server Name: MyQNAP
Domain NetBIOS Name: MyOffice
AD Server Name: MyServer
Domain: MyOffice.local

use the specified WINS server is selected

I'm trying to browse the QNAP from a Windows server 2003 and Windows 7
I can see and connect using \\192.168.2.xxx
If I use \\192.168.2.xxx I can copy files to the shares and read files from the shares

I can see the QNap in my list of devices when I click on the network icon in Windows Explorer
If I double click on the icon for MyQNAP then I get error 0x80070035
If I enter \\MyQNAP in the windows explorer browser I get error 0x80070035
I have tried with several computers and one windows server 2003 computer
I rebooted all devices including the QNAP.

I have two Buffalo Technologies NAS on the same subnet and they are AD integrated. I can browse and see them no problems. They have been on the network for several years with no problems.

I would appreciate some help please.
regards, Mark

[uanmi]

We got AD connected on the TS-439 Pro

Now none of the users can connect from the PCs. Keep getting an authentication error message. We have two Buffalo NAS that work with no problems on the same network.

We also cannot connect from our Beyonwiz PVR. Again the Beyonwiz can connect to Windows server 2003, Windows vista, Windows 7 and to the Buffalo NAS. The problem must be the QNAP.

Can a new firmware be made that works please.

regards
Mark

[QNAPJauss]

We got AD connected on the TS-439 Pro

Now none of the users can connect from the PCs. Keep getting an authentication error message. We have two Buffalo NAS that work with no problems on the same network.

We also cannot connect from our Beyonwiz PVR. Again the Beyonwiz can connect to Windows server 2003, Windows vista, Windows 7 and to the Buffalo NAS. The problem must be the QNAP.

Can a new firmware be made that works please.

regards
Mark

Dear Mark,

did you contact our tech. support for remote assistance ?

If you couldn't reach them, please PM me with your information ( Name, telephone, location, available time, remote connection setting...), I will manage to contact them directly to provide you assistance.

BR,
Jauss

[davispowers]

I have this same issue on a TS-659. The device connects to AD fine and you can see AD users and groups. When I try connecting to the device in Windows Explorer on XP, 7, 2003, or 2000 by typing \\qnap
I get a username and password prompt.

Tried these following domain username combos:
DOMAIN\username - fails
domain\username - fails
username@domain - fails
DOMAIN+username - fails - QNAP telephone support also tried this and failed for him also
domain+username - fails - also tried w/ QNAP support

How do I resolve this?

[uanmi]

Hi, QNAP technical support connected to my system and worked on it for two days. No result. They then told me they would find a solution and get back to me. Hopefully this will happen soon.

regards, Mark

[alael]

Having the exact same problem as davispowers on a Windows 2008 Small Business Server recently installed, and a QNAP TS-439...

[some1else]

Having the exact same problem as davispowers on a Windows 2008 Small Business Server recently installed, and a QNAP TS-439...

Same problem as you With SBS 2008 with SP2 and Windows 7 clients (AD Users).

When i browse \\192.168.0.100 (NAS IP) everything work, but not if i browse \\nas1 or \\nas1.domain.local

This is with v3.2.1 Build 1231 and TS-439PRO

[uanmi]

I would appreciate someone from QNAP letting everyone know what the situation is and then we can work out what to do. What I mean is are they going to fix this or do we have to find a new solution?

regards
Mark

[QNAPJauss]

Dear some1else, alael and davispowers

We are concerned by your issue and try to find a solution, but we cannot reproduce your issue in our lab.

For the original error message :

If I double click on the icon for MyQNAP then I get error 0x80070035
If I enter \\MyQNAP in the windows explorer browser I get error 0x80070035

is due to a name resolution error. If you are using WINS, please don't forget to setup the WINS configuration in the NAS in "Network Services > Microsoft Networking"

Also, please can you verify :
- your DNS setting (System Administration > Network > DNS server)
- Verify that your NAS name is present in your DNS server, and/or your WINS server.
- your DNS resolution : by a command line, from a workstation : " nslookup nasname" and "nslookup nasname.my.domain"
- if you are using WINS, you can verify your WINS resolution by command line :
Download NBLookup.exe command-line tool at http://support.microsoft.com/kb/830578
then :

Code: Select all

D:\nbt>nblookup.exe

NBLookup Interactive Mode

Type 'help' for a list of commands

Default Server: 10.8.2.11

Current option values:
   timeout=2 seconds
   retry=0 retries
   suffix=20
   recursion is on (recurse)
> server 172.17.23.230
Default Server: 172.17.23.230

> nasname          (YOUR NAS MANE)
Recursion is on

Querying WINS Server: 172.17.23.230
NetBIOS Name: NASNAME
Suffix: 20

Name returned: NASNAME
Record type: Unique
IP Address: 10.8.12.57       (YOUR NAS IP)


you should find your NAS ip address.

Don't hesitate to contact technical support to make sure about the problem.
If you still have the problem, please send me a PM and tell more about your environment topology and settings, information to contact you, so we can remotely connect to help.

BR,
Jauss

[some1else]

Still same problem here. anyone solved this yet ?

This is from the server, where zion is the AD, DNS and DHCP server (Not WINS Server).

Code: Select all

C:\Windows\system32>nslookup zion
Server:  zion.some1else.local
Address:  fe80::183b:8e05:e0ac:8d32

Name:    zion.some1else.local
Address:  192.168.0.1


C:\Windows\system32>nslookup zion.some1else.local
Server:  zion.some1else.local
Address:  fe80::183b:8e05:e0ac:8d32

Name:    zion.some1else.local
Address:  192.168.0.1


C:\Windows\system32>nslookup nas1
Server:  zion.some1else.local
Address:  fe80::183b:8e05:e0ac:8d32

Name:    nas1.some1else.local
Addresses:  fe80::208:9bff:febd:9bc0
          192.168.0.100


C:\Windows\system32>nslookup nas1.some1else.local
Server:  zion.some1else.local
Address:  fe80::183b:8e05:e0ac:8d32

Name:    nas1.some1else.local
Addresses:  fe80::208:9bff:febd:9bc0
          192.168.0.100


C:\Windows\system32>nslookup 192.168.0.100
Server:  zion.some1else.local
Address:  fe80::183b:8e05:e0ac:8d32

Name:    nas1.some1else.local
Address:  192.168.0.100

[uanmi]

The problem is being worked on at my site. When it is solved here, I will let everyone know.
Anyone that finds a fix should tell us all please.
regards, mark

[kimbilio]

Just found this post today, after installing a TS-509 late last week. I am also experiencing this problem. With the QNAP joined to a 2008 AD Domain, SMB connections from various different clients (Win 7, Server 2008) can only successfully be made using the IP address of the NAS. Attempts to connect using the DNS name result in a username/password prompt, and no variation of domain usernames/passwords will work.

I have followed the earlier suggestion about checking DNS and WINS records, and these are all correct. I've enabled the system connection logs on the NAS, and it's not even recording a login failure for the domain accounts I've tried. It does however record success for the correct domain user account when I connect using the IP address, and the connections show up in the on-line users log on the NAS.

This would obviously seem to be a problem with the qnap os, given we're all experiencing what seems to be exactly the same problem... How long until we get an update that fixes this?

Thanks,
Michael

[schumaku]

Michael,

An update was scheduled for today - no idea what went wrong.

Check release notes when the update becomes available.

-Kurt.

[jnelson2000]

I have been experiencing similar issues. I have 2 439 ProII and out of the blue started getting prompted for user and password. It is joinned to a 2008R2 domain and shows all the groups fine. Domain\Username fails. I have been removing and re-adding to AD and seems to wotk for a while but fails soon after. This is a royal PITA and needs to be fixed yesterday. I use these for backups and they keep failing because of this. Need update please.

[kimbilio]

Even after the most recent firmware update (3.2.3 Build 0209T), this still seems to be a problem. Adding the NAS to AD is not a problem, but shares can still only be accessed from clients using the IP address of the NAS - any attempts to connect using the hostname fail...

I'm not really familiar with samba, but are there any config options I should be looking to change to get this working correctly? Local DNS infrastructure is working fine, and names resolve ok from the clients, but I noticed in another thread (viewtopic.php?f=185&t=25608&start=0#p109612) that perhaps the nmbd process should be running, which, from what I can tell following the command in the post, it isn't. Should nmbd be running in this situation, and if so, how do I go about loading it?

Any ideas would be most appreciated.

Thanks,
Michael