We've just setup AD and now we have problems joing Computers to the
domain.

Whenever we try it gives an error "RPC server is unavailable"

Ive ran through all the support docs and can't seem to find a fix.

I ran netdiag and it doesn't give any issues, check DNS and no errors
are reported all domain names are resolving fine....

Checked things like the IPSec service... and still cannot find any
fix......


Can anyone provide any suggestions on what fix will do.....

I don't get any errors on the DC or the workstations so really stuck...

Sounds like a DNS problem.  Check %systemroot%\debug\netsetup.log and google
(groups) the errors.  If you can't find anything post the last thirty lines
here.

i reviewed the netsetup.log and it seems to be failing at the


NetpGetComputerObjectDn: Unable to bind to DS on
'\\HK-PSSWN003.asia.internal.com': 0x6ba


04/11 09:57:30 NetpDoDomainJoin
04/11 09:57:30 NetpMachineValidToJoin: 'HK15313'
04/11 09:57:30 NetpGetLsaPrimaryDomain: status: 0x0
04/11 09:57:30 NetpMachineValidToJoin: status: 0x0
04/11 09:57:30 NetpJoinDomain
04/11 09:57:30     Machine: HK15313
04/11 09:57:30     Domain: asia.internal.com
04/11 09:57:30     MachineAccountOU: (NULL)
04/11 09:57:30     Account: cn\test
04/11 09:57:30     Options: 0x27
04/11 09:57:30     OS Version: 5.1
04/11 09:57:30     Build number: 2600
04/11 09:57:30     ServicePack: Service Pack 2
04/11 09:57:30 NetpValidateName: checking to see if 'asia.internal.com'
is valid as type 3 name
04/11 09:57:30 NetpValidateName: 'asia.internal.com' is not a valid
NetBIOS domain name: 0x7b
04/11 09:57:31 NetpCheckDomainNameIsValid [ Exists ] for
'asia.internal.com' returned 0x0
04/11 09:57:31 NetpValidateName: name 'asia.internal.com' is valid for
type 3
04/11 09:57:31 NetpDsGetDcName: trying to find DC in domain
'asia.internal.com', flags: 0x1020
04/11 09:57:32 NetpDsGetDcName: failed to find a DC having account
'HK15313$': 0x525
04/11 09:57:32 NetpDsGetDcName: found DC
'\\HK-PSSWN003.asia.internal.com' in the specified domain
04/11 09:57:32 NetpJoinDomain: status of connecting to dc
'\\HK-PSSWN003.asia.internal.com': 0x0
04/11 09:57:32 NetpGetLsaPrimaryDomain: status: 0x0
04/11 09:57:32 NetpGetDnsHostName: Read NV Hostname: HK15313
04/11 09:57:32 NetpGetDnsHostName: PrimaryDnsSuffix defaulted to DNS
domain name: asia.internal.com
04/11 09:57:32 NetpLsaOpenSecret: status: 0xc0000034
04/11 09:57:32 NetpGetLsaPrimaryDomain: status: 0x0
04/11 09:57:32 NetpLsaOpenSecret: status: 0xc0000034
04/11 09:57:33 NetpJoinDomain: status of creating account: 0x0
04/11 09:57:54 NetpGetComputerObjectDn: Unable to bind to DS on
'\\HK-PSSWN003.asia.internal.com': 0x6ba
04/11 09:57:54 NetpSetDnsHostNameAndSpn: NetpGetComputerObjectDn
failed: 0x6ba
04/11 09:57:54 ldap_unbind status: 0x0
04/11 09:57:54 NetpJoinDomain: status of setting DnsHostName and SPN:
0x6ba
04/11 09:57:54 NetpJoinDomain: initiaing a rollback due to earlier
errors
04/11 09:57:55 NetpGetLsaPrimaryDomain: status: 0x0
04/11 09:57:55 NetpManageMachineAccountWithSid: status of disabling
account 'HK15313$' on '\\HK-PSSWN003.asia.internal.com': 0x0
04/11 09:57:55 NetpJoinDomain: rollback: status of deleting computer
account: 0x0
04/11 09:57:55 NetpLsaOpenSecret: status: 0x0
04/11 09:57:55 NetpJoinDomain: rollback: status of deleting secret: 0x0
04/11 09:57:55 NetpJoinDomain: status of disconnecting from
'\\HK-PSSWN003.asia.internal.com': 0x0
04/11 09:57:55 NetpDoDomainJoin: status: 0x6ba

I've tried using a few diff machines to test and they all return the
same result.. Tried looking at technet and they had something about the
account being used being a member of too many groups the Dom
Administrator acct is only a member of 4 groups.... even tried creating
a new domain admin test account and using that and it didn't
work.......

Tried using nltest /dsget:domain on the wkstation and that all resolved
fine....... so really not sure where to go next..........

Please help...


Show quoteHide quote

Weird.  0x6ba is, I believe, RPC server unavailable -which is usually always
DNS.  However, you are able to resolve your domain name and create a
computer object.

Run DCDIAG /V /C on the DC that is mentioned in the NETSETUP log and see if
there are any errors.

Well finally found the problem....  it was the 135 port was blocked on
the network....

I've had this problem as well, the client was a brand new Windows XP Pro machine, same error, the fix was to make sure the time was the same on the Domain controller!!! as soon as that was fixed, problem solved. -- contort ------------------------------------------------------------------------ contort's Profile: http://forums.techarena.in/members/103476.htm View this thread: http://forums.techarena.in/active-directory/493252.htmhttp://forums.techarena.in

error with ntdsutil
Modify bulk users in AD
Group Policy item applies the first time I login then no more
How to do maintenance repair in AD
Hello Everyone ? On searching Active Directory
cleaning all user created files on logoff
Logon Problem on One Client
Network Question
third level domains in windows server 2003
Export cert from CA