Can't add new W2K3 Server to domain: The remote procedure call failed and did not execute

I've tried everything except what magic will make this work.

Existing Windows 2003 Domain, single server SP1.  I am adding a second Windows 2003 Server SP2.  Go through the process, click OK.  About 10 minutes later, it will timeout with: The following error occured attempting to join the domain "xxxxx" The remote procedure call failed and did not execute.

There are no errors in either servers' Event Logs.

The new server does appear in AD Computers.

I've restarted both servers multiple times.

I have attempted to join by using both the NETBIOS and fully qualified domain name.

I have tested by successfully adding an XP Pro Workstation to the Domain.

I have reformatted the new server, even though it was clean to begin with.

I have changed the name of the new server.

If I supply bogus credentials when attempting to join the domain, it immediately errors out and tells me that my user and password are incorrect.

I'm not running ISA Server.



Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bird DogCommented:
I had troubles one time adding a machine and I ended up having to create new domain admin account and then use that account to add the computer and it worked.Also what is set for the networking on the server you are trying to add. Do you have wins wet up in your domain.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keith AlabasterEnterprise ArchitectCommented:
Sounds like the RSS issue - try this fix please then reattempt - on the new box
NEMCAuthor Commented:
Thanks for the immediate feedback.

Keith: Is RSS enabled by default?  I'm not familiar with it and it wasn't setup proactively.

Welmore: I'll test with a new admin account.  I've never setup WINS support on a network because I've never needed it in the past.  How does WINS contribute to the process of joining a domain?

The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Keith AlabasterEnterprise ArchitectCommented:
Just an issue that is coming up more and more with sp2
NEMCAuthor Commented:
I tried many, many things, including reformatting the new server.  No help.

Solution was to remove the CheckPoint VPN client that was installed on the existing Windows 2003 Server.  I had tried disabling it, but that didn't help.  Once the client was removed and the server restarted, everything worked as expected.

Thanks to everyone.
Keith AlabasterEnterprise ArchitectCommented:
Thanks :) - well found
i had the same issue,

my setup had ISA 2004 on the machine trying to connect, i removed that and at the same time i changed the gateway IP to the DC which was windows 2008

It worked after that..

Good luck
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.