LS-WX2.0 0TL/R1 Firmware 1.65 Fail to join domain

[Lea]

Hi,

I come here because we are in trouble in my company.

We bought a Linkstation Duo, it seems ok but not to join Active Directory.

Our Domain controller is a Windows 2008 server. I had a look on the web to know what are restrictions to join the Buffalo to the domain but nothing works.

- Time settings is ok. Time is within 5 minutes on Linkstation and server
- I added the nas in forward and reverse DNS lookup entries
- IP and domain settings are ok
- The NetBIOS DNS and realname are ok too
- I use an domain administrator account with no special characters inside the name and password

When I add the NAS in the NT domain it works but not Active Directory. Always the same message "Failed to join domain".

I don't understand why it doesn't work. We still have some linkstation LS-WTGL/R1-V3 F/W 3.10 on lan and it works fine. It's totally incomprehensible.  :o

It would be nice if somebody has an idea and could help us please?

[Eastmarch]

- I added the nas in forward and reverse DNS lookup entries
...
- The NetBIOS DNS and realname are ok too

Lea, I've had some luck setting the DNS server on the LinkStation manually (as part of IP setup), and in addition to having actual DNS servers, having the Domain Controller's IP be an entry. That may force you to static IP at least during setup. Give that a shot.

[Lea]

Hi Eastmarch,

Thanks for you reply. I have ip and DNS static for the NAS already. I forgot to specify this.

It still doesn't work.

[Lea]

One more question.

It is possible to have ssh access on this NAS? It would be helpful to see logs of the NAS to know what's wrong because logs of server don't show anything.

[davo]

Afraid not, regarding the issue with joining the domain, it is hard to pin point the exact issue without knowing the settings of the DC, you probably would not be willing to share these on a public forum.

[Lea]

Hi Davo,

My boss is ok for some more details.

NetBIOS name: CORPERWB
Real domain name : CORP.ERWBNET.COM
Domain Controller Name: FR90SW01
Domain admin name: TESTNAS
Password domain admin: ***** (alpha numeric password with no special characters)

Static Ip adresses:

Nas: 170.31.20.227
Subnet Mask: 255.255.255.0
Gateway: 170.31.20.11
Domain controller: 10.129.15.51

In the group Policy management, Nas object is in root. There is just domain Policy GPO on it.

We have modified this in domain Policy GPO  Changing the Default Domain Policy setting in Group Policy Management (ie "Default Domain Policy/Computer Configuration/Windows Settings/Security Settings/Security Options/Network Security: LAN manager Authentication Level/Send LM & NTLM - use NTLMv2 session security if negotiated") like somebody advised on web.

If it can help...

Thanks in advance

[davo]

The NAS needs to be on the same subnet as the domain controller in order to join.

[Lea]

The NAS needs to be on the same subnet as the domain controller in order to join.

Seriously? Old NAS didn't need to be in the same subnet to join. And when they joined the domain, do they need to stay un the same subnet to work?

[davo]

Correct

[Lea]

Correct

My boss will be happy!  :-[

[Lea]

Well. What are restrictions with NT domain mode, please? Because we have different subnets to manage.

[Eastmarch]

Depending on your routers, you could always do some fancy static routing to get around the same subnet restriction. This is not for the faint of heart.

The NT domain that you have successfully connected to can provide user accounts. It works pretty much the same way, but that NT domain has to have the accounts you want.

[Lea]

Hi everybody,

Thanks for your anwers. We know what to do now.