Thursday, June 01, 2000, 10:19:14 AM, Steve Lamb wrote:
> Windows needing to reboot to reset its network configuration when it
> is entered manually.
a) I agree, rebooting just to change a network configuration is lame.
Thankfully, I do believe this is largely resolved in Win2k (but don't
quote me on that).
> Makes it hard to maintain access lists when people's IPs change
> each time they reboot.
b) DHCP, under normal circumstances, will generally not assign a new
IP address at every reboot, assuming you don't pick up and move to
another subnet or wait until after the lease expiration. DHCP clients
automatically try to renew their leases with the same IP address.
Besides, maintaining an access list based solely on IP addresses is
generally considered insecure, since IP addresses can be spoofed
trivially.
Finally, DHCP, as you no doubt know, can, and usually does, provide a
lot more IP information than just an address. Yes, there are other
ways to provide the same information. No, those ways are generally not
as good, efficient, or reliable as DHCP.
---
Tod | [EMAIL PROTECTED]
Stamping out tech snobbery since 1988
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
