1,105,295 Community Members

Strange IP 169.*.*.*

Member Avatar
darkSo
Newbie Poster
1 post since Oct 2012
Reputation Points: 0 [?]
Q&As Helped to Solve: 0 [?]
Skill Endorsements: 0 [?]
 
0
 

Hi all,

I have a little server in my office network with Windows Server 2008. I have assigned it manually the IP: 192.168.1.100, but randomly after a restart, a strange IP was assigned (something like 169...*) then the server is cutted from the network and I have to disable/enable the network to get the correct IP.

Why this happens? I manually assigned IP just for avoiding this problem, but it is still there.

Every solution is accepted, also a workaround!

Thank you a lot for your help!

Member Avatar
JorgeM
IT Addict
6,390 posts since Dec 2011
Reputation Points: 581 [?]
Q&As Helped to Solve: 957 [?]
Skill Endorsements: 172 [?]
Moderator
Featured
Sponsor
 
0
 

A 169.254.x.x address is within the APIPA range (automatic private IP address). This type of address is assigned to a network interface, when it it configured as a DHCP client.

In your case, if you applied a static IP, this should not have happened. Why did it happen? A fluke maybe. Do you have the latest driver applied? Is this a reputable interface adapter? Check your system event log for possible errors.

Member Avatar
cguan_77
Nearly a Posting Virtuoso
1,379 posts since Apr 2007
Reputation Points: 8 [?]
Q&As Helped to Solve: 117 [?]
Skill Endorsements: 0 [?]
 
0
 

have you tried pinging the loop back 127.0.0.1, if you've done manual settings and still doesn't work..it could be a hardware problem, adapter spoiled, network cable issue, network socket loose, spoiled or dirty.. a lot of possible issue...

netsh winsock reset <-- have u tried this?

check out this one as well -- http://support.microsoft.com/kb/299357

You
This article has been dead for over three months: Start a new discussion instead
Post:
Start New Discussion
View similar articles that have also been tagged: