A
A
ASiD2021-12-03 10:18:11
1C-Enterprise
ASiD, 2021-12-03 10:18:11

How to solve the problem of freezing when connecting to IB from some computers?

Good afternoon.

There is a 1C cluster (platform 8.3.12.1790) from one working server. It contains an infobase located in the MS SQL database.
There is a distributed network from the head office and many departments.

Problem: clients connect to the server normally from the head office, but when connecting from remote departments, the connection freezes at the 1s splash screen (waited for an hour and a half - nothing changes), it does not give errors, there is no load on the processor, disk, network, memory. Channel 40 Mb/s. There is the same configuration on the same platform, raised on different equipment in another department - no such problems.

Tell me what could be the problem?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
L
LollyFox, 2021-12-03
@ASiD

If the client-server base hangs on the splash screen even before authorization, then in most cases the client cannot obtain a license, either locally, over the network, or from the server.
What client licenses are used (software or USB) and how do clients get them?

H
hint000, 2021-12-03
@hint000

Use a terminal server at the head office. Remote clients will connect via RDP.
This scheme has been the de facto standard for a hundred years.
An alternative option is to publish the application on a web server (in the same place, at the head office) and work with remote clients through a browser.
Almost no one practices connecting directly with a 1C client via the Internet to a 1C server.

K
Konstantin, 2021-12-03
@fosihas

from the head office, clients connect to the server normally, but when connecting from remote departments, the connection is

child's game, find 10 differences.
Check if the 1s cache is created by the remoters.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question