Vista autoconfiguration 169

Any clues? Is it something to do with the autoconfiguration IPv4 address? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.

I have the same question Report abuse. Details required :. Cancel Submit. Hi John Burton, It is possible that the number of devices connected to the router is not set correctly.

Also I would suggest you to use the below mentioned steps and check - 1. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to Meghmala's post on April 9, Dear Meghmala Sorry to say it, but no change.

As I said I have been researching this problem for some three months and I have done all the obvious things. To your points above: Info is as I previously stated, taken from ipconfig. As I said I am getting Hello, I have the same problem. I am an user of school network for dormitories, but the administrator warned me that I must disable IP autoconfiguration if I don't want to be disconnected from the network.

The registry editing was not successfull, could you please give me some advice? Michal M. First is the same as within previous versions. It's implemented within dhcpsvc. It's implemented within tcpip. This implementation seems not to be affected by a registry settings.

Please note the analysis above may not be correct as I has no access to Windows source code nor developpers documentation. Ignore it if it's not applicable. It is because conflict between DHCP client start it's work start too early - before the network link has been authenticated.

Where this kind of bug shall be reported? Friday, November 23, PM. Monday, November 26, AM. You are true - there are two problems, but they are partially related only. We trying to resolve only one of them here. First - DHCP client start to communicate before The network is unavaiable at all before network card become authenticated, so the DHCP server is unavaiable. Its bug in network stack layering.

This bug is not new on Vista. The XP has the same bug. It's annoyning, but this thread is not dedicated to this particular bug. It's not our case. We have central network management. The computer are allowed to use the address that has been dedicated to it only.

No computer is allowed to use statically configured address nor random address. Even if we resolve the first problem, the second will not disapear - there are uncounted reason for DHCP fail - misconfigured firewall that blocked required communication, virus, broken files or a misconfiguration that case the DHCP client cease to run.

In all cases - the computer administrator mus resolve the primary problem. In the meantime, it is not allowed to use a random address that are not driven by centralised management. Wednesday, November 28, AM. But it's not answer to question how to disable such function on the environmemt where it's unnecesarry and break the security policies nor why DHCP handshaking start before network card become fully operational e.

It's no time related problem - if a client has the problem, it has the problem all the times. Even we will find the solution for the first problem, the main problem is the second.

So question remain - how to disable APIPA on network with central IP management where no other methods are allowed to assign addresses to computer. It's important security question. The network monitoring will detect any unauthized use of IP address and immediatelly block the station access as it classify it as intruder or dangerously misconfigured. Friday, January 11, PM. I've tried setting the AutoIpConfigurationAddress from the to 0.

The question here isn't about whether APIPA should ethically be on or off, the user should have the choice. Sadly that doesn't seem to be the case. Seems to me disabling it is impossible, another unintended "quirk" of Vista. Roll on SP2. Thursday, February 7, AM. I've had exact the same problems. After deinstalling the whole package, the DHCP requests had the source address of 0. This is tricky because in most cases anti-spoofing acls on routers will kill your dhcp request before it will be handled by the dhcp-relay agent.

Tuesday, February 12, PM. I experienced the same issue with a sonicwall tzw, assuming the APIPA assigned address was a spoof attempt. I can't take credit for this fix, but it works.

Click the Start button. Right click Command Prompt and click Run as administrator. Type regedit. Rename the new entry ArpRetryCount leave it set to 0 by default. Restart the computer.

The XP laptops have always connected fine. There were no hardware changes that could have suddenly caused this. When I then explicitly set a static IP address, things start to work.

Another strange thing, is that when my Vista desktop was attempting to connect, I looked at the "DHCP clients table" on my router, and it shows an IP address entry for my desktop, but on the desktop I only see that packets are sent, but never received and the operation eventually fails. I then deleted the DHCP mapping for my desktop after setting it to a static IP and that did not affect my desktop's connectivity over the static IP, as expected.

First advice and teh most noobish one : Have you tried another cable? Does your setup worked before moving to Vista? A friend of mine is having the same problem, but I believe his machine is XP. I would be interested in a solution as well. That may fix your problem. If it were the cable, I'd assume that static IP would also not work, but it does. And yes, it used to work with XP, and even for a while with Vista.

I don't seem to recall what changes happened that caused this to start happening suddenly I tried this and it didn't work : I also updated my nForce drivers from nvidia's website to no avail