Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Wilson]

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?

[md]

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.

[Wilson]

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?

[md]

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.

[Wilson]

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?

[tailslide]

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.

[Wilson]

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?

[tailslide]

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.

[chaicka]

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.

[D-Link Multimedia]

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!

[Robbo]

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.

[chaicka]

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

[phongpq]

it's okay up to work firmware 1.04 . please download here
http://forums.dlink.com/index.php?topic=13099.0

Thanks all