B
B
bigazzzz2013-02-05 16:16:57
Active Directory
bigazzzz, 2013-02-05 16:16:57

dlink DNS-346 in AD 2012

Domain controller on Windows Server 2012 Standard.

When connecting to AD, the error "Improper username used when connecting to the domain controller. Please check to make sure the username is correct”
What was done?
1. REALM\username and [email protected] were checked, well, username is simple
2. A test user with domain administrator rights was added and point 1 was checked.
3. The DNS server points to the controller itself and the controller is visible
4. Date and time checked and the discrepancy is no more than a few seconds
5. The latest stable firmware and the latest beta firmware were installed and checked sequentially
If the password is incorrect, the warning “Incorrect password. Please check the password”, it means that the user simply does not have enough rights to add to the domain, but under this user I can easily add computers to the domain. I specifically set the main group for this user - "Domain Admins". The effect is the same.

Support answer: DNS-346 only works with 2003 AD server (it's strange that I found out about this after buying the device)

What can you advise? What can be tweaked in AD to make it compatible with AD 2003?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
M
merlin-vrn, 2013-02-05
@merlin-vrn

You can twist security policies, in particular, the encryption algorithms used in Kerberos.
support.microsoft.com/kb/961302
technet.microsoft.com/en-us/library/bb742516.aspx

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question