I have two machines that I export offsite as standby VM's and they both have suddenly stopped exporting. None of the permissions have changed and the firewalls are down. I did just do a round of windows updates the day before but I was still exporting right up until this afternoon. I realize that this may not be a RR issue per-se but any ideas would be appreciated. I am unable to even connect far enough to add a new machine to export. I can remote desktop the machine and ping it.
The message "access is denied" raises a connectivity question mark which needs to be addressed first before going into more depth. Since replication goes on port 8006, the simplest test is:
1. stop the core service on the source core
2. run a telnet client pointing to the target core on port 8006
If you get a blank CMD console that cannot be closed via CTRL-C, it means that you have connectivity.
3. stop the target core service and run telnet again from the target.
If you have connectivity it means that someone has hijacked your port 8006 (possibly a recently deployed Apache TomCat server)
4. Telnet again from the Target to the Source (both core services stopped)
Same as above if you have connectivity it means that someone has hijacked your port 8006
5. Start the Source core service (so you have a listener on port 8006) and repeat the test the other way around.
If you have connectivity (and you did not at #4) it means that the connectivity is not your culprit and more troubleshooting is needed.
If you determine that there is something listening on port 8006 on either side and you cannot shut down that application, you can change the replication port as shown below. Please note that the replication port is recorded on the source core only (so there is nothing to do on the target).
Hope that this helps.
In reply to Tudor.Popescu:
In reply to Corrigun:
In reply to Tim Seymour:
After a few successful exports I'm back to square one with a new error- "an existing connection was forcibly closed by the remote host..." Starting over again.
EDIT: We have a bad fiber switch. Not sure how this would present as a permissions issue but fingers crossed.