Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2858
  • Last Modified:

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?
0
rascal
Asked:
rascal
  • 5
  • 4
1 Solution
 
AkinsdNetwork AdministratorCommented:
Check the settings in services - it should be set to automatic, if not, set it.

Also check port 135 on firewall

Check DNS resolution

Is dotnet framework 3.5 enabled on the server role? If not enable it.
0
 
rascalAuthor Commented:
Thanks Akinsd,
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.
0
 
AkinsdNetwork AdministratorCommented:
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
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
rascalAuthor Commented:
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.
0
 
rascalAuthor Commented:
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.replace(/[^\/]+$/, ''),

            init : function() {
                  $().ajaxError(function(e, req, se) {
                        if (req.status)
                              $.WindowManager.status({title : "The server response wasn't JSON format", content : req.responseText});
                  });
            },
0
 
AkinsdNetwork AdministratorCommented:
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
0
 
rascalAuthor Commented:
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.
0
 
AkinsdNetwork AdministratorCommented:
Great!
Glad to hear that
0
 
rascalAuthor Commented:
The actual problem was external (see last comment by Rascal) but your response was completely appropriate. Thanks!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now