Problem with my ip adress
Posted 15 September 2005 - 02:30 PM
Posted 16 September 2005 - 01:03 PM
Posted 17 September 2005 - 06:59 PM
I can see that this has been on ongoing post and your problem has not yet been resolved. In the previous posts and in your listed trouble shooting steps you have already tried the following:
1) I tried renewing the ip address.
2) I even bought a new networking card.
3) Tried resetting the router.
4) Tried restoring the router to Factory Defaults.
5) Tried resetting the modem.
6) Netsh winsock reset.
7) Enable IEEE 802.1x authentication.
8) Updated the Firmware of your Modem.
9) Verified connectivity to your router and not neighbors.
What steps i need you to perform, to better locate where your problem might be:
A) Please connect your system like this:
............Cable Modem -----> Wired NIC (Ethernet Card)
B) Once this is accomplished please verify the light status on your cable modem (reply with Model and Manufacturer and what lights are Solid, blinking and Off all together)
C) Please verify what lights are solid, blinking, and what "color" they are on your Wired Ethernet Card (Tiny lights were you plug in the ethernet cord)
D) Please click on "START" ----> "RUN" -----> Type in "CMD" -----> hit "Enter"
.......D1) At the Command Prompt Type in " ipconfig "
.......D2) Write down your "Default Gateway" - *to be inserted into step D5
.......D3) Type in " ping localhost -l 32 -n 100 "
.......D4) Include the result Averages in your Reply.
.......D5) Type in ping Default Gateway* -l 32 -n 100
.......D6) Include the result Averages in your Reply.
.......D7) Type in ping pingtulsa.coxinet.net -l 32 -n 100
.......D8) Include the result Averages in your Reply
.......D9) Type in exit
E) If you complete Steps A through E, I should be able to resolve your problem or at the very least tell you where the problem is.
Posted 18 September 2005 - 07:48 AM
open a command prompt.
type in: netsh dump
hit enter, then close the command prompt and reboot the computer.
Posted 18 September 2005 - 10:40 AM
Posted 19 September 2005 - 02:32 AM
Posted 19 September 2005 - 05:54 AM
so yes, it wont release, because it cant find anything to get a proper ip from and it'll just keep assigning itself a 169 number until it does.
look at your router settings, firewall, etc. I once had this problem with one of my systems. I put up the firewall and then it was able to see the router. strange really.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users