- Remove From My Forums
-
Вопрос
-
в домене win2003 развернуто пространство имен DFS. корень DFS — доменный. домен построен на двух КД win2003 R2. оба сервера — глобальный коталог.
при просмотре ресурсов DFS первая ссылка указывает на основной КД. вторая — на дополнительный.
основоной КД недавно приказал долго жить. доступ к корню DFS и ресурсам впринципе есть, но ооочень медленно.
хотел переписать все ссылки на второй КД, но из консоли управления DFS когда нажимаю на пространство имен — выдает ошибку «Указанный домен не существует или к нему невозможно подключится»
Еще на КД логе сегодня было такое:
Тип события: Ошибка
Источник события: NETLOGON
Категория события: Отсутствует
Код события: 5719
Дата: 26.11.2010
Время: 8:24:04
Пользователь: Н/Д
Компьютер: S2
Описание:
Компьютер не может установить безопасный сеанс связи с контроллером домена CAPAROL-MALINO по следующей причине:
Отсутствуют серверы, которые могли бы обработать запрос на вход в сеть.
Это может затруднить проверку подлинности. Убедитесь, что компьютер подключен к сети. Если ошибка повторится, обратитесь к администратору домена.Дополнительные сведения
Если данный компьютер является контроллером указанного домена, он устанавливает безопасный сеанс связи с эмулятором основного контроллера этого домена. В противном случае компьютер устанавливает безопасный сеанс связи с произвольным контроллером данного домена.
Ответы
-
очень просто:
Предположим, что на неисправном КД еще и роль ДНС
1) Клиент обращается к первому ДНС, указанному в настройках сети (неисправный КД). Тот не отвечает, таймаут.
2) Клиент обращается ко второму ДНС-серверу и получает адрес-имя неисправного КД, обращается к нему. Тот не отвечает, большой таймаут, т.к. тут таймаут по дефолту больше.
3) Клиент обращается ко второму ДНС-серверу и СНОВА получает адрес-имя неисправного КД, обращается к нему. Тот не отвечает, большой таймаут.
…
n) Клиент обращается ко второму ДНС-серверу и получает адрес-имя исправного КД, обращается к нему. Тот отвечает, и, наконец, все заработало…
устраивает?
Ах, да…
после н-го запроса еще может идти обращение к дохлому КД как к корню ДФС… Таймаут…
Не игнорируйте встроенную справку, читайте ее и большинство вопросов будет решено гораздо быстрее.
-
Помечено в качестве ответа
30 ноября 2010 г. 10:25
-
Помечено в качестве ответа
That amazing moment amazing amazing moment when you are able to resolve a long pending issue even that the TechNet forum was all baboons about it.
Having issues with management of your once applied quotas via File Server Resource Manager (FSRM) on your WIndows Server 2008 R2 SP2. Apparently the following can be the reasons for this error:
- You have installed the FSRM role; created quotas; un-installed the FSRM role and re-installed it.
- You have installed the FSRM as a Windows Feature instead of a Role.
And you will be apparently having these following errors/warnings in your Event Viewer:
- Warning 12317: File Server Resource Manager failed to enumerate share paths or DFS paths. Mappings from local file paths to share and DFS paths may be incomplete or temporarily unavailable. FSRM will retry the operation at a later time.
- Error: DfsMapCacheAdd(Domain), 0x8007054b, The specified domain either does not exist or could not be contacted.
- Error 8197: File Server Resource Manager Service error: Unexpected error.
- Error: CGlobalStoreManager::Install(), 0x80070005, Access is denied.
Now when you access the Quota tab from the FSRM MMC; you get the an error and no quotas are visible. Or you apply a quota on a folder but instead you get an error saying that the quota for the folder already exists but you don’t see any.
This is apparently due to the fact that the system files associated with the FSRM either get corrupted or the SYSTEM account access is restricted to these files or the previously installed FSRM role settings are still not completely removed.
Now the work around to this issue depends upon how bad have you played with your FSRM role. Just to let you know that This workaround will remove all your previously implemented quota rules and templates.
The work around to this is basically deleting the system files related to the FSRM. Before doing that; uninstall the FSRM Role or the FSRM Feature you installed previously.
Now to delete the FSRM related system files; you won’t be able to access them with you Admin credentials (even Enterprise Admin is not able to alter these files). Only the SYSTEM account has access to it.
Now to access these files here is a small tool; rather set of tools I used. Download the PSTools and follow the following steps.
- Unzip the downloaded PSTools.
- Run Command Prompt as Administrator.
- Navigate to the folder where you unzipped the PSTools.
- Execute the following command
PSEXEC -i -s -d CMD
Click YES if you have executed the command for the first time. A new Command Prompt window will be opened which basically is running under the privileges of the SYSTEM Account.
Now what you need to do is first delete a couple of files from inside the partition on which you have applied quotas before. If you have quotas applied on multiple partitions then you will need to repeat the following steps for all the partitions.
What you will basically do is delete the files quota.xml and quota.md from the %SystemVolumeInformationSRM folder. These two system files will be write-protected hence you will need to alter the rights before deleting them.
In the newly opened Command Prompt window; execute the following commands but do not close the windows yet after these commands.
cd System Volume InformationSRM
attrib quota.xml -s -h
attrib quota.md -s -h
del quota.xml
del quota.md
Along these files you will also need to delete the files ReportSettings.xml and SrmGlobalSettings.xml inside the root drive (i.e. C:) %SystemVolumeInformationSRMSettings folder. In the same Command Prompt window opened earlier; execute the following commands.
cd System Volume InformationSRM
attrib ReportSettings.xml -s -h
attrib SrmGlobalSettings.xml -s -h
del ReportSettings.xml
del SrmGlobalSettings.xml
After deleting these system files; install the FSRM Role again; this time hopefully you will be able to install the FSRM Role without any errors. If not then feel free to leave a message! Cheerio!!
References:
- Getting a CMD prompt as SYSTEM in Windows Vista and Windows Server 2008.
- You cannot create quotas on File Server Resource Manager (FSRM) in Windows Server 2003 R2 KB 555941.
Tags: 0x80070005, 0x8007054, 0x8007054b, Access is denied., DfsMapCacheAdd(Domain), Error 8197, Error: CGlobalStoreManager::Install(), File Server Resource Manager, File Server Resource Manager Service error: Unexpected error., FSRM, FSRM Error, Quota Error, quota.md, quota.xml, ReportSettings.xml, SRM, SrmGlobalSettings.xml, SYSTEM Account, SystemVolumeInformationSRM, Warning 12317, Windows SYSTEM Account
This entry was posted on October 3, 2013 at 9:53 PM and is filed under ADMIN$, ICT, Pakistan, Trends & Tech, Uncategorized, Windows, Windows Server 2008 R2. You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
- Remove From My Forums
-
Question
-
We have an Active Directory with a «dotted» NETBIOS domain name (e.g. «CONTOSO.ORG» rather than «CONTOSO»).
We had to rebuild our DirSync server and decided to take a clean install approach using the GA release . Here are the steps we’ve taken:
- Clean install of Windows 2012 R2
- Downloaded and installed the GA release of the new Azure AD Connect tool
- Successfully completed the installation wizard using an account with Azure Global Administrator role as well as being a member of the local AD’s Enterprise Administrators group.
- Launched the Synchronization Service Manager and opened the properties of the connector for the «Active Directory Domain Services» and attempted to view/edit the selection of the directory partitions.
- Got the error message of «The specified domain either does not exist or could not be contacted. (Exception from HRESULT:0x8007054B)
- Attempted to «Refresh Schema» for the connector and get the following message of «An error was encountered during the schema refresh. Please try again later.»
…could these errors be related to the fact that our local AD’s legacy NETBIOS name has a «dot» in it? We’re too scared to do a domain rename operation at this point, but will need to consider it if this is indeed the root cause.
Any help would be GREATLY appreciated!
-
Edited by
Wednesday, July 1, 2015 5:36 PM
Inserted image
Answers
-
-
Proposed as answer by
Arvind S. Iyer
Wednesday, July 1, 2015 9:08 PM -
Marked as answer by
Transporteraccident
Thursday, July 2, 2015 4:39 AM
-
Proposed as answer by