Unable to join domain - Windows 10 machine

Does a NSLOOKUP return correct entries for corp.ebankwest.com?

In addition to what Shaun has mentioned, are you able to ping IP addresses? And what IP is the laptop using for DNS (make sure that something static wasn't somehow configured in)?

Turn the computer off, REMOVE the power cable, wait a few seconds, hook it back up and try again.

Sometimes a NIC keeps junk in it and only a cold boot will clear it .

If it's a laptop, remove the battery as well.

While I was waiting, I did a flushdns and registerdns.  The registerdns came back with an event ID 8019 in the event view.   After I flushed the dns, the was no longer able to ping.  I was able to ping earlier.    We use static IPs in our network, not DHCP.

nslookup on that computer comes back with: DNS request timed out (after 2 sec).  Default server: unknown.  Address: 10.1.1.38 (which is our AD CD ip address).

On my computer, the nslookup comes back with: Default Server: ad1.corp.ebankwest.com.  Address: 10.1.1.38.

ad1 is the name of our dc and the domain is corp.ebankwest.com.

I will try shutting down the computer and unplugging it.  I will let it sit until I come back from lunch.

If it still doesn't work after starting back up, try resetting TCP/IP.

Also make sure no other  NIC is enabled on this computer if you have more than one.
Check DNS / DC server for other NIC enabled.
I had same issue some time ago and for some reason my not connected NIC was registered in DNS and Windows 10 computers had problem to register.

I;ve disabled not used NIC on DC and all start working again

Run CMD as Admin:
netsh advfirewall reset
netsh int ip reset
netsh int ipv6 reset
netsh winsock reset

Also go to Start -> Settings -> Network and Internet -> Status -> choose Network Reset option -> confirm

Also run Windows Troubleshooter that will tell you what's wrong.

I am now getting the message: Network path not found when I try to join to the domain.

Can you post PING result when you try PING your DC name ?

Hi - sounds like you have a DNS resolution issue.

Try assigning a fixed IP address in a suitable subnet with DNS set to your DC hosting DNS and try again.

Tom,  when I ping either 10.1.1.38 or ad1, I get valid reply messages.

RobMobility:  We use static IP addresses.   The IP address, gateway and DNS information is correct on the machine.

Is the DNS information only the domain controller, or is there any system as well? If there is a second server set in there, remove it unless it's a DC.

Can you try join to domain again and after you'll get some error message, can you check DC event log ?

Would it make any sense to restore the computer to its original state and start over?

Tom, I am not sure which DC event log to look at.   The only event I see is a system event.  It is an information event stating that the Portable Device Enumerator Service service entered the stopped state.    Is there a particular log I should be watching on the DC?

I would check application event log.

Have you tried my suggestions? What's the result?

To Hello There:  Yes, I have tried your suggestions.  I still get the message: Network path not found  when I attempt to join the domain.  What is so strange is that this computer was working fine Friday, was shut down for the weekend and then wouldn't connect on Monday morning.    It is a new 2017 HP desktop so age is not a factor.

Before joining any computer back to the domain you have to delete old entries in AD related to that computer.

Also check DNS servers... primary and secondary. Are they correct?

nslookup on that computer comes back with: DNS request timed out (after 2 sec).  Default server: unknown.  Address: 10.1.1.38 (which is our AD CD ip address).

Can you ping 10.1.1.38, if so, telnet to port 53

You need to open the below ports for domain controller communication.

LDAP TCP-in - 389
LDAP UDP in - 389
LDAP for Global Catalog TCP in - 3268
NetBIOS name Resolution UDP in - 138
SAM/LSA TCP in - 445
SAM/LSA UDP in - 445
Secure LDAP TCP in -  636
Secure LDAP for Global Catalog TCP in - 3269
W32Time NTP UDP in - 123
RPC - RPC Dynamic
RPC Endpoint Mapper
DNS - TCP and UDP 53
Kerberos V5 UDP in - 88
Netbios Datagram UDP in - 137

Go to Network Connections
double click on NIC
select properties
select tcp/ip -> properties

Type the DC's IP address in the "Preferred DNS Server" box
Press "Advanced"
go to the DNS tab
Under dns suffix for this connection type fqdn for example  "mydomain.local"

apply changes

Thank you everyone for all of your help.  I was finally able to get the computer to connect to the network.    Someone suggested that I turn off the firewall and attempt to connect.  I thought I had done so, but apparently there was still a portion active.  We use AVG as our firewall.  I also changed the IP address and computer name to something that had not been used in the past.  I'm pretty sure it was getting the firewall completely deactivated temporarily that was the answer.   Once again, thank you!!

Why I asked for a telnet test to port 53 :) in #a42428714

Able to ping 10.1.1.38 = ICMP open
Unable to telnet to 53 = Port blocked