Error adding windows server 2008 to windows sbs 2003 domain

I am setting up a windows server 2008 which will be used to run an application.  We currently have a windows small buisness server 2003 which is our domain.  When trying to connect the 2008 server to the domain I get the following error.

The following error occurred attempting to join the domain "xxxxx.local":
The remote procedure call failed and did not execute.

Any ideas on how to overcome this error?
rrinconesAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
JohnLoConnect With a Mentor Commented:
hopefully the last thing are you by chance running ISA server? If so disable the RPC filter?
0
 
JohnLoCommented:
are you using the wizards or just running DCpromo?
0
 
rrinconesAuthor Commented:
I just changed the settings from workgroup to domain.  
I put the domain name.
It asks for user name and password,
then I get the error mentioned above.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
JohnLoCommented:
ohhh weird! have you tried rebooting the 2003 sbs DC
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
If SBS is at 192.168.20.254, then your member server's NIC settings need to be:

IP: 192.168.20.252
Sub: 255.255.255.0
GW: 192.168.20.1
DNS1: 192.168.20.254
DNS2: Blank

On Win2K8, open a browser and navigate to: http://MySBSName/ConnectComputer

Allow the Intranet Security Settings warning to enable them. If there is a problem, add the /ConnectComputer site to the Trusted Sites and try again.

Otherwise, you can run the following script from an elevated command prompt on the Win2K8 server:
netdom Join Win2K8Name /Domain:MySBSDomain.Local /OU:OU=SBSServers,OU=Computers,OU=MyBusiness,DC=Domain,DC=Local /UserD:MySBSAdmin
/PasswordD:*

Change the domain name as appropriate but leave the OU structure so that the server ends up in the SBSServers OU which is where it needs to be. Change the Win2K8Name to the name of your Win2K8 box.

The asterisk will prompt for the domain admin's password. Reboot.

Philip
0
 
JohnLoCommented:
also what is the windows 2003 sbs server's DNS set as the windows 2008 primary DNS
0
 
JohnLoCommented:
also make sure your sbs is fully up to date if i remember correctly there were some patches for adding vista, win7
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Make sure to copy and paste the netdom command into NotePad to verify that there are no wraps in the line. It looks like there is one after MySBSAdmin above.

Philip
0
 
Shreedhar EtteCommented:
Hi,

Does the SBS 2003 has ISA installed?

Refer this:
http://technet.microsoft.com/en-us/library/cc708131%28WS.10%29.aspx

I hope this helps,
Shree
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Guys, SBS 2003 should have no problems with allowing another server to be connected to the domain _out of the box_.

The first thing that needs to be established is whether the two boxes are able to communicate with each other over the basics, NIC settings, TCP/IP, DNS, and Windows Explorer.

Once the basics have been established, then move from there.

As long as the two servers are communicating as expected, the ConnectComputer wizard or the netdom script will work just fine.

Philip
0
 
JohnLoCommented:
MPECSInc SBS has known issues adding vista and higher withput patches!!!! That is NOT OUT OF THE BOX!!!!!!!

Also ISA has know issues especially adding x64 machines!!!!
0
 
rrinconesAuthor Commented:
Disabling the rpc filter worked on the isa server.
Once the server running 2008 is joined, is it safe to turn the filter back on?
0
 
Shreedhar EtteCommented:
Remain it disabled.

Refer this:
http://support.microsoft.com/kb/887222
0
 
JohnLoCommented:
good deal, glad i could help....
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
We manage _a lot_ of SBS 2003 Premium installations with a mix of Win2K8 RTM and R2 servers in client production networks.

We are a huge fan of ISA 2004 on SBS 2003 and 100% of our SBS 2003 Premium sites have ISA installed and correctly working.

If ISA was causing the communication issues, then the ISA rules are not sorted correctly as per the _SBS 2003_ specific way of doing things. ISA on SBS is _not_ the same as ISA on Windows Server in a standalone setup.

Philip Elder
SBS MVP 2009-2010
0
 
Glen KnightCommented:
Just to re-enforce what Philip is saying.

ISA should NOT be causing a problem with joining ANY type of computer/server to an SBS domain if it has been configured correctly.

SBS2003 DOES allow Vista/2008 operating systems to join to the domain as long as it is FULLY up to date.  An SBS update released very early in 2009 (I think) resolved this issue.

>>Also ISA has know issues especially adding x64 machines!!!!
I have never heard of this, can you provide some document they explains the issue?  I have quite a few SBS with ISA and non SBS ISA installations and have not come across this one.
0
 
JohnLoCommented:
0
 
JohnLoCommented:
0
 
Glen KnightCommented:
That is not specific to x64 machines and if all systems were FULLY patched this would not be a problem.
0
 
Glen KnightCommented:
That second one is the same just a different KB.

It's talking about ISA being installed on 2003 SP1 if all the updates had been performed on the SBS2003 server then this would not cause a problem.

And in fact if it was the problem it would be causing much greater problems.
0
 
JohnLoCommented:
Yes, True but it IS a known issue. this is why i asked if the server was fully updated!

Do a google search on this you will foind the problem happens with x64 machines as well.
0
 
Glen KnightCommented:
It will happen with ALL machines not just x64 if the server was not fully patched.  Which there is no reason why it shouldn't be.

I prefer not to use google, I prefer to give real experience answers.
0
 
JohnLoCommented:
The question is answered and solved whats your issue? What's your deal, You got nothing else better to do but try to get more point for a issue that you didnt even work on in the first place?

Here is a link to a M$ support pro that knew about a specific x64 issue
http://www.vistax64.com/vista-general/153587-cant-join-vista-x64-pc-domain-rpc-error.html#post716585
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
John, we are all here to help.

Philip
0
 
Glen KnightCommented:
My issue is making sure the correct information is available in the questions when they get PAQ'd and not just some link that means nothing to future readers.

I have no interest in the points from this question, if you look at my profile you will see I don't need them.

For me it's about PAQ value, and you will often see me post for this reason even if the question has already been closed.
0
 
rrinconesAuthor Commented:
Guy's the server was to automatically update and from what I can see it is fully patch as a matter of fact the only update that hasn't been installed is internet explorer 8.

As for whether the ISA server is configured correctly, I really don't know.  This is a new client and she commented to me that she has had several IT Guys work on her server several times and that it has had a history of crashes and data loss.  I will investigate whether the rules are sorted correctly but for know the 2008 server is joined to the domain and we have installed the application needed by the customer.

Thanks for your help.  All of you.

0
All Courses

From novice to tech pro — start learning today.