the RPC is unavailable

May 20, 2010 at 07:39:34
Specs: Windows XP
I'm trying to add my workstation to my domain . I got error "The RPC is unavailable"

See More: the RPC is unavailable

Report •


#1
May 20, 2010 at 07:48:24
9 times out of 10 it is usually a DNS issue. Try to Ping your RPC server and see if it resolves an IP address for the Server's name.

If it does then the other problem could be an OU issue. Check to see if this computer doesn't already have an OU in the Active Directory. If so then delete it and try to rejoin.


Report •

#2
May 20, 2010 at 08:21:48
On the client workstation i can ping IP192.168.0.115 with a reply wiht no problem. I want to give more info. on Active Directory
1. domain name: jaballa.com with IP: 192.168.0.115
2. domain controller: stargate.jaballa.com
3. client: workstation01
4. add the ip address of server to the workstatio01 nic tcp/ip preferred DNS server
5. add jaballa.com to primary DNS suffix
6. type jaballa.com to domain
7. login as administrator/password
I still getting same error message about RPC not available
Please advice.........Thanks!

Report •

#3
May 20, 2010 at 09:57:33
Did you ping the Server Name not the IP? By pinging the name you test that the local DNS is working.

Also did you try my second suggestion?


Report •

Related Solutions

#4
May 21, 2010 at 10:55:32
I tried the ping the server name but could not find the host name jaballa.com. I paste my server info.. Please advise

Windows IP Configuration

Host Name . . . . . . . . . . . . : STARGATE
Primary Dns Suffix . . . . . . . : JABALLA.COM
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : JABALLA.COM

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controlle
r
Physical Address. . . . . . . . . : 00-12-3F-2D-38-86
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.115
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 68.87.76.182
68.87.78.134


Report •

#5
May 21, 2010 at 11:03:21
I'm confused with host name and server name. I ping the host name stargate then i got a reply but if i ping jaballa.com could not find host jaballa.com. Please advise. Thanks,

Report •

#6
May 24, 2010 at 07:39:26
It is because the DNS is messed up on the local computer. DNS changes the Full Qualified Domain Name (FQDN) to IP. If the DNS is messed up then it will NOT resolve and because Windows uses FQDN then it fails.

"DNS Servers . . . . . . . . . . . : 68.87.76.182
68.87.78.134"

Ok, you are using your ISPs DNS and you need to add your DNS Server to the IP stack.

http://support.microsoft.com/kb/305553

After you have set this up then try...

IPCONFIG /FLUSHDNS
IPCONFIG /REGISTERDNS

To force the local computer to update it's DNS Cache. If it is still failing then there is some thing wrong in your DNS server's Zones.


Report •

#7
May 24, 2010 at 08:00:48
"DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.115
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1"

Servers NEVER use dhcp. You need a static ip assignment
You are pointed to the router/gateway for dns. This is wrong. You point to your local AD DNS server

This is why its not working. You have NO pointers anywhere saying "go look at my dns server for this"


Report •


Ask Question