I'm pretty sure Jim is familiar with those "5-6" people creating the content on a personal level ;)
 
FWIW, Exchange 2k is dependent on shortname resolution (AKA NetBIOS/WINS name res or in this case, good DNS name resolution practices) for some of it's components.  Which ones?  Setup was one notable. It checks. But after that, you *could* use Exchange 2K without WINS. There are other components that are coded to use shortname resolution, but WINS is not a requirement necessarily. Can be tricky if you don't have it though.
 
If you think that good DNS resolution is going to solve the issue, however, that's not always the case so I'd argue that the kb err's on the side of caution.  In the case detailed below, where you have multiple serverA's shortname doesn't work as expected.  That could be a real problem for you. In that case WINS was/is a better choice IMHO. Not that I want to keep using WINS mind you.
 
Al
 

 
On 6/7/06, Jose Medeiros <[EMAIL PROTECTED]> wrote:
Hi Jim,

I agree with you and I do find technet article's that are unclear and are
missing steps, however much of it is,  that Microsoft has only 5 or 6 people
creating that content and probably do not always test  ( Or have very
limited testing ) what they are listing.

However,  this section below makes a lot a sense. If you have a very flat
domain, you probably would not have an issue. But if you have a large World
Wide enterprise such as Microsoft, Cisco, Intel, Ford Motor Comany, GM, etc,
with a very complex network and many DNS sub domains and childs, this  may
be an issue.

( Please read this sections )
" Name collisions cannot occur when you use WINS. In a WINS environment,
only one computer can be named SERVERA. In DNS, multiple computers can be
named SERVERA. For example, one computer may be named
SERVERA.EUROPE.DOMAIN.COM and another computer may be named
SERVERA.AMERICA.DOMAIN.COM. If a user who is located in the AMERICA domain
types \\SERVERA, they connect to SERVERA in the AMERICA domain. If a user
who is located in the AMERICA domain wants to connect to SERVERA in the
EUROPE domain, that user must specify the fully qualified domain name (FQDN)
SERVERA.EUROPE.DOMAIN.COM. Some programs may only permit entries with a
maximum of 15 characters for NetBIOS names. These programs may still work if
a mechanism exists to avoid duplicate host names and if the DNS suffix list
of domains is provided to all clients."

Any one from Microsoft care to comment on this?

Jose :-)
--------------------------------------------------------------------------------------------------
----- Original Message -----
From: "Jim Harrison" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 06, 2006 5:56 AM
Subject: [ExchangeList] Re: Change private IP on a cluster- Reply-Reply


> http://www.msexchange.org
> -------------------------------------------------------
>
> Some articles are written with good intent, but bad information.
> I spend about 10% of my time getting those corrected.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Jose Medeiros
> Sent: Monday, June 05, 2006 10:13 PM
> To: [EMAIL PROTECTED]; ActiveDir@mail.activedir.org
> Subject: [ExchangeList] Change private IP on a cluster- Reply-Reply
>
> http://www.msexchange.org
> -------------------------------------------------------Hi Jim,
>
> Are you sure that holds true on a clustered Exchange 2000 server?  I
> recall
> from my Microsoft 2000 server clustering class at Quickstart
> Intelligence
> back in 2001,
> http://www.quickstart.com/courses/course.asp?cat=Windows&type=88&course=
> 2087
> that the instructor stated that both Exchange 2000 and SQL 2000
> clustered
> was dependent on NETBIOS. Was this changed in a later service pack? Why
> would Microsoft create this article dated:Article ID : 837391
>      Last Review : March 30, 2006
>      Revision : 4.0
>
>
> Jose :-)
>
> ------------------------------------------------------------------------
> -----
> ----- Original Message -----
> From: "Jim Harrison" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED] >; <ActiveDir@mail.activedir.org>
> Sent: Monday, June 05, 2006 10:01 PM
> Subject: [ExchangeList] Re: Change private IP on a cluster- Reply
>
>
>> http://www.msexchange.org
>> -------------------------------------------------------Neither one had
>
>> this dependency.
>> Exch 2000 runs only on Win2K and Win2K3.
>> Both of these OS prefer DNS to WINS for name resolution and if your
>> network structure provides good DNS services, WINS is a non-issue for
>> Exchange 2K+.
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]] On Behalf Of Jose Medeiros
>> Sent: Monday, June 05, 2006 9:56 PM
>> To: ActiveDir@mail.activedir.org; [EMAIL PROTECTED]
>> Subject: [ExchangeList] Change private IP on a cluster- Reply
>>
>> http://www.msexchange.org
>> -------------------------------------------------------Hi Jim,
>>
>> Looks like your post never made it to the Active Dir list. If I recall
>> Exchange 2000 clustered still had dependencies on Wins, and I was told
>> at a
>> Microsoft Technet event that Exchange 2003 clustered no longer had
> this
>> requirement, until I saw the  Microsoft article that I pointed out
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;837391 .
>>
>> Jose
>>
>>
>> ----- Original Message -----
>> From: "Jim Harrison" <[EMAIL PROTECTED]>
>> To: < [EMAIL PROTECTED]>; <ActiveDir@mail.activedir.org>
>> Cc: < [EMAIL PROTECTED]>
>> Sent: Monday, June 05, 2006 6:17 AM
>> Subject: [ExchangeList] Re: Change private IP on a cluster
>>
>>
>>> http://www.msexchange.org
>>> -------------------------------------------------------837391 is
>> getting
>>> changed.
>>> I'm putting in the technical update today.
>>>
>>> It's wrong
>>> Wrong, wrong, wrong.
>>> Wrgonggitty-wrong-wrong Wrong!
>>>
>>> WINS is *NOT* required for Exch functionality, but proper name
>>> resolution support in the network *IS* required.  If you've built
> your
>>> network, name services & clients properly, using a "simple" name gets
>>> you the same response as using FQDN in a "ping" command.
>>>
>>> -----Original Message-----
>>> From: [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] ] On Behalf Of Jose Medeiros
>>> Sent: Sunday, June 04, 2006 10:29 PM
>>> To: ActiveDir@mail.activedir.org; [EMAIL PROTECTED]
>>> Cc: [EMAIL PROTECTED]
>>> Subject: [ExchangeList] Change private IP on a cluster
>>>
>>> http://www.msexchange.org
>>> -------------------------------------------------------Hi Mike,
>>>
>>> Looks like you are going to also have dependencies on Wins and with
>> the
>>> MSDTC:
>>>
>>> Exchange Server 2003 and Exchange 2000 Server require NetBIOS name
>>> resolution for full functionality
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;837391
>>>
>>> How to configure Microsoft Distributed Transaction Coordinator on a
>>> Windows
>>> Server 2003 cluster
>>> http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
>>>
>>> Regards,
>>>
>>> Jose :-)
>>>
>>> --------------------------------------------------------------------
>>>
>>> ----- Original Message -----
>>> From: Jose Medeiros
>>> To: ActiveDir@mail.activedir.org ; [EMAIL PROTECTED]
>>> Cc: [EMAIL PROTECTED]
>>> Sent: Sunday, June 04, 2006 9:53 PM
>>> Subject: Re: [ActiveDir] Change private IP on a cluster
>>>
>>>
>>> Hi Mike,
>>>
>>> I've only had to change a SQL 2000 Active / Active Cluster IP and it
>>> involves some additional steps for SQL Virtual Names. It's been over
> 5
>>> years
>>> since I built an Exchange 2000 cluster, but I do not recall if
>> Exchange
>>> has
>>> any dependencies (I would probably post this to the Exchange list and
>> I
>>> am
>>> cc'ing them as well)
>>>
>>> Take a look at :
>>> Exchange Server 2003 Cluster Configuration Checklist
>>>
>>
> http://www.microsoft.com/technet/itsolutions/msit/operations/exchcluster
>>> cklist.mspx?pf=true
>>>
>>> Changing the IP address of network adapters in cluster server
>>> http://support.microsoft.com/kb/230356/EN-US/
>>>
>>> Or in PDF format at:
>>>
>>
> http://www.maned.com/support/knowledge_base/Roundhouse/Recommended_Readi
>>> ng/Q230356.pdf
>>>
>>> Also just in case you ever have to change it on a SQL:
>>>
>>> How to change the network IP addresses of SQL Server virtual servers
>>> http://support.microsoft.com/kb/244980/en-us
>>>
>>> Hope this helps,
>>>
>>> Sincerely,
>>> Jose Medeiros
>>> MCP+I, MCSE, NT4 MCT
>>> 408-765-0437 Direct
>>> 408-449-6621 Cell
>>>
>>
> ------------------------------------------------------------------------
>>> --------------------
>>> ----- Original Message -----
>>> From: "Mike Newell" <[EMAIL PROTECTED]>
>>> To: < ActiveDir@mail.activedir.org>
>>> Sent: Sunday, June 04, 2006 12:53 PM
>>> Subject: [ActiveDir] Change private IP on a cluster
>>>
>>>
>>> Doh! Didn't mean to let this go without the OT:. Sorry.
>>>
>>> ________________________________
>>>
>>> From: [EMAIL PROTECTED] on behalf of Mike Newell
>>> Sent: Sun 6/4/2006 11:40 AM
>>> To: ActiveDir@mail.activedir.org
>>> Subject: [ActiveDir] Change private IP on a cluster
>>>
>>>
>>> Hey,
>>> I have an Exchange 2003 active/passive cluster on Windows 2003 and I
>>> need
>>> to change the private ip on both nodes. I realize that while I'm
>>> changing the IP the nodes will not talk to each other and likely kick
>>> the passive node off or stop the cluster service for a few minutes on
>>> the passive node.
>>>
>>> Is there anything else I will need to do or look out for? I don't
>>> *think* this is a big deal but since it's a production cluster, and
>> I've
>>> never had to do this, I thought I would check before I tried it.
>>>
>>> Thanks again.
>>>
>>> Mike.
>>>
>>> -------------------------------------------------------
>>
>

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

Reply via email to