Laptop Won't Connect to Net via DLink Router [Solved/Closed]
McTav
- Posts
- 2
- Registration date
- Tuesday February 3, 2009
- Last seen
- February 5, 2009
Related:
- D'link router not connecting to laptop
- My dlink le petic router is not connecting to win 8.1 - Best answers
- Modem is connected but not the internet? ✓ - Forum - Network
- D-link DIR-615 won't connect ✓ - Forum - Network
- Tp link router not connecting to internet ✓ - Forum - Network
- Router not connecting to internet ✓ - Forum - WiFi
- D'link router password change ✓ - Forum - Network
3 replies
Best answer
im tring to conect to the internet via my wireless router but all I get is status conected at 54mps exelent signal you are conected acquiring network address but it never gets there it just sits there but never conects to the internet ?
A few words of thanks would be greatly appreciated. Add comment
2933 users have said thank you to us this month
- Posts
- 19520
- Registration date
- Wednesday October 8, 2008
- Status
you may have a DHCP problem - DHCP gets the IP address from the router - to test this assumption you can enter the following address for Google http://74.125.95.99/ in your browser. If the browser does in fact connect to Google you can use the following steps to help resolve the problem. I have had mixed results with these tools and can't guarantee anything:
the first thing to check is NetBIOS over TCP/IP
>> Open up network connections (In Control Panel)
>> Right click on your network (Your wireless connection)
>> Click Properties
>> In the General tab click Internet protocol (TCP/IP)
>> Click Properies
>> Click Advanced
>> Click the WINS tab
>> Click the Enable NetBIOS Over TCP/IP button (This is NOT the default option)
The next item to check is the DHCP service itself:
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 STOPED 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 it's 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.
the first thing to check is NetBIOS over TCP/IP
>> Open up network connections (In Control Panel)
>> Right click on your network (Your wireless connection)
>> Click Properties
>> In the General tab click Internet protocol (TCP/IP)
>> Click Properies
>> Click Advanced
>> Click the WINS tab
>> Click the Enable NetBIOS Over TCP/IP button (This is NOT the default option)
The next item to check is the DHCP service itself:
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 STOPED 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 it's 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.