this problem has happend to me on numerous occasions. i have a number of pc's here that we need to join up to the domain. problem is, whenever you go to join them up, it returns a
The following error occurred while trying to join the domain XXXXX. Specified server cannot perform the requested operation
i've looked around and not found out why this happens. if the pc is loaded with xp the nic drivers are found and the pc joins up no problem. with a 2000 pro install however, the drivers are not found, forcing the manual join.
google has failed me with answers. this seems to happen to machines that run 2000 for me.
Are you joining by FQDN like mydomainserver.mydomain.com.local or NETBIOS domain as in MYDOMAIN?
Are you able to ping that domain controller? Shows up in Network Neighborhood? All machines are in the same subnet? Connected to the same ethernet switch. Any systems multi-homed?
What version of Server 2000? 2003? How many domain controllers?
Rip wrote:Are you joining by FQDN like mydomainserver.mydomain.com.local or NETBIOS domain as in MYDOMAIN?
Are you able to ping that domain controller? Shows up in Network Neighborhood? All machines are in the same subnet? Connected to the same ethernet switch. Any systems multi-homed?
What version of Server 2000? 2003? How many domain controllers?
good point. i'll try it by FQDN and check. it was strictly by netbios domain, and there are 2 dc's.
ping? yes, fully ping any machine on the network.
network neighborhood? yes for one, no on the other (odd, it can access any network shares just fine though.)
all on same subnet and same switch. unconfigured cisco wireless card installed, networked via ethernet switch.
unable to join by FQDN with either pc. reports "specified domain does not exist or could not be contacted."
both pc's will ping successfully with FQDN though, so the forward lookups are working properly.
what can cause the "specified server" error? is it dns related? seems odd that it can find the network and ping everything just fine, but can't seem to find the server it just pinged when joining.
ok. i got it. in the net id wizard, after it kicks back the error and then asks for the user/password/domain, i used the fqdn instead of the netbios. that did it. it asked for whether to add a user or not, and prompt for reboot.
thanks for pointing me in the right direction rip.
No problem, fqdn can be a lot easier as dns and the right ports open is all you need. It seems as more and more security issues get fixed NETBIOS becomes less and less useful. Especially in a routed and/or multi-homed enviroment.
If you really want some fun try to try killing your dc that has all the roles with no backup and try to do a fresh install and get everything back up and working That'll teach em to not do backups.
backups we do, just not to the best media available. our 7 some odd year old robot took an early retirement a few weeks back. seems it took a dislike to tapes.
our main citrix box has been throwing up garbage too lately. we've had to jump back from using many of the apps it handles to keep it running. it it's almost as bad as a sole dc going bad.
That'll teach em to not do backups. 