On Tue, Oct 17, 2000 at 08:34 +0200, Eduardo Carriles wrote:
Hi friends all:
Tried to find some $MS info on the issue, and guess what? I found it.
[ ... ]
You can disable automatic private IP addressing in one of two ways:
You can manually configure TCP/IP by following the procedure outlined in the section Manually Configuring IP Addresses later in this chapter. However, this method also disables DHCP.
You can disable automatic private IP addressing (but not DHCP) by editing the registry.
You disable automatic private IP addressing but not DHCP by adding the IPAutoconfigurationEnabled registry entry with a value of DWORD 0x0 in the following registry location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP
Use the Registry Editor to add this entry, then shut down and restart the computer.
Ah, it's not about turning automatic processes on. It's about turning those automatic things off. It's weird. The MS way ... I don't mind installers setting wrong initial values for the user (that's what I know MS for). But I'm struck by the _absence_ of a switch meaning "try to do for me what I don't want to think about". This leads to computers doing whatever they please "since you didn't tell me to stop my own things and do what you told me to do". That's exactly the wrong model of a computer ... Next time you put a CD into the slot it will destroy all your data and install a new system because you didn't tell it otherwise. I'm afraid of this vision.
____________________ As of HOW TO FIND _windozes_ LURKING on the net FOR some IP to use: [Must re/enable DHCP Messages and reboot _windoze_ machines to see pop-ups informing]
AS YOU READ ABOVE:
Unless you have turned DHCP messages off, DHCP messages inform you when you change between DHCP addressing and automatic private IP addressing. If you do accidentally turn DHCP messages off, you can turn them back on by changing the value of the registry entry PopupFlag from 00 to 01 in the following registry location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\DHCP
You must reboot for the change to take effect.
Why do I miss the info here on "how to find DoSes lurking on the net with some IP"? Or is it just that I'm unable to read? The problem I have with this is: When I want to know which machine is misconfigured in the "locallink" way, I have to be able to contact it (listing the shares or locally registered named helps here in recognizing). But to connect I need an IP from the locallink range on the machine I want to lookup from. So one either has to participate in this "lazy / dumb man's networking" or one has to dedicate an alias (and a route) to this mechanism. Hmmm ...
____________________ Hey, be aware that Regedit is sometimes very nasty. ____________________
Not only regedit. But I appreciate your posting and the effort leading to it. Thank you very much! virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you.