rascal
asked on
How to enable RPC on Windows Server 2008 R2?
Hi Experts,
I am not a regular 'server guy' but am trouble-shooting an issue where it appears RPC is not enabled on a Windows Server 2008 R2. It's a brand new installation so may not have everything turned on that has to be. With all the myriad screens for services, rules, features, permissions, roles, and you name it whatever other terminologies are called (my last experience was with Windows 2000 Server!) I'm somewhat overwhelmed.
Can someone explain how (or if it's even possible to configure) to enable RPC on Windows Server 2008 R2?
I am not a regular 'server guy' but am trouble-shooting an issue where it appears RPC is not enabled on a Windows Server 2008 R2. It's a brand new installation so may not have everything turned on that has to be. With all the myriad screens for services, rules, features, permissions, roles, and you name it whatever other terminologies are called (my last experience was with Windows 2000 Server!) I'm somewhat overwhelmed.
Can someone explain how (or if it's even possible to configure) to enable RPC on Windows Server 2008 R2?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try pinging the server by NetBIOS (eg SERVER1) name and also by fqdn (eg SERVER1.domain.local).
If pings are successful in both tests, then you can overrule DNS resolution
If pings are successful in both tests, then you can overrule DNS resolution
ASKER
Thanks, and by the way, this whole issue came about since I was running TinyMCE (it's image manager) on the server and when attempting to view a folder, it clocked/timed-out and came back with a message: Server Error, produced by a source code file called rpc.js so I assume it was a remote procedure call issue since the website is an exact copy of the one on our test servers here in our office where the software runs fine.
ASKER
More details: The rpc.js file contains the following code, where the "The server response wasn't JSON format" message is presented. It's actually trying to execute an ajax function(?) so are there other settings that need to be set on a Windows Server 2008 R2 to allow ajax to execute?
(function($){
window.RPC = {
pageBaseURL : document.location.href.rep lace(/[^\/ ]+$/, ''),
init : function() {
$().ajaxError(function(e, req, se) {
if (req.status)
$.WindowManager.status({ti tle : "The server response wasn't JSON format", content : req.responseText});
});
},
(function($){
window.RPC = {
pageBaseURL : document.location.href.rep
init : function() {
$().ajaxError(function(e, req, se) {
if (req.status)
$.WindowManager.status({ti
});
},
I'm going to assume that IIS is already enabled.
If it was working prior to crashing, try removing and re-installing the following
- IIS
- Dot net framework (2 or 3 or 4 or all as desired)
You may also try installing the Ajax plugin for aspx
http://www.microsoft.com/en-us/download/details.aspx?id=883
If it was working prior to crashing, try removing and re-installing the following
- IIS
- Dot net framework (2 or 3 or 4 or all as desired)
You may also try installing the Ajax plugin for aspx
http://www.microsoft.com/en-us/download/details.aspx?id=883
ASKER
We discovered that the problem was caused by the file ModCloudFlare. When we disabled that we were able to get into our admin side of the WordPress site . We removed and reinstalled the iThemes security plugin just in case, although from the log files it looks like just ModCloudFlare was the culprit.
Great!
Glad to hear that
Glad to hear that
ASKER
The actual problem was external (see last comment by Rascal) but your response was completely appropriate. Thanks!
ASKER
I will check the RPC server to ensure it's set to "automatic", and will check the firewall port 135.
What specifically should I check when you refer to "check DNS resolution" however?
and dotnet 3.5 is enabled on the server role.