| Author |
Message |
Scott
Guest
|
 Posted:
Fri Jan 14, 2005 3:20 am Post subject:
NT to 2003/AD migration |
|
|
I have migrated my NT 4.0 PDC to 2003 and AD. The upgrade
was successful, and the clients (XPPro) can login into the
domain. The problems I am having are:
--The domain name on a couple of the existing workstations
was automatically changed to the DNS name of the domain.
While others still remain named the NETBios name of the
domain. (Looking at the Computer Name Properties Tab)
--I also have created a Default Domain Group Policy item
to direct the clients to my SUS server. Unfortunately,
none of the clients are using the SUS server, and looking
to MS for the Updates.
--The dynamic DNS is not updating for the clients. I
placed the DNS IP Address as the clients primary DNS
server address, and none are dynamically creating resourse
records. The DHCP server is on the BDC, running NT 4.0.
Any help would be appreciated!
I do have a BDC still running NT 4.0, is this why? Or is
there another cause? |
|
| Back to top |
|
 |
Frances [MSFT]
Guest
|
| Posted:
Fri Jan 14, 2005 5:37 pm Post subject:
RE: NT to 2003/AD migration |
|
|
Hello,
According to your description, some of your questions are not directly
related to migration. You had better post them to the related newsgroups
for more accurate information. I will list your questions in sequence and
provide you the information you need.
Q1.The domain name on a couple of the existing workstations was
automatically changed to the DNS name of the domain. While others still
remain named the NETBios name of the domain. (Looking at the Computer Name
Properties Tab)
A: What are the OS of all the clients? Are they all running XPPro?
XP clients are designed to show the DNS names, while some other computers
running Windows NT, win 98, will only show the NetBIOS name.
I send a screen shot to you. It indicates the XP client's domain name in
the Computer Name Properties Tab. Do you refer to the name circled in red
line?
In addition, please check the following two settings on the client:
1. My Computer->Properties->Computer name tab->Change button->Click More
button->Check Change primary DNS suffix when domain membership changes
2. TCP/IP properties->Advanced->DNS->Check "Register this connection's
addresses in DNS"
By default, they should be checked.
Q2.I also have created a Default Domain Group Policy item to direct the
clients to my SUS server. Unfortunately, none of the clients are using the
SUS server, and looking to MS for the Updates.
A:Please post the question to microsoft.public.windows2000.windows_update
newsgroup or microsoft.public.windowsupdate newsgroup for more information.
Q3.The dynamic DNS is not updating for the clients. I placed the DNS IP
Address as the clients primary DNS server address, and none are dynamically
creating resourse records. The DHCP server is on the BDC, running NT 4.0.
A: Please post the question to microsoft.public.windows.networking queue
for more accurate suggestions.
Hope it helps. Any updates, let us get in touch!
Best regards,
Frances He
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
|
Scott
Guest
|
| Posted:
Sat Jan 15, 2005 12:57 am Post subject:
RE: NT to 2003/AD migration |
|
|
Frances,
Thanks for you thorough feedback, much appreciated.
I checked the default settings that you described and both
are indeed selected. My DNS servers are configured for the
PDC DNS as the primary DNS address and then the ISP DNS
server as the secondary DNS, on the client (XP PRO).
Could this be causing the problem? This XP client is still
using the NetBios DNS name on the computer name tab. I am,
however, able to ping the FQDN computername.dnsname.com
from the command prompt, I just cannot figure out as to
why the Domain name hasn't changed to the DNS domain name.
Any other sugestions?
| Quote: | -----Original Message-----
Hello,
According to your description, some of your questions are
not directly
related to migration. You had better post them to the
related newsgroups
for more accurate information. I will list your questions
in sequence and
provide you the information you need.
Q1.The domain name on a couple of the existing
workstations was
automatically changed to the DNS name of the domain.
While others still
remain named the NETBios name of the domain. (Looking at
the Computer Name
Properties Tab)
A: What are the OS of all the clients? Are they all
running XPPro?
XP clients are designed to show the DNS names, while some
other computers
running Windows NT, win 98, will only show the NetBIOS
name.
I send a screen shot to you. It indicates the XP client's
domain name in
the Computer Name Properties Tab. Do you refer to the
name circled in red
line?
In addition, please check the following two settings on
the client:
1. My Computer->Properties->Computer name tab->Change
button->Click More
button->Check Change primary DNS suffix when domain
membership changes
2. TCP/IP properties->Advanced->DNS->Check "Register this
connection's
addresses in DNS"
By default, they should be checked.
Q2.I also have created a Default Domain Group Policy item
to direct the
clients to my SUS server. Unfortunately, none of the
clients are using the
SUS server, and looking to MS for the Updates.
A:Please post the question to
microsoft.public.windows2000.windows_update
newsgroup or microsoft.public.windowsupdate newsgroup for
more information.
Q3.The dynamic DNS is not updating for the clients. I
placed the DNS IP
Address as the clients primary DNS server address, and
none are dynamically
creating resourse records. The DHCP server is on the BDC,
running NT 4.0.
A: Please post the question to
microsoft.public.windows.networking queue
for more accurate suggestions.
Hope it helps. Any updates, let us get in touch!
Best regards,
Frances He
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.
.
|
|
|
| Back to top |
|
|
Scott
Guest
|
| Posted:
Mon Jan 17, 2005 6:14 pm Post subject:
RE: NT to 2003/AD migration |
|
|
****Please see replied messages below****
Scott
"Frances [MSFT]" wrote:
| Quote: | Hello Scott,
I believe the DNS configuration is correct. However, I would like to
confirm some detailed information.
Q1. What is the content in the Primary DNS suffix of this computer located
in My Computer->Properties->Computer name tab->Change button->Click More
button->DNS Suffix and NetBIOS Computer name tab? Is it the domain name or
the NetBIOS name?
The DNS domain name is displayed in the Primary DNS suffix textbox, and the |
NetBIOS name is in the correct text box as well.
| Quote: | Q2. How many DHCP servers are there in your network? Is the DHCP server in
BDC the only server? How do you configure the DHCP server?
One DHCP server, which was NT4.0 (BDC) and was in-place upgraded to W2K3 |
over the weekend. It now cannot join the AD or be installed as a member
server, it fails to locate the domain controller for the AD domain. Even
though the clients can.
| Quote: | Q3. How does the XP client get the IP address? Does it automatically get
one from the DHCP server or does the IP assigned in advance?
All Clients are assigned addresses dynamically. |
| Quote: | Q4. Have you added the NT4emulator registry key on win2k3 server before you
upgrade from NT?
Yes, the first NT4.0 (PDC) upgraded to W2K3 the emulator key was added. |
| Quote: | Generally speaking, this problem can occur during the upgrade process if
the check box of "change primary DNS suffix when domain membership changes"
are not checked for certain causes.
Please use the following steps to check the issue:
Step 1. Manually change the primary suffix
=====================================
Please manually change the content in the Primary DNS suffix of this
computer located in My Computer->Properties->Computer name tab->Change
button->Click More button-> DNS Suffix and NetBIOS Computer name tab.
The suffix already contains the DNS domain name. |
| Quote: | Step 2: Use ipconfig
====================
In the command line, type: ipconfig /registerdns
Did this |
| Quote: | This command forces the client to manually re-register DNS records to the
DNS ser ver.
Step 3: Use nslookup to check the result
==========================================
In the command line, type: nslookup 192.168.120.2
Note: 192.168.120.2 is the IP address of the XP client.
You can also try with the command: nslookup computer1
Note: computer1 is the computer name of the XP client.
These two commands will return the DNS server name and IP address. Please
check to make sure the configuration is correct.
When I perform an NSLookup <clientname> the address of the client is |
resolved, but the DNS Server name is unknown.
| Quote: | If the problem persists, please send the screen shot of the Computer name
changes and DNS Suffix and NetBIOS Computer name tab to
v-franhe@microsoft.com for research. I have sent the screen shots as the
attachments for your reference.
Any update, let us get in touch!
Best regards,
Frances He
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights |
|
|
| Back to top |
|
|
Rebecca Chen [MSFT]
Guest
|
| Posted:
Tue Jan 18, 2005 7:45 pm Post subject:
RE: NT to 2003/AD migration |
|
|
Hi Scott,
It seems the primary DNS suffix is still the NetBIOS name. My opinion of
this issue is that the problematic clients have not correctly contact the
DC since it cannot resolve the DC FQDN by using the NSlookup.
What is the result if you disjoin the client from the domain and rejoin it?
Please NOTE: Point the DNS server to the new win2k3 server and when you
rejoin the client the domain, please key in the FQDN of the domain like
"domain.com", can the client sucessfully join the domain?
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in