Имя пользователя:
Пароль:  
Помощь | Регистрация | Забыли пароль?  

Показать сообщение отдельно

Новый участник


Сообщения: 3
Благодарности: 1

Профиль | Отправить PM | Цитировать


на оффисе бывает скачет свет, на бесперебойник денег жалеют.
ipconfig srv-2
читать дальше »
Windows IP Configuration



Host Name . . . . . . . . . . . . : srv-2

Primary Dns Suffix . . . . . . . : mydomen.by

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : mydomen.by



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

Physical Address. . . . . . . . . : бла бла

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.224

DNS Servers . . . . . . . . . . . : 127.0.0.1

192.168.1.1


ipconfig srv-1 немогу привести, так как немогу залезть на него по rdp, возможно есть другой способ, но я его просто незнаю.

я думаю чт онеработает репликация, так как сыпятся ошибки:

Windows cannot search for Organizational Unit hierarchy. (52). Group Policy processing aborted.
Logon rejected for mydomen\larry. Unable to obtain Terminal Server User Configuration. Error: Access is denied.
Windows cannot determine the user or computer name. (The target principal name is incorrect. ). Group Policy processing aborted.
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
Windows cannot bind to mydomen.by domain. (Local Error). Group Policy processing aborted.
читать дальше »
This is the replication status for the following directory partition on the local domain controller.

Directory partition:
CN=Schema,CN=Configuration,DC=mydomen,DC=by

The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.

More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
1
Tombstone lifetime (days):
60
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.

To identify the domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe.
You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".

читать дальше »
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2007-03-12 10:50:28
Invocation ID of source:
0075f980-f970-0075-0100-000000000000
Name of source:
60f70b01-a183-46f4-bd8c-7a5cddaf9c63._msdcs.mydomen.by
Tombstone lifetime (days):
60

The replication operation has failed.

User Action:

Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:

1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner


For more information, see Help and Support Center at


я слабо знаком с администрированием server 2003. в основном локальные машинки ковырял.

Отправлено: 10:38, 19-06-2007 | #3