Answer the question
In order to leave comments, you need to log in
Windows 7 and DHCP
For a long time I can not understand the cause of the problem with DHCP in the seven.
I have an Asus wl500gp router and it always (!!) gives the computer an ip-address 192.168.1.253, not 1.5 or 1.10, but
1.253 we get again the ill-fated 192.168.1.253 and after 30 seconds the address changes to something like 169.128.1.23.
Help overcome the problem.
Answer the question
In order to leave comments, you need to log in
Before using a d-link, even a new one, it is better to do 30 + 30 + 30 resets - turn on the power, wait a minute until it boots up, hold down the reset, after 30 seconds we pull out the power, after another 30 we insert it back, after another 30 we release the reset.
Treated in this way spontaneous jambs that arose a couple of times with the non-functioning of the internal DNS, it can also help with other issues.
Maybe I did not understand the question, but why in Win7 in the properties of the network card do not put a static ip. Of course, from the range that is set in the LAN settings in the modem (http://192.168.1.1/ usually)
Today they brought me a DIR-320 and I can’t configure it, problems with DHCP, when automatically receiving the address, we again get the ill-fated 192.168.1.253 and after 30 seconds the address changes to something like 169.128.1.23.
Help overcome the problem.
An address like 169.bla-bla-bla means that the DIR-320 does not give your computer an IP via DHCP, or gives it, but your computer does not receive it.
See dir-320 settings. Most likely the problem is in it.
the previous commenter is right. But only the address must be from the range 169.254.0.0/16 - Windows itself takes the address from this range if it cannot get a normal one from the settings / network.
Thus, this is not necessarily a router problem - maybe something is wrong with Windows.
Look at the Windows error log, if there are network errors, take the error code and google it. Perhaps the DHCP service in Windows is not working correctly.
What do you want to achieve? Maybe it's easier to permanently register a specific IP by MAC address?
there was a problem when Vista could not get an address from the Cisco dhcp access point, it was treated by editing the registry, read this article - support.microsoft.com/kb/928233
wired network? this happens because the computer cannot reach the dhcp server at all.
on d-dinka under advanced -> dhcp enable it.
So it's okay. It seems like dnsmasq is used there, it has some kind of distribution algorithm. I assign 192.168.1.123 to the first computer, 192.168.1.107 to the second, and so on. It is pseudo-random, or it just works incorrectly, I don’t know the reasons, probably something like a kernel without rtc, and this pseudo-random takes time for seed.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question