HOW TO fix Windows XP IP Auto configuration Problems

[Naimah]

Sponsored Links

I got a trouble with my 169.168.x.x IP. I am using Microsoft Windows XP, and I don't have any router. I read that this crisis sometimes takes place while you plug in your internet cable to another computer, and your computer misplaced your “IP address”. As a result, I attempted to install Winsock fixes. I try netsh int ip/winstock reset commands, it finished with error: The below DLL helper cannot be loaded: DGNET.DLL). Even tried this thing, but nothing is useful. So please, could anyone help me to sort-out this problem? Here is my Ipconfiguration:
Microsoft Windows XP.
C:\Documents and Settings\Administrator>ipconfig/all
Host Name : abc-f102458be18
WINS Proxy Enabled : No
Node Type : Unknown
IP Routing Enabled : No
Connection-specific DNS Suffix. :
Description : Hamachi Network Interface
Physical Address : 00-13-C1-18-29-09
Dhcp Enabled : Yes
Autoconfiguration Enabled: No
IP Address : 0.0.0.0
Subnet Mask : 0.0.0.0
Default Gateway :
DHCP Server : 255.255.255.255
Ethernet adapter Local Area Connection:
Dhcp Enabled : Yes
Autoconfiguration Enabled: Yes
Autoconfiguration IP Address: 169.168.10.156
Subnet Mask : 255.255.0.0
Default Gateway :

[Steve123]

Here you First uninstall or remove Hamachi, and after doing these run this stack repair again.
TCP/IP stacks repair options for use with Windows XP with SP2/SP3.
Follow the following steps:

1. Start—Run—CMD (to open a command prompt).
2. In the CMD window which opens, just type the following commands, every followed by the Enter key:
3. Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log
4. Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog
5. After the stack is reset shutdown your computer.
6. Take away power from the modem for 20-40 seconds or more.
7. Power up the modem, wait for some minutes.
8. Start the computer and place the following information again.
9. Click on start-- Run and then type CMD and press Enter to open a command prompt. In command prompt window type, “IPCONFIG /ALL” command:

Here you get your solution.

[Shen]

I think its problem with installation of your Service Pack. To fix this problem install SP3. You may attempt to uninstalling/reinstalling the Network Adapter from Device Manager. First click on the Start, and right click on My Computer - Properties - Hardware tab - Device Manager - search you’re Network Adapters and enlarge it. Then right click on NVDIA Adapter and select Uninstall. Restart your system and it should reinstall the adapter for you. Does that computer system work connected to a dissimilar or different network? Could be the NIC expired. If it works at these times here, and works usually somewhere else, begin looking at the modem, router, or the ISP.

[Big Fish]

I have a simple solution for this: Always allocate a permanent private IP address to network adapters which cannot reach a DHCP Server. You should only use IP Auto configuration on adapters which typically can reach a DHCP Server. A few one-way Cable Modem users will have been told by their ISP to enable IP Auto configuration on the Ethernet Adapter that connects to the Cable Modem. Such ISPs always advise this for ease, being unaware of the troubles it causes. It is best to configure such adapters as follows:
IP Address: 10.0.0.1
Mask: 255.0.0.0
Gateway:
While NAT32 is to be installed on a computer system with a private LAN Adapter, you should forever utilize a private Class B IP address on that adapter. In fact, the Adapter should be configured as bellows:
IP Address: 172.168.1.1
Mask: 255.255.255.0
Gateway:
You should too forever enable DNS (Domain name server), giving the host a name of your option on the Domain of your ISP. The DNS address specified should be the address of a quick, reliable DNS server in your surrounding area.