In a trust relationship, how often does the rpc connection check to verify that the link is still up?
Printable View
In a trust relationship, how often does the rpc connection check to verify that the link is still up?
lynnandrea,
The domain controller tries to locate the trusted domain, every 15 minutes.
Further Info:
Once a trust has been established, PDCs and BDCs locate trusted domains while booting up, establishing a password-protected communications “pipe”, RPC. The PDC generates a pulse (approximately every day) and changes the internal password on the secure pipe. If domain controllers do not receive this pulse at boot time for internal password changes or initiations of pass-through authentication, then the trust goes dormant for 15 minutes.
The trust tries to change its internal secure pipe password, and if it cannot communicate the new password to both sides within a week, the trust breaks and you must delete and re-add it.
This password change can be disable through the registry.
regards
------------------
DrEd, MCSE
Australia
[This message has been edited by DrEd (edited 07-13-2000).]
Hi DrEd,
Thank you so much for the answer. It was exactly what I was searching for.
Lynn
Quote:
Originally posted by DrEd:
lynnandrea,
The domain controller tries to locate the trusted domain, every 15 minutes.
Further Info:
Once a trust has been established, PDCs and BDCs locate trusted domains while booting up, establishing a password-protected communications “pipe”, RPC. The PDC generates a pulse (approximately every day) and changes the internal password on the secure pipe. If domain controllers do not receive this pulse at boot time for internal password changes or initiations of pass-through authentication, then the trust goes dormant for 15 minutes.
The trust tries to change its internal secure pipe password, and if it cannot communicate the new password to both sides within a week, the trust breaks and you must delete and re-add it.
This password change can be disable through the registry.
regards