If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
WINIPCFG
Hello. I ahve having trouble getting windows (98 SE) to
release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd |
#2
|
|||
|
|||
WINIPCFG
In article , "Todd"
wrote: Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd The 169.254.x.x IP address is the result of a problem communicating with your ISP, not the cause of the problem. You can't release that address, because it wasn't assigned by a DHCP server. That address indicates that your computer is configured to obtain an IP address automatically, but it can't communicate with your ISP's DHCP server to make the assignment. Something else is causing the problem: the NIC, network cable, cable modem, etc. Your ISP should be able to help you fix the problem. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm |
#3
|
|||
|
|||
WINIPCFG
-----Original Message----- In article 2de7f01c46ae4$d40f5980 , "Todd" wrote: Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd The 169.254.x.x IP address is the result of a problem communicating with your ISP, not the cause of the problem. You can't release that address, because it wasn't assigned by a DHCP server. That address indicates that your computer is configured to obtain an IP address automatically, but it can't communicate with your ISP's DHCP server to make the assignment. Something else is causing the problem: the NIC, network cable, cable modem, etc. Your ISP should be able to help you fix the problem. -- Best Wishes, Steve Winograd, MS-MVP (Windows Networking) Please post any reply as a follow-up message in the news group for everyone to see. I'm sorry, but I don't answer questions addressed directly to me in E-mail or news groups. Microsoft Most Valuable Professional - Windows Networking http://mvp.support.microsoft.com Steve Winograd's Networking FAQ http://www.bcmaven.com/networking/faq.htm . Tks Steve for taking the time to answer my question. My ISP (COX) says that the problem is a WINDOWS problem. I spend an hour on the phone going though all kinds of stitutions with them. COX said that they can communicate with the modem and the steps they had me go though showed that the NIC card and modem was working as perfect or ok. Could there be something else? TKS again, Todd |
#4
|
|||
|
|||
WINIPCFG
"Todd" wrote in message ...
Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd how many NIC cards do you have in your machine? i had the exactly same problem couple days ago when i tried to installed a NIC card (a 3Com 3c905-tx model) in my wirelss ready machine. the nic card repeatly fails to communicate with router (i use Cox cable as well), IP for the NIC shows up as 169.254.*. the 169.254.*.* address is an autoip address, a feature implemented since win98, in supporting of upnp. basically, if dhcp fails, autoip will kick in and configure the address. so basically dhcp failed on your ethernet card. check settings on your card and your router's dhcp configuration. here's what i found out in my case, the NIC card i tried to install doesn't like my wireless card, after i removed the wireless card from my machine, reinstalled the NIC card, released all the current settings for NIC and reboot, and bingo! it works like a charm. |
#5
|
|||
|
|||
WINIPCFG
-----Original Message----- "Todd" wrote in message ... Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd how many NIC cards do you have in your machine? i had the exactly same problem couple days ago when i tried to installed a NIC card (a 3Com 3c905-tx model) in my wirelss ready machine. the nic card repeatly fails to communicate with router (i use Cox cable as well), IP for the NIC shows up as 169.254.*. the 169.254.*.* address is an autoip address, a feature implemented since win98, in supporting of upnp. basically, if dhcp fails, autoip will kick in and configure the address. so basically dhcp failed on your ethernet card. check settings on your card and your router's dhcp configuration. here's what i found out in my case, the NIC card i tried to install doesn't like my wireless card, after i removed the wireless card from my machine, reinstalled the NIC card, released all the current settings for NIC and reboot, and bingo! it works like a charm. . HI TKS for your reply. Well I only have one NIC in my pc and the setting on it are ok. The right driver is installed and under system props it is working properily. This is a brand new NIC card but I also have a 2 years old nic card from my old computer and was install correctly as well. I did remove the other nic before installing the other one. SO I am at a lost here as what is wrong. |
#6
|
|||
|
|||
WINIPCFG
Your syntax is wrong- run command ipconfig /release.
Type ipconfig ? to get the correct syntax for release and renew commands. Hope this helps. -----Original Message----- Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd . |
#7
|
|||
|
|||
WINIPCFG
Hello TKS for your reply. I guess I forgot the enter that
syntax in the message as well. I also tried the rlease and renew as well as the release_all and renew_all. Both give me the same response by NOT releasing the addy. Any other ideas? TKS for your help, Todd -----Original Message----- Your syntax is wrong- run command ipconfig /release. Type ipconfig ? to get the correct syntax for release and renew commands. Hope this helps. -----Original Message----- Hello. I ahve having trouble getting windows (98 SE) to release the current IP address of 167.254.172.65 so I can replace it with my ISPs (cox) IP addy. I have tried to release it under RUN buy typing in winipcfg but the message I get is "DCHP (I think)can not contact" and the same goes for trying to release under the MSDOS prompt by typing in c:\windows.release_all and then renew_all. I have a new nic card with the drive loaded correctly and my ISP (cox) tells me that as far as their computers says and the couple of different ways they have checked it my 3com cable modem and linksys nic card are working properily with no conflicts under system properties. The nic card shows up as loaded correctly under the NETWORK (under control panel) and also shows uop under the winipcfg. My ISP (cox) says it is a windows problem. help!!!!! lol TKS Todd . . |
#8
|
|||
|
|||
WINIPCFG
wrote in message ...
HI TKS for your reply. Well I only have one NIC in my pc and the setting on it are ok. The right driver is installed and under system props it is working properily. This is a brand new NIC card but I also have a 2 years old nic card from my old computer and was install correctly as well. I did remove the other nic before installing the other one. SO I am at a lost here as what is wrong. did you remove your old NIC card's driver as well - not only the card? here's what i suggest: completely remove your new and old NIC cards and do a fresh install of your new NIC, use ipconfig to check your current IP settings after reinstall. if it's still listed as autoip address 169.254.*, then release the settings (use winipcfg at command line). then reboot and check your new ip address. if this still doesn't work, try to upgrade your OS to newer OS (windows 2000/XP), this seems to be a windows98 related problem. |
#9
|
|||
|
|||
WINIPCFG
TKS agian for your reply. I did what you said to do but
still no go with it releasing the addy. This is a new computer as far as the MB, NIC and memory goes. Everything else is from old computer. The MB died so I had to buy a new MB for it along with new memory. Could the MB be keeping it from working? -----Original Message----- wrote in message ... HI TKS for your reply. Well I only have one NIC in my pc and the setting on it are ok. The right driver is installed and under system props it is working properily. This is a brand new NIC card but I also have a 2 years old nic card from my old computer and was install correctly as well. I did remove the other nic before installing the other one. SO I am at a lost here as what is wrong. did you remove your old NIC card's driver as well - not only the card? here's what i suggest: completely remove your new and old NIC cards and do a fresh install of your new NIC, use ipconfig to check your current IP settings after reinstall. if it's still listed as autoip address 169.254.*, then release the settings (use winipcfg at command line). then reboot and check your new ip address. if this still doesn't work, try to upgrade your OS to newer OS (windows 2000/XP), this seems to be a windows98 related problem. . |
#10
|
|||
|
|||
WINIPCFG
wrote in message ...
TKS agian for your reply. I did what you said to do but still no go with it releasing the addy. This is a new computer as far as the MB, NIC and memory goes. Everything else is from old computer. The MB died so I had to buy a new MB for it along with new memory. Could the MB be keeping it from working? it's hard to tell when went wrong without seeing the computer. i'm just telling from my experience what might be wrong. and i am no expert on this, either. i suggest you either seek help from Microsoft or simply upgrade your OS. this could be a windows98 related problem. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WINIPCFG | Todd | Internet | 1 | July 17th 04 12:07 PM |
WINIPCFG Help | Sheila | Networking | 2 | June 16th 04 06:06 PM |