RPC Service unavailable

Dear all,

Strange problem to solve...

I have migrated 2003 server to another server and all seem to work fine.
All the logons work perfect but there's something wrong with DNS, internet
on client computers don't work and also the GPO's do not reach the clients.
With an internal test for GPO's they work fine but when actualy testing them
on client computers I get the error: RPC service unavailable.

I have reinstalled both DHCP and DNS server but that diddn't help.

My best guess is because of a problem with RPC Service the DNS won't work as
it should (on the server internet works fine), and the cause is that
replicating the servers while migrating diddn't went well (and the old server
died already).

I have not one idea how to fix this RPC Service and get the DNS working
properly...

anyone ideas??

Hi there, firstly have you run ipconfig /all on the clients to check they
have the server configured as their dns server? Is the server installed with
Server 2003 SP2? Make sure all the latest updates are installed on the
server? From the clients are you able to ping an ip address on the internet,
this will test conenctivity and take dns out of the equation. On the server
go Start>Run>"services.msc"> Enter. Then in the services console scroll down
to Remote Procedure Call and check that the service is running. Right click
it and >Properties. Check the recovery tab and make sure that the service is
always configured to restart if it fails. Let me know how youget on, good
luck!! James.
--
James Yeomans, BSc, MCSE


"Harmjan Olthoff" wrote:

> Dear all,
>
> Strange problem to solve...
>
> I have migrated 2003 server to another server and all seem to work fine.
> All the logons work perfect but there's something wrong with DNS, internet
> on client computers don't work and also the GPO's do not reach the clients.
> With an internal test for GPO's they work fine but when actualy testing them
> on client computers I get the error: RPC service unavailable.
>
> I have reinstalled both DHCP and DNS server but that diddn't help.
>
> My best guess is because of a problem with RPC Service the DNS won't work as
> it should (on the server internet works fine), and the cause is that
> replicating the servers while migrating diddn't went well (and the old server
> died already).
>
> I have not one idea how to fix this RPC Service and get the DNS working
> properly...
>
> anyone ideas??

Dear James,

All the clients get the corret IP, Gateway and DNS from the server, if I
configure them manualy with the same DNS and Gateway all works fine.
The server is the latest 2003 R2 server with SP2.
If I can ping an IP adress from a client I have to test again, I thought I
could but Im not sure.
On the server RPC is running and starts automaticly and on recovery tab it's
set on reboot when failure.

hopefully this information wil help examening the problem

"James Yeomans BSc, MCSE" wrote:

> Hi there, firstly have you run ipconfig /all on the clients to check they
> have the server configured as their dns server? Is the server installed with
> Server 2003 SP2? Make sure all the latest updates are installed on the
> server? From the clients are you able to ping an ip address on the internet,
> this will test conenctivity and take dns out of the equation. On the server
> go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> to Remote Procedure Call and check that the service is running. Right click
> it and >Properties. Check the recovery tab and make sure that the service is
> always configured to restart if it fails. Let me know how youget on, good
> luck!! James.
> --
> James Yeomans, BSc, MCSE
>
>
> "Harmjan Olthoff" wrote:
>
> > Dear all,
> >
> > Strange problem to solve...
> >
> > I have migrated 2003 server to another server and all seem to work fine.
> > All the logons work perfect but there's something wrong with DNS, internet
> > on client computers don't work and also the GPO's do not reach the clients.
> > With an internal test for GPO's they work fine but when actualy testing them
> > on client computers I get the error: RPC service unavailable.
> >
> > I have reinstalled both DHCP and DNS server but that diddn't help.
> >
> > My best guess is because of a problem with RPC Service the DNS won't work as
> > it should (on the server internet works fine), and the cause is that
> > replicating the servers while migrating diddn't went well (and the old server
> > died already).
> >
> > I have not one idea how to fix this RPC Service and get the DNS working
> > properly...
> >
> > anyone ideas??

Just confirm that if you configure them statically then it everything works
fine but if they are dhcp clients then thats when you get the rpc problems?
Do you have the dhcp client service running on the server?It needs to be to
update dns records etc (believe it or not).
--
James Yeomans, BSc, MCSE


"Harmjan Olthoff" wrote:

> Dear James,
>
> All the clients get the corret IP, Gateway and DNS from the server, if I
> configure them manualy with the same DNS and Gateway all works fine.
> The server is the latest 2003 R2 server with SP2.
> If I can ping an IP adress from a client I have to test again, I thought I
> could but Im not sure.
> On the server RPC is running and starts automaticly and on recovery tab it's
> set on reboot when failure.
>
> hopefully this information wil help examening the problem
>
> "James Yeomans BSc, MCSE" wrote:
>
> > Hi there, firstly have you run ipconfig /all on the clients to check they
> > have the server configured as their dns server? Is the server installed with
> > Server 2003 SP2? Make sure all the latest updates are installed on the
> > server? From the clients are you able to ping an ip address on the internet,
> > this will test conenctivity and take dns out of the equation. On the server
> > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > to Remote Procedure Call and check that the service is running. Right click
> > it and >Properties. Check the recovery tab and make sure that the service is
> > always configured to restart if it fails. Let me know how youget on, good
> > luck!! James.
> > --
> > James Yeomans, BSc, MCSE
> >
> >
> > "Harmjan Olthoff" wrote:
> >
> > > Dear all,
> > >
> > > Strange problem to solve...
> > >
> > > I have migrated 2003 server to another server and all seem to work fine.
> > > All the logons work perfect but there's something wrong with DNS, internet
> > > on client computers don't work and also the GPO's do not reach the clients.
> > > With an internal test for GPO's they work fine but when actualy testing them
> > > on client computers I get the error: RPC service unavailable.
> > >
> > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > >
> > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > it should (on the server internet works fine), and the cause is that
> > > replicating the servers while migrating diddn't went well (and the old server
> > > died already).
> > >
> > > I have not one idea how to fix this RPC Service and get the DNS working
> > > properly...
> > >
> > > anyone ideas??

Dear James,

Thanx for the very quick responces.
I am now behind the server and checked some things.

The clients can ping external IP adresses but no names.
When I configure it manualy it does work fine.
On the server both DNS client and server, and both DHCP client and server
are running.

The RPC error I receive when I test GPO's with Group policy results.
before I got the message when opening Group policy management but that
message is gone and GP management opens good.

Testing with Group modeling results run fine.

also the GPO on the server runs fine.

If there are any other answers I can give that wilo help...

Im working on this problem for about 2 weeks and I cannot see the problem

Thanx for the support!

"James Yeomans BSc, MCSE" wrote:

> Just confirm that if you configure them statically then it everything works
> fine but if they are dhcp clients then thats when you get the rpc problems?
> Do you have the dhcp client service running on the server?It needs to be to
> update dns records etc (believe it or not).
> --
> James Yeomans, BSc, MCSE
>
>
> "Harmjan Olthoff" wrote:
>
> > Dear James,
> >
> > All the clients get the corret IP, Gateway and DNS from the server, if I
> > configure them manualy with the same DNS and Gateway all works fine.
> > The server is the latest 2003 R2 server with SP2.
> > If I can ping an IP adress from a client I have to test again, I thought I
> > could but Im not sure.
> > On the server RPC is running and starts automaticly and on recovery tab it's
> > set on reboot when failure.
> >
> > hopefully this information wil help examening the problem
> >
> > "James Yeomans BSc, MCSE" wrote:
> >
> > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > have the server configured as their dns server? Is the server installed with
> > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > server? From the clients are you able to ping an ip address on the internet,
> > > this will test conenctivity and take dns out of the equation. On the server
> > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > to Remote Procedure Call and check that the service is running. Right click
> > > it and >Properties. Check the recovery tab and make sure that the service is
> > > always configured to restart if it fails. Let me know how youget on, good
> > > luck!! James.
> > > --
> > > James Yeomans, BSc, MCSE
> > >
> > >
> > > "Harmjan Olthoff" wrote:
> > >
> > > > Dear all,
> > > >
> > > > Strange problem to solve...
> > > >
> > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > on client computers I get the error: RPC service unavailable.
> > > >
> > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > >
> > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > it should (on the server internet works fine), and the cause is that
> > > > replicating the servers while migrating diddn't went well (and the old server
> > > > died already).
> > > >
> > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > properly...
> > > >
> > > > anyone ideas??

Maby some helpfull information:

The DNS event viewer gives Event ID 800.
I have troubleshooted this as good as pssible, checked settings in SOA but
it all seems to be normal.
Primary server is DC01.maddogs.local (that is the correct name)
Name server has FQDN and the right IP adress (192.168.2.2 and 127.0.0.1)
no WINS and no Zone Transfers are configured.

the old server was corrctly demoted and no replication between these servers
is configured however I do think this server is still looking for the old
server

"Harmjan Olthoff" wrote:

> Dear James,
>
> Thanx for the very quick responces.
> I am now behind the server and checked some things.
>
> The clients can ping external IP adresses but no names.
> When I configure it manualy it does work fine.
> On the server both DNS client and server, and both DHCP client and server
> are running.
>
> The RPC error I receive when I test GPO's with Group policy results.
> before I got the message when opening Group policy management but that
> message is gone and GP management opens good.
>
> Testing with Group modeling results run fine.
>
> also the GPO on the server runs fine.
>
> If there are any other answers I can give that wilo help...
>
> Im working on this problem for about 2 weeks and I cannot see the problem
>
> Thanx for the support!
>
> "James Yeomans BSc, MCSE" wrote:
>
> > Just confirm that if you configure them statically then it everything works
> > fine but if they are dhcp clients then thats when you get the rpc problems?
> > Do you have the dhcp client service running on the server?It needs to be to
> > update dns records etc (believe it or not).
> > --
> > James Yeomans, BSc, MCSE
> >
> >
> > "Harmjan Olthoff" wrote:
> >
> > > Dear James,
> > >
> > > All the clients get the corret IP, Gateway and DNS from the server, if I
> > > configure them manualy with the same DNS and Gateway all works fine.
> > > The server is the latest 2003 R2 server with SP2.
> > > If I can ping an IP adress from a client I have to test again, I thought I
> > > could but Im not sure.
> > > On the server RPC is running and starts automaticly and on recovery tab it's
> > > set on reboot when failure.
> > >
> > > hopefully this information wil help examening the problem
> > >
> > > "James Yeomans BSc, MCSE" wrote:
> > >
> > > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > > have the server configured as their dns server? Is the server installed with
> > > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > > server? From the clients are you able to ping an ip address on the internet,
> > > > this will test conenctivity and take dns out of the equation. On the server
> > > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > > to Remote Procedure Call and check that the service is running. Right click
> > > > it and >Properties. Check the recovery tab and make sure that the service is
> > > > always configured to restart if it fails. Let me know how youget on, good
> > > > luck!! James.
> > > > --
> > > > James Yeomans, BSc, MCSE
> > > >
> > > >
> > > > "Harmjan Olthoff" wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > Strange problem to solve...
> > > > >
> > > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > > on client computers I get the error: RPC service unavailable.
> > > > >
> > > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > > >
> > > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > > it should (on the server internet works fine), and the cause is that
> > > > > replicating the servers while migrating diddn't went well (and the old server
> > > > > died already).
> > > > >
> > > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > > properly...
> > > > >
> > > > > anyone ideas??

Have you checked the event logs on the workstations and the server, an RPC
failure should write an event to the event log? The only thing i can think of
is that the dhcp server is assigning some options incorrectly, is the server
definitely configured with the right subnet mask because thats the subnet
mask it will assign to clients. Are the dhcp scope options also configured to
assign a dns address and gateway? This is a strange one because assuming dhcp
is assigning the right options it makes no difference to a client whether its
got a static or dynamic ip. James :)
--
James Yeomans, BSc, MCSE


"Harmjan Olthoff" wrote:

> Dear James,
>
> Thanx for the very quick responces.
> I am now behind the server and checked some things.
>
> The clients can ping external IP adresses but no names.
> When I configure it manualy it does work fine.
> On the server both DNS client and server, and both DHCP client and server
> are running.
>
> The RPC error I receive when I test GPO's with Group policy results.
> before I got the message when opening Group policy management but that
> message is gone and GP management opens good.
>
> Testing with Group modeling results run fine.
>
> also the GPO on the server runs fine.
>
> If there are any other answers I can give that wilo help...
>
> Im working on this problem for about 2 weeks and I cannot see the problem
>
> Thanx for the support!
>
> "James Yeomans BSc, MCSE" wrote:
>
> > Just confirm that if you configure them statically then it everything works
> > fine but if they are dhcp clients then thats when you get the rpc problems?
> > Do you have the dhcp client service running on the server?It needs to be to
> > update dns records etc (believe it or not).
> > --
> > James Yeomans, BSc, MCSE
> >
> >
> > "Harmjan Olthoff" wrote:
> >
> > > Dear James,
> > >
> > > All the clients get the corret IP, Gateway and DNS from the server, if I
> > > configure them manualy with the same DNS and Gateway all works fine.
> > > The server is the latest 2003 R2 server with SP2.
> > > If I can ping an IP adress from a client I have to test again, I thought I
> > > could but Im not sure.
> > > On the server RPC is running and starts automaticly and on recovery tab it's
> > > set on reboot when failure.
> > >
> > > hopefully this information wil help examening the problem
> > >
> > > "James Yeomans BSc, MCSE" wrote:
> > >
> > > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > > have the server configured as their dns server? Is the server installed with
> > > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > > server? From the clients are you able to ping an ip address on the internet,
> > > > this will test conenctivity and take dns out of the equation. On the server
> > > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > > to Remote Procedure Call and check that the service is running. Right click
> > > > it and >Properties. Check the recovery tab and make sure that the service is
> > > > always configured to restart if it fails. Let me know how youget on, good
> > > > luck!! James.
> > > > --
> > > > James Yeomans, BSc, MCSE
> > > >
> > > >
> > > > "Harmjan Olthoff" wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > Strange problem to solve...
> > > > >
> > > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > > on client computers I get the error: RPC service unavailable.
> > > > >
> > > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > > >
> > > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > > it should (on the server internet works fine), and the cause is that
> > > > > replicating the servers while migrating diddn't went well (and the old server
> > > > > died already).
> > > > >
> > > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > > properly...
> > > > >
> > > > > anyone ideas??

Also when you manually configure the DNS address of the clients what
addresses do you give them?
--
James Yeomans, BSc, MCSE


"Harmjan Olthoff" wrote:

> Dear James,
>
> Thanx for the very quick responces.
> I am now behind the server and checked some things.
>
> The clients can ping external IP adresses but no names.
> When I configure it manualy it does work fine.
> On the server both DNS client and server, and both DHCP client and server
> are running.
>
> The RPC error I receive when I test GPO's with Group policy results.
> before I got the message when opening Group policy management but that
> message is gone and GP management opens good.
>
> Testing with Group modeling results run fine.
>
> also the GPO on the server runs fine.
>
> If there are any other answers I can give that wilo help...
>
> Im working on this problem for about 2 weeks and I cannot see the problem
>
> Thanx for the support!
>
> "James Yeomans BSc, MCSE" wrote:
>
> > Just confirm that if you configure them statically then it everything works
> > fine but if they are dhcp clients then thats when you get the rpc problems?
> > Do you have the dhcp client service running on the server?It needs to be to
> > update dns records etc (believe it or not).
> > --
> > James Yeomans, BSc, MCSE
> >
> >
> > "Harmjan Olthoff" wrote:
> >
> > > Dear James,
> > >
> > > All the clients get the corret IP, Gateway and DNS from the server, if I
> > > configure them manualy with the same DNS and Gateway all works fine.
> > > The server is the latest 2003 R2 server with SP2.
> > > If I can ping an IP adress from a client I have to test again, I thought I
> > > could but Im not sure.
> > > On the server RPC is running and starts automaticly and on recovery tab it's
> > > set on reboot when failure.
> > >
> > > hopefully this information wil help examening the problem
> > >
> > > "James Yeomans BSc, MCSE" wrote:
> > >
> > > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > > have the server configured as their dns server? Is the server installed with
> > > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > > server? From the clients are you able to ping an ip address on the internet,
> > > > this will test conenctivity and take dns out of the equation. On the server
> > > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > > to Remote Procedure Call and check that the service is running. Right click
> > > > it and >Properties. Check the recovery tab and make sure that the service is
> > > > always configured to restart if it fails. Let me know how youget on, good
> > > > luck!! James.
> > > > --
> > > > James Yeomans, BSc, MCSE
> > > >
> > > >
> > > > "Harmjan Olthoff" wrote:
> > > >
> > > > > Dear all,
> > > > >
> > > > > Strange problem to solve...
> > > > >
> > > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > > on client computers I get the error: RPC service unavailable.
> > > > >
> > > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > > >
> > > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > > it should (on the server internet works fine), and the cause is that
> > > > > replicating the servers while migrating diddn't went well (and the old server
> > > > > died already).
> > > > >
> > > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > > properly...
> > > > >
> > > > > anyone ideas??

Dear James,

At this moment the eventlog does nog tive RPC errors, there are no important
errors at all...

Below are settings with fixed and DHCP settings on one op the clients:

Fixed IP

Hostname: bar03
Primary DNS suffix: maddogs.local
Node Type: Hybrid
IP Routing enabled: No
WINS Proxy enabled: No
DNS Suffix search list: maddogs.local

DHCP Enabled: no
IP Adress: 192.168.2.3
Subnet Mask: 255.255.255.0
Default gateway: 192.168.2.1
DNS servers: 192.168.2.2

DHCP IP

Hostname: bar03
Primary DNS suffix: maddogs.local
Node Type: Hybrid
IP Routing enabled: No
WINS Proxy enabled: No

DHCP Enabled: Yes
automatic configuration: Yes
IP Adress: 192.168.2.3
Subnet Mask: 255.255.255.0
Default gateway: 192.168.2.1
DNS servers: 192.168.2.2

also when setting things on DHCP I can still access the client woth RDP
through it's hostname.

"James Yeomans BSc, MCSE" wrote:

> Have you checked the event logs on the workstations and the server, an RPC
> failure should write an event to the event log? The only thing i can think of
> is that the dhcp server is assigning some options incorrectly, is the server
> definitely configured with the right subnet mask because thats the subnet
> mask it will assign to clients. Are the dhcp scope options also configured to
> assign a dns address and gateway? This is a strange one because assuming dhcp
> is assigning the right options it makes no difference to a client whether its
> got a static or dynamic ip. James :)
> --
> James Yeomans, BSc, MCSE
>
>
> "Harmjan Olthoff" wrote:
>
> > Dear James,
> >
> > Thanx for the very quick responces.
> > I am now behind the server and checked some things.
> >
> > The clients can ping external IP adresses but no names.
> > When I configure it manualy it does work fine.
> > On the server both DNS client and server, and both DHCP client and server
> > are running.
> >
> > The RPC error I receive when I test GPO's with Group policy results.
> > before I got the message when opening Group policy management but that
> > message is gone and GP management opens good.
> >
> > Testing with Group modeling results run fine.
> >
> > also the GPO on the server runs fine.
> >
> > If there are any other answers I can give that wilo help...
> >
> > Im working on this problem for about 2 weeks and I cannot see the problem
> >
> > Thanx for the support!
> >
> > "James Yeomans BSc, MCSE" wrote:
> >
> > > Just confirm that if you configure them statically then it everything works
> > > fine but if they are dhcp clients then thats when you get the rpc problems?
> > > Do you have the dhcp client service running on the server?It needs to be to
> > > update dns records etc (believe it or not).
> > > --
> > > James Yeomans, BSc, MCSE
> > >
> > >
> > > "Harmjan Olthoff" wrote:
> > >
> > > > Dear James,
> > > >
> > > > All the clients get the corret IP, Gateway and DNS from the server, if I
> > > > configure them manualy with the same DNS and Gateway all works fine.
> > > > The server is the latest 2003 R2 server with SP2.
> > > > If I can ping an IP adress from a client I have to test again, I thought I
> > > > could but Im not sure.
> > > > On the server RPC is running and starts automaticly and on recovery tab it's
> > > > set on reboot when failure.
> > > >
> > > > hopefully this information wil help examening the problem
> > > >
> > > > "James Yeomans BSc, MCSE" wrote:
> > > >
> > > > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > > > have the server configured as their dns server? Is the server installed with
> > > > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > > > server? From the clients are you able to ping an ip address on the internet,
> > > > > this will test conenctivity and take dns out of the equation. On the server
> > > > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > > > to Remote Procedure Call and check that the service is running. Right click
> > > > > it and >Properties. Check the recovery tab and make sure that the service is
> > > > > always configured to restart if it fails. Let me know how youget on, good
> > > > > luck!! James.
> > > > > --
> > > > > James Yeomans, BSc, MCSE
> > > > >
> > > > >
> > > > > "Harmjan Olthoff" wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > Strange problem to solve...
> > > > > >
> > > > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > > > on client computers I get the error: RPC service unavailable.
> > > > > >
> > > > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > > > >
> > > > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > > > it should (on the server internet works fine), and the cause is that
> > > > > > replicating the servers while migrating diddn't went well (and the old server
> > > > > > died already).
> > > > > >
> > > > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > > > properly...
> > > > > >
> > > > > > anyone ideas??

Maby I need to feel quite stupid now...

In scope options there was no DNS server configured (however on ipconfig the
right DNS server was shown).
Ive added the DNS server in de DHCP scope options and it all seem to work
fine...
Internet works, GPO's work
Tonight final check

"James Yeomans BSc, MCSE" wrote:

> Also when you manually configure the DNS address of the clients what
> addresses do you give them?
> --
> James Yeomans, BSc, MCSE
>
>
> "Harmjan Olthoff" wrote:
>
> > Dear James,
> >
> > Thanx for the very quick responces.
> > I am now behind the server and checked some things.
> >
> > The clients can ping external IP adresses but no names.
> > When I configure it manualy it does work fine.
> > On the server both DNS client and server, and both DHCP client and server
> > are running.
> >
> > The RPC error I receive when I test GPO's with Group policy results.
> > before I got the message when opening Group policy management but that
> > message is gone and GP management opens good.
> >
> > Testing with Group modeling results run fine.
> >
> > also the GPO on the server runs fine.
> >
> > If there are any other answers I can give that wilo help...
> >
> > Im working on this problem for about 2 weeks and I cannot see the problem
> >
> > Thanx for the support!
> >
> > "James Yeomans BSc, MCSE" wrote:
> >
> > > Just confirm that if you configure them statically then it everything works
> > > fine but if they are dhcp clients then thats when you get the rpc problems?
> > > Do you have the dhcp client service running on the server?It needs to be to
> > > update dns records etc (believe it or not).
> > > --
> > > James Yeomans, BSc, MCSE
> > >
> > >
> > > "Harmjan Olthoff" wrote:
> > >
> > > > Dear James,
> > > >
> > > > All the clients get the corret IP, Gateway and DNS from the server, if I
> > > > configure them manualy with the same DNS and Gateway all works fine.
> > > > The server is the latest 2003 R2 server with SP2.
> > > > If I can ping an IP adress from a client I have to test again, I thought I
> > > > could but Im not sure.
> > > > On the server RPC is running and starts automaticly and on recovery tab it's
> > > > set on reboot when failure.
> > > >
> > > > hopefully this information wil help examening the problem
> > > >
> > > > "James Yeomans BSc, MCSE" wrote:
> > > >
> > > > > Hi there, firstly have you run ipconfig /all on the clients to check they
> > > > > have the server configured as their dns server? Is the server installed with
> > > > > Server 2003 SP2? Make sure all the latest updates are installed on the
> > > > > server? From the clients are you able to ping an ip address on the internet,
> > > > > this will test conenctivity and take dns out of the equation. On the server
> > > > > go Start>Run>"services.msc"> Enter. Then in the services console scroll down
> > > > > to Remote Procedure Call and check that the service is running. Right click
> > > > > it and >Properties. Check the recovery tab and make sure that the service is
> > > > > always configured to restart if it fails. Let me know how youget on, good
> > > > > luck!! James.
> > > > > --
> > > > > James Yeomans, BSc, MCSE
> > > > >
> > > > >
> > > > > "Harmjan Olthoff" wrote:
> > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > Strange problem to solve...
> > > > > >
> > > > > > I have migrated 2003 server to another server and all seem to work fine.
> > > > > > All the logons work perfect but there's something wrong with DNS, internet
> > > > > > on client computers don't work and also the GPO's do not reach the clients.
> > > > > > With an internal test for GPO's they work fine but when actualy testing them
> > > > > > on client computers I get the error: RPC service unavailable.
> > > > > >
> > > > > > I have reinstalled both DHCP and DNS server but that diddn't help.
> > > > > >
> > > > > > My best guess is because of a problem with RPC Service the DNS won't work as
> > > > > > it should (on the server internet works fine), and the cause is that
> > > > > > replicating the servers while migrating diddn't went well (and the old server
> > > > > > died already).
> > > > > >
> > > > > > I have not one idea how to fix this RPC Service and get the DNS working
> > > > > > properly...
> > > > > >
> > > > > > anyone ideas??

In news:04584C75-7DE8-493D-8185-5FD8E2A3EFEC@microsoft.com,
Harmjan Olthoff <HarmjanOlthoff@discussions.microsoft.com> requesting
assistance, typed the following:
> Maby I need to feel quite stupid now...
>
> In scope options there was no DNS server configured (however on
> ipconfig the right DNS server was shown).
> Ive added the DNS server in de DHCP scope options and it all seem to
> work fine...
> Internet works, GPO's work
> Tonight final check
>

RPC errors such as this for the most part are caused by DNS config errors.
Glad it's been straightened out.

Also, don't forget to remove the local loopback (127.0.0.1) from the DC's
config and leave the actual DC's IP (192.168.2.2). The loopback was put in
by dcpromo when first promoting the DC into a new domain/forest. It should
have the actual IP address of the DC.

Cheers!

--
Regards,
Ace

This posting is a personal opinion based on experience, and is provided
"AS-IS" with no warranties or guarantees and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.

The IP 127.0.0.1 I believe is configured, automatically within the DCpromo
process and if the Server is also configured as DNS at the time DCpromo run,
(there is no DNS service yet) the TCP/IP stack regardless what is put in
there reset to loopback IP.
I was wondering if anyone out there do know why the loopback is hardcoded to
the process? (any KB??) Only reason I can think of is the order of DNS
service, and the DC needs to register dynamic records into its own database
so that DNS database must be up and running before the registration or
dynamic records happens and loopback means to locate the local DNS service ???

Thanks for the feedback
--oz

--
Oz Ozugurlu
MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +


oz@SMTp25.org
http://smtp25.blogspot.com (Blog)


"Ace Fekay [Microsoft Certified Trainer]" wrote:

> In news:04584C75-7DE8-493D-8185-5FD8E2A3EFEC@microsoft.com,
> Harmjan Olthoff <HarmjanOlthoff@discussions.microsoft.com> requesting
> assistance, typed the following:
> > Maby I need to feel quite stupid now...
> >
> > In scope options there was no DNS server configured (however on
> > ipconfig the right DNS server was shown).
> > Ive added the DNS server in de DHCP scope options and it all seem to
> > work fine...
> > Internet works, GPO's work
> > Tonight final check
> >
>
> RPC errors such as this for the most part are caused by DNS config errors.
> Glad it's been straightened out.
>
> Also, don't forget to remove the local loopback (127.0.0.1) from the DC's
> config and leave the actual DC's IP (192.168.2.2). The loopback was put in
> by dcpromo when first promoting the DC into a new domain/forest. It should
> have the actual IP address of the DC.
>
> Cheers!
>
> --
> Regards,
> Ace
>
> This posting is a personal opinion based on experience, and is provided
> "AS-IS" with no warranties or guarantees and confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
> Microsoft Certified Trainer
>
> For urgent issues, you may want to contact Microsoft PSS directly.
> Please check http://support.microsoft.com for regional support phone
> numbers.
>
>

In news:04857D6F-B472-4019-9DE2-FEBB4359BE31@microsoft.com,
oz.ozugurlu <ozozugurlu@discussions.microsoft.com> requesting assistance,
typed the following:
> The IP 127.0.0.1 I believe is configured, automatically within the
> DCpromo process and if the Server is also configured as DNS at the
> time DCpromo run, (there is no DNS service yet) the TCP/IP stack
> regardless what is put in there reset to loopback IP.
> I was wondering if anyone out there do know why the loopback is
> hardcoded to the process? (any KB??) Only reason I can think of is
> the order of DNS service, and the DC needs to register dynamic
> records into its own database so that DNS database must be up and
> running before the registration or dynamic records happens and
> loopback means to locate the local DNS service ???
>
> Thanks for the feedback
> --oz

I believe that would be a fair assumption. During a brand new domain in a
new forest promotion, and opt dcpromo to install DNS, it's the way dcpromo
guarantees it will be able to register into the new DNS service so AD will
function. Of course after the restart, you would change it.

Ace