Do not let some computers on the server by name?

Question

Windows Server

Hello colleagues.
A problem arose ... For the third day I have been fighting ... I can’t find anything worthwhile.
There is Windows Server 2012, which is used as a file cleaner. The server is in the domain (domain controllers on win 2003, in the same place WINS and DNS).
Some users cannot access the server by name - neither fileserver nor fileserver.domain. For some, the message " Username not found " pops up , and for some it simply asks for a username and password, after entering it asks to enter again (although they are entered without errors).
Guest included.
All users in the domain.
If you put the policy " Network access: Sharing and security model for local accounts. " in " Guest"Nothing changes.
Firewall and antivirus turned off.
There is one feature here ... If you turn off VPN (PPTP, we have an Internet through it), then problem computers come by name without questions. When we turn on the VPN, they first come by name, and then, after a few minutes, again " Username not found ".
But it lets you through IP without problems. And it doesn’t matter if the user is in the domain or not, whether VPN is enabled or not.
Another part of the users logs in without problems, either by name or by IP, both with VPN enabled and
without.Client computers on Windows 7 (x32 and x64)
.I sinned on WINS, but it sees the fileserver (there are two of them and they are replicated).I also registered filesever statically there, not to no avail.What
could be Where to dig?

Answer 1

Try changing the user's rasphone.pbk:
%ProgramData%\Microsoft\Network\Connections\Pbk
or
%appdata%\Microsoft\Network\Connections\Pbk\
All Connections are there. Find your VPN and change the line:
UseRasCredentials=1 to =0
you need to restart the VPN or every fireman on the entire PC.
We had a problem that when entering the share server, the name of the VPN-User was taken, which was different from the domain name. After the change, there were no more problems with this.

Answer 2

Since the problem is clearly a transport problem, it’s worth running wireshark on the file cleaner and seeing who can’t reach where.
And why the hell did you give up WINS?

Answer 3

ipconfig /flushdns have you tried clearing the cache?

Answer 4

If I'm not mistaken, in Windows the VPN connection becomes the default route with a better metric. Try to register a static route to the internal network with a metric of 1

Answer 5

And if you forcefully change the SID on these computers, everything is possible because of him. Google Newsid.