asked on
Windows Remote Management Fails When Connecting to Computer with RPC Server Error
I am attempting to connect to several workstation through the active directory users and computers snap in. I right click on the computer and select manage, after a period of time I receive and error saying that the "RPC Server is not available", all computers are windows 7, some computers have Norton 360 Firewall and others have the microsoft security essentials, if I disable the fire wall, I can connect and remotely manage, except when I attempt to access the Disk Management Snap in, when I receive a message that Disk management could not start the VDS service, and that the remote computer does not support VDS or is blocked by a firewall.
Do I need to setup an incoming rule in the firewall for the remote managment, if so, what do I need to do for Norton 360 V6 and Microsoft Security Suite. What needs to be done to address the Disk Management issue.
Thank you
Steve
Do I need to setup an incoming rule in the firewall for the remote managment, if so, what do I need to do for Norton 360 V6 and Microsoft Security Suite. What needs to be done to address the Disk Management issue.
Thank you
Steve
Windows OSMicrosoft Legacy OSWindows 7
Last Comment
LeeTutor
ASKER
Thank you for taking the time to answer, I am connecting from the server to a workstation. The article did mention to start the VDD service in control panel, which I did and set to automatic, I also enabled the netbios over tcpip. I have no trouble getting a remote desktop connection, but still getting that RPC error. I am uninstalling Norton 360, and installing the MS Security Essentials, I setup a few group policy settings to create some firewall exceptions. Thanks again and lets see if this helps. Thanks
ASKER
I also ran winrm quickconfig on the workstation and server, I am still getting the "RPC Server not available" message when attempting to connect to the windows 7 computer using the manage option in the active directory users and computers. When I also attempt to access device manager, I receive a message that the "computer can not be accessed, make sure that this computer is on the network, remove administration is enabled and the plug and play and remote registry services are running", I checked and verified that all these settings are enabled and running.
I found several articles on group policy settings to enable remote management access, most of these I had already set at the workstation level. Still no improvement. Thank you.
I found several articles on group policy settings to enable remote management access, most of these I had already set at the workstation level. Still no improvement. Thank you.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I disabled the Norton 360 firewall, after that I was able to remotely manage the workstation from the fileserver, although the disk management and the device manager wound not work. Since and can manage the firewall setting from group policy, I removed Norton 360, installed the security essentials, and used group policy to configure the firewall and was able to remotely manage although I could still not access the disk or devices management. I could have left the Norton installed and just disabled the firewall and enable the windows firewall, but I thought using Norton was just a habit, with the security essentials and the other tools in WIN7 and WIN8 I am thinking Norton is less necessary.
Thank for the advice, and will get that posted asap.
all the best
Steve
Thank for the advice, and will get that posted asap.
all the best
Steve
ASKER
I have been off for a few days, thanks for the advice, I am working on generating the GPResult File.
Thank You
Steve
Thank You
Steve
I've requested that this question be deleted for the following reason:
Not enough information to confirm an answer.
Not enough information to confirm an answer.
http://www.petri.co.il/rpc-server-is-unavailable-error.htm