pabby061203
asked on
the specified server cannot perform the requested operation - trying to join a 2003 domain
HI,
I have a new member server that I will be looking to do a swing migration for Exchange but initially I wanted to bring it onto our domain but when i try I am getting the error above. Other 3 servers are 2003 and clients are xp - not a big environment really - I noticed a couple of weeks ago that one or two pc's started saying the same thing - when I tried to re-join them to the domain.
any assistance welcome - thanks
I have a new member server that I will be looking to do a swing migration for Exchange but initially I wanted to bring it onto our domain but when i try I am getting the error above. Other 3 servers are 2003 and clients are xp - not a big environment really - I noticed a couple of weeks ago that one or two pc's started saying the same thing - when I tried to re-join them to the domain.
any assistance welcome - thanks
ASKER
Hi,
As it is a server of our network, I gave it a static IP 192.168.3.70 (other servers are 192,168.3.xx)and then the existing 2 internal DNS server IP addresses on our LAN
A couple of weeks ago we dropped out one of our older servers that was a dns machine too and replaced it with a new server , one of its roles is a DNS server - not sure if this has any bearing on the problem,
thanks
As it is a server of our network, I gave it a static IP 192.168.3.70 (other servers are 192,168.3.xx)and then the existing 2 internal DNS server IP addresses on our LAN
A couple of weeks ago we dropped out one of our older servers that was a dns machine too and replaced it with a new server , one of its roles is a DNS server - not sure if this has any bearing on the problem,
thanks
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Make sure the firewall is turened off on the server.
Go to start then run and then services.msc
Go to windows firewall and right click then properties.
Disable the service for startup.
Then click the stop option to stop the service. Try joining the domain again
Go to start then run and then services.msc
Go to windows firewall and right click then properties.
Disable the service for startup.
Then click the stop option to stop the service. Try joining the domain again
ASKER
scratch that - just had another look at the other new server (that replaced the old one) and DNS is not there as a server role - so we are down to one dns server on the LAN
OK go back to the server having issues joining the domain. Make sure only the one DNS server is listed there.
Once done run an ipconfig /flushdns
Try joining the domain again
Once done run an ipconfig /flushdns
Try joining the domain again
ASKER
OK - there is one dns server listed in TCP/IP properties of the NIC (of the server having issues)- I ran the ipconfig/flush - tried again - same error
Are you able to ping the DNS server?
You have one remaining DC right?
You have one remaining DC right?
ASKER
HI,
I can ping the one remaining dns server ok -
I used the metadata process and at first it was unable to see any servers at the 'list servers in site' stage. After another try, it found the servers and I was able to clean up the server that had not been removed correctly via dc promo. I haven't tried to join the domain again yet as I need to set up the recently added dc as a secondary dns on my existing domain - can you advise on this process and then I will return to the 'joining the domain' issue - your assistance is very much appreciated, thanks
I can ping the one remaining dns server ok -
I used the metadata process and at first it was unable to see any servers at the 'list servers in site' stage. After another try, it found the servers and I was able to clean up the server that had not been removed correctly via dc promo. I haven't tried to join the domain again yet as I need to set up the recently added dc as a secondary dns on my existing domain - can you advise on this process and then I will return to the 'joining the domain' issue - your assistance is very much appreciated, thanks
What did you put in for the first DNS and second dns servers? They should both be internal DNS servers not an ISP dns server address.
Thats normally the first cause