Re: RPC server is unavailable

Tech-Archive recommends: Fix windows errors by optimizing your registry

If the Windows Firewall was disabled on the client computer then the problem
is not related to the Windows Firewall. The link below explains how the
Windows Firewall needs to be configured including the use of the allow use
of remote administration exception.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/BookofSP1/a940a24d-34c2-471c-89e5-d9f1500374c9.mspx

But since it does not appear to be a firewall issue you need to run the
support tools dcdiag, netdiag, and gpotool on your domain controllers to
make sure they are configured correctly particularly in regard to dns,
proper services are running, and they are replicating correctly. Also check
Event Viewer on your domain controllers for any pertinent errors.

Run the support tool netdiag on a couple client domain computers where you
can not run RSOP to see what is reported, check Event Viewer for any
pertinent errors, run the support tool gpresut on the client computer to see
what it reports as far as the domain controller used, Group Policies
applied, and the last time they were applied for the computer/user, verify
that the client computer can ping the domain controller by name and IP
address and that the domain controller can do the same to the client, verify
that an administrator can access the administrative share such as C$ on the
domain client from the domain controller, verify that the domain user logged
onto the client computer can access the sysvol share on the domain
controller which can be seen in My Network Places, and use nsloookup to
verify that the client computer can access the _srv records of the domain
controller as shown in the first KB article below. If ipsec is used in the
domain it must be configured so that domain computers do not use ipsec for
traffic to and from domain controllers. You can not run a RSOP against a
domain user/computer unless that domain user has successfuly logged onto the
domain computer at least once. If you still are having problems see the
second link below on how to troubleshoot RPC errors. --- Steve

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sag_dns_tro_dclocator_verifysrv.mspx
http://support.microsoft.com/default.aspx?scid=kb;en-us;839880



"gafoorgk" <gafoorgk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43B16DC3-5A37-4F43-B45C-17CB14B3B54D@xxxxxxxxxxxxxxxx
>i tried that before. i tried it again in every client, but getting the same
> error. any other solution ?!!!
>
> "Steven L Umbach" wrote:
>
>> Try temporarily disabling the firewall on a computer or two to see what
>> happens. If that works you know it is firewall related and you can
>> troubleshoot further by enabling logging of the Windows Firewall to see
>> what
>> traffic is dropped when it is enabled. If it is not the firewall than the
>> problem could be dns related and using the support tool netdiag on your
>> XP
>> Pro client computers would be worth trying to see if any pertinent
>> problems
>> are found such as dns, dc discovery, or trust/secure channel. Review the
>> KB
>> link below to make sure dns is configured correctly in your domain. ---
>> Steve
>>
>> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382
>>
>> "gafoorgk" <gafoorgk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:C29168A1-AFEC-4E85-A79C-F3F5AAECF598@xxxxxxxxxxxxxxxx
>> >i am trying to get resultant set of policies in each XP SP2 client from
>> > Windows 2003 Server. it's giving me error msg "The RPC server is not
>> > available".
>> >
>> > i used portqryui to query port 135 in each client. it's saying
>> > LISTENING,
>> > but also says "RPC query failed (5)" with return code 0x00000000
>> >
>> > when i used portqueryui to query port 135 on the server, it says
>> > LISTENING
>> > and works fine.
>> >
>> > all related ports are open in each WinXP SP2 client firewall.
>> >
>> > what could be wrong? please help
>> >
>>
>>
>>


.

Relevant Pages

  • Re: Setting up DHCP
    ... My machine has 2 NICs and is a domain controller. ... All the the "home user" Firewall device are ... But I'm having to specify a DNS server address on the ... and are not effected by by subnet that the Client is in. ...
    (microsoft.public.windows.server.networking)
  • RE: I can not Access other pc and server in my domin?
    ... The domain client will query the Domain Controller to get the ... Double check your WINS server if you have. ... Please check if you have firewall installed on the client. ...
    (microsoft.public.windows.server.sbs)
  • RE: I can not Access other pc and server in my domin?
    ... The domain client will query the Domain Controller to get the ... Verify if the computer browser service is working on the domain ... Please check if you have firewall installed on the client. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD Authentication Process
    ... The domain controller uses the site information ... to check the IP address of the client computer against the list of subnets ... in the forest. ...
    (microsoft.public.windows.server.dns)
  • Event ID 8003
    ... I have a domain controller that keeps getting this error every hour or so. ... The master browser has received a server announcement from the computer ... I'm using Symantec Client Firewall and I disabled it and then the 8003 ...
    (microsoft.public.windows.server.general)