|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (7 bit)
Join Date: Mar 2003
Posts: 87
|
Do something about this Microsoft's Windows Ugly Feature...
Hello friends
I hv been trying to find The solution of renewing the IP Address In XP/2k/98/me for several purposes like CABLE Modem connections, Small Home Networks. But if the IP address is 169.254.*.* IT SHOWS THAT NIC(HARDWARE) IS WORKING ..(Am i correct..) According to Site http://www.practicallynetworked.com/ Problem: Network Connection Has IP Address 169.254.x.x Description: The network card is configured to obtain an IP address automatically, and it’s connected to a network with a DHCP server: hardware router, another computer running Internet Connection Sharing, cable modem, DSL modem, etc. But it gets a 169.254.x.x IP address, which indicates that it can’t communicate with the DHCP server: Possible Solutions: Connect the computer using a different Ethernet cable or hub/switch/router port. Download and install the latest firmware for the hardware router. Disable XP’s Internet Connection Firewall on the local area network connection. The card is configured to automatically sense network speed and duplex mode, but auto-sensing is failing. Configure the speed and duplex mode manually. For example, most switches and routers use 100 Mb speed and full duplex. To make the settings, right click the network connection and click Properties | Configure | Advanced. Un-install the network card and move it to a different slot. If you have a cable modem connection, turn off the computer, turn off the cable modem, and wait a few minutes. Turn on the cable modem, and then turn on the computer. If I try to renew it Gives an Error Error enewing a DHCP lease fails, with error message “An error occurred while renewing interface Problem: Network connection configured to obtain an IP address automatically has IP address 0.0.0.0 Solution: Make sure that the DHCP Client service is running: Right click My Computer, and click Manage. Double click Services and Applications. Double click Services. Double click DHCP Client. If the Service status is Stopped, click Start. Set the Startup type to Automatic. Thanks to Lightcap, who suggested this fix in a news group message. Even tried disabling APIPA Method ===== Disabling APIPA In rare situations, you might want to disable APIPA, which you do by modifying client Registry. Run regedt32.exe and go to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\Tcpip\ Parameters\Interfaces. Select the adapter for which you want to disable APIPA. Add the value IPAutoconfigurationEnabled of data type REG_DWORD and set it to 0 to disable it, as Screen 2 shows. This entry isn't present by default because the OS enables APIPA and assumes a value of 1. You need to add this value only if you want to disable APIPA. If you have multiple adapters and you want to disable APIPA for all of them, simply add the entry IPAutoconfigurationEnabled at the HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\ Tcpip\Parameters level and set it to 0 No Go.... Does it has anything to do with Winsock ... (My understanding it is not) m basically talking about the cable/dsl modems. If during installtion we get an IP address 169.254.*.* , That means it is an internal IP address assiged by Windows . After performing all the steps that i hv mentioned in my original post, we hv still of cases in which we can't get an IP address from ISP DHCP server. I really want to know , do you know any other tip thru which we can get rid of this windows APIPA address. 169.254.*.* proves that NIC is working fine and it is a problem with software (Am I correct) I only want to know how to get rid of 169.254.*.* I hv tried all the above options but success rates are very small Lets Discuss it with U experts out here..... |
|
|
|
|
|
#2 |
|
Member (11 bit)
|
You cannot get rid of that address. It is the address assigned to allow you access to settings of your router. Are you saying that you have a dedicated server performing DHCP? I think probably not. I am unsure of why you are even using ICS. With a broadband ethernet router you should have no need of ICS at all. Connect cable modem to household cable coax and router to cable modem with supplied Cat5 cabling according to your router guide. Connect ethernet cable to each NIC of each machine. Launch your browser and type the 169.254.xx.xx address in the address bar of your browser and enter. You may have set password or changed user (usually Admin or Administrator)for entry, be prepared to enter. If you have not set a password just enter without inputting a p/w. Once in the settings there usually is several tabs that you can navigate. Make sure that Enable DHCP is checked. Menus differ somewhat from router to router, but it should be similar. You should see the ISP's IP address in there but your router address is set. That will be the only address needed for your ISP to supply internet connectivity. All PC's connected to the router will be behind a NAT firewall and have internet if proporly configurednetworking convention is used. There is no need to go into NIC properties unless you have made previous changes. NO gateway DNS settings are needed. Your router is taking care of assigning IP addresses to each machine on your network. Do not confuse WAN (internet) from LAN (your internal network.
Last edited by AlwaysUp; 06-08-2003 at 09:55 AM. |
|
|
|
|
|
#3 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 37,791
|
Whenever I get an APIPA address like this, I give the device an appropriate static IP for the particular network, this usually takes care of things.
|
|
|
|
|
|
#4 |
|
Member (11 bit)
|
There would still be no reason to use ICS, would there GLC?
|
|
|
|
|
|
#5 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 37,791
|
He isn't saying that he is using ICS, that's just an item mentioned in his paste of an article.
|
|
|
|
|
|
#6 |
|
Member (10 bit)
Join Date: Dec 2002
Location: SE-PA
Posts: 896
|
The reason you're getting the 169.xxx.xxx.xxx address is that your PC can't find a DHCP server. It's not a "Windows Ugly Feature", but rather a default address when address resolution fails.
Perhaps if you'd state what configuration you have, and what you're trying to accomplish, we could be more constructive. ![]() From your limited information, I'd say that you haven't actually established a connection with your cable ISP, and their DHCP server isn't available. |
|
|
|
|
|
#7 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
MS has an update for this, and there are two tools you can use.
The first is explained here: http://www.mikeshardware.com/tips/ti...ml#anchor12531 The second is Winsockfix.exe from here: http://members.shaw.ca/techcd/ |
|
|
|
|
|
#8 |
|
Member (9 bit)
Join Date: May 2002
Posts: 298
|
It all depends on how your network is setup and what you are using it for. Why do you have a router AND a server with ICS installed onto the network. If you are using the router as a mechanism to access Internet, you don't need the ICS then. An APIPA address is assigned to your network card because it isn't communicating with the DHCP server, so that means something on the network is not configured correctly.
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|