This really isn't a problem. Don't have AD on servers with lots of IP
addresses. MS recommends AD on separate machines in large enterprises anyway
and I agree with that. So this seems to be a non-issue unless there is a
different problem.
- Steve Pierce
-----Original Message-----
From: Mike Amburn [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 05, 2000 3:26 PM
To: Cf-Talk
Subject: FW: WINDOWS 2000 SERVER LIMITED TO 51 IP ADDRESSES
FYI
-----Original Message-----
Sent: Wednesday, April 05, 2000 3:15 PM
Subject: FYI* WINDOWS 2000 SERVER LIMITED TO 51 IP ADDRESSES
* WINDOWS 2000 SERVER LIMITED TO 51 IP ADDRESSES
A bug in Windows 2000 (Win2K) prevents it from using more than 51 IP
addresses, a major flaw for anyone hoping to use the new OS to host
multiple Web sites. A variety of independent labs eventually confirmed
the bug, which Microsoft originally ignored. As of today, Microsoft has
confirmed it. The bug affects Win2K server-class machines that have
been configured as domain controllers: Once the 52nd IP address is
added, all domain-related activities quit operating properly until the
IP is removed--and the machine is incapable of authenticating users or
administering the network.
Although only a relatively small number of machines will need to
provide Active Directory (AD)-based DNS services and more than 51 IP
addresses simultaneously (Microsoft recommends that large-scale
production Web servers not host AD as well), this Win2K limitation will
likely cause some of the company's largest customers serious problems.
And Web servers aren't the only reason one would need to allocate such
a large number of IP addresses from a single Win2K machine: BugNet,
which first verified the bug after Microsoft ignored it, says that mail
servers and Application Service Providers (ASPs) often need this
feature.
"Microsoft would not likely produce a hotfix for this, given that
none of our customers have reported the issue," a Microsoft
spokesperson told BugNet. "If a customer does report this, however, we
will take it very seriously." Despite the comment, expect a hotfix in
the coming days. The fix will also be included in Service Pack 1 (SP1)
for Win2K.
I'll be interviewing one of the people who discovered this bug this
week so stay tuned. In the meantime, see Microsoft's belated response.
http://support.microsoft.com/support/kb/articles/q258/8/11.asp
----------------------------------------------------------------------------
--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
