I have a workstation that cannot connect to the Internet nor ping to anything other than 127.0.0.1 Event ID 7003 for DHCP Client and the TCP/IP NetBIOS Helper state that these depend on a nonexistent service: NetBT. How do I reinstall these files. This is on an Enterprise license XP Pro - so repair install was not an available option.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to reinstall NetBT in XP Pro SP2?
- Thread starter mkinsman
- Start date
faq779-4625
1. Perform a winsock Fix including reinstalling TCP/IP
Reinstall of the TCP/IP protocol to restore Winsock functionality
Step 1: Delete registry keys
A) Open Regedit from the Run line
B) Go to both of the following keys, export each of them, and then delete them:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2
C) Restart the computer
NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.
Step 2: Install TCP/IP on top of itself
A) Open the properties window of the network connection
B) Click Install
C) Click Protocol, then Add
D) Click Have Disk
E) Type the path to the nettcpip.inf file, for example: c:\windows\inf, and click
OK (if you try to click Browse, then browse to the \inf folder, it may not show up
in the list).
F) You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G) Restart the computer
When the computer reboots you will have functional Winsock keys.
Step #3: Start, Run, CMD
netsh int ip reset resetlog.txt
netsh winsock reset catalog
When you receive a message that a restart is required, reboot the computer.
1. Perform a winsock Fix including reinstalling TCP/IP
Reinstall of the TCP/IP protocol to restore Winsock functionality
Step 1: Delete registry keys
A) Open Regedit from the Run line
B) Go to both of the following keys, export each of them, and then delete them:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2
C) Restart the computer
NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.
Step 2: Install TCP/IP on top of itself
A) Open the properties window of the network connection
B) Click Install
C) Click Protocol, then Add
D) Click Have Disk
E) Type the path to the nettcpip.inf file, for example: c:\windows\inf, and click
OK (if you try to click Browse, then browse to the \inf folder, it may not show up
in the list).
F) You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G) Restart the computer
When the computer reboots you will have functional Winsock keys.
Step #3: Start, Run, CMD
netsh int ip reset resetlog.txt
netsh winsock reset catalog
When you receive a message that a restart is required, reboot the computer.
- Thread starter
- #3
bcastner,
Thanks for the tip - tried it - still no go. Services still lists the DHCP Client and TCP/IP NetBIOS Helper services as not started - and when attemping to start either one - an error message - Error 1075 is returned.
Any ideas? I was able to perform ALL the steps you had outlined.
Thanks
Thanks for the tip - tried it - still no go. Services still lists the DHCP Client and TCP/IP NetBIOS Helper services as not started - and when attemping to start either one - an error message - Error 1075 is returned.
Any ideas? I was able to perform ALL the steps you had outlined.
Thanks
MiltoxBeyond
Programmer
I had a similar problem on a home computer and tried the following to fix my problem:
1) Open up a command window
2) Type: nbtstat -R
3) Be sure you typed a capital R...
4) Check if it fixed it.
Not sure if you have the exact same circumstances but give it a try.
1) Open up a command window
2) Type: nbtstat -R
3) Be sure you typed a capital R...
4) Check if it fixed it.
Not sure if you have the exact same circumstances but give it a try.
NetBT is not a service, but a protocol.
The TCP/IP Netbios service does not start by default. To set it to its startup state:
. Be certain File and Printer Sharing are selected for the network connection;
. Under Internet Protocol - TCP/IP, highlight this. Click Properties. Click the Advanced button. Click the WINS tab. select 'enable netbios over TCP/IP'
The DHCP service has no service dependencies. It will use IPSEC if you have implemented IPSEC filtering, and NetBT if you use this for HOST resolution.
The important thing is whether you are obtaining an IP automaticly, or using static IP addresses for your LAN.
The TCP/IP Netbios service does not start by default. To set it to its startup state:
. Be certain File and Printer Sharing are selected for the network connection;
. Under Internet Protocol - TCP/IP, highlight this. Click Properties. Click the Advanced button. Click the WINS tab. select 'enable netbios over TCP/IP'
The DHCP service has no service dependencies. It will use IPSEC if you have implemented IPSEC filtering, and NetBT if you use this for HOST resolution.
The important thing is whether you are obtaining an IP automaticly, or using static IP addresses for your LAN.
- Status
Similar threads
- Locked
- Question