Re: Hacked? IP address changes in Event Log?
From: Phillip Windell (_at_.)
Date: 08/04/04
- Next message: pittspeed: "Re: Logon script UN password prompt on LPT1"
- Previous message: Doug Sherman [MVP]: "Re: Slow Win98 Client Win Explorer"
- In reply to: Scott Harding - MS MVP: "Re: Hacked? IP address changes in Event Log?"
- Next in thread: Roland Hall: "Re: Hacked? IP address changes in Event Log?"
- Reply: Roland Hall: "Re: Hacked? IP address changes in Event Log?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 13:03:11 -0500
"Scott Harding - MS MVP" <scrockel@**NO_SPAM**hotmail.com> wrote in message
news:OHSx59jeEHA.3792@TK2MSFTNGP09.phx.gbl...
> The 169 address space is reserver for AIPA. Automatic Ip addressing. If a
> machine is set to DHCP but cannot locate a DHCP server it will assign
itself
> a 169. something address.
Ok. I didn't see the post where he indicated that address till after. But in
the first post it was called a secondary address. Maybe the terminology was
just used loosely, but an actual real "secondary address" cannot come from
DHCP (or even attempt to, then fail and get a 169.* address) to my
knowledge. Only a primary address can come from DHCP. Isn't that the case?
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: pittspeed: "Re: Logon script UN password prompt on LPT1"
- Previous message: Doug Sherman [MVP]: "Re: Slow Win98 Client Win Explorer"
- In reply to: Scott Harding - MS MVP: "Re: Hacked? IP address changes in Event Log?"
- Next in thread: Roland Hall: "Re: Hacked? IP address changes in Event Log?"
- Reply: Roland Hall: "Re: Hacked? IP address changes in Event Log?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|