При присоединении к домену произошла следующая ошибка сетевой ресурс или устройство более недоступно

• Remove From My Forums

• Question

• Hi!

  We have two companies in our building, Company A and Company B. Company A has 50 client computers and one brand new DC (Win 2012 R2 Std). Company B has 5 clients and one established DC (Win 2008 R2 Foundation). 

  I work for Company A and I have the job of connecting all 50 clients to the new DC. Up until last week we had a workgroup set up and it has been my task to migrate our clients onto the domain. I have done 10 migrations of Win 7 machines so far, but three
  others seem to be unable to connect with the error: The specified network name is no longer available.

  I have connected these successfully to Company B Domain Controller successfully so this seems to point towards Company A DC being wrong somewhere, but doesn’t make sense as to why 10 other clients have connected fine.

  Here are the troubleshooting steps I have taken so far:

  I am in the Domain Admin group on Company A Active Directory

  Computer Browser Service is running on server and affected client
  Workstation Service is running on server and affected client
  Server Service is running on server and affected client

  To connect to the domain I have tried using the NetBIOS and the FQDN, I get the same error message.

  NETLOGON service is enabled tried restarting — no difference

  Windows Firewall is off
  No AV installed at the moment. I have Sophos waiting to go on once the machine is hooked onto the domain.

  DNS Reverse lookup manually created as it wasn’t there

  Tried ipconfig /flushdns /release /renew

  NSLookup sucessful, can ping NETBIOS, FQDN of server and both client and server IP both directions

  Affectted clients are configured with one network card.

  I’ve been pulling my hair out for a few days on this one. Anyone have a possible solution for this.

  Many thanks,

  Matt

  • Edited by

    Friday, July 18, 2014 8:56 AM

• Remove From My Forums

• Question

• Hi!

  We have two companies in our building, Company A and Company B. Company A has 50 client computers and one brand new DC (Win 2012 R2 Std). Company B has 5 clients and one established DC (Win 2008 R2 Foundation). 

  I work for Company A and I have the job of connecting all 50 clients to the new DC. Up until last week we had a workgroup set up and it has been my task to migrate our clients onto the domain. I have done 10 migrations of Win 7 machines so far, but three
  others seem to be unable to connect with the error: The specified network name is no longer available.

  I have connected these successfully to Company B Domain Controller successfully so this seems to point towards Company A DC being wrong somewhere, but doesn’t make sense as to why 10 other clients have connected fine.

  Here are the troubleshooting steps I have taken so far:

  I am in the Domain Admin group on Company A Active Directory

  Computer Browser Service is running on server and affected client
  Workstation Service is running on server and affected client
  Server Service is running on server and affected client

  To connect to the domain I have tried using the NetBIOS and the FQDN, I get the same error message.

  NETLOGON service is enabled tried restarting — no difference

  Windows Firewall is off
  No AV installed at the moment. I have Sophos waiting to go on once the machine is hooked onto the domain.

  DNS Reverse lookup manually created as it wasn’t there

  Tried ipconfig /flushdns /release /renew

  NSLookup sucessful, can ping NETBIOS, FQDN of server and both client and server IP both directions

  Affectted clients are configured with one network card.

  I’ve been pulling my hair out for a few days on this one. Anyone have a possible solution for this.

  Many thanks,

  Matt

  • Edited by

    Friday, July 18, 2014 8:56 AM

• Remove From My Forums

Проблема с вводом гостевой ОС в домен

• Вопрос

• Доброго времени суток.

  Имеется недорогой сервер для решения несложных задач, Intel S5000VSA + 28 Гб озу под управлением Windows 2008 Standart.

  Установлены следующие роли: AD, DNS, DHCP, Hyper-V.

  Ввод физических машин в домен проходит на ура, никаких проблем.

  При попытке присоединения гостевой виртуальной машины (xp, vista, 2008R2) к домену вылазит ошибка: «При присоединении к домену произошла следующая ошибка: сетевой ресурс или устройство более недоступно».

  Тип виртуальной сети — внешний (т.е. настройки протокола IPv4 на физических и виртуальных машинах идентичны).

  Если «сетевой адаптер» меняю на «устаревший сетевой адаптер», все ок.

All replies

• Hi,

   
  Thank you for sharing this.

  Best Regards,

  Sally Tang

• Hi

  I have a 2003 server trying to join a single DC site which is getting this same error.

  The workstation, server service and Computer Browser service are started on the domain controller server.

  I can add a regular worstation but cannot add this server.

  Any other suggestions!

  Thanks

• Hi Mack

  One thing that can be checked here is whether the reverse lookup zone is configured for your domain. You can check this in the dns management console.If the reverse lookup zone is not there for the domain machine then create one manually.

  Also try running the nslookup command and see whether the domain details (IP and domain server) are displayed correctly.

  Thanks

  Akash

• This could be due to an incorrectly configured IP settings on the new computer. Try and see if it is configured with two network cards, one to communicate with another subnet and another one to communicate with the subnet where the domain controller is.
  If this is the case, disable the secondary network card which is communicating to the  other subnet and try joining the machine to the domain. That should work. If not, check your IP settings and DNS settings.

• Solution — Check the following services on the domain machine

  — Browser service

  — Workstation

  — Server

  And start them. This should solve the issue.

  Thanks

  Old thread, but this solution worked for me. All above services were already running but only after I restarted them, I was able to join the domain.

All replies

• Hi,

   
  Thank you for sharing this.

  Best Regards,

  Sally Tang

• Hi

  I have a 2003 server trying to join a single DC site which is getting this same error.

  The workstation, server service and Computer Browser service are started on the domain controller server.

  I can add a regular worstation but cannot add this server.

  Any other suggestions!

  Thanks

• Hi Mack

  One thing that can be checked here is whether the reverse lookup zone is configured for your domain. You can check this in the dns management console.If the reverse lookup zone is not there for the domain machine then create one manually.

  Also try running the nslookup command and see whether the domain details (IP and domain server) are displayed correctly.

  Thanks

  Akash

• This could be due to an incorrectly configured IP settings on the new computer. Try and see if it is configured with two network cards, one to communicate with another subnet and another one to communicate with the subnet where the domain controller is.
  If this is the case, disable the secondary network card which is communicating to the  other subnet and try joining the machine to the domain. That should work. If not, check your IP settings and DNS settings.

• Solution — Check the following services on the domain machine

  — Browser service

  — Workstation

  — Server

  And start them. This should solve the issue.

  Thanks

  Old thread, but this solution worked for me. All above services were already running but only after I restarted them, I was able to join the domain.