Why does Windows authorization not work in 1C enterprise 8.3?

Question

1C

Good afternoon friends!

We have made a terminal server for working with 1C based on regular Windows 7, on the same machine the 1C enterprise server and MSSQL are paired with it.

Everything was fine, users successfully logged into their Windows authorization accounts.

Now the configuration has changed: a local network, 2 separate machines, the same 1C + MSSQL is running on one, but the terminals have moved to a separate machine, made by the same collective farm from Windows 7. Now, accordingly, the address of the server and database has changed from "localhost / mybase " to "192.168.10.132/mybase"... However, now authorization through Windows accounts does not work for us.

Naturally, there is no domain controller, no working group - there is nothing simply as unnecessary.

The question is how to make the 1C server accept Windows authorization if the terminal is now on a different physical machine?