[ExchangeList] Re: Change private IP on a cluster- In DNS, multiple computers can be named with the same name

  • From: "Jim Harrison" <Jim@xxxxxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 7 Jun 2006 06:17:22 -0700

http://www.msexchange.org
-------------------------------------------------------

Actually, "..only 5 or 6 people.." is untrue.
Every CSS engineer has the tools available to them to write KBs.
Additionally, every product team member has access to these as well and
all of them are strongly encouraged to make their knowledge public
through KBs, whitepapers, TechNet, etc., etc.

It's the same argument.
Name collisions cannot occur if:
1. WINS doesn't exist or is built properly (replication, etc.)
2. DNS structure is built properly

BTW; I'm "from Microsoft"...

-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jose Medeiros
Sent: Wednesday, June 07, 2006 5:28 AM
To: exchangelist@xxxxxxxxxxxxx; ActiveDir@xxxxxxxxxxxxxxxxxx
Cc: Medeiros, Jose; douggg@xxxxxxxxxxx; president@xxxxxxxx
Subject: [ExchangeList] Re: Change private IP on a cluster- In DNS,
multiple computers can be named with the same name

http://www.msexchange.org
-------------------------------------------------------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" <Jim@xxxxxxxxxxxx>
To: <exchangelist@xxxxxxxxxxxxx>
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: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jose Medeiros
> Sent: Monday, June 05, 2006 10:13 PM
> To: exchangelist@xxxxxxxxxxxxx; ActiveDir@xxxxxxxxxxxxxxxxxx
> 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" <Jim@xxxxxxxxxxxx>
> To: <exchangelist@xxxxxxxxxxxxx>; <ActiveDir@xxxxxxxxxxxxxxxxxx>
> 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: exchangelist-bounce@xxxxxxxxxxxxx
>> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jose Medeiros
>> Sent: Monday, June 05, 2006 9:56 PM
>> To: ActiveDir@xxxxxxxxxxxxxxxxxx; exchangelist@xxxxxxxxxxxxx
>> 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" <Jim@xxxxxxxxxxxx>
>> To: <exchangelist@xxxxxxxxxxxxx>; <ActiveDir@xxxxxxxxxxxxxxxxxx>
>> Cc: <mike.newell@xxxxxxxxxxxx>
>> 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: exchangelist-bounce@xxxxxxxxxxxxx
>>> [mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Jose
Medeiros
>>> Sent: Sunday, June 04, 2006 10:29 PM
>>> To: ActiveDir@xxxxxxxxxxxxxxxxxx; exchangelist@xxxxxxxxxxxxx
>>> Cc: mike.newell@xxxxxxxxxxxx
>>> 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@xxxxxxxxxxxxxxxxxx ; exchangelist@xxxxxxxxxxxxx
>>> Cc: mike.newell@xxxxxxxxxxxx
>>> 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" <mike.newell@xxxxxxxxxxxx>
>>> To: <ActiveDir@xxxxxxxxxxxxxxxxxx>
>>> 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: ActiveDir-owner@xxxxxxxxxxxxxxxxxx on behalf of Mike Newell
>>> Sent: Sun 6/4/2006 11:40 AM
>>> To: ActiveDir@xxxxxxxxxxxxxxxxxx
>>> 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 Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 


All mail to and from this domain is GFI-scanned.

-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials: 
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: