Unable to join domain "the specified network name is no longer available"

Hello,

I am trying to add a new server do my domain and I get the message that it is unable to join the domain "xxx" because "the specified network name is no longer available".

Main domain server runs Windows 2008 R2. New server is also running Windows 2008 R2. I was able to join another server (with the same exact hardware) to the domain last week without any problems.

New server can ping main domain server and vice-versa. New server can resolve the domain name (including domain + suffix). I have tried different names for the server and nothing has worked so far.

Any clues?

Thank you in advance for your help.
mbertuolAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

tamaneriCommented:
Try setting up your DNS to point to the main server. Also try the FQDN (domain.local) or whatever it is.

Sometimes just the netbios name of the domain doesn't work.
0
greg wardSystems EngineerCommented:
Can you still add desktop machines to the domain?
Have you tried the FQDN?
 
Greg
0
mbertuolAuthor Commented:
It already had the DNS poiting to the main server. And it was also pinging FQDN.

0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

mbertuolAuthor Commented:
I found the solution. I had assigned a static IP. When I changed and let it get an automatic IP address, I was able to join the domain immediately!
0

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
greg wardSystems EngineerCommented:
The solution was that DNS picked up your WINS settings.
Greg
0
greg wardSystems EngineerCommented:
I meant dhcp NOT  dns
0
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 Server 2008

From novice to tech pro — start learning today.