Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

AD Site replication - RPC failed to initialise

Featured Replies

Mornin' !

I'm having problems with AD not replicating across sites, there are three sites in the domain, all running server 2003, site 1 is the central site and replicates without any problems to site 2, site 3 cannot ( or will not) replicate to sites 1 or 2. Yes, ive checked all necassary ports are open on the hardware firewalls using portqry and the RPC services are running on site 3's DC. AD sites & services appears to be set up correctly, based upon the topology of sites 1&2, all relevant subnets are listed and assigned to the correct sites.

I've tried forcing replication from all sites, still with the same error...

replmon can access all sites and confirms connections (and the errors!)

All DC's were configured and AD replicated at site 1 before being physically and logically - within AD anyway- moved to their final locations

All sites are connected by WAN links, using VSAT, all sites can see each other and logon using remote desktop and logon to http & ftp servers.

I have four other domains using the same topology all with remote sites connected via VSAT and they're quite happy....

Any ideas?

Cheers,

10forcash


Are the Site Transports configured correctly for Site 3? IE: IP and SMTP

Try deleting the default or automatically configured replication methods and recreating your own.

  • Author

Tguy,

Thanks -the links are ok, as verified by portqry - however...

did a bit more work with dcdiag /e & nltest, it appears that the schannel was being ignored, due to a problem with the GUID at site 3 resetting the schannel appears to have cured it. For info the command is 'nltest /server:dc1 /sc_reset:mydomain\dc2'

I ran it at both ends and forced replication, 12 hours later everything is running as it should do.....

for anyone else that has a similar problem, nltest sometimes reports 'no logon servers available' and 'no such domain' if run on the FSMO, which can induce minor heart attacks! apparently this is a 'feature' - fanx Bill!

Cheers,

10forcash

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.