[Unable to browse] FTP, E-mail and Ping OK

issue

I have been following the thread from people with similar problems but mine is not fixed. This all happened yesterday when AVG falsely identified Zone Alarm as a Trojan and the 'Resident Shield' collected 350,000 examples as Zone Alarm ran all night. I uninstalled both AVG and Zone alarm but since then I am unable to browse the internet for longer than a few minutes. A reboot then restores access for a few minutes.

I have tried everything. I can access email and ftp. I can ping to URL and IP but cannot browse to either (therefore not DNS?) I have tried to fix with winsockxpfix but no effect. Have used netsh reset winsock catalogue no effect.

The effect occurs on different networks. I am using XP + SP2. Have used SP2 winsock fix also.

Could it be TCP/IP stack? Or corruptred browser? Tried system restore - no use.

Solution

Here are a few more things you can try. They might help :)

• Click on start, run, Enter 'services.msc'
• Look for DHCP client.

if it says acquiring network address that means that the DHCP client is DISABLED OR STOPPED¦ highlight the DHCP client and on the left side you will see START the service, click on it and then it will say STOP, RESTART then double click on the service and on the startup type select automatic, apply

Symptom
DHCP Client Service may not start automatically. When you attempt to start the Service manually, the following error may be displayed:

Error: Could not start the DHCP Client Service on local computer
Error 1068: The dependency service or group failed to start.

Resolution
The DHCP Client Service in Windows XP, depends on these three components:

• AFD
• NetBios over Tcpip
• TCP/IP Protocol Driver

If one of the above drivers fail to start, then the DHCP Client Service may not start.

Step I - Make sure that the three driver files are present

Open Windows Explorer and navigate to /Windir/System32Drivers folder. Make sure that the following files are present in the folder:

• afd.sys
• tcpip.sys
• netbt.sys

If one or more of the above driver files are missing, extract them from the Windows XP CD-ROM or from the ServicePackFilesi386 folder, whichever is the latest version.

Step II - Verify the number of Dependencies

From other sources in the Web, I've found that some versions of Norton Antivirus (NAV) adds an entry to the DHCP Service Dependencies, and removing NAV does not remove the appropriate value from the DHCP Dependencies.

To quickly determine the Dependency services for DHCP Client Service, type the following command in Start, Run dialog:

CMD /K SC QC DHCP

Verify the output. It should be exactly as below:

[SC] GetServiceConfig SUCCESS

SERVICE_NAME: dhcp
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:WINDOWSsystem32svchost.exe -k netsvcs
LOAD_ORDER_GROUP : TDI
TAG : 0
DISPLAY_NAME : DHCP Client
DEPENDENCIES : Tcpip
: Afd
: NetBT
SERVICE_START_NAME : LocalSystem

If additional entries are listed under DEPENDENCIES
If any other additional drivers or Services are mentioned in the DEPENDENCIES section, you need to remove them via the registry. Follow these steps:

• Click Start, Run and type Regedit.exe
• Navigate to the following branch:
• Backup the branch to a REG file

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Dhcp

• Double-click DependOnService MULTI_SZ value and set its data as follows:

Tcpip
Afd
NetBT

• Close Regedit.exe

Step III - Verify that the Dependency Service / components are running

Next step is to verify that the three dependency components are running. As the three components are actually the Kernel Drivers (Driver Service), you need to manage then via the Device Manager.

Follow these steps:

• Click Start, Run and type DEVMGMT.MSC
• In the View menu, click Show hidden devices
• Double-click Non-Plug and Play drivers section
• Double-click the entry - AFD Networking Support Environment, and click the Driver tab
• Set the Startup type to System.
• Start the service. Note down the error message if any.
• Similarly start the two other drivers namely:
• TCP/IP Protocol Driver
• NetBios over Tcpip
• Close Device Manager and restart Windows.