RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conv
- From: "pbrill1" <pbrill1@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 2 Sep 2005 15:46:01 -0700
Thank you for the information, Vincent.
Based on your info, I noticed that our WINS server still references
Our DHCP Server still references the Server Option
46 WINS/NBT Node Type as 0x8 - H-node, which a microsoft reference tells me
means "h-node (0x8): Query WINS server first and then broadcast'
(We never changed this from the NT days, and I'm not sure how to check if we
need this, since we are now an environment with W2K3/W2K Servers, and XP/2000
clients...but possibly have some legacy network (printer/etc) devices.
2 Follow up questions:
1) WINS naming:
In WINS, the old domain name references
OURCOMPANY_NT [1bh] Domain Master Browser 10.0.0.7 ACTIVE
(which does reference our primary DC)
and
OURCOMPANY_NT [1Ch] Domain Controller 10.0.0.7 ACTIVE
which (in the Properties, references a few IP numbers of old servers
that have been removed.
Q: 1) Should I delete/tombstone these, given my DHCP setup, or will this
keep other computers from referencing the DC?
2) if Q1 is yes, should I rename, rather than delete, the WINS
record? (I'll admit my lack of understanding about what will happen to
connectivity if I delete the DC and DMB records from WINS).
3) Are there new DHCP settings that I should look to, now - given our
client/server situation? (Incidentally, we are a fairly small shop. approx
10 servers (2 of them terminal servers that ppc2000 handhelds dial into), 80
desktop clients)
I'd appreciate assistance on this...to resolve the last migration leftovers
that I've been curious to fix.
Thanks,
--
pbrill1
"Vincent Xu [MSFT]" wrote:
> Hi,
>
> Since you upgrade from NT4 to 2003, the domain name should keep the same.
> How it can be the old domain name remains?
>
> If you performed a migration from NT4 to 2003, the NT4 domain name may
> stored in Wins record. We may need to clean Wins record. Please refer to
>
> <http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Serv
> erHelp/8fd40dad-8d31-491d-a19d-5568cecf9b60.mspx>
>
> Best regards,
>
> Vincent Xu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
> This and other support options are available here:
> BCPS:
> https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
> Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
>
> If you are outside the United States, please visit our International
> Support page: http://support.microsoft.com/common/international.aspx.
>
> Newsgroup Web Interface Upgrade
>
> Please complete a one-time registration process on your first visit to the
> Partner Portal beginning July 11, 2005 at 9 A.M. PST by entering the secure
> code mspp2005 when prompted. This secure code will be valid for 6 months
> after which you will need to update your registration by entering the new
> secure code. We will post announcements in the newsgroups prior to
> expiration. Once you have entered the secure code mspp2005 , you will be
> able to update your profile and access the the partner newsgroups. Please
> update your Favorites link to the newsgroups web page, your current link
> will redirect until November 1, 2005.
>
> Please post any comment, questions or concerns to the
> microsoft.private.directaccess.partnerfeedback newsgroup. For more
> information, please go to:
> https://partner.microsoft.com/global/technicalsupport/registeredsupport/4001
> 4662
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --------------------
> >>Thread-Topic: Pre-Win 2000 logon remains in "Log onto" field after W2K3
> conversi
> >>thread-index: AcWuWibgPncXtqdEQ4i8WHbEwwVjFw==
> >>X-WBNR-Posting-Host: 64.109.69.90
> >>From: "=?Utf-8?B?cGJyaWxsMQ==?=" <pbrill1@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>Subject: Pre-Win 2000 logon remains in "Log onto" field after W2K3
> conversi
> >>Date: Wed, 31 Aug 2005 11:31:07 -0700
> >>Lines: 19
> >>Message-ID: <6CF6521D-2376-48DF-81D7-B668FF144266@xxxxxxxxxxxxx>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="Utf-8"
> >>Content-Transfer-Encoding: 7bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>Content-Class: urn:content-classes:message
> >>Importance: normal
> >>Priority: normal
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>Newsgroups: microsoft.public.windows.server.migration
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.migration:11815
> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>
> >>We upgraded from NT4 some time ago - to DC's that are all W2K3.
> >>
> >>The Forest and Domain are also set at W2K3 native.
> >>
> >>Still, I see the "pre-Windows 2000" log in domain whenever a client or
> >>server logs in. At this point, we only have W2K3 and W2K servers, and
> W2K/XP
> >>clients.
> >>
> >>Is there a setting that needs to switch over to get rid of the Pre W2K
> login
> >>domain (our old NT4 domain name)?
> >>
> >>Are there any consequences with respect to DNS and WINS (or DHCP, for
> that
> >>matter) to consider?
> >>
> >>...from one that still is unsure if I've completely left behind the
> ghosts
> >>of NT4....
> >>
> >>--
> >>pbrill1
> >>
>
>
.
- Follow-Ups:
- RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conv
- From: Vincent Xu [MSFT]
- RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conv
- References:
- Pre-Win 2000 logon remains in "Log onto" field after W2K3 conversi
- From: pbrill1
- RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conversi
- From: Vincent Xu [MSFT]
- Pre-Win 2000 logon remains in "Log onto" field after W2K3 conversi
- Prev by Date: Re: FSmigrate crashes, disables admin acct... reliable?
- Next by Date: Migrating Routing and Remote Access
- Previous by thread: RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conversi
- Next by thread: RE: Pre-Win 2000 logon remains in "Log onto" field after W2K3 conv
- Index(es):
Relevant Pages
|