Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RPC-Server problem 1

Status
Not open for further replies.

Benja1

Technical User
Nov 19, 2002
9
DE
Hi

I have a littel Network with 1 Server (Win2000 Server, SP4, all patches available installed) and 8 Clients (most Win2000, some NT).
The Server works as the only DomainController in the Domain which consists of exactely this 9 PCs. It hosts a DNS-Server, too (because Active-Directory is used).

Users can log in on the Workstations, print, surf, work - all works fine.

But the Event-log of the Server shows many many errors :(

I searched this forum but I could not find answers fitting to my problem. I DO NOT have Problems with w32Blast. I am sure with that.
Ok, here is the main Problem:

The RPC-Server is not available. Event-ID 1722

This is the only error netdiag and dcdiag find, too.

Other errors and their Event-IDs say, that that problem is their reason. For example Event-IDs 1655, 1126, 1000

My timeserver is working an I do not have error-messages with w32time any more. I have had them but I could fix that problem some time ago.

I hope, somebody can help me with my problem.

Thanks.

Benjamin
 
From Event ID.net

"Value 1722 - "The RPC Server is unavailable" - Usually occurs when DNS servers are not configured properly. There is connectivity but not at the service level. See the Q260371 link below for troubleshooting such issues. One note here, usually it may appear that DNS is set properly but one has to double-check all the aspects of DNS registration/resolution as the problem may not be that obvious. See also Q261007 - It says that this behavior can occur if the address for the configured preferred DNS server on the client is invalid or unreachable.
From a newsgroup post: "Do the following to ensure that the SRV records for the AD servers are in DNS properly: (from the DOS prompt)

nslookup
set type=srv
set type=srv
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM
Server: dnsserver.yourdomain.com
Address: 192.168.100.2

you should see something like this:

_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server2.YOURDOMAIN.COM
server1.YOURDOMAIN.COM internet address = 1.1.1.2
server2.YOURDOMAIN.COM nternet address = 1.1.1.1

If you don't then you definately have a DNS problem."


Hope this helps,

Patty [ponytails2]
 
thx. I know :)

If I do this, I can see no errors. It looks like it looks in the example - although I only get 1 response like


_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM

But - I only have 1 Server so I think that is okay.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top