Quote:
|
Originally Posted by alanf617
Now THAT looks brilliant!
BUT there are 7 subfolders, all with names beginning with {and numbers or letters. Which is the correct one?
|
LOL, I don't know!
My "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi c es\Tcpip\Parameters\Interfaces\" section has 6 interface folders.
One of the six folders has a great deal more info in it than the other five, including the IP address, DNS address, subnet mask etc. of the adapter. The other five have less info in them, less entries, etc.
The only thing I can suggest (unless someone can explain an easy way to ID them), is to look through each of your seven folders, & find the one which has the correct info for the device in question.
Quote:
|
I'll try that before I try the micro$oft solution.
|
Hopefully it will help
Quote:
|
And no, no firewall ( I think there is something of a firewall inside the router, does NAT sound right?).... I did have mcafee firewall but it seems unnecessary and kept giving me error messages saying that it had failed to start.
|
Yeah, the router will have its own built-in NAT (network address translation) firewall.
Quote:
|
Manual addresses seemed a bit more stable, but still occasionally got corrupted to the 169.x.x.x address
|
Changing the registry as above should stop the IP changing to an APIPA 169.x.x.x address.
It may still be worth a try switching to manual addresses too.
And there's still the winsock workaround to try out.
Of course, it still would be nice to find out exactly why you seem to be losing the DHCP lease in the first place!
