Networking – Windows 10 can’t rejoin domain to Windows Server 2003

I have Windows 10 Pro (upgraded from Windows 8.1 Pro) and am having trouble joining the domain. All existing profiles and settings work, but today I needed log in with a user account which never logged in to that computer before. And I got the message:

There are currently no logon servers available to service the logon

Tried these steps: log in to local admin, leave domain, reboot, changed computer host-name, reboot again, join domain.

But now I'm stuck because I can't join domain again. I got message that domain name is not found or can't be contacted.

I removed the computer from DC active directory, flushed DNS on computer and DC, rebooted DC, changed DNS manually on computer, enabled NetBIOS over TCP/IP on IPv4. But nothing helps, always get the same message that domain is not found or can't be contacted.

This is what I found in WINDOWS\debug folder in one text file (doesn't remember file name)

09/03/2015 15:49:29:477 NetpDoDomainJoin
09/03/2015 15:49:29:477 NetpDoDomainJoin: using current computer names
09/03/2015 15:49:29:477 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
09/03/2015 15:49:29:477 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
09/03/2015 15:49:29:477 NetpMachineValidToJoin: 'IVETA-PC'
09/03/2015 15:49:29:477 NetpMachineValidToJoin: status: 0x0
09/03/2015 15:49:29:477 NetpJoinDomain
09/03/2015 15:49:29:477     HostName: Iveta-PC
09/03/2015 15:49:29:477     NetbiosName: IVETA-PC
09/03/2015 15:49:29:477     Domain: NEPLPADOME
09/03/2015 15:49:29:477     MachineAccountOU: (NULL)
09/03/2015 15:49:29:477     Account: NEPLPADOME\administrator
09/03/2015 15:49:29:477     Options: 0x27
09/03/2015 15:49:29:493 NetpValidateName: checking to see if 'NEPLPADOME' is valid as type 3 name
09/03/2015 15:49:29:555 NetpCheckDomainNameIsValid [ Exists ] for 'NEPLPADOME' returned 0x0
09/03/2015 15:49:29:555 NetpValidateName: name 'NEPLPADOME' is valid for type 3
09/03/2015 15:49:29:555 NetpDsGetDcName: trying to find DC in domain 'NEPLPADOME', flags: 0x40001010
09/03/2015 15:49:44:559 NetpDsGetDcName: failed to find a DC having account 'IVETA-PC$': 0x525, last error is 0x0
09/03/2015 15:49:59:562 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0
09/03/2015 15:49:59:562 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b
09/03/2015 15:49:59:562 NetpJoinDomainOnDs: Function exits with status of: 0x54b
09/03/2015 15:49:59:562 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
09/03/2015 15:49:59:562 NetpDoDomainJoin: status: 0x54b

What can be causing this? The server is old and wasn't me who configured Server 2003 and DC. I don't think that there is any special configuration, just simple DC.

I can ping server from cmd by name and IP address. I use the same network as the domain. After changed DNS to server IP address (which is one by default when use automatic) and re-registered DNS, I got the same error.