Hi all,
Nothing, to my knowledge, has changed since we fixed the last problem. No passwords, computer names or IP's have been changed. I've tried restarting the machine and the DNS services, flushed the dns and reregistered on all machines as well as replicating the AD a couple of times. Previously this seemed to fix the problem but I'm not so lucky this time.
Logs showing: ID: 5002 - dfs rep service encountered an error communicating with partner x for replication group y. Error: 1825 (A security package specific error occurred)
I've tried to do a propagation report between the two servers but this fails with a login failure - the target account name is incorrect. This machine is part of a domain controlled by AD. Would resetting the computer account in AD fix this and what implications would this have?
I've tried removing and re-creating the group but this now gives me: 'Computer name' The server's OS version cannot be retrieved. Access is denied. The dfsr service status cannot be queried. MachineName value is invalid.
The other interesting log that keeps appearing is: Event ID:64 "Certificate for local system with Thumbprint ... is about to expire or already expired." I don't think this one is related but thought I should mention it in case it helps...
I can successfully ping each partner from the opposite partner however I have noticed that the response is IPv6. There are a few entries on our DC which relate to these machines and the addresses are the ones I'm getting back from the ping. I'm confused at this point as to why they're there. We've never used IPv6 and all other servers in the domain are IPv4 based. I'm slightly reluctant to go in and remove these, as the servers are in a production environment. Could someone advise on the best way to update these, if required?
Windows firewalls are switched off and the machines are all on the same LAN.
Just for info, I'll list the related services and the accounts they're running under. (I've tried restarting these services but that didn't seem to make a difference):
DCOM Server Process Launcher - started - auto - local system
DFS Namespace - started - auto - local system
DFS Replication - started - auto -local system
Remote Procedure Call - started - auto - network service
Can anyone shed some more light on this one please? I really don't understand what's caused the problem to reappear. (DCDIAG comes back clear.)
Thanks in advance.
Mark