Home »
Networking
»
Network IP Addressing
Read the article that everyone's commenting on.
Subscribe to the RSS Feed for comments on this article.
I have now experienced this problem with two clients and its the same problem with both wireless and wired pc and laptops. Something strange is going on here. I have tried every possible solution on google. I got so pissed I finally just reload XP on the computer and all was good. But I still haven't come up with a solution. But I'm on the job and I will post the solution here on this site.
Posted by: armetra at December 16, 2008 8:53 AMWell I guess I was wrong. To get my client back on the net. I looked up his Ip address via his router then I regedit the registry and I searched for 169.254.16.119, his current stuck address and replaced it with and ip address in the real range of addresses and default gateway of 255.255.255.0 and ran winsockfix. I found on google and I am writing this fix on right know on his computer and he is very happy. It worked! I will do more research on this cause I want to know why this is happening.
Posted by: armetra at December 16, 2008 10:46 AMI am trying to recocnise a Vivotex PT 7137 PTZ camera usung supplier install software.
All is fine, with an IP Address of 10.0.0.8 from a router DHCP server, in ipconfig until I run the discover program, then I end up with the following ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 169.254.19.220
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : 10.0.0.8
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 10.0.0.2
Is this a standard problem for the discover programs?
Thanks
Rod
I solved the problem pretty easily (I have vista though). The only thing I did is clicked ''diagnostic and repair'' on the connection menu and chose ''get an ip address for the connection''. I actually tried it a couple of time yesterday night and it didn't work. I just waited until this morning and it worked the first time I tried. It's probably because I left my laptop closed for several hours. Good luck to all!
Posted by: mathieu at April 13, 2009 9:55 AMThe best way I have found this issue to be resolved if all wlse fails like
netsh winsock reset catalog (vista)
or netsh winsock reset (XP)
try resetting the TCP/IP Stack in cmd prompt which is netsh int ip reset resetlog.txt
see if that works. Sometimes as i have learnt Winsock does not always repair the issue even though it's a last resort cmd. but resetting the tcp/ip stack can sometimes resolve this issue.
Hello
I have the same problem, But this occur in my phone
recently i updated the software then after i cant access WIFI in my phone . Strange thing is I can access other Wireless network & My own Pc internet is working fine . I req everybodu plz help me . My OS is vista home
big thanks in advance
To post a comment on "Why can't I connect with a 169.254.x.x IP address?", please return to that article's main page.