Windows Server

Tom · Guest

I am looking for some help with a DS site name issue I am having..

I've hit rock bottom so I figure I post my semi-technical question
here...

I have a exchange 5.5 box running in a windows 2003 active directory
TEST environment. The TEST AD environment was recently brought up a
week ago. Here are the two servers in question:

1 windows 2000 server running exchange 5.5
1 windows 2003 server running active directory in NT4 Emulator mode.

Both the active directory and exchange server was copied from the
production environment. The exchange 5.5 system works perfectly in the
test environment.

I want to upgrade the exchange server from 5.5 to 2000. Following the
microsoft guidelines, I've ran a few tests such as dcdiag.exe and
netdiag.exe. Fixed whatever problems arised.

Now i run NLTEST.EXE /DSGETSITE from the exchange 5.5 server to verify
that it does return the proper active directory site name and i get the
following error:

Status = 1919 0x77f ERROR_NO_SITENAME

looking on google, I find that http://support.microsoft.com/kb/259427
supposdily addresses this issue.

However it does not work for me. In fact, just for kicks I run
NLTEST.EXE /DSGETSITE on my production environment to see if it works
properly there...and it turns out all the clients and servers return
"Status = 1919 0x77f ERROR_NO_SITENAME"

The only computer in the production domain that returns the proper
information without error is the actual windows 2003 domain controller
in the environment.

Does anyone have any information who's actually done these tests or the
exchange upgrade?

I'm really stumped.... My AD has one site and its been assigned and IP
subnet already.

Bob Qin [MSFT] · Guest

Hi Tom,

Thanks for your posting here.

Is your Exchange 5.5 server a member server?
Does the problem occur on other DC?

Based on my experiences, the problem can occur if the Exchange server and
the schema master must both be pointed to valid internal DNS servers.

Please make sure that the DNS settings on the schema master domain
controller and the member server are pointed to valid internal DNS servers.
If the schema master is the DNS server, make sure that the schema master
uses its own Internet Protocol (IP) address and is the preferred DNS server.

To change the DNS settings:

1. Right-click My Network Places, and then click Properties in the shortcut
menu to open the "Network and Dial-up Connections" dialog box.

2. Right-click Local Area Connection, and then click Properties in the
shortcut menu.

3. Click Internet Protocol (TCP/IP), and then click Properties.

4. Change the preferred internal DNS server.

Wish it helps!

Regards,
Bob Qin
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.

--------------------
From: "Tom" <tsai0610@hotmail.com>
Newsgroups: microsoft.public.windows.server.migration
Subject: exchange 5.5 -> 2000 -> 2003 upgrade SETUP /forestprep
NLTEST /dsgetsite failure
Date: 30 Dec 2004 15:13:51 -0800

I am looking for some help with a DS site name issue I am having..

I've hit rock bottom so I figure I post my semi-technical question
here...

I have a exchange 5.5 box running in a windows 2003 active directory
TEST environment. The TEST AD environment was recently brought up a
week ago. Here are the two servers in question:

1 windows 2000 server running exchange 5.5
1 windows 2003 server running active directory in NT4 Emulator mode.

Both the active directory and exchange server was copied from the
production environment. The exchange 5.5 system works perfectly in the
test environment.

I want to upgrade the exchange server from 5.5 to 2000. Following the
microsoft guidelines, I've ran a few tests such as dcdiag.exe and
netdiag.exe. Fixed whatever problems arised.

Now i run NLTEST.EXE /DSGETSITE from the exchange 5.5 server to verify
that it does return the proper active directory site name and i get
the
following error:

Status = 1919 0x77f ERROR_NO_SITENAME

looking on google, I find that http://support.microsoft.com/kb/259427
supposdily addresses this issue.

However it does not work for me. In fact, just for kicks I run
NLTEST.EXE /DSGETSITE on my production environment to see if it works
properly there...and it turns out all the clients and servers return
"Status = 1919 0x77f ERROR_NO_SITENAME"

The only computer in the production domain that returns the proper
information without error is the actual windows 2003 domain controller
in the environment.

Does anyone have any information who's actually done these tests or
the
exchange upgrade?

I'm really stumped.... My AD has one site and its been assigned and IP
subnet already.

Tom · Guest

Hi Bob,

Let me clarify. I have 2 servers in a test environment:

1 windows 2003 AD server, DC-TEST, running DNS and has all 5 FSMO
pointing to DC-TEST, including being the schema master.
1 windows 2000 member server, running exchange 5.5

1) Both servers are pointing to the internal DNS server only.
2) Both servers have the append paren suffixes of the primary DNS
suffix option
3) the only site defined in AD has an IP subnet assigned to it.
(172.16.2.0/24)
4) the exchange server is part of the 172.16.2.0 subnet

Bob can you think of anything else that would prevent NLTEST /dsgetsite
from working properly? Again, this function does not even work in our
production AD environment, which we upgraded to from a NT4 domain 2
months ago. (NT4EMULATOR is enabled!)
I hope you can reply again with more useful information! Thanks!

Tom · Guest

Hi Bob,

Let me clarify. I have 2 servers in a test environment:

1 windows 2003 AD server, DC-TEST, running DNS and has all 5 FSMO
pointing to DC-TEST, including being the schema master.
1 windows 2000 member server, running exchange 5.5

1) Both servers are pointing to the internal DNS server only.
2) Both servers have the append paren suffixes of the primary DNS
suffix option
3) the only site defined in AD has an IP subnet assigned to it.
(172.16.2.0/24)
4) the exchange server is part of the 172.16.2.0 subnet

Bob can you think of anything else that would prevent NLTEST /dsgetsite
from working properly? Again, this function does not even work in our
production AD environment, which we upgraded to from a NT4 domain 2
months ago. (NT4EMULATOR is enabled!)
I hope you can reply again with more useful information! Thanks!

Tom · Guest

Hi Bob,

Let me clarify. I have 2 servers in a test environment:

1 windows 2003 AD server, running DNS and has all 5 FSMO's, including
being the schema master.
1 windows 2000 member server, running exchange 5.5

1) Both servers are pointing to the internal DNS server only.
2) Both servers have the append paren suffixes of the primary DNS
suffix option
3) the only site defined in AD has an IP subnet assigned to it.
(172.16.2.0/24)
4) the exchange server is part of the 172.16.2.0 subnet

Bob can you think of anything else that would prevent NLTEST /dsgetsite
from working properly? Again, this function does not even work in our
production AD environment, which we upgraded to from a NT4 domain 2
months ago. (NT4EMULATOR is enabled!)
I hope you can reply again with more useful information! Thanks!

Tom · Guest

Hi Bob,

Let me clarify. I have 2 servers in a test environment:

1 windows 2003 AD server, DC-TEST, running DNS and has all 5 FSMO
pointing to DC-TEST, including being the schema master.
1 windows 2000 member server, running exchange 5.5

1) Both servers are pointing to the internal DNS server only.
2) Both servers have the append paren suffixes of the primary DNS
suffix option
3) the only site defined in AD has an IP subnet assigned to it.
(172.16.2.0/24)
4) the exchange server is part of the 172.16.2.0 subnet

Bob can you think of anything else that would prevent NLTEST /dsgetsite
from working properly? Again, this function does not even work in our
production AD environment, which we upgraded to from a NT4 domain 2
months ago. (NT4EMULATOR is enabled!)
I hope you can reply again with more useful information! Thanks!

Bob Qin [MSFT] · Guest

Hi Tom,

Thanks for your update.

Since Exchange 5.5 is a member server. The problem can be related to the
NT4EMULATOR setting.

Please try to add the NeutralizeNT4Emulator registry value under the
following key in the registry on the Exchange 5.5 server.

HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Netlogon/Parameters

Then reboot Exchange server and try again. What is the result?

For more information, please refer to the following document.

How to prevent overloading on the first domain controller during domain
http://support.microsoft.com/?id=298713

Regards,
Bob Qin
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.

--------------------
From: "Tom" <tsai0610@hotmail.com>
Newsgroups: microsoft.public.windows.server.migration
Subject: Re: exchange 5.5 -> 2000 -> 2003 upgrade SETUP /forestprep
NLTEST /dsgetsite failure

Hi Bob,

Let me clarify. I have 2 servers in a test environment:

1 windows 2003 AD server, DC-TEST, running DNS and has all 5 FSMO
pointing to DC-TEST, including being the schema master.
1 windows 2000 member server, running exchange 5.5

1) Both servers are pointing to the internal DNS server only.
2) Both servers have the append paren suffixes of the primary DNS
suffix option
3) the only site defined in AD has an IP subnet assigned to it.
(172.16.2.0/24)
4) the exchange server is part of the 172.16.2.0 subnet

Bob can you think of anything else that would prevent NLTEST
/dsgetsite
from working properly? Again, this function does not even work in
our
production AD environment, which we upgraded to from a NT4 domain 2
months ago. (NT4EMULATOR is enabled!)
I hope you can reply again with more useful information! Thanks!

Tom · Guest

Bob,

Thanks for your help.

I did not even begin to contemplate the fact that nt4emulator would
cause a problem like getting the site information from active
directory. I was waiting until I returned into work on the 3rd and it
worked terrific!

I have a few other minor tasks to clean up, but hopefully nothing too
serious.

Thanks again...

Thomas

Bob Qin [MSFT] · Guest

Hi Tom,

Please feel free to post back if you have any update.

Happy New Year!

Regards,
Bob Qin
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.

--------------------
From: "Tom" <tsai0610@hotmail.com>
Newsgroups: microsoft.public.windows.server.migration
Subject: Re: exchange 5.5 -> 2000 -> 2003 upgrade SETUP /forestprep
NLTEST /dsgetsite failure
Date: 3 Jan 2005 04:24:02 -0800

Bob,

Thanks for your help.

I did not even begin to contemplate the fact that nt4emulator would
cause a problem like getting the site information from active
directory. I was waiting until I returned into work on the 3rd and it
worked terrific!

I have a few other minor tasks to clean up, but hopefully nothing too
serious.

Thanks again...

Thomas

exchange 5.5 -> 2000 -> 2003 upgrade SETUP /forestprep NLTES

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1