ZAP reports incoming from 169.254.***.***. Reserved range, what gives?

Here is maybe a hint. "Automatic Private IP Addressing" uses the address range 169.254.0.0 through 169.254.255.255. Windows assigns an address from this range if the box is set up for dhcp but can not find a dhcp server. Which is better than getting a BSOD, I guess.

Look around your local net for other windows boxes requiring but not finding a dhcp server. If you find none, your dsl/cable provider may not be blocking 168.254.xxx.xxx addresses (bad of them) and you may be getting signals from other nearby PC's crying out in vain for a dhcp server.

Why should it BSOD?

- If it doesn't need anything from a server in order to boot, then all it would have to do is leave the NIC without an IP address. Windows PCs are (generally speaking) able to run stand-alone without difficulty, with or without a NIC.

- If it does need something from a server in order to boot (e.g., "diskless boot" then it isn't going to be able to talk to that server while it has the 169.254.0.0 IP address, not unless that server has deliberately added a 169.254.0.0 IP to one if its interfaces (not particularily likely.)

In neither case is a BSOD made noticably less likely by using a

169.254.0.0 does have a purpose, but that purpose is mostly related to being able to drop a bunch of PCs onto a LAN and have them talk to each other without any prior setup (e.g., the home user or organization doesn't -have- a systems administrator who knows how to set IP addresses.) A situation like that is likely to be virus- encrusted in short order, but it's an obvious extension of the notion that "Computers ought to be foolproof, obvious to use, and need no administration, just the way you don't need to 'administer' your TV or telephone."