MSM720 ERROR: Failure #4000. (64)

[Chris991]

Hello!

A MSM720 on a remote branch loses for a few days the power.

The day after the users write to me the can not use the AD authenticated Wi-Fi Network. All other Wi-Fi networks work fine.

Thus I checked the MSM, MS-AT, GPOs the client.

My assumption was that the MSM loses the AD trust. So I deleted the AD Computer and DNS object.

When I do I join the MSM displays the message ERROR: Failure #4000. (64)

Has anybody a clue?

I was on version 6.0.2.0. Now I use 6.0.3.0-18516

The Domain Controllers on the site are all W12R2

[RamKrish]

Hi

Can you check the DNS server ip address specified on the controller (Network --> DNS).

Make sure its pointing to the correct Domain controller/DNS.

[Chris991]

Yes, I checked it already. I can also ping the DNS Server and can execute over the MSM cli nslookup which resolves DNS names to IP Addresses.

[Chris991]

I use now the version V6.5.3.0-MSM720-B22590 but no change

[Chris991]

I did a wireshark sesion on the DNS Server while a tryed the DNS join.

I am now on version 6.6.0.0-22530

10.0.57.241 IP of the MSM

988   11:56:56.993874000   DC01.domain.com      10.0.57.241       DNS        170   Standard query response 0xe3db No such name

[RamKrish]

Hi

If you are getting a no response for the standard domain query (source ip with MSM) indicate that you have the netbios name configured incorrectly on the controller Active Directory section.

You can also do a simple trace on the controller itself (Tools --> Network Trace --> select either Accessport or Internet port depending upon which is the next hop to reach the DNS server ip).  You can filter for port 53 or 389 (filter command: port 53 or port 389).  This should give you the whole transaction starting from DNS query and LDAP binding.

[Chris991]

The netbios name looks correct on the MSM UI.

I did a trace on the controller, like you said.

Please have a look on the pcap file in the zip