Why lets through RDP only when using the server name?

Question

RDP

This morning I encountered the fact that access to the 1C server via RDP fell off - there were no special errors, just a login / password window appeared ... "Invalid credentials"
take.ms/JZdYD
I could not log in remotely even under administrator with specifying the admin session in which terminal licenses should not be used.
Given (all licensed)
server - win 2003, on which AD is spinning. Chief, everything is on it. DNS, DHCP...
server2 - win 2008r2, on which there is a terminal server + terminal licensing service + 1C
rdp_file - in which all settings, parameters, addresses and password hash are registered - double click and you work in 1C ...

screen mode id:i:2
use multimon:i:0
session bpp:i:24
winposstr:s:0,1,2275,68,3422,976
compression:i:1
keyboardhook:i:2
audiocapturemode:i:0
videoplaybackmode:i:1
connection type:i:4
displayconnectionbar:i:1
disable wallpaper:i:1
allow font smoothing:i:1
allow desktop composition:i:1
disable full window drag:i:0
disable menu anims:i:1
disable themes:i:0
disable cursor setting:i:0
bitmapcachepersistenable:i:1
full address:s:***ip***
audiomode:i:2
redirectprinters:i:1
redirectcomports:i:0
redirectsmartcards:i:0
redirectclipboard:i:1
redirectposdevices:i:0
redirectdirectx:i:1
autoreconnection enabled:i:1
authentication level:i:0
prompt for credentials:i:0
negotiate security layer:i:1
remoteapplicationmode:i:0
alternate shell:s:
shell working directory:s:
gatewayhostname:s:
gatewayusagemethod:i:4
gatewaycredentialssource:i:4
gatewayprofileusagemethod:i:0
promptcredentialonce:i:1
use redirection server name:i:0
username:s:***DOMAIN\user.name***
drivestoredirect:s:
password 51:b:***хеш_пароля***

***It was in the morning
Trying to log in from home - error - take.ms/JZdYD Trying
to log in via rdp first to the 2003 server - normal, now from it, error - no free licenses for the terminal
Licenses were, about 10 free, but in the logs win2008 then found that the trial period was over (so the server has been running for 5 years, everything was activated, about 50 licenses in total!).
*** Became day
Came legs to computers.
Did so ( www.raymond.pro/poleznye-programmy/remont-sistemy/... ) - by
MSLicensing deleted on clients - by
Omitting the rest of the little things - globally killed the roles, installed the roles, activated the licenses again - free 47 pieces.
Nothing plows anyway, but now it was already possible to go to the server from home. Progress ... As it turned out later - only under the administrator, but the first shift was.
Buhi from home by IP (white IP at the office, ports are forwarded on the nix gateway to servers) still cannot log in.
Inside the locale - similarly. Moreover, the user sees a message about the invalidity of the data. Not a word about missing licenses.
One friend (Oleg, hi), from a similar experience of the problem, advised using not the IP of the server, but his name, i.e. server2. It fucking worked!
those. there is an rdp file - the IP of the server is specified there - the first start - does not plow.
copy this file, change IP in notepad to "server2" - it worked!!! even the terminal server gave the computer a face.
We try to go through the IP - it also works.
we reboot the machine - we specify the IP, it fell off again ...
Remotely, boos naturally cannot connect. Second shift.
DHCP and DNS for 2003 the server hang, there in a reverse lookup zone registered handles "name-ip"
take.ms/K0Ykm
where to dig? at first he sinned on the terminal server, but after all the manipulations ... after he demolished and set the roles from scratch
... .. go home to think. *** From noticed/done brought 1s server 2008 out of AD, changed the name to server3, cleaned DHCP on the 2003 server, put it back in, saved the IP, registered it as static. did not help.
At some point, after removing the computer from AD or renaming, I received an error on the 2008 server when logging in from the administrator "Violation of trust between the workstation and the domain controller."
After that brought out of the domain, entered into the domain. The error disappeared, but not for RDP
If you do NOT manually prescribe the reverse lookup zone (as here take.ms/K0Ykm ), then you can access the 1C server via RDP only by name (server3), and then by IP. after reboot again only by name.
If to register - it is possible and on IP at once.
But such a chip seems to be only on one computer, on the second it is impossible. As if iron hashes are stored. But I reinstalled the roles...
From 2003 the server cannot be entered on 2008 on RDP - swears a obscene language on the missing server of licenses. But it is, even the base one for 2003, which has nothing to do with it !!! Mystic for me.
If you do not log in from the local area (from home) - under a user with admin rights - it does not let you. If from the same computer to enter an uchetka "absolutely" the administrator (change only login/password) - comes.
=============
update2
Decision to remove the bug patch from MS
habrahabr.ru/post/252875

Answer 1

The decision to remove the bug patch from MS
habrahabr.ru/post/252875

Answer 2

I have had updates for 2003 for half a year - users in RDP had to replace User with Domain\User