Foreword:
Today's test environment requires a win7 system, but this error occurred when win7 linked to the domain environment
Let me write down how I recovered here
repair:
Try to modify HOST:
First look at the error reported, enter the error that the DNS cannot be connected, in this case, first determine whether the host can not resolve to my domain control server IP normally, first look at my win7 network configuration
Among them, 192.168.1.3 is the IP of my domain controller.
I pinged and found that I couldn’t find it. Since the DNS resolution failed, I changed the host to force you to resolve the IP I specified.
Modify the hosts file to force resolution to the DNS server I specified.
Ping the following test and resolve to the normal IP
At this time, I went to connect to the domain controller and found that it still reported an error.
Disable IPV6:
It's very strange at this time, but it still doesn't work. Take a look at your configuration at this time
nslookup galaxy.org
It can be seen that our 192.168.1.3 is not resolved
Then it is possible to use IPV6 instead of IPV4, try to disable IPV6,
Then use nslookup, you can see the normal analysis
It's ok to link again
Summarize:
The solution is as follows:
- See if the requirement is to assign IP manually or automatically
- Disable IPV6
- If not, add the address of your own domain control host in hosts