Network exception repair caused by sep mistaken removal of tcpip. sys

After September 27, updated the virus database, many of the company's winxp sp3 users reported that the lan network could not be connected. There are two phenomena:

1. DHCP cannot completely obtain the IP address, but the local connection status shows that it is connected, and the sending and receiving byte is zero. It fails to start DHCP and DNS manually in the system "service;

2. An IP address is available, but the connection to the domain fails, and some information systems cannot log on;

After roaming GOOGLE, this phenomenon is not a patent of one of our companies:

650) this. width = 650; "title =" sep.jpg "src =" http://img1.51cto.com/attachment/201307/104510555.jpg "/>

The common fault is that tcpip. sys is mistakenly killed:

650) this. width = 650; "title =" sep mistaken "src =" http://img1.51cto.com/attachment/201307/103159817.jpg "/>

It hasn't been a long time before the last time SEP was killed by mistake. What plane is symantec doing? 650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131227/1H2525L7-2.gif "/>

Manual solution:

1. Upgrade the virus database to the latest version, at least 20130728 or higher;

2. Restore the accidentally killed file;

3. Fixed the tcpip protocol.

I have compiled an Automatic Repair Tool for this fault, download: http://down.51cto.com/data/892361

This article is from "Zhang Hong's blog site (ID: boyhong)" blog, please be sure to keep this source http://boyhong.blog.51cto.com/367889/1261115