Re: Win32 The RPC server is unavailable



In news:2D2868A5-2881-4CB6-AFBB-92B5ECF1129D@xxxxxxxxxxxxx,
kalamiti <kalamiti@xxxxxxxxxxxxxxxxxxxxxxxxx> stated, which I commented on
below:
I am trying to run an inventory program and it is failing because of
WMI errors the seem to be RPC related. I have been testing the
problem with wbemtest. I get the RPC unavailable error and in the
event viewer it shows up with this error DCOM was unable to
communicate with the computer name using any of the configured
protocols. All od the port are unblocked between the servers and the
one I am using and I have tested some ports with telnet: 135,139,445.
The account has admin access and can be used to remote and of the
servers I am trying to inventory. Please help

Usually RPC errors are due to name resolution or blocked ports. Keep in
mind, the ports you mentioned are not the only ports required. Besides
authentication traffic ports (Kerberos, LDAP, GC, etc), it also needs UDP
1023 wide open.

Back to name resolution: What DNS addresses is the workstation running the
app using in it's IP properties? Is this all setup in an AD environment? If
so, and using the wrong DNS addresses, this can be the cause. But there are
other issues that can cause it to that is related to DNS and AD
misconfiguration.

So it depends on your environment, configuration and infrastructure. If you
can elaborate and offer an ipconfig /all of this workstation for starters,
and possibly of one of your local DCs, we can see if that part is configured
correctly. If going across a router to authenticate/connect, then also make
sure all ports are opened as well as leaving the MTU settings to 1500. ADSL
is also known to cause RPC issues across a VPN using ADSL as one of the
endpoints.

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...


.



Relevant Pages

  • Re: need explanation from a question for 70-291 exam MS Press bo
    ... subsection, I'm pretty sure that I won't get any answer from there. ... If you were to allow PPTP, then you would need these ports in additon: ... Microsoft MVP - Directory Services ... Instead of the website you're using, try using OEx (Outlook Express ...
    (microsoft.public.windows.server.networking)
  • Re: RPC ports over a firewall
    ... > 1) Does the RPC need to be restricted to a static port on ServerB as well ... you restrict RPC to a small number of ports. ... UDP 88 Kerberos Authentication ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcpromo failed
    ... way to lock rpc down to specific ports and keep high ports turned off. ... MVP - Directory Services ... I disjoined the server from the domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RCP/HTTPS on SBS 2003 Server
    ... Certianly not needed for RPC over HTTP. ... Did you open the correct ports on your server's router as well? ... So we know all the server components are installed> correctly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Ports when used on DMZ
    ... When I was doing testing, the absolute minimum was - RPC with 1 static port, ... DNS (UDP only is sufficient if no long response is expected), ... > than likely your problem is with dynamic RPC in that you are finding ports ... > 1025-1030 being dropped by your firewall. ...
    (microsoft.public.security)

Loading