can't join Domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When trying to join a domain I receive the error "The remote procedure call
failed and did not execute." I've checked ISA 2004 and all filtering is
disabled on the internal network yet I still can't get it to join the domain.
All other test opertaing systems connect just fine.

Any suggestions?
 
Just an idea: check the firewall settings. Vista has outgoing firewall too.
Or perhaps some other blocking on the way to your server?
Eric
 
What is your domain? 2000 mixed? 2000 Native? 2003 Native?

Can you ping the domain simple name from the computer in question?

Bill F.
 
The server is Windows Server 2003 R2 Standard Edition with ISA server 2004.
All service updates are applied to both. I can ping the server fine, map
drives using another user ID and access the IIS default web page. I disabled
the firewall in Vista but still can't get it to join the domain.
 
Thanks for the reply Eric.

I tried disabling the Vista firewall, no cange. The strange thing is I can
access the server in every way I've tried, maping dives with a different user
ID, accessing the IIS web page, etc. It just won't allow me to join the
domain. I checked the ISA log and no communications are beind blocked by
ISA. I do see the RPC connection being opened and closed in quick succession
for four iterations before it errors out.
 
Well, I did some testing and here are the results. The problem is the same
with both the standard and Enterprise editions of the 64-bit builds. The
problem is not there in the 32-bit builds. Not sure what the issue is, but
it appears to be a bug in the 64-bit versions. My server is 32-bit Windows
Server 2003 R2
 
Try this...(I just posted this in a thread above as well) It's a shot in the
dark but it may solve your issue as I've had other connecting issues fixed
by doing this:

Uncheck the IPv6 for your adapter and set WINS to Enable Netbios over
TCP/IP.

IPV6 is on by default I think on all network adapters....turn it off and let
me know if you still have the same problem. If you do it may be DNS server
related....a least we can start with the IPv6

Jeff
 
Back
Top