Buffalo Forums

I have a TeraStation PRO which I purchased about a year ago The person on the phone explained to me that Active Directory compatibility will not be a problem. After owning another TeraStation, I was pleased with the product and didn't have much complaints.

Behold, I upgrade my systems to 2008 Active Directory, and now my TeraStation is incompatible. I am unable to join the domain, and If i do i have lots of trouble with the users being integrated into the NAS. Now, even if i get it by using workarounds, the system does not let anyone in leaving us completely out of options but to run in on a workgroup - which defeats the entire purpose of security.

Now is there a fix or is there not a fix? Is there ANYTHING I can do to get this thing functional on a 2008 R2 domain controller? All I have heard from reps at Buffalo is that "We should have a fix in 1-2 months"

Its been over 2 years!!!!!!!!!

How long do you expect your customers to wait for your fix to come out? We have been anticipating this "fix" forever, and instead we buy a product that is barely up to technology. You guys need to wrap it up and make your fix or give me a refund for this product that CLAIMS to work with active directory and DOESNT!

PLEASE HELP.

**SIGH**

Yes it does work with server 08 and AD. Upgrade to FW 1.33 or did you just miss this before going on your pointless rant.

Taken from the 1.33 release notes: "Support for AD on Server 2008, Vista SP1 AD issues fixed, add NFS and HTTPS support"

Model Name

---

teamaamaster wrote:

You don't have a TS-RHTGL

---

No, i have an TS-HTGL/R5 which is the same unit just not rackmount. Tested and works fine with Server 2008 R2, whats the actual errors you are getting?

I was able to join the domain, however - the users were not populated. So i rejoined again - I had to do this 2-3 times before everything "seemed" to work.

Now I am unable to browse by IP \\192.168.1.x, the only place im able to do it from is the domain controller, and only by name \\terastation

YAY for double posts!  The IP you had it set to was 192.168.10.1 according to another thread which I suggested setting it to 192.168.10.150 to avoid a networking conflict but now the IP subnet has changed so try setting it to 192.168.1.150 and see if that resolves it.  Please don't start more than one thread for an ongoing issue.