Ошибка соидинения
Список форумов
→
RMS: Техническая поддержка, тестирование, неполадки и другие вопросы
|
Цитировать выделенное |
Ошибка соидинения 1 В общем. Есть айпи . 2 Но когда пытаюсь войти, пишет вот это. 3 Ошибка соидинения. Осталось попыток : 4 |
| Профиль | Сообщений: 4 | Дата создания: 08.04.2019 00:10:08 |
|
|
alex Модератор 
Цитировать выделенное |
alextarbot, значит данный IP не доступен. дело не в RMS. |
| Профиль | Сообщений: 3312 | Дата создания: 08.04.2019 00:17:38 |
|
|
alextarbot
Цитировать выделенное |
alex писал(а): даже мой? |
| Профиль | Сообщений: 4 | Дата создания: 08.04.2019 00:21:56 |
|
|
alextarbot
Цитировать выделенное |
alex писал(а):
значит данный IP не доступен. дело не в RMS. что за галочка возле компютера? и пишет что нету соидинения |
| Профиль | Сообщений: 4 | Дата создания: 08.04.2019 00:30:54 |
|
|
alex Модератор
Цитировать выделенное |
alextarbot, зеленая галочка означает, что комп пингуется. |
| Профиль | Сообщений: 3312 | Дата создания: 08.04.2019 01:21:31 |
|
|
alextarbot
Цитировать выделенное |
alex писал(а): почему я на него не могу зайти? |
| Профиль | Сообщений: 4 | Дата создания: 08.04.2019 08:11:51 |
|
|
alex Модератор
Цитировать выделенное |
alextarbot, причин может быть множество, файрволл например. |
| Профиль | Сообщений: 3312 | Дата создания: 08.04.2019 12:38:05 |
| Авторизация |
|
Зарегистрированный пользователь Новый пользователь |
Список форумов
→
RMS: Техническая поддержка, тестирование, неполадки и другие вопросы
|
Цитировать выделенное |
Скажите пожалуйста. Установил себе на ноут хост. На другой ноут установил программу. На ноуте где хост через командную строку узнал ip. На основном ноуте ввел этот ip. Все нормально работало. Ноут на котором хост перезагружал и все работало. Хост активировал ключем. При состыковки 2 ноута были на одном вай фай модеме. Вечером попытался подключиться к ноуту- не получилось. Пишет не в сети. Хотя он в сети. Либо при подключении загорается экран в программе и желтый треугольник. Почему не подключается? | |
| Профиль | Сообщений: 2 | Дата создания: 25.07.2013 13:25:33 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
Formacevt, нужно смотреть логи соединения. дело не в RMS, разбирайтесь с сетью. |
|
| Профиль | Сообщений: 3284 | Дата создания: 26.07.2013 13:57:18 |
||
|
||
|
Formacevt
Цитировать выделенное |
А не подскажите где это надо смотреть и как сделать по шагово? Просто я не настолько силен в этой области. | |
| Профиль | Сообщений: 2 | Дата создания: 27.07.2013 19:41:09 |
||
|
||
|
beatless
Цитировать выделенное |
У меня тоже такая проблема. Иногда нормально подключается, а иногда нет. | |
| Профиль | Сообщений: 1 | Дата создания: 08.08.2013 17:14:47 |
||
|
||
|
zimmer
Цитировать выделенное |
Formacevt писал(а):
Почему не подключается?
я бы в первую очередь копал в сторону анитивируса….. туда добавте в исключения… А не подскажите где это надо смотреть и как сделать по шагово? в настройках хоста, вкладка логирование… в вивере файл — настройки — журнал событий…. |
|
| Профиль | Сообщений: 76 | Дата создания: 08.08.2013 23:07:07 |
||
|
||
|
zimmer
Цитировать выделенное |
Formacevt писал(а):
На ноуте где хост через командную строку узнал ip может у вас динамический ip?… |
|
| Профиль | Сообщений: 76 | Дата создания: 08.08.2013 23:49:17 |
||
|
||
|
dimonfdr
Цитировать выделенное |
помогите не подключится с мобильного модема с проводного инета подключаюсь с мобильного нет в чем может быть проблема | |
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 14:11:43 |
||
|
||
|
dimonfdr
Цитировать выделенное |
и что за ошибка 53 | |
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 14:13:43 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
dimonfdr, нужно смотреть логи. dimonfdr, |
|
| Профиль | Сообщений: 3284 | Дата создания: 16.09.2013 14:47:30 |
||
|
||
|
dimonfdr
Цитировать выделенное |
Ошибка #53 Невозможно подключить сетевой диск. Не найден сетевой путь ***** Журнал завершен ***** при попытке перезагрузить удаленно хост |
|
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 15:03:52 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
Ну, собственно ошибка в том, что нет прямого доступа к компьютеру, либо отключены механизмы, которые нужны для работы удаленной установки. | |
| Профиль | Сообщений: 3284 | Дата создания: 16.09.2013 15:40:15 |
| Code | Reason |
| 0 | No error |
| 1 | User-initiated client disconnect. |
| 2 | User-initiated client logoff. |
| 3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
| 260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
| 262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 266 | The smart card service is not running. Please start the smart card service and try again. |
| 516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
| 522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
| 772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
| 1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
| 1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
| 1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
| 1796 | This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
| 2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
| 2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
| 2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
| 2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
| 2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
| 2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
| 2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
| 3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
| 3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
| 3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
| 3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
| 3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
| 3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
| 3592 | Failed to reconnect to your remote session. Please try to connect again. |
| 3593 | The remote PC doesn’t support Restricted Administration mode. |
| 3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
| 3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
| 4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
| 4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
| 4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
| 4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
| 5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
| 6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
| 7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
| 8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
| 9479 | Could not auto-reconnect to your applications,please re-launch your applications |
| 9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
| 33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
| 33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
| 50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
| 50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
| 50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
| 50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
| 50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
| 50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
| 50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
| 50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
| 50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
| 50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
| 50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
| 50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
| 50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
| 50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
| 50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
| 50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
| 50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
| 50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
| 50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
| 50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
| 50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
| 50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
| 50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
| 50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
| 50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
| 50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
| 50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
| 50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
| 50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
| 50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
| 50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
| 50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 50331699 | The connection has been disconnected because the session timeout limit was reached. |
| 50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
| 50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
| 50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
| 50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
| 50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
| 50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
| 50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
| 50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
| 50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
| 50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
| 50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
| 50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
| 50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
| 50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
| 50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
| 50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
| 50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
| 50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |
- Remove From My Forums
-
Вопрос
-
Добрый день все.
Опять проблемы. Прошу помощи.
Развернул AD RMS, создал шаблон прав, в IIS дал разрешения на сайт. С клиентских машин по адресу https://win04.domain.local/_wmcs/certification/certification.asmx и https://win04.domain.local/_wmcs/licensing/license.asmx все открывается.
Расшарил папку с хранением шаблонов.При попытке подключения к серверу управления правами и получить шаблон, получаю ошибку: «Произошла ошибка при попытке связаться с сервером AD RMS. Повторите попытку позднее.»
Ошибка кажется банальной, просто где-то что-то не дал разрешения, а вот где споткнулся не могу понять. Подскажите где смотреть.
Спасибо за помощь.
|
Цитировать выделенное |
Скажите пожалуйста. Установил себе на ноут хост. На другой ноут установил программу. На ноуте где хост через командную строку узнал ip. На основном ноуте ввел этот ip. Все нормально работало. Ноут на котором хост перезагружал и все работало. Хост активировал ключем. При состыковки 2 ноута были на одном вай фай модеме. Вечером попытался подключиться к ноуту- не получилось. Пишет не в сети. Хотя он в сети. Либо при подключении загорается экран в программе и желтый треугольник. Почему не подключается? | |
| Профиль | Сообщений: 2 | Дата создания: 25.07.2013 13:25:33 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
Formacevt, нужно смотреть логи соединения. дело не в RMS, разбирайтесь с сетью. |
|
| Профиль | Сообщений: 3284 | Дата создания: 26.07.2013 13:57:18 |
||
|
||
|
Formacevt
Цитировать выделенное |
А не подскажите где это надо смотреть и как сделать по шагово? Просто я не настолько силен в этой области. | |
| Профиль | Сообщений: 2 | Дата создания: 27.07.2013 19:41:09 |
||
|
||
|
beatless
Цитировать выделенное |
У меня тоже такая проблема. Иногда нормально подключается, а иногда нет. | |
| Профиль | Сообщений: 1 | Дата создания: 08.08.2013 17:14:47 |
||
|
||
|
zimmer
Цитировать выделенное |
Formacevt писал(а):
Почему не подключается?
я бы в первую очередь копал в сторону анитивируса….. туда добавте в исключения… А не подскажите где это надо смотреть и как сделать по шагово? в настройках хоста, вкладка логирование… в вивере файл — настройки — журнал событий…. |
|
| Профиль | Сообщений: 76 | Дата создания: 08.08.2013 23:07:07 |
||
|
||
|
zimmer
Цитировать выделенное |
Formacevt писал(а):
На ноуте где хост через командную строку узнал ip может у вас динамический ip?… |
|
| Профиль | Сообщений: 76 | Дата создания: 08.08.2013 23:49:17 |
||
|
||
|
dimonfdr
Цитировать выделенное |
помогите не подключится с мобильного модема с проводного инета подключаюсь с мобильного нет в чем может быть проблема | |
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 14:11:43 |
||
|
||
|
dimonfdr
Цитировать выделенное |
и что за ошибка 53 | |
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 14:13:43 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
dimonfdr, нужно смотреть логи. dimonfdr, |
|
| Профиль | Сообщений: 3284 | Дата создания: 16.09.2013 14:47:30 |
||
|
||
|
dimonfdr
Цитировать выделенное |
Ошибка #53 Невозможно подключить сетевой диск. Не найден сетевой путь ***** Журнал завершен ***** при попытке перезагрузить удаленно хост |
|
| Профиль | Сообщений: 3 | Дата создания: 16.09.2013 15:03:52 |
||
|
||
|
alex
Модератор
Цитировать выделенное |
Ну, собственно ошибка в том, что нет прямого доступа к компьютеру, либо отключены механизмы, которые нужны для работы удаленной установки. | |
| Профиль | Сообщений: 3284 | Дата создания: 16.09.2013 15:40:15 |
| Code | Reason |
| 0 | No error |
| 1 | User-initiated client disconnect. |
| 2 | User-initiated client logoff. |
| 3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
| 260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
| 262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 266 | The smart card service is not running. Please start the smart card service and try again. |
| 516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
| 522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
| 772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
| 1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
| 1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
| 1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
| 1796 | This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
| 2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
| 2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
| 2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
| 2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
| 2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
| 2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
| 2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
| 3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
| 3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
| 3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
| 3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
| 3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
| 3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
| 3592 | Failed to reconnect to your remote session. Please try to connect again. |
| 3593 | The remote PC doesn’t support Restricted Administration mode. |
| 3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
| 3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
| 4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
| 4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
| 4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
| 4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
| 5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
| 6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
| 7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
| 8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
| 9479 | Could not auto-reconnect to your applications,please re-launch your applications |
| 9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
| 33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
| 33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
| 50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
| 50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
| 50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
| 50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
| 50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
| 50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
| 50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
| 50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
| 50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
| 50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
| 50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
| 50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
| 50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
| 50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
| 50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
| 50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
| 50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
| 50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
| 50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
| 50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
| 50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
| 50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
| 50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
| 50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
| 50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
| 50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
| 50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
| 50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
| 50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
| 50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
| 50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
| 50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 50331699 | The connection has been disconnected because the session timeout limit was reached. |
| 50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
| 50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
| 50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
| 50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
| 50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
| 50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
| 50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
| 50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
| 50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
| 50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
| 50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
| 50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
| 50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
| 50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
| 50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
| 50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
| 50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
| 50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |
- Remove From My Forums
-
Question
-
Hi all,
All my client can’t connect to AD RMS Server (Win 2008 R2 SP1), error like this :
This
service is temporarily unavailable. Ensure that you have connectivity to this server. this error could be because you are working offline, your proxy settings are preventing your connection, or you are experiencing intermittent network issues.From the client I have configure URL to local trust site, can ping the server, can access the url RMS, IE online.
what could probably wrong ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Answers
-
Oh … just noticed it’s a Win XP SP2 box need to update it via the Internet direct from Microsoft update. Faced the same on XP desktops, need to fully update with IE, .net framework and office patches.
Have you checked with Windows 7 if you are having the same issue?
Just FYI — XP SP2 out of support
Blog Link: http://blogs.cyquent.ae | Follow us on Twitter:
@cyquent | ADRMS Wiki Portal:Technet Wiki
-
Edited by
Wednesday, July 27, 2011 10:52 AM
added a response line -
Marked as answer by
Brad Mahugh — (Microsoft)
Thursday, April 4, 2013 3:35 AM
-
Edited by
-
Hi Alokemc,
I think you should open a new thread for yourself m8.
Hi All,
I uninstall existing ADRMS server (SVR01) and install at SVR02, the problem still the same. Then I try a fresh installation Windows XP and try to disable IE GPO, then it works. I think the major problem is the IE GPO (User Configuration).
So how can I revert back all the settings from my client, either the IE settings or the old credential from RMS, the registry settings also, so I have a clean client ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Marked as answer by
Brad Mahugh — (Microsoft)
Thursday, April 4, 2013 3:36 AM
-
Marked as answer by
-
Hi
Looks pretty much standard configuration, I believe you need to make a few changes in the following sections and life would be good,
Local intranet (Security Level: Medium-low) > Sites in this zone >
Add the Intranet URL for the AD RMS serverLocal intranet (Security Level: Medium-low) > Sites >
Include all sites that bypass the proxy server > Set to Enable
Let me know how it goes ..
Blog Link: http://blogs.cyquent.ae | Follow us on Twitter:
@cyquent | ADRMS Wiki Portal:
Technet Wiki-
Marked as answer by
Brad Mahugh — (Microsoft)
Thursday, April 4, 2013 3:36 AM
-
Marked as answer by
-
Hi Team,
I found the same issue with my one of the client. Here (In development) it’s working fine. with and without domain (using citrix). But there at client end it’s not working.
They have Windows 7 + Office 2010.
Same From IRMS Check Configuration
Check 1: Microsoft Office Server is not installed.
Need helps from you.
Thanks & Regards, Brijesh Shah
-
Marked as answer by
Brad Mahugh — (Microsoft)
Thursday, April 4, 2013 3:36 AM
-
Marked as answer by