Re: RPC server is unavailable
From: Scott Elgram (SElgram_at_verifpoint.com)
Date: 04/11/05
- Next message: Jim Matthews: "Can't assign "log on locally" right"
- Previous message: Carlos A. Morillo: "802.1x Authentication for non-domain machines"
- In reply to: Steven L Umbach: "Re: RPC server is unavailable"
- Next in thread: Steven L Umbach: "Re: RPC server is unavailable"
- Reply: Steven L Umbach: "Re: RPC server is unavailable"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 11 Apr 2005 12:18:11 -0700
Yes, Netdiag showed Pass on the DC too. I checked the "Trust computer for
delegation" and re-ran DCDiag and now all tests pass. But the problem is
still showing up in the logs of some machines. I have not rebooted the DC
yet and probably will not be able to for some time.
Last week I went through the Event log of every computer on the network
and discovered that all the affected systems have MSN Messenger installed
and the unaffected machines do not. This lead me to think maybe it could be
a problem between the machines and the MSN server because of my firewall.
After looking into it some more I remembered that this issue did not start
until about a month ago and there have been no significant changes made to
it that could affect communication between a computer on the network and the
internet. Just for kicks though I checked the log and could not find any
entry coinciding with the messages in the event logs.
-Scott
"Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
news:%23N1gB6IPFHA.3188@TK2MSFTNGP10.phx.gbl...
> Did netdiag show a pass for everything on the domain controller?? The
error
> below is significant. Find the computer account for the DC in AD Users and
> Computers and look in properties and make sure "trust computer for
> delegation" is checked which domain controllers should be. I don't know if
> that is the krux of the problem but that would be a good start and then
see
> if that error goes away with dcdiag or not. I don't know if the domain
> controller needs to be restarted after enabling for delegation. If the
error
> in dcdiag persists it would be a good idea to restart it if it will not
> cause too much disruption. Also see if there are any pertinent events in
> Event Viewer on the domain controller that may be helpful. --- Steve
>
>
> "Scott Elgram" <SElgram@verifpoint.com> wrote in message
> news:uV55SxHPFHA.1176@TK2MSFTNGP12.phx.gbl...
> >I ran NetDiag on some of the affected machines and received pass on all
> > tests performed, additionally, I ran DcDiag on the domain controller and
> > received a pass on all tests performed except
>
> -------------------------------------------------------------------------
> > Starting test: MachineAccount
> > * MAINSERVER is not trusted for account delegation
> > ......................... MAINSERVER failed test MachineAccount
>
> -------------------------------------------------------------------------
> > If I am reading this right the above failed test doesn't matter because
my
> > DC is the only one on the network. Is this correct?, any other thoughts
> > on
> > this matter?
> >
> > -Scott
> >
> > "Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
> > news:uETOGgFPFHA.3668@TK2MSFTNGP14.phx.gbl...
> >> See the link below for more details as this is often a name resolution
or
> >> network connectivity problem. Your domain clients should be able to
ping
> > the
> >> domain controller by it's IP address and fully qualified domain name as
> >> in
> >> dc1.mydomain.com as an example of a FQDN. The domain controller should
be
> >> able to do the same for the domain clients. Look in Event Viewer on the
> >> domain controller to see if any related events are being recorded that
> >> may
> >> help you resolve the problem such as failed services,etc. The support
> >> tool
> >> netdiag and dcdiag are also very helpful in tracking down domain
> >> configuration/network connectivity problems. Use netdiag on any
computer
> > and
> >> dcdiag on just domain controllers. Dns misconfiguration in the domain
for
> >> domain clients [Windows 2000/XP/2003] and/or domain controllers also is
> >> often the cause of such problems. If you are using downlevel clients
in
> > the
> >> domain, netbios name resolution also needs to be correctly configured
> >> with
> >> domain controllers also being wins clients. --- Steve
> >>
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q224370
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;321708 ---
> > netdiag
> >> and how to install support tools.
> >> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382 --
> >> AD
> >> dns FAQ.
> >>
> >>
> >> "Scott Elgram" <SElgram@verifpoint.com> wrote in message
> >> news:uSuN5RFPFHA.2532@TK2MSFTNGP09.phx.gbl...
> >> > Hello,
> >> > I have recently been experiencing a problem on many of the
computers
> > on
> >> > my network. All these affected systems are having trouble logging
off.
> >> > From what I have been able to find out I believe that this problem is
> > some
> >> > how related to similar errors like this:
> >> > -------------------------------------------
> >> > The COM+ Event System failed to fire the Logoff method on
subscription
> >> > {AAD1D51F-1279-4831-8684-D99F99B3CC62}. The subscriber returned
> >> > HRESULT
> >> > 800706BA.
> >> > -------------------------------------------
> >> > After some research into these problems I found that 800706BA
refers
> > to
> >> > 0x800706BA which means "The RPC server is unavailable". This is
where
> > I'm
> >> > stuck......if I am understanding this right it's a problem with my
> >> > Win2k
> >> > Server and or the communication between the server and the affected
> >> > machines. I also found that this is a side effect from the MSBlaster
> >> > virus
> >> > because it utilizes DCom and the RPC server for it self. So I ran
> >> > scans
> >> > but
> >> > found nothing.
> >> >
> >> > Any suggestions on how I may resolve this please?
> >> > --
> >> > -Scott
> >> >
> >> >
> >>
> >>
> >
> >
>
>
- Next message: Jim Matthews: "Can't assign "log on locally" right"
- Previous message: Carlos A. Morillo: "802.1x Authentication for non-domain machines"
- In reply to: Steven L Umbach: "Re: RPC server is unavailable"
- Next in thread: Steven L Umbach: "Re: RPC server is unavailable"
- Reply: Steven L Umbach: "Re: RPC server is unavailable"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
