RPC server not available- Error message

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hello ..

I am trying to connect to a server using RDP, but I get a message "RPC server is not available".

Any idea.

Regards,

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Well - you havn't given us much to go on!

NAT? Firewalls? Server running? Changed port on server? Using a gateway?

Harry.

 

I would first check if you have a network connection. look under network connection in control panel.

Look at the properties of the connection. Is the IP address and DNS address manually or automatic configured?

Second do you have a roaming or local profile?

 

Harry's right we need more info what server system is it? What type of network, switches hub do you have an error message ID event code?
Can you give us a screen shot

The other thing you could try is pinging the server

 

I am able to connect to the machine using local ADMINISTRATOR account, but when I try to log on using a DOMAIN ACCOUNT, it is not able to log me in.

 

This is over my head so I'm just throwing this out here. Wouldn't the event log give a more detailed error report then "RPC server is not available"?

 

stolenblessing,

Questions:

1. When you say "I am able to connect to the machine..." is it possible that you are logging into your local client machine instead of the remote computer?
2. What Operating System is running on your client computer?
3. What Operating System is running on the remote computer?

 

Just a wild guess...

stolenblessing if you are using XP/SP2 turn off the firewall and see if that works....

I've had a similar issue once where the XP firewall was stoping remote access to rsop data, turned it off and queries were running fine.

Amine

 

Is your there a domain controller online on the network, if so can you communicate with it?

 

I'm just looking at the same issue with one of my servers... think its an authentication error between the server and the DC.

I can login immediately after a reboot with a domain account, but after a couple of days i get the same error.

Do you have any A/V installed on yours? I've removed mine temporarily, and have took everything off except the print server and MySql databases.

Anything in common there?

ta
Karl

 

We get this at work sometimes on our systems.

This week it was because some units were on one subnet and the other on a different subnet, even though it seemed they were on the same IP range.

If it were me i would start from the begining and check all IP settings are correct, the User logged in is correct,
is There is a connection to the DC (maybe try from another pc?) disable any firewalls etc.

 

I'm sure it is one of the earlier mentioned issues, but that will sometimes happen if you have a memory leak on your server. We have Trend Mico on our network, and it causes random non-paged pool memory leaks. If we start having issues with the server and we go to RDP in, we'll get that message. We'll usually need to connect to the console via ILO and end up getting a memory error when attempting to log on. We then need to flip the server and we are back in business. Hopefully you are just dealing with a setting somewhere (which is most likely the case). I wouldn't wish memory leaks on anyone.

 

edit sorry wrong letters

RDT

 

I get this error at one of my clients' networks, when trying to add users to local users and grous. I can usually get around it by running ipconfig /flushdns on the machine having the problem.

 

Last time i got this error i had to reboot the domain controller for it to be resolved. Other stuff was affected as well, thank god for another 7 DC's so it didn't really matter