Server 2003 RPC and DC errors,

[Jason490]

Hello everyone,

Just found this board and I hope you can help. We are running windows server 2003 on 2 seperate HP servers. One is the DNS and the other is the main server. We are continually getting RPC Errors and " the domain controller cannot be located or does not exist"

We set a batch file up to flush the dns and as soon as you do that, the remote users can log back on, but sometimes 30 minutes later, the same errors and we flush again.

The errors are as follows

The domain controller and RPC error seems to be 1053, that is the main one we are getting

In the event log we are also seeing a lot of 1219

One other I found that was strange is 11


Any and all help you could give would be greatly appreciated. I have scratched my head on this one for awhile. I am taking over a huge client and this has plagued them for awhile and I need to get it fixed of course. Thanks again for any info and help.

[frank vandebergh]

What do you mean with the 'main' server ?
So you are working with a domain? Is that server also DHCP server or using a router for that ? Both servers are domain controllers ?
Please post the results here from the ipconfig /all command on each server

[Jason490]

Frank,

Thanks for the reply. One is a domain controller and the other server is where they login to access their apps.

Here is the results you asked for.

The domain controller is this:

Hostname: camrett01
Prim DNS: CAMRETT
node type: hybrid
ip routing: no
wins: no
dns suffix: CAMRETT

Description- netgear ga302t gig adapter
Physical Addy- 00-09-5B-22-D9-2C
DHCP- no
IP: 192.168.50.11
Sub: 255.255.255.0
Gateway: 192.168.50.1
DNS Servers: 192.168.50.1
192.168.50.11


Ok and the other server is this

Hostname: camrett01
Prim DNS: CAMRETT
node type: unknown
ip routing: no
wins: no
dns suffix: CAMRETT

Description- HP NC7781 Gigabit Server adapter
Physical Addy- 00-0E-7F-5F-59-56
DHCP- no
IP: 192.168.50.12
Sub: 255.255.255.0
Gateway: 192.168.50.1
DNS Servers: 192.168.50.11
192.168.50.1


Thanks again for your help frank, would love to get this solved

[clausw]

"node type: unknown"
for camrett01 which node type ist it ?
"dns suffix: CAMRETT"
your fqdn ist konfigured camrett01.CAMRETT
is this suffix the right Domain Name and the name of your DNS Zone ?
wins: no
do you have netbios enabled on TCP/IP ?
is your DNS Zone AD integrated ?

[clausw]

reason for use the gateway as first DNS on DC ?
DNS Servers: 192.168.50.1
192.168.50.11
check your DNS configuration
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

[Paul Slijkhuis]

It seems you only have a single DNS server. a second DNS entry in the IP setting makes no sence, you should leave it empty then.

The primairy DNS (top entry) is the first server to respond to a request. This is most likely what is going wrong.

I advise to use DNS integrated zones, to achieve the least administrative effort in your Windows environment.

-Paul

[Jason490]

Thanks for all of the help guys,

This is a large client that I just took over. I thought the same thing on the dns when I saw it, so I understand what you all are saying. I will take a look at all these and let you know what turns out.

Thanks again a bunch!

[frank vandebergh]

Ok, so your domain controller' DNS should point only to its own ip address, eventually you can make a forwarder with the address of your gateway or isp. All the other servers and clients their dns should then point to the domain controller alone.

[Jason490]

Frank,

Ok the Domain controller is setup in the DNS interface to only listen to 192.168.50.11 which is the DNS address and the IP of the DC.

Here is my question. For some reason whoever set this up has 192.168.50.1 in the forwarders tab.

Now that should not be like that right? I would think it would either be the 50.11 or 50.12

[frank vandebergh]

No, it is correct.
DC DNS service listens on ip address of the server, and the forwarders must contain the addresses of the gateway or isp dns. In your case the .1 is the gateway so the forwarder should be correct.

When clients perform a dns lookup, they have the dc listed so they request dns at the dc. The DC forwards this request using the gateway to your isp, and then sends it back to the client.