Solve the problem that XP can access the Internet at the company and cannot access the internet at home

The XP notebook is added to the domain in the company. It uses the domain account to log on, and the domain controller IP address as the DNS

 

If you do not renew your domain or use a local account, you will not be able to access the Internet. However, you can ping the public IP address, which is a DNS resolution problem.

 

The DNS set for the NIC is changed to public DNS, and ipconfig/all check is indeed public DNS, but NSLookup is still the domain controller of the company by default.

 

Try to exit the XP Domain and you will be able to access the Internet. Basically, you can confirm that it is caused by the domain environment.

 

The strange thing is: Only XP has this problem. If the client is 2003, it will be okay.

 

The above situation is analyzed by Dr. Chang Bo for two reasons:

1. DNS Cache

2. Domain policies forcibly specify DNS

 

Therefore, net stop Dnscache and NSLookup remain unchanged, which is not the first cause.

 

FoundHttp://tech.bestjoin.net/2006/06/post-111.html.

 

That must be the second point. I decided on the train of thought and checked the policy one by one.

 

Finally found

 

 

 

Previously it was enabled, and the value was a domain control IP address. Now I have changed it. The Group Policy is refreshed on the client XP and takes effect. NSLookup is normal.

 

In the future, we can rectify the company's intranet. Next we can add all the machines to the domain for permission control. In this case, people may not install software in disorder, but also the virus.

 

 

So when did this policy be added? I was not impressed with this operation.

 

I think a local Windows Update was previously implemented, and it is estimated that it was an automatic modification policy. I would like to remind my friends here (but I am not sure)

 

Thank you again!