D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: access on February 23, 2010, 02:35:39 AM
-
DNS343
Firmware 1.03 ADS 1.0
recently purchased dns343...
was attracted by the ADS support
Well that was a mistake...
after hours of messing around i finally log on here and after a few hours trolling and reading i find that the whole thing is fairly well broken......
I like other members have managed to get it partially working in AD....
That is i can see my users and user groups and can get the device to show in network list
Double clicking results in a password box that wont work
addressing the device via IP address allows full access no password...
creating a folder from any machine assigns that machines credentials only
any attempt at changing security on created folder fails....
can the Admins here please let me know when ver 1.04 fw will be released to fix these problems
and allow Ad to work properly???????? >:(
-
pasted from another thread 2 months ago......
Dlink people your flyer on this product says AD support?????????????
Please reply to me --- not flaming just want an answer
Re: ADS 1.0: Active Directory & Authentication Partially Broken
« Reply #12 on: December 17, 2009, 03:01:29 PM » Quote
--------------------------------------------------------------------------------
There hasn't been much response from D-Link Engineering on this one. I'm not certain if the silence should be taken as "will not fix", "we're so busy on projects it isn't funny any more", or "we're working on it ... but we're so busy on projects it isn't funny any more"
In any case, a quick response from their side would be most appreciated.
Cheers,
-
below was the most helpful post on the forums
however i got mine partially working without the corp. part
Please dlink engineers look into this before you add extra features
fix the ADS feature that doesnt work
this post below was 6 months ago
ADS 1.0: Active Directory & Authentication Partially Broken
« on: September 23, 2009, 03:20:39 PM » Quote
--------------------------------------------------------------------------------
Hi All,
After some research, I've succeeded in getting 'Active Directory' functionality to work with F/W 1.03 & ADS Package 1.0. I've managed to accomplish some connectivity (authentication) by configuring the Device Settings with:
Username : DNSAdmin <A/D Account /w Domain priviledges>
Password : DNS343b4605a!
DNS1 : Provided via DHCP <A/D Integrated>
DNS2 : Provided via DHCP <A/D Integrated>
Host Name : DNSTORNAS01
Workgroup : TERRAFLORA
Realm Name: CORP.TERRAFLORA.COM <internal A/D domain, NetBIOS is terraflora>
AD Server : DC1terraflora01
Note that the DNS-343 and test workstation were restarted between tests.
TESTS:
1) Behavior when selecting Active Directory as the Network Type so as to allow the DNS-343 to join the domain:
RESULT:
•The computer object appears in A/D as expected - displays a 'success' message.
•Moving the object to an OU still allows access to the object from 'Microsoft Windows Network'
'Microsoft Windows Network'
•The DNS-343 object (DNSTORNAS01) appears as expected in TERRAFLORA.
2) Behavior when attempting to connect using DC1TERRAFLORA (Domain Controller, LMCompatibilityLevel=2):
RESULT:
•Double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network' displays the username/password prompt.
•Using the IP Address (\\###.###.###.###) displays the shared object contents.
EXPECTED BEHAVIOR:
•Shared object contents should have been displayed when double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network'
•Selecting an object displayed inside DNSTORNAS01 should prompt for credentials if required.
3) Behavior when attempting to connect using a domain workstation (LMCompatibilityLevel=0, LMCompatibilityLevel=2, and/or LMCompatibilityLevel=3):
RESULT:
•Double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network' displays the username/password prompt.
•Using the IP Address (\\###.###.###.###) displays the shared object contents.
EXPECTED BEHAVIOR:
•Shared object contents should have been displayed when double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network'
•Selecting an object displayed inside DNSTORNAS01 should prompt for credentials if required.
4) Behavior when attempting to connect by mapping the resource using a command prompt:
NET USE X: \\DNSTORNAS01\Volume_1 /USER:<username> *
NET USE X: \\###.###.###.###\Volume_1 /USER:<username> *
RESULT:
•The drive letter is successfully mapped.
5) Account Name/Password supplied at prompts throughout the tests:
RESULT:
•Account name and password supplied had to be:
Username: <REALM>\<username> (ex: CORP\Administrator)
Password: <password> (ex: DNS343b4605a!)
EXPECTED BEHAVIOR:
•Should have had to supply the following:
Username: <WORKGROUP>\<username> (ex: TERRAFLORA\Administrator)
Password: <password> (ex: DNS343b4605a!)
In summary, there continues to be an issue with prompting for username/password when initially double-clicking the DNS-343 object from 'Microsoft Windows Network'. Additionally, there appears to be and issue with the credentials that need to be passed for authentication; in my tests, I should have had to supply TERRAFLORA\<username> and not CORP\<username>.
Cheers,
-
wondering if you got any further with the ad hook up
i have similar connection
but didnt use the corp. before domain
a question if you dont mind ,,,,
why did you use corp.
the realm field should have FQDN...
i have tried many variations ,,,but works best with just the domain part
eg .....
but refuses to allow me to change any permissions on folders..
Posted here in case others wish to correct, elaborate, respond, and/or comment.
The ADS 1.0 package functionality is broken in several ways as you have discovered. And don't bother with the W2K8, it simply isn't supported - period.
Authentication
For authentication in my W2K3 A/D domain, I should have been able to authenticate in either fashion:
username: <pre-W2K>\username (ex: terraflora\testuser)
and/or
username: <fqdn>\username (ex: corp.terraflora.com\testuser)
username: username@<fqdn> (ex: testuser@corp.terraflora.com)
Instead, I had to use:
username: <first_dotted_part_fqdn>\username (ex: corp\testuser)
The users and computer objects in my domain reside in an OU container such as: .\MyBusiness\Users and .\MyBusiness\Computers leaving the standard OU containers as "default" as possible. This is similar in design to MS SBS 2K3 where the objects do not reside in the default A/D Users & Computers OU container.
Folder Permissions
Not possible as the file system on the DNS-343 is EXT2/3 ... at least not without some form of 'fun_plugging' or other hack - which shouldn't be required IMHO.
From what I gather, joining the DNS-343 to an A/D domain should allow an Administrator to control access to shared folders by assigning user/group to a shared folder. An Administrator would assign 'Administrative' access to the 'Volume_##' folders to prevent direct access by others, share folders, and assign user/group as required to the shared folder.
HTH,
-
Thanks for posting so quickly hilaireg
What's annoying is there seems to be no response from Dlink on this....
They have released and adverstised this functionality and it doesnt work...
The problem is there and easily found (replicated)
they seem to be working on other features rather
than fixing the ones that are busted...
Unfortunately I dont have the luxury to wait if a fix isnt coming SOON...
Need to move shared folders and "ad" user/group security from server drives
to a quality NAS
Will be returning the DNS343 and getting something that really supports "AD"
not just advertised to support it
should not be advertising it in there flyers
Correct me if im wrong isnt this false advertising??.
Their lack of replies on here also shows little respect for their customers.
I am in charge of a fairly sizable IT budget
and its experiences like this that don't go down well.
Peter - Dissappointed
-
You are right, AD does not work as it should on this unit. Anyone who wants an AD supported box should try something else. Worse than the fact that AD just doesn't work as it should, if you try to go backwards from AD the box crashes. Right now mine will not boot and of course I have data on it I need to get to.
-
Thanks to my reseller (MediaByt)
I have gotten a response from Tech support Australia _sydney
Speaking with Danny and Dean & Dlink See belowreply to my reseller
Graeme,
We are working on the issue with our development team in Taiwan, I cannot give you a eta at this stage, if the customer does not want to wait I can offer you a credit back via your distributor
Dean Williams
Consumer Product Manager
D-Link Australia Pty. Ltd. Head Office (Sydney)
Building A, Level 3, 11 Talavera Rd
North Ryde, NSW, 2113
Direct:
Fax:
Mobile:
Email:
Web: +61 (0)2 8899 1800
+61 (0)2 8899 1883
+61 (0)2 8899 1868
+61 (0)409 173 615
dwilliams@dlink.com.au
http://www.dlink.com.au
I have contacted Danny@Dlink directly and asked for a tighter time frame on the fix as it
will influence my decision on keeping the box.
I suggest other people do the same abs this migh speed up the process
will keep the forum advised on the reply from Danny/Dean
-
Posted here in case others wish to correct, elaborate, respond, and/or comment.
The ADS 1.0 package functionality is broken in several ways as you have discovered. And don't bother with the W2K8, it simply isn't supported - period.
Authentication
For authentication in my W2K3 A/D domain, I should have been able to authenticate in either fashion:
username: <pre-W2K>\username (ex: terraflora\testuser)
and/or
username: <fqdn>\username (ex: corp.terraflora.com\testuser)
username: username@<fqdn> (ex: testuser@corp.terraflora.com)
Instead, I had to use:
username: <first_dotted_part_fqdn>\username (ex: corp\testuser)
The users and computer objects in my domain reside in an OU container such as: .\MyBusiness\Users and .\MyBusiness\Computers leaving the standard OU containers as "default" as possible. This is similar in design to MS SBS 2K3 where the objects do not reside in the default A/D Users & Computers OU container.
Folder Permissions
Not possible as the file system on the DNS-343 is EXT2/3 ... at least not without some form of 'fun_plugging' or other hack - which shouldn't be required IMHO.
From what I gather, joining the DNS-343 to an A/D domain should allow an Administrator to control access to shared folders by assigning user/group to a shared folder. An Administrator would assign 'Administrative' access to the 'Volume_##' folders to prevent direct access by others, share folders, and assign user/group as required to the shared folder.
Hi as I know, the account of 343 is managed by Samba, so if you want to change the permission, you need to logon to the UI and make such changes.
HTH,
-
below was the most helpful post on the forums
however i got mine partially working without the corp. part
Please dlink engineers look into this before you add extra features
fix the ADS feature that doesnt work
this post below was 6 months ago
ADS 1.0: Active Directory & Authentication Partially Broken
« on: September 23, 2009, 03:20:39 PM » Quote
--------------------------------------------------------------------------------
Hi All,
After some research, I've succeeded in getting 'Active Directory' functionality to work with F/W 1.03 & ADS Package 1.0. I've managed to accomplish some connectivity (authentication) by configuring the Device Settings with:
Username : DNSAdmin <A/D Account /w Domain priviledges>
Password : DNS343b4605a!
DNS1 : Provided via DHCP <A/D Integrated>
DNS2 : Provided via DHCP <A/D Integrated>
Host Name : DNSTORNAS01
Workgroup : TERRAFLORA
Realm Name: CORP.TERRAFLORA.COM <internal A/D domain, NetBIOS is terraflora>
AD Server : DC1terraflora01
Note that the DNS-343 and test workstation were restarted between tests.
TESTS:
1) Behavior when selecting Active Directory as the Network Type so as to allow the DNS-343 to join the domain:
RESULT:
•The computer object appears in A/D as expected - displays a 'success' message.
•Moving the object to an OU still allows access to the object from 'Microsoft Windows Network'
'Microsoft Windows Network'
•The DNS-343 object (DNSTORNAS01) appears as expected in TERRAFLORA.
2) Behavior when attempting to connect using DC1TERRAFLORA (Domain Controller, LMCompatibilityLevel=2):
RESULT:
•Double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network' displays the username/password prompt.
•Using the IP Address (\\###.###.###.###) displays the shared object contents.
EXPECTED BEHAVIOR:
•Shared object contents should have been displayed when double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network'
•Selecting an object displayed inside DNSTORNAS01 should prompt for credentials if required.
3) Behavior when attempting to connect using a domain workstation (LMCompatibilityLevel=0, LMCompatibilityLevel=2, and/or LMCompatibilityLevel=3):
RESULT:
•Double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network' displays the username/password prompt.
•Using the IP Address (\\###.###.###.###) displays the shared object contents.
EXPECTED BEHAVIOR:
•Shared object contents should have been displayed when double-clicking the DNSTORNAS01 object from 'Microsoft Windows Network'
•Selecting an object displayed inside DNSTORNAS01 should prompt for credentials if required.
4) Behavior when attempting to connect by mapping the resource using a command prompt:
NET USE X: \\DNSTORNAS01\Volume_1 /USER:<username> *
NET USE X: \\###.###.###.###\Volume_1 /USER:<username> *
RESULT:
•The drive letter is successfully mapped.
"Look like 2 & 3 caused by the same problem, only can access through ip but not netbios name. But according to your test, with "Net" command, it works well with both IP and Netbios name"
5) Account Name/Password supplied at prompts throughout the tests:
RESULT:
•Account name and password supplied had to be:
Username: <REALM>\<username> (ex: CORP\Administrator)
Password: <password> (ex: DNS343b4605a!)
Hi Access, why logon in this way is wrong. I check my NAS with other branded, it can logon in this way too. As 343 is a device inside a domain, it should be ok to logon in this method.
EXPECTED BEHAVIOR:
•Should have had to supply the following:
Username: <WORKGROUP>\<username> (ex: TERRAFLORA\Administrator)
Password: <password> (ex: DNS343b4605a!)
In summary, there continues to be an issue with prompting for username/password when initially double-clicking the DNS-343 object from 'Microsoft Windows Network'. Additionally, there appears to be and issue with the credentials that need to be passed for authentication; in my tests, I should have had to supply TERRAFLORA\<username> and not CORP\<username>.
Cheers,
-
dlink support is awful when it comes to this issue. They should just admit that it doesn't work. Instead, they have me running in circles with the device doing all kinds of things that were a complete waste of time.
-
@access,
If you have check the posts in this forum, I trust you will find mine, hilaireg and a few others on Active Directory related issues. Well, we have waited for few months now and still no sign of real Active Directory support. In fact, I have waited since its early firmware prior to 1.02 for Active Directory support. Again and again, I am getting disappointment after disappointment.
If use of DNS-343 with Active Directory and real NAS manageability is what you are looking for, then just return and refund. It's pointless to wait for fix when the next firmware release would most likely be not a full fix that truly fully supports Active Directory that is expected of a true NAS.
I have given up and in mist of replacement - QNAP. Though more expensive, it truly provides manageability of what's expected of a NAS (even for its non-Pro series).
-
@access,
If you have check the posts in this forum, I trust you will find mine, hilaireg and a few others on Active Directory related issues. Well, we have waited for few months now and still no sign of real Active Directory support. In fact, I have waited since its early firmware prior to 1.02 for Active Directory support. Again and again, I am getting disappointment after disappointment.
If use of DNS-343 with Active Directory and real NAS manageability is what you are looking for, then just return and refund. It's pointless to wait for fix when the next firmware release would most likely be not a full fix that truly fully supports Active Directory that is expected of a true NAS.
I have given up and in mist of replacement - QNAP. Though more expensive, it truly provides manageability of what's expected of a NAS (even for its non-Pro series).
Yep ......I think even in the short time here I am very dissapointed...
No contact back from the email sent to Sydney office...
so its a return it to them...funny you mention QNAP as i have already marked that as a replacement if necessary
-
If you would like to beta 1.04 with ONLY the ADS fix please contact me by Private Message.
-
and just another note...but this version should work with Windows 2008 as well.
-
I'm running into the same troubles plus a couple others.. the ADS authentication stops working after a couple days and the only solution is to stop and start the addon, at that point it starts working again. This is not a good solution, so I tried uninstalling the ADS plugin.
It uninstalled OK but now all the screens to setup the built in security are all still disabled! Is there any way to go back to regular security without copying all the data off the drive, reformatting, and copying it back?
Edit:
Bonus: now it's forgetting my shares and making them reconfigure them when I restart the plugin >:(
-
Has anyone the 1.04 beta, or can help in in the AD Case?
Need it very urgently!
Kinds regards
Malte
-
Has anyone tried the ADS in new 1.04 beta fw ?
-
I've seen some postings on other sites saying someone got the 1.04 firmware and it helped him with his ADS issues, can someone please send it to me?
-
Send me a PM on the boards with your email if you want to try beta 1.04.
-
I'm really reluctant to try the AD support again, as I have a whole department working from this DNS 343. Problem is, with SMB user/groups I have continual problems with users creating folders that no one else can access. No way to reset permissions to what they should be?
My setup is matched user accounts/passwords for all the graphics department, through a single share, giving all users R/W. Still there are folders that get created Read only for all but the owner/creator!
Please Dlink engineers, let's have a way to control these permissions!
Dwayne Matthews
I.T. Director
Nood Furniture and Design Ltd
-
Send me a PM on the boards with your email if you want to try beta 1.04.
I have a question before I try a beta:
If I take off my current RAID with 1.03fw, install new drives and beta 1.04fw, decide I want to go back to 1.03fw and my old data, will this work? or will my old RAID and data be lost?
I don't want to beta with real important data, but have enough hard drives to experiment with a new set of drives and see if the AD issues is truely resolved with Win2K8R2
-
Ok, so I had to do a work around as there was too much disruption to the workflow in the graphics/web department....
So I
1. setup my FTP client and saved logins matching ALL the teams user accounts and passwords to login to the DNS 343
2. I can use Windows explorer to browse a folder that someone's created and everyone else is either read only or no access at all... choose properties of the folder, security tab, and I can at least SEE who is the owner, even though I can't take ownership or change or access thecontents....
3. Now I use the FTP client to login as the "owner" of the folder in question, and view the properties of that folder... where I can change the properties to allow EVERYONE to read and write (777)!
Now everyone in my department can work on the files/folders. I have sent a procedural email to all parties, to email me whenever they find a folder they can't access, then I will set the permissions.
NOw, all you network administrators out there... Isn't this RIDICULOUS! A product released on the market advertising Active Directory support, and this is what we have to do to keep USING IT!!!!!
I for one am not impressed with this company's level of professionalism in the marketplace. Where's the leadership, quality assurance, etc?
Dwayne Matthews
I.T. Director
-
Dwayne
Can't agree more
Although as the starter to this thread. they have reacted quite quickly for me in the release of version 1.04 firware.
So FTP in does allow the saving of permissions changes....
I tried in the normal way as the owner creator of folders to change permissions but it refuses to stick and reverts back to the creator as the only write read priveledge...
Interesting if the FTP module is correctly allowing permissions to be set. Or is it just allowing full read write priveldges - bypassing AD completely...
BTW.... I will be returnming my unit as its jut too unstable to trust with my companies and users data...
Hope FW 1.04 corrects the issue for all others that dont have the Return option.
IT Manager
Access
-
Yes, 'access', actually, the FTP program I am using is SmartFTP, and I am only really getting by on "fully opening" permissions to '777'. EVen though I can use windows exporer and view the permissions in the security tab before I use the FTP program, AFTER I change to full access, I can't view any permissions, even though everyone can then access the folder.
Essentially, this is a very 'temporary' way to make is work. I wish I had the luxury of packing it up and buying a new NAS, something higher quality and proven, but the reason I bought this DNS343, is because is met a very tight budget. The proven network solutions seemed much more costly.
-
Must admit based mine purchase on the simple line supports AD....
Hmmmmmm next time I think more homework (look in afew forums first)
I just dont belive that this problem has been around for so long
yet they (Dlink) continue to advertise and sell the product as supporting ADS
I love the computer industry,,the only place you can buy something not working
then pay through the nose for patches and upgrades :).
My time spent on this to date is ridiculous.....
I forgot to ask in my last post.....
Please anyone who has tried the BETA Firmware 1.04 for ADS post your findings
Im sure this forum has many lurkers wanting to know the answer..
The QNap has a good reputation..yes more expensive but least will do what it advertises..
-
I've been monitoring the A/D related thread(s) for a while ... actually since my original post(s) ... in the hopes that resolution would arrive in a timely fashion.
Guess what? Still waiting ...
What additionally confuses me is that F/W 1.03 was available in BETA, similarly to what is going on with F/W 1.09 for the DNS-323. Yet; for F/W 1.04, a PM is required. At the moment, I'm sitting on two DNS-343's which can't be put into service as the administrative nightmare of daily "folder level" and DNS specific account management is too time consuming ... not to mention ineffective.
IMHO, this issue should have been resolved many months ago. As a result of the delays and lack of response, D-Link has lost potential revenue as I cannot recommend the unit to my SBS business clients.
:(
* EDIT *
I'm also getting tired of having to upgrade F/W on a regular basis as well as being an unpaid member of the QA, Alpha, and Beta departments.
-
Here, here! ...beta trial guinea pigs, 1 year or often more after release to the market place!
I've come to accept that to some degree, but it's still not acceptable to advertise something that clearly hasn't worked for so long. The AD point was a big selling factor for me.
My fantasy is to actually force the owners of companies like this to 'read' the forums and frustrations of their 'guinea pigs'
-
Here are my findings with the 1.04 beta firmware. My big problem in both 1.03 and 1.04 is AD authentication stops working every couple days and I have to restart the ADS addon. If anyone has any suggestions for a fix I'd love to hear them. Maybe it's falling off the domain? I am seriously considering setting up our old DNS-323 again and backing the whole thing up and resetting it to factory defaults so I can go back to the built in security.
AD Server: Win 2008R2, x64
Good:
- I can now map to a drive using the name of the NAS rather than the IP address.
- Before I had one workstation out of several that would not connect no matter what I tried, it can now connect
Bad:
- After it has been running for a few days, my drive mappings to the NAS still stop working. I have to stop and start the ADS addon then they start working again.
(could the NAS be falling off the domain and then re-registering when I restart the addon?)
-If I uninstall the ADS addon, all the options to setup the onboard user accounts are still grayed out.
-
After it has been running for a few days, my drive mappings to the NAS still stop working. I have to stop and start the ADS addon then they start working again.
(could the NAS be falling off the domain and then re-registering when I restart the addon?)
Noticed the same thing with the ADS 1.0 add-on. When this occurs, I observed that trying to view any folders with a "working" user account (ex: corp\johndoe) ceases to function as well.
-
Noticed the same thing with the ADS 1.0 add-on. When this occurs, I observed that trying to view any folders with a "working" user account (ex: corp\johndoe) ceases to function as well.
Thanks will look into it to see where the issue is.
-
I don't feel like a guinea pig, I feel like a real sucker. I used to recommend D-link as a good value for your technical dollar. After trying to get AD to work with the DNS-343, I can no longer recommend or sell
D-Link products and feel I am doing my customers justice. I am very disappointed that a network product will not work with the largest standard in file server networking, being Active Directory. If it doesn't work with AD, just say that and be honest. I can respect and appreciated an honest answer.
Really, how hard can it be to get things working with AD?
Please send me the 1.04 beta or make it available for download.
-
Well I couldn't connect again today so I went to restart the addon again..
Web admin page was not responding. Could not ping the box.
Tried shutting it down with the button on the front.. just went into an eternal 'shutting down...' display.
Eventually had to unplug it and plug it back in. Now it's responding to pings but the web page is still unavailable and the drive maps are not there.
I fear I may have lost a lot of data. Is there any kind of emergency recovery procedure?
-
If everything else fails, try to use R-Studio 5 in order to recover the data from the disks in a normal computer. In another topic here is described how to set the parameters (you may check the tutorial from R-Studio website for recovering data from RAID5 volumes too).
I never tried it personally but theoretically it can be done.
-
If everything else fails, try to use R-Studio 5 in order to recover the data
Wow, that looks like an amazing tool, I didn't know such a thing existed. Next time I am at the NAS I will make sure to number my drives with a marker, looks like it might help knowing the physical order they were in if things go really wrong.
My DNS-343 eventually recovered, it seems like during the intial stages of the recovery (sync?) the web server goes unavailable. 40 hours later.. sync was done and it's working again. Not sure if my hang was related to the beta firmware or not as I see others with this issue on the forum. I didn't see this in the few weeks I ran it before the beta update.
-
Glad to see your DNS is fine now.
Yes it's a good idea to number your drives. I already did this some time ago on my drives. I believe that no.1 is at the top.
-
Glad to read that you were able to access the data on the RAID. That said, yes I know you know what I'm going to say next ... ;)
BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP BACKUP
... and oh yes, BACKUP BACKUP
Always remember that RAID is meant for real-time protection of data until the failed member is replaced. It is not a replacement for a proper backup solution.
:)
-
My important data is not on this raid, it's on a 300 Mb raid on my server that is backed up and offsited daily. Unfortunately, backing up a 6tb NAS is beyond my finances at the moment. Most of it is backed up. It wouldn't be the end of the world if I lost some files, I'd be disappointed if it was lost in a fire, robbery, etc but i'd hoped to not lose it to buggy firmware.
Edit:
Well, happened again I guess it'll be usable in another 40 hours.
-
I have the same issue with the NAS not working with ADS after a few days.
Fortunately - D-link login security is so bad, that you can access the form-script, if you have the direct URL.
So I made a VBScript, which I run once every night as a scheduled task. Hopefully, this will fix my problems.
The script simple stops the ADS service and then starts it again:
'---------------------------------
Dim NasIP
NasIP = "192.168.1.3"
Set objHTTP = CreateObject("Microsoft.XMLHTTP")
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=0"
Set objHTTP = Nothing
Set objHTTP = CreateObject("Microsoft.XMLHTTP")
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=1"
Set objHTTP = Nothing
'---------------------------------
Hope this is usefull to others - please comment
/MD
-
I have the same issue with the NAS not working with ADS after a few days.
Fortunately - D-link login security is so bad, that you can access the form-script, if you have the direct URL.
/MD
Wow, that is great! I was thinking about doing the same thing but my VBS is rusty. Interesting it is not password protected. Thank you !!
:D :D :D
FYI, my crashing problem keeps reoccuring when I try to overwrite a particular file.. I ran every scan disk and diagnostic under maintenance and they all came back 'OK'. So I just renamed the file "DONOTDELETEME" ::)
-
Wow, that is great! I was thinking about doing the same thing but my VBS is rusty. Interesting it is not password protected. Thank you !!
:D :D :D
FYI, my crashing problem keeps reoccuring when I try to overwrite a particular file.. I ran every scan disk and diagnostic under maintenance and they all came back 'OK'. So I just renamed the file "DONOTDELETEME" ::)
The fix has not been applied to 1.04 yet for Add-On's but it is already live in 1.08 for DNS-323. On final release that 'hole' wont be there.
After renaming your file the ADS no longer crashes at that part of copying?
-
The fix has not been applied to 1.04 yet for Add-On's but it is already live in 1.08 for DNS-323. On final release that 'hole' wont be there.
After renaming your file the ADS no longer crashes at that part of copying?
No, ADS still crashes.. I have a file that whenever I try to overwrite it, it causes my DNS-343 to hang and not shut down. I have to unplug the box. May or may not be related to ADS.
Also, MD's script is not working for me... it runs but ADS doesn't get shut down. Maybe this got fixed in the beta firmware... I'll try and tweak it to go through the login process
-
So I made a VBScript, which I run once every night as a scheduled task. Hopefully, this will fix my problems.
I had to add the login process to the script then it started working for me.. note you have to re-login after stopping it.
Dim NasIP
NasIP = "192.168.12.131"
Set objHTTP = CreateObject("Microsoft.XMLHTTP")
objHTTP.open "POST", "http://" & NasIP & "/web/login.asp?id=9999", False
objHTTP.send "f_LOGIN_NAME=admin&f_LOGIN_PASSWD=mypassword"
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=0"
objHTTP.open "POST", "http://" & NasIP & "/web/login.asp?id=9999", False
objHTTP.send "f_LOGIN_NAME=admin&f_LOGIN_PASSWD=mypassword"
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=1"
Set objHTTP = Nothing
-
Here are my findings with the 1.04 beta firmware. My big problem in both 1.03 and 1.04 is AD authentication stops working every couple days and I have to restart the ADS addon. If anyone has any suggestions for a fix I'd love to hear them. Maybe it's falling off the domain? I am seriously considering setting up our old DNS-323 again and backing the whole thing up and resetting it to factory defaults so I can go back to the built in security.
AD Server: Win 2008R2, x64
Good:
- I can now map to a drive using the name of the NAS rather than the IP address.
- Before I had one workstation out of several that would not connect no matter what I tried, it can now connect
Bad:
- After it has been running for a few days, my drive mappings to the NAS still stop working. I have to stop and start the ADS addon then they start working again.
(could the NAS be falling off the domain and then re-registering when I restart the addon?)
-If I uninstall the ADS addon, all the options to setup the onboard user accounts are still grayed out.
Hello, how many ad users do you have?
-
Hello, how many ad users do you have?
35 users total but only a few are active. The only reason I have an AD server is I am a software developer and need it for developing against.
As a side note, that script seems to have done the trick for me except for the programs that gripe about the drive disappearing during the restart every night.
-
35 users total but only a few are active. The only reason I have an AD server is I am a software developer and need it for developing against.
As a side note, that script seems to have done the trick for me except for the programs that gripe about the drive disappearing during the restart every night.
Did you do file copying or any specified operation before the authentication stops? I am wondering what could be the problem? I have been power on my 343 with AD server authenticated for a week, it is still working properly. Is anyone here have the same problem?
-
I have the same issue with the NAS not working with ADS after a few days.
Fortunately - D-link login security is so bad, that you can access the form-script, if you have the direct URL.
So I made a VBScript, which I run once every night as a scheduled task. Hopefully, this will fix my problems.
The script simple stops the ADS service and then starts it again:
'---------------------------------
Dim NasIP
NasIP = "192.168.1.3"
Set objHTTP = CreateObject("Microsoft.XMLHTTP")
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=0"
Set objHTTP = Nothing
Set objHTTP = CreateObject("Microsoft.XMLHTTP")
objHTTP.open "POST", "http://" & NasIP & "/goform/Module_Enable_Disable", False
objHTTP.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
objHTTP.send "f_module_name=ADS&f_enable=1"
Set objHTTP = Nothing
'---------------------------------
Hope this is usefull to others - please comment
/MD
Could I know what AD server is in used?
-
Could I know what AD server is in used?
I am not sure what you question is?
The AD service is running on a Windows 2003 Small Business Server.
-
I am not sure what you question is?
The AD service is running on a Windows 2003 Small Business Server.
Sorry, what I mean is : are you using 2003 server 32bits/64bits or 2008 server 32bits/64bits?
-
Sorry, what I mean is : are you using 2003 server 32bits/64bits or 2008 server 32bits/64bits?
It is a Windows 2003 Small Business Server 32-Bit.
-
It is a Windows 2003 Small Business Server 32-Bit.
I am trying the v1.04b02 f/w without any problem with Server 2003 32bits and Server 2008 32bits. Did you ever try this beta f/w?
-
Just a followup that may make it easier for the dlink techs to reproduce this problem...
I notice when I reboot my (sole) active directory machine and bring it back up, no one can connect to the DNS-343. It looks similar to what happens when I have to restart the ADS add-on. May or may not be the same issue.
-
Just a followup that may make it easier for the dlink techs to reproduce this problem...
I notice when I reboot my (sole) active directory machine and bring it back up, no one can connect to the DNS-343. It looks similar to what happens when I have to restart the ADS add-on. May or may not be the same issue.
So, you mean when you restart the Active Directory Machine which is a Windows PC will cause disconnection from 343, right? Could I know how many ads users in your environment?
-
So, you mean when you restart the Active Directory Machine which is a Windows PC will cause disconnection from 343, right? Could I know how many ads users in your environment?
Seemed like this would happen.. although after I made that post I had to reboot the ADS and it didn't do it the second time. However, the day after that the DNS-343 froze for the third time since I bought it, requiring a power off an on followed by a 48 hour raid sync with extremely degraded performance.
Decided to cut my losses, given up and ordered a NAS from a different company, the time I have wasted on this box has far exceeded it's purchase price.
-
Finally, after so long, full Active Directory support.
With the firmware 1.04 beta 03 and the ADS add-on 1.01, full active directory support and windows support.
- Active Directory in Native Modes (Windows 2008 Native, Windows 2003 Native) in Forest (parent domain, child domains, child-child domains)
- Active Directory 64-bit Support
- Windows Vista, Windows 7 and Windows 2008 Support
Now the shares on DNS-343 is accessible with permissions set using active directory groups (even if there is a space in the group name), no longer need to change the security policy of Windows Vista/7/2008, and accessible via FQDN in UNC.
-
Finally, after so long, full Active Directory support.
With the firmware 1.04 beta 03 and the ADS add-on 1.01, full active directory support and windows support.
- Active Directory in Native Modes (Windows 2008 Native, Windows 2003 Native) in Forest (parent domain, child domains, child-child domains)
- Active Directory 64-bit Support
- Windows Vista, Windows 7 and Windows 2008 Support
Now the shares on DNS-343 is accessible with permissions set using active directory groups (even if there is a space in the group name), no longer need to change the security policy of Windows Vista/7/2008, and accessible via FQDN in UNC.
Thank you for your feedback. I am glad to hear it is up and running under your environments!
-
I have 1.04Beta 2 and AD 1.00. AD stopped working so I went back to WORKGROUP. DLink Support are you able to direct me to 1.04Beta 3 and AD 1.01 or should I send you an email?
Cheers.
-
I have 1.04Beta 2 and AD 1.00. AD stopped working so I went back to WORKGROUP. DLink Support are you able to direct me to 1.04Beta 3 and AD 1.01 or should I send you an email?
Cheers.
Beta 3 is in the Beta Code section of this forum.
http://forums.dlink.com/index.php?board=250.0
-
it's okay up to work firmware 1.04 . please download here
http://forums.dlink.com/index.php?topic=13099.0
Thanks all