configure tcp/ip on ethernet card?? Lost tcp/ip binding. 1

[jlockley]

A malware attack unregistered most w2k hot fixes forced a massive update, after which the LAN card will not work with DSL.

Although the connection shows tcp/ip protocol installed, the connection software can't find it (Error E0083) and cannot set up an internet connection. (Error message states no tc/ip configuration).

Unsuccessful measures:
-uninstall Lyncsys ethernet card and reboot.
-Windows repair from CD
-Deletion of SBC DSL software and reinstallation.
-Uninstall and reinstall tcp/ip protocol on existing connection.

What file could I replace? Winsock fix?? Help much appreciated.

 

[bcastner]

faq779-4625

 

[LawnBoy]

Excellent FAQ.

 

[jlockley]

Thanks. Actually that didn't work.

It was not the malware that caused the problem (I am up again) but the Windows upgrade. I regained connectivity, or at least some of it, by running windows repair again. Now, however, I have no hot fixes, which means more malware.

Let me add that one of the losses in the process was the virtual ethernet adapter (as opposed to the lan card) which connects to Enternet (the SBC interface) and did not reinstall. It was eventually put back bu the add/remove hardware protocol.

I have some thirty pages of things I downloaded. I will put them here, hoping not to offend anyone with plagiarism.

And no, Windows does not have the right answer on this.

 

[jlockley]

The total winsock error wisdom of the web.

Winsock Errors

Winsock Error Repair


Instead of uninstalling/reinstalling tcp/ip, you can RESET it :

> Click Start/Run
> Enter this command: netsh int ip reset c:\resetlog.txt
> Hit Enter or OK.

You may want to save this info to view offline, as winsock errors will block you from

http://www access.

--------------------------------------------------------------------------------
Xp only??
To Reinstall TCP/IP

To do this you need a copy of nettcpip.inf. There is one on the Windows XP CD and there may be one on your hard drive at C:\WINDOWS\inf\nettcpip.inf. Note: To see the inf folder, open My Computer and go to the menu item Tools > Folder Options... > View > and choose Show hidden files and folders.
Right click "My Network Places" select Properties.
Right click the connection(s) and select Properties.
Click Install >Protocol >add >have disk.
Browse to the location of nettcpip.inf .
Select nettcpip.inf then click Open then OK then Internet Protocol (TCP/IP) then OK then Close
Reboot

-------------------------------------------------------------------------------------------------
Winsock2 Fix
IMPORTANT NOTE: The author of this program has left Boston University and we do not offer any technical support for this fix. Please do not call us about this tool. We leave this page up as a courtesy to the many people who still come to it through search engines and outside links, but we will no longer answer any questions about it and, in fact, we believe that it may no longer be the best solution. Even the older operating systems are now compatible with the newer winsockfix.exe utility (although it may first be necessary to install the runtime library available at

http://support.microsoft.com/default.aspx?scid=kb;en-us;290887

) and we have not used or tested our own fix in a long time.
Having said that, if you still want to give it a try, here it is... If you need assistance, you may want to consult the error codes listed at the bottom of this page.
Winsock2 Fix (w2fix.exe)
Written by Tom Kynch
This program should (only) be used on Windows 98, 98SE, or Windows Me computers whose Winsock2 information has been corrupted by poorly-written Internet programs or spyware.
This program is designed to fix a situation where all of the following are true:
· the computer can get a valid IP address
· the computer can ping DNS numbers
· the computer can be pinged from other computers
· all other network services do not work (Telnet, ftp and Web browsers)
This program removes the Winsock2 key from the Registry and uninstalls then reinstalls Dial-up Networking. A backup of the registry is made before any changes are attempted (the registry is backed up to user.tom system.tom).
Instructions for the Winsock 2 Fix:
IMPORTANT: w2fix.exe ONLY WORKS for Windows 98, 98SE, and Windows Millennium
1. Download w2fix.exe to the desktop. (Important: w2fix.exe cannot be run from a floppy disk as the program reboots the computer and a floppy disk would interfere with the boot sequence.)

Note: If you accidentally downloaded the program to a location other than the Desktop, copy it to the Desktop now
2. Double click on the w2fix file on your Desktop and follow the on-screen instructions. You will be prompted to reboot your computer twice before the fix is complete.
3. You can delete the w2fix.exe file from your computer after the fix is installed.
Tom's Information on Error Codes for the Winsock 2 Fix:
My first suggestion to a W2fix error would be to shut down ALL programs currently running AND remove ANY suspicious programs (spyware etc) from the computer, then try again.
Here are all the non-trivial error messages the program generates (I might have missed
some, but this is the majority of them.) They share the same basic format: Action attempted -> Error Code generated.
====
Unable to check for DUN Upgrades. There was an error While opening the registry key:
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall
Error Code:
----
w2fix is trying to open up the uninstall registry key.. nothing should go
wrong with this. The only thing I could imagine is that the key does not
exist.. which it SHOULD. Or the reg is corrupted.
====
Unable to query information from
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall
This could indicate a problem. Please report error code:
----
At this point it is getting the number of keys beneath the Uninstall
key - again this should not be a problem unless the registry is corrupt.
====
There has been an error while enumerating keys under
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\n"
This may indicate a problem. Please report error code:
----
Something happened while the program was searching through the keys underneath
uninstall. Basically it is looking for DUN upgrades that were installed by
the user. If this or any of the above isnt working, add and remove programs
probably wont work. Again this shouldn't happen unless the reg is messed up.
====
Unable to open the key:
HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce.
Error code:
----
The program is trying to get itself in the run section of the registry so
it'll restart at reboot. Again this should work. If it fails here, you can
let the machine reboot and then try running w2fix again, it should pick up
where it left off. Again this isn't a good thing to happen.
====
We were unable to write data to the registry key:
HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce
The errorcode was:
----
There is definitely something wrong here. The program was able to open
up the registry key, but it couldn't write to it. Not good.
====
Unable to open the key:
HKLM\System\CurrentControlSet\Services
Unable to continue.
----
This is a showstopper. We can't open up the Winsock2's parent key for whatever
reason. Try going there through the registry.. but again it's not a good sign.
====
There was an error deleting the winsock2 key.
The error code is as follows:
----
We couldn't delete the winsock2 key. This operation should go through unless the key
doesn't exist already, or something else is wrong.
=====================================================
Error codes:
#define EPERM 1 //You do not have permission to perform this action
#define ENOENT 2 //The requested object doesn't seem to exist
#define EINTR 4 //The program was interrupted during a critical operation
#define EIO 5 //An I/O error has occured
#define ENXIO 6 //No such address or device
#define E2BIG 7 //Argument list provided was too long
#define ENOEXEC 8 //Unable to execute process because arg list was too long
#define EBADF 9 //The file descriptor was invalid.
#define EAGAIN 11 //Try again... resource is busy
#define ENOMEM 12 //Not enough mem to complete the operation
#define EACCES 13 //You dont have the access rights to perform the op
#define EFAULT 14 //Bad address was given to a function
#define EBUSY 16 //Device was busy, try again
#define EEXIST 17 //The file/object already exists
#define ENODEV 19 //No such device exists
#define ENOTDIR 20 //Not a directory
#define EISDIR 21 //Is a directory
#define EINVAL 22 //Invalid argument
#define ENFILE 23 //Too many open files system wide
#define EMFILE 24 //Too many openfiles process wide
#define ENOTTY 25 //Inappropriate IO operation
#define EFBIG 27 //File too large to operate on
#define ENOSPC 28 //No space left
#define ESPIPE 29 //Illegal seek on a file
#define EDOM 33 //Argument provided beyond a valid domain
#define ERANGE 34 //Arguemen provided was beyond a valid range
#define EDEADLK 36 //DEAD LOCK 2 processes are waiting for the same resource
//and will never execute.
#define ENOSYS 40 //Subsystem that would process command is not present
hand removal…..
after removing malware:
Disable And Enable System Restore

Often times, you may have trouble removing a virus, trojan, spyware, etc. because system restore has saved it as a check point and it can not be accessed. To solve this, you will need to disable system restore, reboot, scan for the problem and finally re-enable system restore.



For Windows Millenium:

1: Right-click My Computer, and then click Properties.
2: On the Performance tab, click File System, or press ALT+F.
3: On the Troubleshooting tab, click to select the Disable System Restore check box.
4: Click OK twice, and then click Yes when you are prompted to restart the computer.
5: To re-enable System Restore, follow steps 1-3, but in step 3, click to clear the Disable System Restore check box.
2: Enable viewing of hidden files, system files and file extensions


Some programs hide themselves by making their files invisible in normal Windows settings. Run the steps in the below link (has steps for ALL Win OS's) to make them easier to find.

- Right Click Start.
- Select Explore
- Select the Tools menu and click Folder Options.
- Select the View Tab.
- Under the Hidden files and folders heading select Show hidden files and folders.
- Uncheck the Hide protected operating system files (recommended) option.
- Click Yes to confirm
- Click OK.

Download the attach GetRunKey.zip to your PC someplace you can locate it. Then extract the files from the ZIP. Locate the getrunkey.bat file and double click on it to run it. It will create a file named runkeys.txt in the root of drive C: (C:\runkeys.txt) . This log will also popup in a notepad window which your can just close. Upload the runkeys.txt file here as an attachment.


Windows 98/ME Manual DNS Repair
Go to your network settings. Right-click Network Neighborhood on the desktop, click Properties. Remove everything with the exception of the adapters.

Click OK. Don't reboot though! You've more to do.

Now open regedit and remove the following registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Dhcp
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Dhcpoptions
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\MSTCP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VXD\Winsock2
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2

Go back to the network properties and click Add->Protocol->TCP/IP. Also add Client for Microsoft Networks if it isn't added automatically. You'll likely need your Windows CD with you so it can copy various files from it.

Empty the hosts file (Windows\hosts) by opening it with notepad and deleting the entries. Save a backup beforehand. Reboot, and you should be good to go.
Collection of security software and scanning tools

http://www.palmersoft.co.uk/main.asp?content=malwarefaq

Spyware & Malware
Firewalls help prevent Spyware being installed on your computer, but your computer may already contain some unwelcome content. Spyware is defined as any program, applet, ActiveX control, Browser Helper Object, or other code, script or website which transmits information to or from a computer or represents a service which meets one or more of the following criteria:
Is installed without a user's explicit knowledge or explicit consent.
Uploads information without a user's explicit knowledge or explicit consent.
May upload information with personally-identifiable details, such as registration information, credit card details or data collected from third-party sources.
There are several tools for removing such problems, but the Network Administration Team recommend the use of Ad-Aware for the removal of unwanted material.
Some programs may be advertised as web-enhancers (for example to find related web pages), or as extra toolbars with various short-cuts or utilities. These work as add-ons to Internet Explorer (or sometimes other web browsers), and are often known as Browser Helper Objects (or BHOs). Some of them will change your default startup page, or even the default search engine, and may keep resetting these after you change them back.
BHOs have also been implicated in a major security flaw in Microsoft's Internet Explorer web browser. This has lead some organisations to recommend the use of alternative browsers such as Netscape, Mozilla or Opera.
How do I prevent spyware?
Ad-Aware
Spybot Search & Destroy
The above are two programs which will scan for, detect and remove most variants of spyware/adware/malware. You will need to close all Internet browser windows before using these tools. These programs need to be updated on a daily basis to prevent "new" spyware from infecting your computer
SpywareGuard
Spyware Blaster
These two programs are not scanners they run all the time to prevent spyware from being installed on your computer. They are much like an anti virus program which protects you from viruses.
CWShredder
CWShredder is a small utility for removing CoolWebSearch (aka Cool

http://WwwSearch,

YouFindAll, White-Pages.ws and a dozen other names). Spybot S&D tends to forget essential parts of the hijack, so until it updates, you can just this to completely remove the hijack. Updated to remove the new variants once they come out.
This tool will find and destroy all traces of the CoolWebSearch (CWS) hijacker on your system. This includes:
· Redirections to CoolWebSearch related pages
· Redirections when mistyping URLs
· Redirections when visiting Google
· Enormous IE slowdowns when typing
· IE start page/search page changing on reboot
· Sites in the IE Trusted Zone you didn't add
· Popups in Google and Yahoo when searching
· Errors at startup mentioning WIN.INI or IEDLL.EXE
· Unable to change or see certain items in IE Options
· Unable to access IE Options at all
The following website also provides useful information on dealing with Spyware.
Repairing Spyware Damage
Over the last 12 months particularly malicious Spyware code has left many Windows based computers unable to connect to the Internet after they have been cleaned. Occasionally after running any of the Spyware cleanup tools (including SpyBot - Search & Destroy or Ad-Aware SE Personal Edition) it is possible that your internet connection will stop working. In some cases only Web activity will be problematic and at other times you may experience a total loss of network connectivity.
The first thing to do if you can't connect is to back up critical files. Anytime you need to perform non-standard recovery techniques, it is always a good idea to back up your critical files first just in case your system is no longer bootable.
To repair a damaged Windows XP/2000 Winsock2 Stack, two utilities LSP Fix and Winsock XP Fix can be used. Both of these require the Windows registry to be backed up first.
Registry Backup
Download and run the erunt-setup.exe from Lars Hederer's Website
You should be able to accept the defaults. When prompted if you wish to place a shortcut in your Start-Up Group indicate "No" and then from the Welcome screen click OK.
In the next window keep the default "Backup to:" entry and click OK.
At the next prompt click "Yes" to create the folder.
You will see a status screen as your registry is being backed up which will look something like this.
That's it in terms of backing up the Windows registry.

Winsock XP Fix
Winsock XP Fix is easier to use and restores your registry and settings to their initial, default state. Download the Winsock XP Fix utility from the Spychecker website. This utility will make a backup of parts of your Windows registry, reset your TCP/IP settings, replace your existing Winsock2 registry entries with a default set, and replace your Hosts file with a default one.
Next launch the WinsockXPFix.exe. On the "Winsock and TCP Repair Utility" screen, click ReG-Backup, this will take you through the Registry Backup.
The first thing to do is to reset the Winsock Stack. On the "Winsock and TCP Repair Utlity" screen click Fix.
You need to apply the "VB_Winsock fix?" so click Yes.
The Winsock and TCP Repair Utility screen will display a status message as the repair takes place.
On the "Repair Completed" screen click OK to re-boot your computer.
You should have connectivity restored. If you still can't connect...
LSP Fix
This mini application attempts to correct problems caused when Layered Service Provider (LSP) software is not properly removed. It is trickier to use than Winsock XP Fix, so is used primarily by network administrators, but it preserves more custom settings than Winsock XP Fix can. If you're going to try both utilities then LSP Fix should be used first. If LSP Fix cannot resolve the problem, then Winsock XP Fix is the next step.
To repair the Winsock Stack using LSP Fix download the LSP Fix utility.
Launch the application by double clicking on the LSPFix.exe file and on the main Winsock 2 Repair Utility screen place a check mark next to "I know what I'm doing" and click on the entry you wish to mark for removal.
This is the step that requires some working knowledge of Windows networking since you need to select one or more entries to remove from the Winsock stack. In our case, the newdotnet6_38.dll was the entry that was unexpected so we marked it for removal. Click the >> button to move the item(s) to the Remove window.

Click Finish to remove the entry from the Winsock stack. Once you have done this the process is finalised and click "OK" to finish.

Restart your system and you should have connectivity restored.
Still Not Working?
· If you encounter problems with only one or more specific applications, you may need to re-install or repair those applications.
· Follow the suggestions from the Microsoft Knowledgebase on how to determine and recover from Winsock2 corruption.
· The last resort is that you will need to follow the system restore procedures or re-install Windows XP/2000 from CD. Back up all your work and format your hard drive. Remember it is important that you back up all your data and check it is verified as it will be lost when you reformat and reinstall your operating system.

Security downloads

http://www.bluetack.co.uk/forums/lofiversion/index.php/t1435.html

I've tried everything, but nothing works! What should I do?
A: We understand! Networking software often brings surprises.
EnterNet is no longer provided or supported actively by Siemens. For now this is all we can recommend:
1. If it doesn't work, try to identify the exact error message or behavior.
2. READ the FAQs one more time, very closely!
3. Try installing the latest evaluation version from our website . Often your problem will have been fixed in the latest version, but your ISP hasn't finished their own internal testing requirements before they can go to distribution. If the eval fixes your problem, you ask that your ISP provide it to you, or purchase it directly from our website. Please do not ask for free upgrades from Siemens Subscriber Networks.
4. Try changing the Settings to use the Protocol Driver if the default settings fail.
5. If it's a connectivity problem, take a detailed trace . This will help your ISP locate the problem quickly.
6. Consider upgrading to our next-generation PPPoE client software, Tango Access.
7. Contact your ISP. Please do not try to contact Siemens Subscriber Networks. In most cases, we've never seen our customers' networks or routers; often they've modified our software for their own specific network requirements.
Still doesn't work? Here's the last resorts to try, in the following order:
1. Be sure to uninstall the EnterNet software completely and re-boot before re-installing.
2. Try eliminating any non-essential networking software (but be sure to leave at least one ethernet adapter and TCP protocol). If your company requires you to install special client software to access their network, it could be the problem.
3. Try eliminating any non-essential applications that start automatically from your System Tray. Disable Antiviruses, personal web or firewall services, network utilities, etc. Use the MS Information tool to stop apps from loading automatically.
4. If the system is unable to restart, or freezes after installing EnterNet, try rebooting using the safe mode. For NT, try booting from the last known working system (hit space bar). Remove the Siemens Subscriber Networks PPPoE adapter from the Control Panel -> Network Properties, then reboot and do a full uninstall before re-installing.
5. Next to last resort (This has been known to resolve cases where a Microsoft DLL or Vxd was corrupted)
o Remove all Networking drivers (be sure to have your Windows CD-rom and network adapter disks before doing this!) from your Control Panel Network Properties.
o Re-add the ethernet or DSL adapters, TCP/IP protocol, and Windows Clients.
o Verify that the ethernet TCP stack is functional (adapter diagnostics, Winipcfg, etc.).
§ On NT, save the Hardware Profile from your Control Panel-> System properties.
§ On Windows98, save the configuration using the Accessories-> System Information -> Configuration tool.
o Re-install (the latest version you can get of) EnterNet, reboot, and try again.
6. If it still doesn't work, the final resort is to uninstall EnterNet and re-install WIndows. This should save your current system configuration. You should not have to re-format your disk.
In almost every case, this has been enough to get most systems working. Always contact your ISP when you're having problems. They can escalate it through their local support experts, and have designated specialists with access to Siemens Subscriber Networks for problems they're unable to resolve.
return to top of page

Change enternet settings

What is in the Settings -> Advanced options?
The Application Settings controls the global settings for the EnterNet application. These parameters apply to every profile created in the EnterNet Folder.

From the Settings dialog described above, click the Advanced button to try alternative methods for connecting with Enternet.


The Advanced settings are used to determine how the EnterNet application will control the setting of the IP address and the access to the Network drivers.
In most cases the default settings of Private API and Filter Driver should be sufficient. However, when having problems connecting or loading drivers, or when using various VPN sofware, it may be necessary to try the alternative methods in this Advanced Settings dialog.
A description follows:
IP Configuration:
When you click the Connect button, a series of packets are exchanged between EnterNet and the Network Access Server to define the parameters, authenticate the user, and negotiate the IP Addresses for the session. After the negotiation is completed, the EnterNet application takes these new addresses and assigns them to the Windows TCP/IP Protocol. There are two methods by which this can be accomplished.
Private API The default setting is Private API. The addresses are passed to the Windows TCP/IP protocol programmatically. This method was introduced starting with version 1.34 and is the default setting because it's faster.Limitation: Private API will not work with some VPN client software.
Use DHCP When DHCP is used, the TCP/IP protocol broadcasts a DHCP Request packet. Within the Efficient Networks PPPoE driver is a limited DHCP server that responds automatically with the negotiated addresses. The Windows TCP/IP protocol then recieves the new address as if they were from a remote DHCP server.Limitation: Use DHCP requires a minimum of 4 extra packets and a minor delay in processing the packets.

Network Access:
The Efficient Networks PPPoE Driver "taps" into the Windows Network properties as an intermediate NDIS driver. The PPPoE driver is then able to intercept packets, add and remove PPPoE headers, and then pass it back to Windows as if it were a regular TPC/IP packet. Starting with version 1.34, there are two methods available:

Filter Driver The default setting is the Filter Driver. In this mode packets are filtered for PPPoE headers, stripped out and passed to the TCP/IP protocol for processing.Limitation: Filter Driver will not work with some VPN clients, and will not work on Multi-processor systems or systems using EnterNet DUN. In rare cases, an error is presented saying the Tap Driver is unable to load.
Protocol Driver The Protocol Driver can be used in cases where the Tap driver is unable to load using the Filter Driver setting. It processes some of the TCP/IP parameters before passing up to the protocol.Limitation: Slightly more overhead than the Filter driver from the extra processing of packets.
________________________________________-\
How to Troubleshoot TCP/IP Connectivity with Windows 2000 or Windows NT
View products that this article applies to.
Article ID : 102908
Last Review : May 6, 2003
Revision : 2.0
This article was previously published under Q102908
For a Microsoft Windows XP version of this article, see 314067 (

http://support.microsoft.com/kb/314067/EN-US/).

SUMMARY
The ARP, PING, FTP, NETSTAT, and NBTSTAT utilities can provide useful information when you are trying to determine the cause of TCP/IP networking problems with Windows. Below is a list of possible TCP/IP symptoms with recommendations for using these utilities to diagnose the problems. Although this is not a complete list, these are examples of how you might use these utilities to track down problems on the network.
MORE INFORMATION
Q: How can I determine whether TCP/IP is installed correctly on a Windows system?

A: Trying using PING on the local system by typing the IP loopback address of 127.0.0.1 at the command line:
ping 127.0.0.1


The system should respond immediately. If PING is not found, or the command fails, check the event log with Event Viewer and look for problems reported by Setup or the TCP/IP service. You should also attempt to use PING with the IP addresses of your local interface(s) to determine whether you configured IP properly. Successful use of PING indicates that the IP layer on the target system is probably functional.

Q: How can I determine if the FTP Server service is installed correctly on a Windows system?

A: Try using FTP on the local system by typing the IP loopback address at the command line:
ftp 127.0.0.1


The interaction with the server locally is identical to the interaction expected for other Windows (and most UNIX) clients. This command can also be used to determine whether the directories, permissions, and so on of the FTP Server service are configured properly.

Q: What causes Error 53 when I'm connecting to a Windows NT, Windows for Workgroups, or Microsoft LAN Manager server?

A: Error 53 is returned when the specified computername cannot be resolved. If the computer is on the local subnet, confirm that the name is spelled correctly and that the target system is running TCP/IP as well. If the computer is not on the local subnet, make sure that its name and IP address mapping are available in the LMHOSTS file. If everything appears to be installed properly, try using PING with the remote system to make sure that its TCP/IP software is functional.

Q: After I've added a new mapping to the LMHOSTS file, what can I do if it takes an unusually long time to connect to the server?

A: A large LMHOSTS file with an entry at the end of the file, possibly following some #INCLUDEs, could cause this behavior. You can do two things to speed up the connect time: either mark the entry as a preloaded entry by following the mapping with the #PRE tag and use the NBTSTAT -R command to update the local name cache immediately, or place the mapping higher in the LMHOSTS file.

The LMHOSTS file is parsed sequentially to locate non #PREloaded entries. Therefore, you should place frequently used entries near the top of the file and the #PRE entries near the bottom.

Q: What should I do if users are having difficulty connecting to a particular server, even when specifying the same name?

A: Use the NBTSTAT -N command to determine (authoritatively) what name the server registered on the network. The output of this command lists several names that the system has registered using NetBIOS over TCP/IP. One resembling the system's computername should be present. If not, try one of the other unique names displayed. The NBTSTAT command can also display the cached entries for remote systems either #PREloaded from LMHOSTS or recently resolved names due to current network activity. If the name the remote users are using is the same, and the other systems are on a remote subnet, make sure that they have the system's mapping in their LMHOSTS file.

Q: What should I do when I cannot connect to foreign systems with hostnames using TELNET, FTP, and so on, but can only connect using IP addresses?

A: Using the Network icon in Control Panel, check the hostname resolution configuration (found under the TCP/IP Connectivity option) to be sure that the appropriate HOSTS and DNS setup has been configured for the system. If you are using the HOSTS file, make sure the remote system is spelled the same way in the file as it is being used by the application. If you are using DNS, make sure the IP addresses of the DNS servers are correct and in the proper order. To determine whether the hostname is being resolved properly, try using PING with the remote system by typing both the hostname and IP address.

Q: The banner displayed when I am using TELNET with a particular computer identifies a computer other than the one that I intended to connect to, even when I am specifying the correct IP address. How can this be?

A: Situations like this usually arise when two systems on the same network are configured (mistakenly) with the same IP address. The Ethernet and IP address mapping is done by the address resolution protocol (ARP) module, which believes the first response it receives. So the impostor computer's reply sometimes comes back before the intended computer's reply. These problems are difficult to isolate and track down. The command ARP -g displays the mappings in the ARP cache. If you know the Ethernet address for the intended remote system, you can easily determine if the two match. If not, try using ARP D to delete the entry, then PING the same address (forcing a new ARP mapping) and check the Ethernet address in the cache again using ARP -g. Chances are that if both systems are on the same network, you will eventually get a different response. If not, you may need to filter the traffic from the impostor host to determine the owner or location of the system.

Q: What should I do when a TCP/IP connection to a remote system appears to be hung?

A: The NETSTAT -a command shows the status of all activity on TCP and UDP ports on the local system. The state of a good TCP connection is usually established with 0 bytes in the send and receive queues. If data is blocked in either queue or if the state is irregular, there is probably a problem with the connection. If not, you are probably experiencing network or application delay.

Q: What should I do when the TCP/IP configuration dialog box reports: "Your default gateway does not belong to one of the configured interfaces. Do you want to change it?"

A: This error indicates that the default gateway is not located on the same logical network as any of the installed interface(s) on the system. This is determined by comparing the net ID portion of the default gateway (by computing a bitwise AND operation between the subnet mask and the default gateway) and the net ID(s) of any of the installed interfaces. For example, a system with a single interface configured with an IP address of 102.54.0.1 and a subnet mask of 255.255.0.0 would require that the default gateway be of the form 102.54.a.b because the net ID portion of the IP interface is 102.54.
--------------------------------------------------------------------------------\\How to remove and reinstall TCP/IP for Windows 2000
View products that this article applies to.
Article ID : 285034
Last Review : December 21, 2004
Revision : 4.3
This article was previously published under Q285034
SUMMARY
This article describes how to remove and reinstall TCP/IP on a Windows 2000-based computer.
MORE INFORMATION
You may want to remove and reinstall TCP/IP to help resolve the following issues:
• Bindings that are improperly configured on a server.
• Dial-up clients that are unable to connect to a RAS server.
• Network adapter drivers that do not properly bind to the protocol.
To remove TCP/IP from your Windows 2000-based computer:
1. Click TCP/IP, and then click Uninstallfrom all dial-up connections and from all LAN connections in the Network and Dial-up Connections tool.
2. Install another protocol (NWlink or NetBEUI) to maintain a placeholder for each connection.
3. Restart your computer.
4. Click LAN connections, reinstall TCP/IP, and then restart your computer.
For additional information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base:
151237 (

http://support.microsoft.com/kb/151237/)

Error message when installing TCP/IP or adding TCP/IP service
For additional information about how to remove TCP/IP from a Windows 2000 domain controller, click the following article number to view the article in the Microsoft Knowledge Base:
299451 (

http://support.microsoft.com/kb/299451/)

How to remove and reinstall TCP/IP on a Windows 2000 domain controller
How to Troubleshoot Basic TCP/IP Problems
View products that this article applies to.
Article ID : 169790
Last Review : December 16, 2004
Revision : 2.2
This article was previously published under Q169790
On This Page
SUMMARY
MORE INFORMATION
Connect to an IP Address
UNABLE TO CONNECT TO A SPECIFIC IP ADDRESS
Check Your TCP/IP Configuration
Ping the Loopback Address
Ping Your Computer's IP Address
Clear the Address Resolution Protocol (ARP) Cache
Verify the Default Gateway
Ping the IP Address of the Other Computer
Verify Persistent Route Table Entries
Use the TRACERT Command
Verify Server Services on the Other Computer
Check IP Security on the Server
Unable to Connect to a Specific Host or NETBios Name
Check the HOSTS File
Check Your Domain Name Service (DNS) Configuration
Check the LMHOSTS File
Check Your Windows Internet Name Service (WINS) Configuration
SUMMARY
This article describes how to troubleshoot some common network communication problems you may experience when you use TCP/IP as your network protocol. These problems usually fall into one of the following two categories:
• You are unable to connect to a specific IP address.
• You are unable to connect to a specific host or NetBIOS name.
If you are unable to connect to a specific IP address, the problem is related to basic connectivity. If you are able to connect to a specific IP address, but you are not able to connect using the host or NetBIOS name for that IP address, the problem is related to name resolution.

NOTE: All of the troubleshooting steps below will work on the NT and 2000 platforms, but may not work on the Win9x (except Win ME) platforms. However, the basic diagnostic and troubleshooting methods are the same for all of these Windows operating systems.
Back to the top
MORE INFORMATION
To determine whether the problem is related to basic connectivity or name resolution, use the following procedure to determine whether you can connect to a specific IP address.
Back to the top
Connect to an IP Address
Try to connect to another computer on your network using its IP address and the TCP/IP program or utility of your choice. Web browsers, ftp, and Telnet are some programs and utilities commonly used to connect to other computers with TCP/IP.

NOTE: If you do not know the IP address for your Windows NT or 2000 computer that you are attempting to connect to, run the IPCONFIG /ALL command at a command prompt on the other computer.

If you cannot connect to the other computer using its IP address, there is a basic connectivity problem. Use the information in the "Unable to Connect to a Specific IP Address" section below to resolve your issue. If you can connect to the other computer using its IP address, but you are not able to connect using the host or NetBIOS name of the other computuer, there is probably a name resolution problem. Use the information in the "Unable to Connect to a Specific Host or NetBIOS Name" section below to resolve your issue.
Back to the top
UNABLE TO CONNECT TO A SPECIFIC IP ADDRESS
Follow the procedures in each of the following sections in order. After you finish each procedure, check to see if you can connect to the other computer using its IP address.
Back to the top
Check Your TCP/IP Configuration
When you use TCP/IP as your network protocol, an incorrect TCP/IP setting (such as an incorrect IP address or an incorrect subnet mask) can cause communication problems. To determine whether Windows NT or 2000 has recorded an error due to an incorrect TCP/IP setting, examine the Event Viewer system log and look for any entry with TCP/IP or DHCP as the source. To read an Event Viewer entry, double-click the entry.

NOTE: If Event Viewer records a DHCP error, you should report the error to your network administrator.

If you receive TCP/IP errors in the Event Viewer system log, resolve each error received as indicated by the error message. For example, if you receive an error stating that the IP address parameter is incorrect, you should verify that your IP address is valid.

If there are no errors in the Event Viewer system log, follow these steps to make sure that the correct TCP/IP configuration information is being used:
1. Use the IPCONFIG command to determine your computer's basic TCP/IP settings. To do so, type ipconfig at a command prompt.
2. Verify that the IP address and subnet mask displayed by the IPCONFIG command are the correct values for your computer. If you are not sure what the correct values are, contact your network administrator.
Back to the top
Ping the Loopback Address
Use the PING command to verify that TCP/IP is working properly. To do so, ping the loopback address (127.0.0.1) by typing the following command at a command prompt:
ping 127.0.0.1
You should receive a response similar to the following:
Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time=<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time=<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time=<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time=<10ms TTL=128

If you receive an error message at this point, TCP/IP is not properly installed. To remove and reinstall TCP/IP, follow these steps:

NOTE: You must be logged on as a user with Administrator rights to complete these steps.
1. In Control Panel, double-click Network, and then click the Protocols tab.
2. Click TCP/IP Protocol to select it, click Remove, and then click Yes.
3. Click Close, and then click Yes to restart the computer.
4. Log on as a user with Administrator rights.
5. In Control Panel, double-click Network, and then click the Protocols tab.
6. Click Add, click TCP/IP Protocol to select it, and then click OK.
7. If you want to use DHCP, click Yes when prompted. If you do not want to use DHCP, click No.
8. When prompted, type the path for the Windows NT source files, click Continue, and then click Close.
9. If you are not using DHCP, you are prompted for your TCP/IP configuration information. Provide the appropriate values, and then click OK. If you are not sure what the appropriate values are, contact your network administrator.
10. Click No when you are prompted to restart your computer. If you have installed a Windows NT Service Pack, you need to reinstall the Service Pack before you restart your computer.
11. Restart your computer.
If you receive an error message while removing and reinstalling TCP/IP, you may need to manually remove TCP/IP from the Windows NT registry. For information about manually removing TCP/IP from the Windows NT registry, see the following article in the Microsoft Knowledge Base:
ow To Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows 2000
View products that this article applies to.
Article ID : 300986
Last Review : August 12, 2005
Revision : 5.0
This article was previously published under Q300986
On This Page
SUMMARY
Your Computer Configuration
To View the TCP/IP Configuration by Using the Ipconfig.exe Tool
To Display Connection Information by Using the Nbtstat.exe Tool
Testing Connections to Remote Servers
To Test Connections by Using Ping.exe
To Test Connections by Using Tracert.exe
To Test Connections by Using the NET VIEW Command
Troubleshooting
I Can Contact a Network Resource Directly, but If I "Ping" the Resource It Always Returns "Request Timed Out"
I Can Ping a Resource by Its IP Address, but I Can Not "Ping" It by Name
REFERENCES
SUMMARY
This article provides information about how to diagnose and test Transmission Control Protocol/Internet Protocol (TCP/IP) or NetBIOS network configurations. This article also describes the use of the most common diagnostic tools along with basic network analysis techniques.
Back to the top
Your Computer Configuration
When you want to troubleshoot a TCP/IP networking problem, first check the TCP/IP configuration of the computer that is experiencing the problem.


To View the TCP/IP Configuration by Using the Ipconfig.exe Tool
1. Click Start, click Run, type cmd, and then press ENTER.
2. At the command prompt, type ipconfig, and then press ENTER. This command displays your computer's DNS suffix, IP address, subnet mask, and default gateway.
3. If you need more information and want to display a detailed configuration report, type ipconfig /all at the command prompt, and then press ENTER.
4. Confirm that your computer has the appropriate settings for DNS and WINS servers, an available IP address, the proper subnet mask, the proper default gateway, and the correct host name.
To Display Connection Information by Using the Nbtstat.exe Tool
NetBIOS over TCP/IP (NetBT) resolves NetBIOS names to IP addresses. TCP/IP provides many options for NetBIOS name resolution, including local cache lookup, WINS server query, broadcast, DNS server query, and LMHOSTS and HOSTS lookup.

Nbtstat.exe is a useful tool for troubleshooting NetBIOS name resolution problems. You can use the nbtstat.exe command to remove or correct preloaded entries. To use the nbtstat.exe command:
• To list the NetBIOS table of the local computer, type nbtstat -n at the command prompt, and then press ENTER. This command displays the names that were registered locally on the computer by programs such as the server and redirector.
• To list the contents of the NetBIOS name cache, type nbtstat -c at the command prompt, and then press ENTER. This command shows the NetBIOS name cache, which contains name-to-address mappings for other computers.
• To purge the name cache and reload it from the LMHOSTS file, type nbtstat -R at the command prompt, and then press ENTER.
• To perform a NetBIOS adapter status command against the computer that you specify by name, type nbtstat -a NetBIOS computer name at the command prompt, and then press ENTER. The adapter status command returns the local NetBIOS name table for that computer and the MAC address of the network adapter.
• To display a list of client and server connections, type nbtstat -s at the command prompt, and then press ENTER. This command lists the current NetBIOS sessions and their status, including statistics, as shown in the following example:
NetBIOS Connection Table

Local Name State In/Out Remote Host Input Output
------------------------------------------------------------------
DAVEMAC1 <00> Connected Out CNSSUP1<20> 6MB 5MB
DAVEMAC1 <00> Connected Out CNSPRINT<20> 108KB 116KB
DAVEMAC1 <00> Connected Out CNSSRC1<20> 299KB 19KB
DAVEMAC1 <00> Connected Out STH2NT<20> 324KB 19KB
DAVEMAC1 <03> Listening

Back to the top
Testing Connections to Remote Servers
If you are unable to contact to a remote server, there are two common tools that you can use. Use the ping command to verify that a host computer can connect to the TCP/IP network and network resources. Use the tracert command to examine the route taken to a destination.


To Test Connections by Using Ping.exe
You can use the ping command as a troubleshooting tool to sequentially test connectivity to various network resources. To ping a network host directly:
1. Click Start, click Run, type cmd, and then press ENTER.
2. Type ping IP address of the remote network host (for example, ping 192.168.1.104) or ping host name (for example, ping

http://www.microsoft.com),

and then press ENTER.
3. Check for a reply that may look like this: Reply from 192.168.1.104: bytes=32 time=40ms TTL=61 If this message displays, the server is available on the network. If you are unable to contact the resource, you can troubleshoot the connection by using the ping command to test connectivity to various network resources: a. Ping the loopback address (by using the ping 127.0.0.1 command) to verify that TCP/IP is installed and working correctly on the local computer.
b. Ping the IP address of the local computer to verify that it was added to the network correctly.
c. Ping the IP address of the default gateway to verify that the gateway is functional and it is possible to connect to a local host on the local network. You can obtain the IP address of the local default gateway by using the ipconfig command.
d. Ping the IP address of another remote host to verify that you can communicate through a router.

To Test Connections by Using Tracert.exe
Tracert.exe is a route-tracing utility that you can use to determine the network path to a destination. To determine the path that a packet takes on the network and where that path may be ending:
1. Click Start, click Run, type cmd, and then press ENTER.
2. At the command prompt, type tracert IP address of the remote network host, and then press ENTER.
3. Examine the results to determine the length of time that the packet took to reach each network segment and the point at which the connection may stop working.
To Test Connections by Using the NET VIEW Command
1. Click Start, click Run, type cmd, and then press ENTER.
2. At the command prompt, type net view \\computer name, and then press ENTER. A list of the file and print shares of a computer that is running Windows 2000 is generated by establishing a temporary NetBIOS connection. If there are no file or print shares available on the specified computer, you receive a "There are no entries in the list." message. If the command does not work, type net view \\IP address of the remote computer, and then press ENTER. If the command works, but a net view attempt to the computer name does not work, the computer name may be resolving to the wrong address. If the command does not work and generates a "System error has occurred" error message, verify that you typed the correct name of the remote computer, that the computer is operational (and is running the File and Printer Sharing for Microsoft Networks service), and that all of the gateways (routers) between the local computer and the remote host are operational by using the ping command.
Back to the top
Troubleshooting
This section describes how to troubleshoot some of the issues that you may have.


I Can Contact a Network Resource Directly, but If I "Ping" the Resource It Always Returns "Request Timed Out"
Many organizations block the return of ICMP (ping) packets as a security measure. Because of this, if you are trying to contact a resource across the Internet, or critical internal systems, it may not be possible to obtain a response to a "ping" or "tracert" message.


I Can Ping a Resource by Its IP Address, but I Can Not "Ping" It by Name
If it is possible to contact a resource by using its IP address but a ping message to its host name does not work, the problem is likely caused by a name resolution failure, rather than network connectivity. Check to make sure that the computer is configured with the proper DNS or WINS entries, and that the DNS or WINS servers are available.
You receive an error message in Windows 2000 when you run the ipconfig /renew command
View products that this article applies to.
Article ID : 886223
Last Review : November 10, 2004
Revision : 1.0
SYMPTOMS
When you run the ipconfig /renew command at a command prompt to renew your computer IP address, you may receive the following error message:
No adapters bound to TCP/IP are enabled for DHCP.
Back to the top
WORKAROUND
To work around this behavior, follow these steps:
1. Install the latest service pack for Windows 2000. For additional information about how to obtain and install the latest service pack for Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
260910 (

http://support.microsoft.com/kb/260910/)

How to obtain the latest Windows 2000 service pack
2. Remove the network adaptor driver from your computer. To do this, follow these steps:
a. Click Start, right-click My Computer, and then click Properties.
b. On the Hardware tab, click Device Manager, and then double-click Network adapters.
c. Double-click your network adaptor.
d. Click the Driver tab, click Uninstall, and then click OK.

3. Re-install the network adaptor driver. To do this, follow these steps:
a. Click Start, point to Settings, click Control Panel, and then click Add/Remove Hardware.
b. Click Next, click Add/Troubleshoot a device under Choose a Hardware task, and then click Next.
c. In the Devices list, click Add a new device, and then click Next.
d. Click No, I want to select the hardware from a list, and then click Next.
e. Click Network adapters, and then click Next.
f. In the Manufacturers box, click the name of your network adaptor manufacturer.
g. In the Network Adapter box, click the name of your network adaptor, and then click Next. If your network adaptor does not appear in the Network Adapter box, click Have Disk, and then use the driver CD that was supplied by the network adaptor manufacturer.

Note You may be prompted to insert the Microsoft Windows 2000 CD or the driver CD that was supplied by the manufacturer.
h. Click Next, and then click Finish.


IPCONFIG Diagnostic Utility: Parameters and Usage
View products that this article applies to.
Article ID : 117662
Last Review : May 6, 2003
Revision : 2.0
This article was previously published under Q117662
SUMMARY
IPCONFIG.EXE is a new utility included with Windows. The purpose of this utility is to provide the user with diagnostic information related to TCP/IP network configuration. IPCONFIG also accepts various Dynamic Host Configuration Protocol (DHCP) commands, allowing a system to update or release its TCP/IP network configuration.
MORE INFORMATION
Example:
IPCONFIG [/? | /all | /release [adapter] | /renew [adapter]]
/?: Displays this help message.
/all: Displays full configuration information.
/release: Releases the IP address for the specified adapter.
/renew: Renews the IP address for the specified adapter.
With no parameters, IPCONFIG will display only the IP address, subnet mask and default gateway for each adapter bound to TCP/IP.

With the /all switch, IPCONFIG will display all the current TCP/IP configuration values including the IP address, subnet mask, default gateway and Windows Internet Naming Service (WINS) and DNS configuration.

If adapter name is not specified with either the /Release or /Renew switch, then the IP address leases for all adapters bound to TCP/IP will be released or renewed.

NOTE: The /Release and /Renew switches can only be used on a system that is configured with DHCP

A Network Adapter Is Missing in Device Manager After a Full Restore
View products that this article applies to.
Article ID : 318715
Last Review : December 4, 2003
Revision : 4.0
This article was previously published under Q318715
SYMPTOMS
After you use Ntbackup.exe to perform a full restore or a full System State restore to restore a Windows 2000 installation over a clean Windows 2000 installation, the network adapter may be missing in Device Manager. Instead of the correct network adapter, a new device, such as a WAN miniport (L2TP) device, may be listed. You also might not be able to reinstall the network adapter.
Back to the top
CAUSE
This behavior can occur if the deployment method that was used to install the clean Windows 2000 installation differs from the deployment method that was used to install the original installation.
Back to the top
RESOLUTION
Before you perform the restore operation, you must reinstall Windows 2000 by using the same deployment method that was used to install the original installation. For example, if the original installation was installed by using the Windows 2000 CD-ROM, you must install the clean installation of Windows 2000 by using the Windows 2000 CD-ROM. If the installation was originally installed by using an unattended installation script, you must use the same script to install the clean installation. After you perform the clean installation by using the same deployment method, you can perform the restore operation.

You might also be able to work around this behavior with an in-place upgrade of Windows 2000 after you perform the restore operation. For additional information about performing an in-place upgrade, click the article number below to view the article in the Microsoft Knowledge Base:
292175 (

http://support.microsoft.com/kb/292175/EN-US/)

How to Perform an In-Place Upgrade of Windows 2000
If an in-place upgrade of Windows 2000 does not correct the issue, the following workaround might resolve the issue:
1. Install a secondary protocol such as the NetBEUI protocol. If you already have a secondary protocol installed, skip this step.
2. If the computer is a domain controller, restart the computer in Directory Services Restore mode. Otherwise, restart the computer in "Safe Mode with Networking" mode.
3. Remove the TCP/IP protocol from properties of the Local Area Connection.
4. If the computer is a domain controller, restart the computer again in Directory Services Restore mode. Otherwise, restart the computer again in "Safe Mode with Networking" mode. You must restart the computer again at this stage because the TCP/IP protocol is not available for reinstallation until you restart the computer.
5. Reinstall the TCP/IP protocol in the Local Area Connection properties.
6. Remove the protocol that you temporarily added in step 1 (if appropriate), and then restart the computer.

Unable to connect to ISP by using DSL in Windows Millennium Edition, in Windows 2000 Professional, in Windows NT Workstation 4.0, in Windows 98, and in Windows 95
View products that this article applies to.
Article ID : 289802
Last Review : December 21, 2004
Revision : 4.1
This article was previously published under Q289802
SYMPTOMS
When you try to start your Internet Service Provider (ISP) connection, which uses Digital Subscriber Line (DSL), one of the following error messages may appear:
E0041: Failed on create device: NTSPPP3
OR
Windows stopped responding while attempting to start this device and therefore will never attempt to try to start this device again - Code 11
Back to the top
CAUSE
This behavior can occur if the Point to Point Protocol over Ethernet (PPPoE) adapter is incompatible with DSL.
Back to the top
RESOLUTION
To resolve this behavior, contact your ISP or DSL provider for specific settings and hardware requirements.
Back to the top

 

[jlockley]

And yes, that was a very cool faq. Unfortunately it wasn't my problem. I have it stashed off line for the next time, however.