Home All Groups Group Topic Archive Search About

remote procedure call failed and did not execute

Author
23 Oct 2006 4:31 PM
Crickee
Have been running my XP/SP2 machine that authenticates to my company network
for months without problems. I went to logon to my network this morning and
the logon takes a long time. Once connected I do not have access to my
network components (shared drives, applications, etc.). If I run an IPCONFIG
all looks fine. There is an event log entry that states the following error:

"No domain controller is available for domain 'MYDOMAIN' due to the
following error: the remote procedure call failed and did not execute"

If I restart my PC in safe mode with network support then I do not have any
problems (access to newtork components are fine). This scenario has also
occurred with a brand new PC that we attempted to deploy into our network.

This is obviously causing major problems and I am very concerned that this
will propogate to other users. I have searched the KB and came across a ton
of potential troubleshooting techniques but to no avail thus far.

Any help would be greatly appreciated!!

Author
23 Oct 2006 7:08 PM
Robert L [MVP - Networking]
I would check   DNS settings first. Or this troubleshooting may help,

Network errors Remote Procedure Call Failed · The remote procedure call failed and did not run RPC Server is Unavailable TCP/IP transport not installed ...
      www.chicagotech.net/neterrors.htm 


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
  "Crickee" <Cric***@discussions.microsoft.com> wrote in message news:63EB2F25-DDC4-4DD0-ACB0-6EA2B9AB7BF1@microsoft.com...
  Have been running my XP/SP2 machine that authenticates to my company network
  for months without problems. I went to logon to my network this morning and
  the logon takes a long time. Once connected I do not have access to my
  network components (shared drives, applications, etc.). If I run an IPCONFIG
  all looks fine. There is an event log entry that states the following error:

  "No domain controller is available for domain 'MYDOMAIN' due to the
  following error: the remote procedure call failed and did not execute"

  If I restart my PC in safe mode with network support then I do not have any
  problems (access to newtork components are fine). This scenario has also
  occurred with a brand new PC that we attempted to deploy into our network.

  This is obviously causing major problems and I am very concerned that this
  will propogate to other users. I have searched the KB and came across a ton
  of potential troubleshooting techniques but to no avail thus far.

  Any help would be greatly appreciated!!
Author
23 Oct 2006 9:15 PM
Crickee
Thanks for the quick response!!

Stopping the Microsoft Firewall services solved my problem... I had it
disabled through the GUI but I guess that was not enough... I now have it
disabled in the services...

Show quoteHide quote
"Robert L [MVP - Networking]" wrote:

> I would check   DNS settings first. Or this troubleshooting may help,
>
> Network errors Remote Procedure Call Failed · The remote procedure call failed and did not run RPC Server is Unavailable TCP/IP transport not installed ...
>       www.chicagotech.net/neterrors.htm 
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>   "Crickee" <Cric***@discussions.microsoft.com> wrote in message news:63EB2F25-DDC4-4DD0-ACB0-6EA2B9AB7BF1@microsoft.com...
>   Have been running my XP/SP2 machine that authenticates to my company network
>   for months without problems. I went to logon to my network this morning and
>   the logon takes a long time. Once connected I do not have access to my
>   network components (shared drives, applications, etc.). If I run an IPCONFIG
>   all looks fine. There is an event log entry that states the following error:
>
>   "No domain controller is available for domain 'MYDOMAIN' due to the
>   following error: the remote procedure call failed and did not execute"
>
>   If I restart my PC in safe mode with network support then I do not have any
>   problems (access to newtork components are fine). This scenario has also
>   occurred with a brand new PC that we attempted to deploy into our network.
>
>   This is obviously causing major problems and I am very concerned that this
>   will propogate to other users. I have searched the KB and came across a ton
>   of potential troubleshooting techniques but to no avail thus far.
>
>   Any help would be greatly appreciated!!
Author
24 Oct 2006 12:47 PM
Crickee
Follow up:

Bob - do you have any idea as to why this would have occurred all of a
sudden? I have many other workstations that do not experience this problem.
As mentioned before, my PC had no issues until I turned it off/on (same with
the new PC).

So, if I want to use the Windows Firewall, I have to enable the service and
jeopordize my PC again... strange...

Any insights would be appreciated...

Show quoteHide quote
"Crickee" wrote:

> Thanks for the quick response!!
>
> Stopping the Microsoft Firewall services solved my problem... I had it
> disabled through the GUI but I guess that was not enough... I now have it
> disabled in the services...
>
> "Robert L [MVP - Networking]" wrote:
>
> > I would check   DNS settings first. Or this troubleshooting may help,
> >
> > Network errors Remote Procedure Call Failed · The remote procedure call failed and did not run RPC Server is Unavailable TCP/IP transport not installed ...
> >       www.chicagotech.net/neterrors.htm 
> >
> >
> > Bob Lin, MS-MVP, MCSE & CNE
> > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> >   "Crickee" <Cric***@discussions.microsoft.com> wrote in message news:63EB2F25-DDC4-4DD0-ACB0-6EA2B9AB7BF1@microsoft.com...
> >   Have been running my XP/SP2 machine that authenticates to my company network
> >   for months without problems. I went to logon to my network this morning and
> >   the logon takes a long time. Once connected I do not have access to my
> >   network components (shared drives, applications, etc.). If I run an IPCONFIG
> >   all looks fine. There is an event log entry that states the following error:
> >
> >   "No domain controller is available for domain 'MYDOMAIN' due to the
> >   following error: the remote procedure call failed and did not execute"
> >
> >   If I restart my PC in safe mode with network support then I do not have any
> >   problems (access to newtork components are fine). This scenario has also
> >   occurred with a brand new PC that we attempted to deploy into our network.
> >
> >   This is obviously causing major problems and I am very concerned that this
> >   will propogate to other users. I have searched the KB and came across a ton
> >   of potential troubleshooting techniques but to no avail thus far.
> >
> >   Any help would be greatly appreciated!!
Author
24 Oct 2006 2:46 PM
Robert L [MVP - Networking]
These disputations may help,

A domain controller could not be contacted - Solution 14 Oct 2006
  Re: A domain controller could not be contacted - Solution Bob 14 Oct 2006
  Re: A domain controller could not be contacted - Solution 14 Oct 2006
http://chicagotech.net/discussions.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
  "Crickee" <Cric***@discussions.microsoft.com> wrote in message news:56710670-BEE7-4F19-B900-0DBB0C70C7B5@microsoft.com...
  Follow up:

  Bob - do you have any idea as to why this would have occurred all of a
  sudden? I have many other workstations that do not experience this problem.
  As mentioned before, my PC had no issues until I turned it off/on (same with
  the new PC).

  So, if I want to use the Windows Firewall, I have to enable the service and
  jeopordize my PC again... strange...

  Any insights would be appreciated...

Show quoteHide quote
  "Crickee" wrote:

  > Thanks for the quick response!!
  >
  > Stopping the Microsoft Firewall services solved my problem... I had it
  > disabled through the GUI but I guess that was not enough... I now have it
  > disabled in the services...
  >
  > "Robert L [MVP - Networking]" wrote:
  >
  > > I would check   DNS settings first. Or this troubleshooting may help,
  > >
  > > Network errors Remote Procedure Call Failed · The remote procedure call failed and did not run RPC Server is Unavailable TCP/IP transport not installed ...
  > >       www.chicagotech.net/neterrors.htm 
  > >
  > >
  > > Bob Lin, MS-MVP, MCSE & CNE
  > > Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
  > > How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
  > >   "Crickee" <Cric***@discussions.microsoft.com> wrote in message news:63EB2F25-DDC4-4DD0-ACB0-6EA2B9AB7BF1@microsoft.com...
  > >   Have been running my XP/SP2 machine that authenticates to my company network
  > >   for months without problems. I went to logon to my network this morning and
  > >   the logon takes a long time. Once connected I do not have access to my
  > >   network components (shared drives, applications, etc.). If I run an IPCONFIG
  > >   all looks fine. There is an event log entry that states the following error:
  > >
  > >   "No domain controller is available for domain 'MYDOMAIN' due to the
  > >   following error: the remote procedure call failed and did not execute"
  > >
  > >   If I restart my PC in safe mode with network support then I do not have any
  > >   problems (access to newtork components are fine). This scenario has also
  > >   occurred with a brand new PC that we attempted to deploy into our network.
  > >
  > >   This is obviously causing major problems and I am very concerned that this
  > >   will propogate to other users. I have searched the KB and came across a ton
  > >   of potential troubleshooting techniques but to no avail thus far.
  > >
  > >   Any help would be greatly appreciated!!