We are using a moodle XAMPP installation on Windows 2008 for our credentials forwarding server for Moodle A. This is within our DMZ. We're Moodle version 2.5.2 for Moodle A.
We have our learning content on Moodle B which is in the cloud on a Linux server.
We have firewall ports open on 80 and 443 in both directions for communication between Moodle A and Moodle B.
LDAP authentification is working just fine on Moodle A. We've had single signon working ok with
users logging onto Moodle A then getting to courses on Moodle B. Then it stopped working with
users getting an MNET timeout error:-
"Ooops! Your MNET communication has failed! Here's that error message to pass on to your administrator: connect() timed out!ERROR 28:
28:connect() timed out!"
Some users get the 'page can't be displayed' instead of the MNET timeout error.
Then it started working again - it wasn't clear why. Then it stopped working again. And it started working and stopped.... alternating over a period of three weeks.
Our supplier for Moodle B in the cloud has a number of customers using a similar credentials-forwarding configuration without problems, but they are all using LAMPP (Linux) for their Moodle A. We're the only customer with these problems.
We find that on Moodle B we have to paste in the public key for the Moodle A peer, it doesn't pick it up automatically. We get a message on the peer page that the public key doesn't match the one on moodle A and the public key for Moodle A is reported as being blank:
"The public key you are holding for this host is different from the public key it is currently publishing.
The current public key is: <BLANK>"
However in spite of the above error message we find users can still logon to Moodle A and get to content on Moodle B SOME OF THE TIME.
Is anyone aware of similar MNET issues for the windows platform?
If so is there a resolution to these problems?
Any ideas at all out there?
If you were me would you throw away Windows Moodle A and start over again with a Linux/LAMPP Moodle A?
Thanks for your attention so far.