ip address

Pardus

Diamond Member
Jun 29, 2000
8,197
21
81
my pc keeps getting a 169.xxx.xxx.xxx ip address between the pc and my cable modem, what causes this address and how can i get the pc to issue a normal ip address.

thanks
 

bwnv

Senior member
Feb 3, 2004
419
0
0
169.x.x.x is the default that XP will use if it can't get an addy through DHCP. Either your modem isn't set up for DHCP (need to use a static IP addyif so), or if the modem can't serve DHCP you'll need to buy a router for it. If this is your only computer just set the ip manually. You'll need the addy's from your ISP for that. Try opening a run box, type CMD, click OK, in the command prompt type IPCONFIG/RELEASE press enter, type IPCONFIG/RENEW press enter, check your addy again, if it's still 169.x.x.x than you don't have a DHCP server.
 

sieistganzfett

Senior member
Mar 2, 2005
588
0
0
hi, many things actually can cause that problem, but i need more of an idea of your exact setup configuration... when did it start doing this? was it working before?
1. have you tried unplugging the cable modem, then waiting 2 minutes, then plugging it back it and checking the lights?
2. did you remove spyware, then this occured?
3. have you tried releasing the ip with ipconfig /release then renewing it with /renew
4. have you tried perhapo another pc connected to it to see if that works properly?
5. its just the modem connecting the the pc through an ethernet cable? or is it usb? or do you have routers or anything else?
 

Pardus

Diamond Member
Jun 29, 2000
8,197
21
81
hi, many things actually can cause that problem, but i need more of an idea of your exact setup configuration... when did it start doing this? was it working before?
1. have you tried unplugging the cable modem, then waiting 2 minutes, then plugging it back it and checking the lights?
yes
2. did you remove spyware, then this occured?
no
3. have you tried releasing the ip with ipconfig /release then renewing it with /renew
didnt work, still holding the 169.x address
4. have you tried perhapo another pc connected to it to see if that works properly?
don't have a 2nd pc to use/test
5. its just the modem connecting the the pc through an ethernet cable? or is it usb? or do you have routers or anything else?
connected via a router, well was, not connected straight thru.


prob going to reformat to fix this.
 

zeroreality

Junior Member
Apr 11, 2006
4
0
0
I am having a similar issue and can provide some more details, for my case anyway.

I am using a DLink DI-524 wireless/wired router. I purchased this back in September 2005 and until a few days ago everything was gravy. Then I purchased a 360 and things seem in total disarray now. So once I have my 360 (hardlined into the router) and a laptop using wireless. However, whenever the 360 is connected I cannot obtain a "real" ip address on my laptop. I keep getting a 169.xxx (I am running win2k sp4 on my laptop). UNLESS I plug my laptop into the router itself, then I get a real ipaddress for both the wire and the wireless connection to my laptop. Then today I received my desktop, which I hardwired into my router. NOW my laptop gets a real ip address (wirelessly) my 360 gets a real IP address, but my desktop keeps getting a false ip address. And here is also something that seems odd . . . I cannot ping my 360's ipaddress from my laptop (which both have "real" address) i keep getting timed out.

So in short, I have no idea what is going on or how to fix this, please advise.
 

zeroreality

Junior Member
Apr 11, 2006
4
0
0
Oh and here are the things I have tried:

1. I have tried setting all my machines to receive static and dynamic addresses. The static address worked it seemed, but my computer (MCE) still could not see my xbox, so this isnt a solution.
2. I have tried releasing and renewing the ip address of my desktop, to no avail. Here is the error I receive when I try and renew "WSAStartup cannot function at this time because the underlying system it uses to provide netowrk services is currently unavailable"
 

zeroreality

Junior Member
Apr 11, 2006
4
0
0
Think i figured it out. My DSL modem also had its default gateway set to 192.168.0.1 Once I changed my router's default gateway to 192.168.0.2 I was all set.