Terastation AD User issue

[mushtie]

   

I am having problems as follows:

 

Terastation TS-RHTGL/R5 F/W 1.30 - 2TB Rackmount

 

A computer account has been created in AD and given pre-2K compatibility permissions.

 

Date and Time is within 3-5 Seconds on the server and terastation

 

Username is administrator and the password has no complexity problems i.e. No special characters used

 

IP address is static, Default Gateway and DNS have been set correctly.

 

Added to AD successfully no errors

 

 

Although when I go to the User Management I cannot obtain a list of AD Users.

 

I have removed Antivirus and Firewall products just in case and to help troubleshoot.

 

Any ideas would be gratefully appreciated 

 

 

[Colin137]

What version of Windows Server do you have? How many users are on the domain, and is the domain part of a larger domain?

[mushtie]

   

Server 2003 R2.

 

There are approx 40 users on the domain and it is a single domain, i.e. not a child domain or part of a larger company.

[Nox]

   

I had the same issue when I upgraded my firmware from 1.22 to 1.33.  It was working, but then it stopped pulling AD users.

 

I changed it back to a workgroup, applied the changes, then changed it back to Active Directory and all was happy again.

 

If that doesn't work, test the basics:  can you ping the terastation from the domain controller?  is there a firewall between you and the domain controller?  (if your domain controller has the Windows Firewall service started and enabled, stop the service and disable it for testing purposes).  They should not need to be on the same subnet, but it is something you can try.

 

I do not know if WINS is required, but we have a WINS server and did specify it in the configuration, and your NETBIOS name will be different from your DNS/Realm Name.

 

Hope that helps!

[mushtie]

   

Thanks for your reply..

 

We can successfully ping the terastation by hostname from anywhere in the network.

 

I am a little concerned about the Firewall as we use F-Secure but I have created an exception that allows all traffic from the IP address that has been reserved for the Terastation.

 

I will consider adding a WINs server as a temp basis to test, but I have been kind of ensured by Buffalo that WINs isn't needed.

 

Again thanks for your help so far.

[Jason]

You NEED to have something in the WINS box, if you don't have an actual WINS server just put in the IP of your DC.

[Nox]

   

Hmm, that's good to know.  We happen to have WINS on our DC, but we don't use it and have been wanting to get rid of it for some time.  That's just one less thing we have to worry about.

 

:)

[Colin137]

mushtie, try resetting it to defaults from Maintenance->Initialization, Restore, then set it up again. Make sure your time and time zone settings are correct, that the primary dns server is set to the ip address of the domain controller, and that you're putting the ip of the DC in the WINS server address.

[tparsons]

   

Hi

Same problem here except maybe 1 in 30 tries I can pull user names or group names but rest of time I get "cannot obtain" from users or "aquisition failure" from groups.  Did the about one get resolved and if so what was the solution?  Support has had me create computer name manually first, I have set back to factory defaults many times.  Tried many things like with or without WINS, pre 2000 or not pre 2000 computer name(when do name first in AD).  DC is on same site and no firewall between DC and TeraStation.  DC is Win 2003 SP2.  I have tried changing  back to work group then back to AD but no luck

Todd

[mushtie]

   

Hi,

 

This is still a problem...I have been speaking to Buffalo and they have said that they cannot help me anymore because it must be a problem with the network and not the terastation.

 

I have joined and rejoined the terastation countless amount of times.

Time is within 3 seconds

Created computer account first with pre-2000 compat

There are only 50 Users on the domain

Single domain name (not sub-domain)

Tested terastation on a test domain and it worked ok!!!

 

I have ran some network monitoring tools and I can see LDAP queries from the IP of the terastation hitting the domain controller but the only indication is a problem with the Digest MD5 having invalid credentials. I am currently researching this but unsure whether I am "barking up the wrong tree" yet.

 

I tried explaining my monitoring results to Buffalo but they seemed unable to discuss the matter either due to not knowing how LDAP works or just saying that there is nothing wrong with the terastation and it is a network/domain issue.

[tparsons]

   

Hi

 

Let me know if you don't have instructions for overwriting the firmware with same verison and I can get them to you-if you think it might help you with some testing. This is the only thing I could get from them when I called in for support.  They say they have never seen issue before yet online it looks like most people never had this issue until upgrading to the newer versions.  Over writing the firmware did nothing for me  and never even cleared out my settings like it was supposed to.

 

Todd

[mushtie]

   

I have already completed the Firmware update which apparently fixes a few AD issues but this has not resolved the problem I am experiencing.

 

Latest Firmware is 1.33

[tparsons]

   The instructions they sent me are for overwriting 1.33 with 1.33 incase you corrupt it or with an older version since normally it prevents this.  You modify the ini file in the install files....but no it did not help me.

[ggruen]

   

I had same troubles with resolving UserNames after upgrade to V1.33.

Final solution was to correct AD DomainName.

 

With previous version it worked with:

AD DomainName NETBIOS: GROUP.INTERNAL

AD DomainName DNS/Realm: GROUP.INTERNAL

 

Now I had to set:

AD DomainName NETBIOS: GROUP

AD DomainName DNS/Realm: GROUP.INTERNAL

[maverick2689]

   

I seem to be having close to the same problem.

 

The Terastation seems to be reading my AD groups, but not users.

 

ggruen:

 

So what you are saying is the entry should be like this

 

AD DomainName NETBIOS: acme

AD DomainName DNS/Realm: acme.com