Changing Server IP Address

I had to retire some subnets due to the sale of our company.
I put the new_ip as the preferred dns and added the old_ip as a second ip
under the advanced tcpip setting -> ip setting. Rebooted the server.
All of my static ip clients could now see both ip addresses and login with
no problems.

Now to my problems.
It now takes 3-5 minutes to get a desktop at the server console or when
using terminal services when I remove the old_ip address from the nic .
Also, the group policy management editor shows no computer or user polices
defined when I run a report and runs real slow. Last, the event viewer has
directory service errors complaining that the server’s global catalog was
found but could not communicate with it. (The server is still listed as a
global catalog under AD sites and services.)

I know if I put the old_ip back in place everything will start working,
which is not an option. What do I need to do to fix these problems?

Thanks..

 

Sounds like DNS issue. Have you checked the DNS record to make sure no old
computer uses old IP? Or use dcdiag to check any errors.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

 

I would agree but I can't figure out where.

There are no old_ip records in the DNS and no other pc is using old_ip.
I have searched the registry for old_ip and found no references.
Dcdiag states my server resolves from old_ip but can't be reached by ping.
I don't know where dcdiag is resolving the old_ip. The rest of dcdiag looks
good.

I noticed in the group policy mgmnt editor that only the sid's show up under
the security filtering section. If you try to remove the object you get
"network path not found" error, like it is trying to use a GUID from old_ip.

The only error on replication happens when the ForestDnsZones trys to
contact the
server: DsBindWithCred to SERVER1 failed with status 1722 (0x6ba):
The RPC server is unavailable.
Every hour, since the removal of old_ip, I get 3 Global Catalog errors,
1869 (located gc), 1655 (attempt to communicate with gc & was unsuccessful),
1126 (use dc locator to find available gc).
Clearly my SERVER1 has a problem.

Could I have some orphaned GUID's or Cname records? If so where?

Please let me know if you can think of something to resolve this.
Any help is appreciated.

 

You have stale DNS Records. Examine every DNS record that has the old IP#.
Don't just automatically delete them,...you may just have to edit them
depending on what they are.

Remove any WINS entries that still use the old IP#.

Then right-click on the Zone Name and choose Properties.
go to the Name Servers Tab and make sure the contents are correct.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

 

There are no records that have the old_ip address. I don't use WINS. The NS
records reflect the correct new_ip.
I ran another searched on the registry using the hex equivalent of the old_ip
address and came up empty.

Thanks...

 

Dear Customer,

Thanks for posting here.

Changing IP subnet scope is always not a simple project. It may cause many
problem if we inappropriately change IP scope.

Based on your description, It's probably DNS related issue. Because there
might be many servers involved in this problem, I will take GC for example
for your reference.

After changing IP address of GC and DNS, we should adjust the DNS server IP
address to the updated one on the GC server. Then, please use command "net
stop netlogon" and "net start netlogon" to force this GC server to
reregister the corresponding SRV records in DNS server. After repeat these
steps on other the DCs and relevant servers, please see if this issue still
persists.

Here, I also list some common aspects we should consider when changing IP
address in local network:

1. All computers' IP address should be changed correctly.

2. Related services such as DHCP, DNS, WINS, RRAS, ISA (or 3rd party
firewall application), etc., should be adjusted.

3. We should clean DNS cache on all computers and point the computers to
use the correct DNS and WINS servers.

4. All computers should register their new IP addresses with DNS and WINS
servers.

5. For some shortcuts, or other related applications settings that locate
target computers using their IP addresses instead of using FQDN, we must

adjust them manually.

I hope this helps. I appreciate if you would drop me any update.

Thanks.


Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->Thread-Topic: Changing Server IP Address
--->thread-index: Ach4pMKNGnHb/xPIRHasPecaIyb9qA==
--->X-WBNR-Posting-Host: 207.46.19.197
--->From: =?Utf-8?B?QmlnTW8=?= <>
--->References: <>
<>
<>
<>
--->Subject: Re: Changing Server IP Address
--->Date: Tue, 26 Feb 2008 10:24:01 -0800
--->Lines: 106
--->Message-ID: <>
--->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.2992
--->Newsgroups: microsoft.public.windows.server.networking
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:10987
--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->X-Tomcat-NG: microsoft.public.windows.server.networking
--->
--->There are no records that have the old_ip address. I don't use WINS.
The NS
--->records reflect the correct new_ip.
--->I ran another searched on the registry using the hex equivalent of the
old_ip
--->address and came up empty.
--->
--->Thanks...
--->
--->"Phillip Windell" wrote:
--->
--->> You have stale DNS Records. Examine every DNS record that has the
old IP#.
--->> Don't just automatically delete them,...you may just have to edit
them
--->> depending on what they are.
--->>
--->> Remove any WINS entries that still use the old IP#.
--->>
--->> Then right-click on the Zone Name and choose Properties.
--->> go to the Name Servers Tab and make sure the contents are correct.
--->>
--->> --
--->> Phillip Windell
--->> www.wandtv.com
--->>
--->> The views expressed, are my own and not those of my employer, or
Microsoft,
--->> or anyone else associated with me, including my cats.
--->> -----------------------------------------------------
--->>
--->> --->> >I would agree but I can't figure out where.
--->> >
--->> > There are no old_ip records in the DNS and no other pc is using
old_ip.
--->> > I have searched the registry for old_ip and found no references.
--->> > Dcdiag states my server resolves from old_ip but can't be reached
by ping.
--->> > I don't know where dcdiag is resolving the old_ip. The rest of
dcdiag
--->> > looks
--->> > good.
--->> >
--->> > I noticed in the group policy mgmnt editor that only the sid's show
up
--->> > under
--->> > the security filtering section. If you try to remove the object you
get
--->> > "network path not found" error, like it is trying to use a GUID
from
--->> > old_ip.
--->> >
--->> > The only error on replication happens when the ForestDnsZones trys
to
--->> > contact the
--->> > server: DsBindWithCred to SERVER1 failed with status 1722 (0x6ba):
--->> > The RPC server is unavailable.
--->> > Every hour, since the removal of old_ip, I get 3 Global Catalog
errors,
--->> > 1869 (located gc), 1655 (attempt to communicate with gc & was
--->> > unsuccessful),
--->> > 1126 (use dc locator to find available gc).
--->> > Clearly my SERVER1 has a problem.
--->> >
--->> > Could I have some orphaned GUID's or Cname records? If so where?
--->> >
--->> > Please let me know if you can think of something to resolve this.
--->> > Any help is appreciated.
--->> >
--->> > "Robert L. (MS-MVP)" wrote:
--->> >
--->> >> Sounds like DNS issue. Have you checked the DNS record to make
sure no
--->> >> old
--->> >> computer uses old IP? Or use dcdiag to check any errors.
--->> >>
--->> >> --
--->> >> Bob Lin, MS-MVP, MCSE & CNE
--->> >> Networking, Internet, Routing, VPN Troubleshooting on
--->> >> http://www.ChicagoTech.net
--->> >> How to Setup Windows, Network, VPN & Remote Access on
--->> >> http://www.HowToNetworking.com
--->> >>
--->> >>
--->> >> --->> >> >I had to retire some subnets due to the sale of our company.
--->> >> > I put the new_ip as the preferred dns and added the old_ip as a
second
--->> >> > ip
--->> >> > under the advanced tcpip setting -> ip setting. Rebooted the
server.
--->> >> > All of my static ip clients could now see both ip addresses and
login
--->> >> > with
--->> >> > no problems.
--->> >> >
--->> >> > Now to my problems.
--->> >> > It now takes 3-5 minutes to get a desktop at the server console
or when
--->> >> > using terminal services when I remove the old_ip address from
the nic
--->> >> > .
--->> >> > Also, the group policy management editor shows no computer or
user
--->> >> > polices
--->> >> > defined when I run a report and runs real slow. Last, the event
viewer
--->> >> > has
--->> >> > directory service errors complaining that the server's global
catalog
--->> >> > was
--->> >> > found but could not communicate with it. (The server is still
listed as
--->> >> > a
--->> >> > global catalog under AD sites and services.)
--->> >> >
--->> >> > I know if I put the old_ip back in place everything will start
working,
--->> >> > which is not an option. What do I need to do to fix these
problems?
--->> >> >
--->> >> > Thanks..
--->> >> >
--->> >>
--->> >>
--->>
--->>
--->>
--->

 

Yes, I did post this in two different areas. I wasn't sure where it belonged.
So, let get down to some troubleshooting.

I removed the GC from my Server1 (new_ip) and my 3 Global Catalog errors
went away,
[1869 (located gc), 1655 (attempt to communicate with gc & was unsuccessful),
1126 (use dc locator to find available gc).] However, it still took a full
5 minutes to login at the Server1 console and get a desktop. I added the GC
back onto Server1 and the GC errors returned. I rebooted Server1. Still the
same. I have 2 other DC's in this domain and executed a netlogon stop and
start. Still the same.

The DNS has a SRV record for each server, an A record for each server and a
Cname (made by windows) for each server. The _MSDCS.my.dom exists along with
my Forward and Reverse zones. DNS "looks" good, but I know that is the
problem.

Nslookup resolves the correct information when Server1 is listed as the 1st
preferred DNS.

Dcdiag didn't complain about not being able to find Old_IP after adding the
GC back onto Server1. It now complains about not being able to contact
Server1, like it can't find it's SRV record. It also fails at the
ForestDNSzone test with RPC unavailable. All of the others Schema, Config,
etc, pass.

Repadmin /showreps also fails a the ForestDNSzone with RPC unavailable.

->1. All computers' IP address should be changed correctly.

All 300 of my systems have static ip and dns. This is why I had the new_ip
and old_ip on the server nic. All of those systems have been changed over to
the new subnet ip address and point to server1 new_ip as their primary dns.
The last step was to remove the old_ip from Server1.

-> 2. Related services such as DHCP, DNS, WINS, RRAS, ISA (or 3rd party
firewall application), etc., should be adjusted.

I use only DNS and IIS, no dhcp, wins, host files, lmhost, rras, isa, etc.

->3. We should clean DNS cache on all computers and point the computers to
use the correct DNS and WINS servers.

Ever computers cache was cleared using ipconfig /flushdns before and after
the IP address change.

->4. All computers should register their new IP addresses with DNS and WINS
servers.

All computers have an A record and PTR record.

->5. For some shortcuts, or other related applications settings that locate
target computers using their IP addresses instead of using FQDN, we must
adjust them manually.

Not an issue. If I add shortcuts to the end users desktop I always use FQDN
UNC.

I had the network team turn off all routing to the Old_IP subnet. I don't
expect that to help.

I also turned on the Network monitor on Server1 and then went to another pc
and did a remote login using terminal services. It took a full 5 minutes,
just like the console login. I briefly looked at the data but nothing jumped
off the page at me. Not sure if I get a true data picture of the login. Did
see large gaps in time (15sec) between the 2 machines talking to one another
while others where in the millisecond range.

What would you like me to try next? I'm still stumped..

Thanks.....

 

Dear Customer,

Thanks for posting back.

Before we go any further, I'd like to explain more about newsgroup service.
Newsgroup only focuses on the break/fix based and non-urgent technical
issues. Our response is usually within 24 hours excluding weekend.

If you are experiencing a business critical situation and prefer a real
time communication, please consider Microsoft Customer Support Service
(CSS) for further assistance so that this problem can be resolved
efficiently. To obtain the phone numbers for specific technology request
please take a look at the web site listed below:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

However, if you are glad to continue working with me here, I will try my
best to assist you with this issue.

Based on my research, event ID 1868 and 1655 may be caused by the following
factors:

1) When communicating with the GC, it returns either that it's not a GC
(ie, not publishing itself - which can occur during normal replication
process) or returned some bad information to the local machine.

2) If the GC is out of its site, it will invalidate the information by a
background task that cleans the cache of old unused GCs.

3) The DsCrackNames (which is used to convert from one naming syntax to
another, ie, Cn=Bob, OU=Users, DC=domain, dc=my to Domain\Bob) returns an
error from the GC .

Please user command ipconfig/flushdns to clear the DNS cache and nbtstat -R
to clear the Netbios cache. And try to manually modify SRV record of GC in
DNS server according to you environment, then use NSlookup tool to text if
your client can retrieve the correct record for the domain.

On the client, please use NSlookup tool to retrieve the SRV record of GC:

Run nslookup. Make sure the server is correct.

Type the following command one by one:

set type=SRV

_ladp._tcp.gc._msdcs.<DomainName>

Please replace <DomainName> by the actual domain name.

And check if the retrieved information is consistent with the actual GC in
your LAN.

"Dcdiag didn't complain about not being able to find Old_IP after adding
the GC back onto Server1. It now complains about not being able to contact
Server1, like it can't find it's SRV record. It also fails at the
ForestDNSzone test with RPC unavailable. All of the others Schema, Config,
etc, pass."

[Morgan]:

I suggest you check these SRV on Server 1 records on DNS and manually
adjust them to the correct ones. Besides, verify the site settings in the
DCs if they coincide with your actual environment.

And if this issue still persists, please send Userenv.log, MPS
report(Microsoft Product Support's Report) of DS and the detailed
description of your network environment to me by for
further troubleshooting.

About Userenv.log
=============

Location: %Systemroot%\Debug\UserMode\Userenv.log

Enable by:

Use Registry Editor to add or to modify the following registry entry:

Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
Entry: UserEnvDebugLevel
Type: REG_DWORD
Value data: 10002 (Hexadecimal)

UserEnvDebugLevel can have the following values:
NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000

The default value is NORMAL|LOGFILE (0x00010001)

About MPS report:
================

Microsoft Product Support's Reporting to get more information about our
computer situation. This tool facilitates the gathering of critical system
and logging information used in troubleshooting support issues. After this
tool stops automatically, navigate to the folder "
%SYSTEMROOT%\MPSReports\DirSvc\Logs " and please send all these files back
to me.

You can get this tool from the link:

Microsoft Product Support's Reporting Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
Please download MPSRPT_DirSvc.EXE and collect MPSReport of all DCs and send
to me.

You can also get more information about how to use it in the same page (the
readme.txt)

I look forward to your reply.

Thanks.

Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->Thread-Topic: Changing Server IP Address
--->thread-index: Ach5mRhw0XMgT8riQBG1W9i9UDDTmQ==
--->X-WBNR-Posting-Host: 207.46.19.168
--->From: =?Utf-8?B?QmlnTW8=?= <>
--->References: <>
<>
<>
<>
<>
<>
--->Subject: Re: Changing Server IP Address
--->Date: Wed, 27 Feb 2008 15:33:02 -0800
--->Lines: 293
--->Message-ID: <>
--->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.2992
--->Newsgroups: microsoft.public.windows.server.networking
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:11019
--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->X-Tomcat-NG: microsoft.public.windows.server.networking
--->
--->Yes, I did post this in two different areas. I wasn't sure where it
belonged.
--->So, let get down to some troubleshooting.
--->
--->I removed the GC from my Server1 (new_ip) and my 3 Global Catalog
errors
--->went away,
--->[1869 (located gc), 1655 (attempt to communicate with gc & was
unsuccessful),
--->1126 (use dc locator to find available gc).] However, it still took a
full
--->5 minutes to login at the Server1 console and get a desktop. I added
the GC
--->back onto Server1 and the GC errors returned. I rebooted Server1.
Still the
--->same. I have 2 other DC's in this domain and executed a netlogon stop
and
--->start. Still the same.
--->
--->The DNS has a SRV record for each server, an A record for each server
and a
--->Cname (made by windows) for each server. The _MSDCS.my.dom exists
along with
--->my Forward and Reverse zones. DNS "looks" good, but I know that is the
--->problem.
--->
--->Nslookup resolves the correct information when Server1 is listed as the
1st
--->preferred DNS.
--->
--->Dcdiag didn't complain about not being able to find Old_IP after adding
the
--->GC back onto Server1. It now complains about not being able to contact
--->Server1, like it can't find it's SRV record. It also fails at the
--->ForestDNSzone test with RPC unavailable. All of the others Schema,
Config,
--->etc, pass.
--->
--->Repadmin /showreps also fails a the ForestDNSzone with RPC unavailable.
--->
--->->1. All computers' IP address should be changed correctly.
--->
--->All 300 of my systems have static ip and dns. This is why I had the
new_ip
--->and old_ip on the server nic. All of those systems have been changed
over to
--->the new subnet ip address and point to server1 new_ip as their primary
dns.
--->The last step was to remove the old_ip from Server1.
--->
--->-> 2. Related services such as DHCP, DNS, WINS, RRAS, ISA (or 3rd party
---> firewall application), etc., should be adjusted.
--->
--->I use only DNS and IIS, no dhcp, wins, host files, lmhost, rras, isa,
etc.
--->
--->->3. We should clean DNS cache on all computers and point the computers
to
--->use the correct DNS and WINS servers.
--->
--->Ever computers cache was cleared using ipconfig /flushdns before and
after
--->the IP address change.
--->
--->->4. All computers should register their new IP addresses with DNS and
WINS
--->servers.
--->
--->All computers have an A record and PTR record.
--->
--->->5. For some shortcuts, or other related applications settings that
locate
---> target computers using their IP addresses instead of using FQDN, we
must
---> adjust them manually.
--->
--->Not an issue. If I add shortcuts to the end users desktop I always use
FQDN
--->UNC.
--->
--->I had the network team turn off all routing to the Old_IP subnet. I
don't
--->expect that to help.
--->
--->I also turned on the Network monitor on Server1 and then went to
another pc
--->and did a remote login using terminal services. It took a full 5
minutes,
--->just like the console login. I briefly looked at the data but nothing
jumped
--->off the page at me. Not sure if I get a true data picture of the
login. Did
--->see large gaps in time (15sec) between the 2 machines talking to one
another
--->while others where in the millisecond range.
--->
--->What would you like me to try next? I'm still stumped..
--->
--->Thanks.....
--->
--->
--->"Morgan che(MSFT)" wrote:
--->
--->> Dear Customer,
--->>
--->> Thanks for posting here.
--->>
--->> Changing IP subnet scope is always not a simple project. It may cause
many
--->> problem if we inappropriately change IP scope.
--->>
--->> Based on your description, It's probably DNS related issue. Because
there
--->> might be many servers involved in this problem, I will take GC for
example
--->> for your reference.
--->>
--->> After changing IP address of GC and DNS, we should adjust the DNS
server IP
--->> address to the updated one on the GC server. Then, please use command
"net
--->> stop netlogon" and "net start netlogon" to force this GC server to
--->> reregister the corresponding SRV records in DNS server. After repeat
these
--->> steps on other the DCs and relevant servers, please see if this issue
still
--->> persists.
--->>
--->> Here, I also list some common aspects we should consider when
changing IP
--->> address in local network:
--->>
--->> 1. All computers' IP address should be changed correctly.
--->>
--->> 2. Related services such as DHCP, DNS, WINS, RRAS, ISA (or 3rd party
--->> firewall application), etc., should be adjusted.
--->>
--->> 3. We should clean DNS cache on all computers and point the computers
to
--->> use the correct DNS and WINS servers.
--->>
--->> 4. All computers should register their new IP addresses with DNS and
WINS
--->> servers.
--->>
--->> 5. For some shortcuts, or other related applications settings that
locate
--->> target computers using their IP addresses instead of using FQDN, we
must
--->>
--->> adjust them manually.
--->>
--->> I hope this helps. I appreciate if you would drop me any update.
--->>
--->> Thanks.
--->>
--->>
--->> Sincerely
--->> Morgan Che
--->> Microsoft Online Support
--->> Microsoft Global Technical Support Center
--->>
--->> 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.
--->>
--->>
--->> --------------------
--->> --->Thread-Topic: Changing Server IP Address
--->> --->thread-index: Ach4pMKNGnHb/xPIRHasPecaIyb9qA==
--->> --->X-WBNR-Posting-Host: 207.46.19.197
--->> --->From: =?Utf-8?B?QmlnTW8=?= <>
--->> --->References: <>
--->> <>
--->> <>
--->> <>
--->> --->Subject: Re: Changing Server IP Address
--->> --->Date: Tue, 26 Feb 2008 10:24:01 -0800
--->> --->Lines: 106
--->> --->Message-ID: <>
--->> --->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.2992
--->> --->Newsgroups: microsoft.public.windows.server.networking
--->> --->Path: TK2MSFTNGHUB02.phx.gbl
--->> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->> microsoft.public.windows.server.networking:10987
--->> --->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->> --->X-Tomcat-NG: microsoft.public.windows.server.networking
--->> --->
--->> --->There are no records that have the old_ip address. I don't use
WINS.
--->> The NS
--->> --->records reflect the correct new_ip.
--->> --->I ran another searched on the registry using the hex equivalent
of the
--->> old_ip
--->> --->address and came up empty.
--->> --->
--->> --->Thanks...
--->> --->
--->> --->"Phillip Windell" wrote:
--->> --->
--->> --->> You have stale DNS Records. Examine every DNS record that has
the
--->> old IP#.
--->> --->> Don't just automatically delete them,...you may just have to
edit
--->> them
--->> --->> depending on what they are.
--->> --->>
--->> --->> Remove any WINS entries that still use the old IP#.
--->> --->>
--->> --->> Then right-click on the Zone Name and choose Properties.
--->> --->> go to the Name Servers Tab and make sure the contents are
correct.
--->> --->>
--->> --->> --
--->> --->> Phillip Windell
--->> --->> www.wandtv.com
--->> --->>
--->> --->> The views expressed, are my own and not those of my employer,
or
--->> Microsoft,
--->> --->> or anyone else associated with me, including my cats.
--->> --->> -----------------------------------------------------
--->> --->>
--->> --->> --->> --->> >I would agree but I can't figure out where.
--->> --->> >
--->> --->> > There are no old_ip records in the DNS and no other pc is
using
--->> old_ip.
--->> --->> > I have searched the registry for old_ip and found no
references.
--->> --->> > Dcdiag states my server resolves from old_ip but can't be
reached
--->> by ping.
--->> --->> > I don't know where dcdiag is resolving the old_ip. The rest
of
--->> dcdiag
--->> --->> > looks
--->> --->> > good.
--->> --->> >
--->> --->> > I noticed in the group policy mgmnt editor that only the
sid's show
--->> up
--->> --->> > under
--->> --->> > the security filtering section. If you try to remove the
object you
--->> get
--->> --->> > "network path not found" error, like it is trying to use a
GUID
--->> from
--->> --->> > old_ip.
--->> --->> >
--->> --->> > The only error on replication happens when the ForestDnsZones
trys
--->> to
--->> --->> > contact the
--->> --->> > server: DsBindWithCred to SERVER1 failed with status 1722
(0x6ba):
--->> --->> > The RPC server is unavailable.
--->> --->> > Every hour, since the removal of old_ip, I get 3 Global
Catalog
--->> errors,
--->> --->> > 1869 (located gc), 1655 (attempt to communicate with gc & was
--->> --->> > unsuccessful),
--->> --->> > 1126 (use dc locator to find available gc).
--->> --->> > Clearly my SERVER1 has a problem.
--->> --->> >
--->> --->> > Could I have some orphaned GUID's or Cname records? If so
where?
--->> --->> >
--->> --->> > Please let me know if you can think of something to resolve
this.
--->> --->> > Any help is appreciated.
--->> --->> >
--->> --->> > "Robert L. (MS-MVP)" wrote:
--->> --->> >
--->> --->> >> Sounds like DNS issue. Have you checked the DNS record to
make
--->> sure no
--->> --->> >> old
--->> --->> >> computer uses old IP? Or use dcdiag to check any errors.
--->> --->> >>
--->> --->> >> --
--->> --->> >> Bob Lin, MS-MVP, MCSE & CNE
--->> --->> >> Networking, Internet, Routing, VPN Troubleshooting on
--->> --->> >> http://www.ChicagoTech.net
--->> --->> >> How to Setup Windows, Network, VPN & Remote Access on
--->> --->> >> http://www.HowToNetworking.com
--->> --->> >>
--->> --->> >>
--->> --->> >> --->> --->> >> >I had to retire some subnets due to the sale of our company.
--->> --->> >> > I put the new_ip as the preferred dns and added the old_ip
as a
--->> second
--->> --->> >> > ip
--->> --->> >> > under the advanced tcpip setting -> ip setting. Rebooted
the
--->> server.
--->> --->> >> > All of my static ip clients could now see both ip
addresses and
--->> login
--->> --->> >> > with
--->> --->> >> > no problems.
--->> --->> >> >
--->> --->> >> > Now to my problems.
--->> --->> >> > It now takes 3-5 minutes to get a desktop at the server
console
--->> or when
--->> --->> >> > using terminal services when I remove the old_ip address
from
--->> the nic
--->> --->> >> > .
--->> --->> >> > Also, the group policy management editor shows no computer
or
--->> user
--->> --->> >> > polices
--->> --->> >> > defined when I run a report and runs real slow. Last, the
event
--->> viewer
--->> --->> >> > has
--->> --->> >> > directory service errors complaining that the server's
global
--->> catalog
--->> --->> >> > was
--->> --->> >> > found but could not communicate with it. (The server is
still
--->> listed as
--->> --->> >> > a
--->> --->> >> > global catalog under AD sites and services.)
--->> --->> >> >
--->> --->> >> > I know if I put the old_ip back in place everything will
start
--->> working,
--->> --->> >> > which is not an option. What do I need to do to fix these
--->> problems?
--->> --->> >> >
--->> --->> >> > Thanks..
--->> --->> >> >
--->> --->> >>
--->> --->> >>
--->> --->>
--->> --->>
--->> --->>
--->> --->
--->>
--->>
--->

 

I've sent the info you request via e-mail

Thanks...

 

Dear Mike,

Thanks for the collected information and your efforts.

Analysis:
=========

After checking MPSreport logs, I found the following entries in
ETDCPDWY_DCDIAG log and also enclosed below for your reference:

<<Performing initial setup:
* Verifying that the local machine etdspdwy, is a DC.
* Connecting to directory service on server etdspdwy.
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
[etdspdwy] Directory Binding Error 1722:
The RPC server is unavailable.
This may limit some of the tests that can be performed.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 3 DC(s). Testing 1 of them.
Done gathering initial info.>>

These messages indicate this issue might be related to RPC traffic, which
is critical to DCs communication, like DC replication etc. I suppose the
related firewalls would not be adjusted after IP address is changed.

Suggestion:
=========

To further troubleshoot RPC issues, you may use "Portqry" to isolate it.
Here, I also listed some articles about how to troubleshoot RPC issues for
your reference.

About RPC:
http://technet2.microsoft.com/WindowsServer/en/library/4dbc4c95-935b-4617-b4
f8-20fc947c72881033.mspx?mfr=true

How to troubleshoot RPC Endpoint Mapper errors
http://support.microsoft.com/?kbid=839880

Below is an article about the PORTTQRY tool
http://support.microsoft.com/?kbid=310099

Below is a link to download the PORTQRY tool
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-4638-
A2D5-AC828BDC6983&displaylang=en

If possible, you can also disable the all firewalls on the DCs and between
the DCs and test the result. Besides, please check the site and subnet
information in Active Directory Sites and Services to verify whether it
complies with your actual environment.

If this symptom persists, please send me the Userenv.log file. Please note
Userenv.log will generate after completing the necessary setting in
registry and rebooting the computer.

I look forward to your reply.

Thanks and have a nice day!



Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->Thread-Topic: Changing Server IP Address
--->thread-index: Ach6NkCoPrURPn6CQ+GkKnDgMASacA==
--->X-WBNR-Posting-Host: 207.46.19.197
--->From: =?Utf-8?B?QmlnTW8=?= <>
--->References: <>
<>
<>
<>
<>
<>
<>
<>
--->Subject: Re: Changing Server IP Address
--->Date: Thu, 28 Feb 2008 10:18:01 -0800
--->Lines: 306
--->Message-ID: <>
--->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.2992
--->Newsgroups: microsoft.public.windows.server.networking
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:11038
--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->X-Tomcat-NG: microsoft.public.windows.server.networking
--->
--->I've sent the info you request via e-mail
--->
--->Thanks...
--->
--->"Morgan che(MSFT)" wrote:
--->
--->> Dear Customer,
--->>
--->> Thanks for posting back.
--->>
--->> Before we go any further, I'd like to explain more about newsgroup
service.
--->> Newsgroup only focuses on the break/fix based and non-urgent
technical
--->> issues. Our response is usually within 24 hours excluding weekend.
--->>
--->> If you are experiencing a business critical situation and prefer a
real
--->> time communication, please consider Microsoft Customer Support
Service
--->> (CSS) for further assistance so that this problem can be resolved
--->> efficiently. To obtain the phone numbers for specific technology
request
--->> please take a look at the web site listed below:
--->>
--->> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
--->>
--->> If you are outside the US please see http://support.microsoft.com
for
--->> regional support phone numbers.
--->>
--->> However, if you are glad to continue working with me here, I will try
my
--->> best to assist you with this issue.
--->>
--->> Based on my research, event ID 1868 and 1655 may be caused by the
following
--->> factors:
--->>
--->> 1) When communicating with the GC, it returns either that it's not a
GC
--->> (ie, not publishing itself - which can occur during normal
replication
--->> process) or returned some bad information to the local machine.
--->>
--->> 2) If the GC is out of its site, it will invalidate the information
by a
--->> background task that cleans the cache of old unused GCs.
--->>
--->> 3) The DsCrackNames (which is used to convert from one naming syntax
to
--->> another, ie, Cn=Bob, OU=Users, DC=domain, dc=my to Domain\Bob)
returns an
--->> error from the GC .
--->>
--->> Please user command ipconfig/flushdns to clear the DNS cache and
nbtstat -R
--->> to clear the Netbios cache. And try to manually modify SRV record of
GC in
--->> DNS server according to you environment, then use NSlookup tool to
text if
--->> your client can retrieve the correct record for the domain.
--->>
--->> On the client, please use NSlookup tool to retrieve the SRV record of
GC:
--->>
--->> Run nslookup. Make sure the server is correct.
--->>
--->> Type the following command one by one:
--->>
--->> set type=SRV
--->>
--->> _ladp._tcp.gc._msdcs.<DomainName>
--->>
--->> Please replace <DomainName> by the actual domain name.
--->>
--->> And check if the retrieved information is consistent with the actual
GC in
--->> your LAN.
--->>
--->> "Dcdiag didn't complain about not being able to find Old_IP after
adding
--->> the GC back onto Server1. It now complains about not being able to
contact
--->> Server1, like it can't find it's SRV record. It also fails at the
--->> ForestDNSzone test with RPC unavailable. All of the others Schema,
Config,
--->> etc, pass."
--->>
--->> [Morgan]:
--->>
--->> I suggest you check these SRV on Server 1 records on DNS and manually
--->> adjust them to the correct ones. Besides, verify the site settings in
the
--->> DCs if they coincide with your actual environment.
--->>
--->> And if this issue still persists, please send Userenv.log, MPS
--->> report(Microsoft Product Support's Report) of DS and the detailed
--->> description of your network environment to me by
for
--->> further troubleshooting.
--->>
--->> About Userenv.log
--->> =============
--->>
--->> Location: %Systemroot%\Debug\UserMode\Userenv.log
--->>
--->> Enable by:
--->>
--->> Use Registry Editor to add or to modify the following registry entry:
--->>
--->> Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
--->> NT\CurrentVersion\Winlogon
--->> Entry: UserEnvDebugLevel
--->> Type: REG_DWORD
--->> Value data: 10002 (Hexadecimal)
--->>
--->> UserEnvDebugLevel can have the following values:
--->> NONE 0x00000000
--->> NORMAL 0x00000001
--->> VERBOSE 0x00000002
--->> LOGFILE 0x00010000
--->> DEBUGGER 0x00020000
--->>
--->> The default value is NORMAL|LOGFILE (0x00010001)
--->>
--->> About MPS report:
--->> ================
--->>
--->> Microsoft Product Support's Reporting to get more information about
our
--->> computer situation. This tool facilitates the gathering of critical
system
--->> and logging information used in troubleshooting support issues. After
this
--->> tool stops automatically, navigate to the folder "
--->> %SYSTEMROOT%\MPSReports\DirSvc\Logs " and please send all these files
back
--->> to me.
--->>
--->> You can get this tool from the link:
--->>
--->> Microsoft Product Support's Reporting Tools
--->>
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
--->> 88B7-F9C79B7306C0&displaylang=en
--->> Please download MPSRPT_DirSvc.EXE and collect MPSReport of all DCs
and send
--->> to me.
--->>
--->> You can also get more information about how to use it in the same
page (the
--->> readme.txt)
--->>
--->> I look forward to your reply.
--->>
--->> Thanks.
--->>
--->> Sincerely
--->> Morgan Che
--->> Microsoft Online Support
--->> Microsoft Global Technical Support Center
--->>
--->> 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.
--->>
--->>
--->> --------------------
--->> --->Thread-Topic: Changing Server IP Address
--->> --->thread-index: Ach5mRhw0XMgT8riQBG1W9i9UDDTmQ==
--->> --->X-WBNR-Posting-Host: 207.46.19.168
--->> --->From: =?Utf-8?B?QmlnTW8=?= <>
--->> --->References: <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> --->Subject: Re: Changing Server IP Address
--->> --->Date: Wed, 27 Feb 2008 15:33:02 -0800
--->> --->Lines: 293
--->> --->Message-ID: <>
--->> --->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.2992
--->> --->Newsgroups: microsoft.public.windows.server.networking
--->> --->Path: TK2MSFTNGHUB02.phx.gbl
--->> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->> microsoft.public.windows.server.networking:11019
--->> --->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->> --->X-Tomcat-NG: microsoft.public.windows.server.networking
--->> --->
--->> --->Yes, I did post this in two different areas. I wasn't sure where
it
--->> belonged.
--->> --->So, let get down to some troubleshooting.
--->> --->
--->> --->I removed the GC from my Server1 (new_ip) and my 3 Global Catalog
--->> errors
--->> --->went away,
--->> --->[1869 (located gc), 1655 (attempt to communicate with gc & was
--->> unsuccessful),
--->> --->1126 (use dc locator to find available gc).] However, it still
took a
--->> full
--->> --->5 minutes to login at the Server1 console and get a desktop. I
added
--->> the GC
--->> --->back onto Server1 and the GC errors returned. I rebooted
Server1.
--->> Still the
--->> --->same. I have 2 other DC's in this domain and executed a netlogon
stop
--->> and
--->> --->start. Still the same.
--->> --->
--->> --->The DNS has a SRV record for each server, an A record for each
server
--->> and a
--->> --->Cname (made by windows) for each server. The _MSDCS.my.dom
exists
--->> along with
--->> --->my Forward and Reverse zones. DNS "looks" good, but I know that
is the
--->> --->problem.
--->> --->
--->> --->Nslookup resolves the correct information when Server1 is listed
as the
--->> 1st
--->> --->preferred DNS.
--->> --->
--->> --->Dcdiag didn't complain about not being able to find Old_IP after
adding
--->> the
--->> --->GC back onto Server1. It now complains about not being able to
contact
--->> --->Server1, like it can't find it's SRV record. It also fails at
the
--->> --->ForestDNSzone test with RPC unavailable. All of the others
Schema,
--->> Config,
--->> --->etc, pass.
--->> --->
--->> --->Repadmin /showreps also fails a the ForestDNSzone with RPC
unavailable.
--->> --->
--->> --->->1. All computers' IP address should be changed correctly.
--->> --->
--->> --->All 300 of my systems have static ip and dns. This is why I had
the
--->> new_ip
--->> --->and old_ip on the server nic. All of those systems have been
changed
--->> over to
--->> --->the new subnet ip address and point to server1 new_ip as their
primary
--->> dns.
--->> --->The last step was to remove the old_ip from Server1.
--->> --->
--->> --->-> 2. Related services such as DHCP, DNS, WINS, RRAS, ISA (or 3rd
party
--->> ---> firewall application), etc., should be adjusted.
--->> --->
--->> --->I use only DNS and IIS, no dhcp, wins, host files, lmhost, rras,
isa,
--->> etc.
--->> --->
--->> --->->3. We should clean DNS cache on all computers and point the
computers
--->> to
--->> --->use the correct DNS and WINS servers.
--->> --->
--->> --->Ever computers cache was cleared using ipconfig /flushdns before
and
--->> after
--->> --->the IP address change.
--->> --->
--->> --->->4. All computers should register their new IP addresses with
DNS and
--->> WINS
--->> --->servers.
--->> --->
--->> --->All computers have an A record and PTR record.
--->> --->
--->> --->->5. For some shortcuts, or other related applications settings
that
--->> locate
--->> ---> target computers using their IP addresses instead of using FQDN,
we
--->> must
--->> ---> adjust them manually.
--->> --->
--->> --->Not an issue. If I add shortcuts to the end users desktop I
always use
--->> FQDN
--->> --->UNC.
--->> --->
--->> --->I had the network team turn off all routing to the Old_IP subnet.
I
--->> don't
--->> --->expect that to help.
--->> --->
--->> --->I also turned on the Network monitor on Server1 and then went to
--->> another pc
--->> --->and did a remote login using terminal services. It took a full 5
--->> minutes,
--->> --->just like the console login. I briefly looked at the data but
nothing
--->> jumped
--->> --->off the page at me. Not sure if I get a true data picture of the
--->> login. Did
--->> --->see large gaps in time (15sec) between the 2 machines talking to
one
--->> another
--->> --->while others where in the millisecond range.
--->> --->
--->> --->What would you like me to try next? I'm still stumped..
--->> --->
--->> --->Thanks.....
--->> --->
--->> --->
--->> --->"Morgan che(MSFT)" wrote:
--->> --->
--->> --->> Dear Customer,
--->> --->>
--->> --->> Thanks for posting here.
--->> --->>
--->> --->> Changing IP subnet scope is always not a simple project. It may
cause
--->> many
--->> --->> problem if we inappropriately change IP scope.
--->> --->>
--->> --->> Based on your description, It's probably DNS related issue.
Because
--->> there
--->> --->> might be many servers involved in this problem, I will take GC
for
--->> example
--->> --->> for your reference.
--->> --->>
--->> --->> After changing IP address of GC and DNS, we should adjust the
DNS
--->> server IP
--->> --->> address to the updated one on the GC server. Then, please use
command
--->> "net
--->> --->> stop netlogon" and "net start netlogon" to force this GC server
to
--->> --->> reregister the corresponding SRV records in DNS server. After
repeat
--->> these
--->> --->> steps on other the DCs and relevant servers, please see if this
issue
--->> still
--->> --->> persists.
--->> --->>
--->> --->> Here, I also list some common aspects we should consider when
--->> changing IP
--->> --->> address in local network:
--->> --->>
--->> --->> 1. All computers' IP address should be changed correctly.
--->> --->>
--->

 

Morgan,

I found the problem. Didn't have anything to do with firewalls. There was
an old_ip address entry in the host file.
Once I removed it and rebooted the server things were o.k. Windows 2003
server must use that file even if you have configured the system not to use
it.

Thanks...

 

Hi Mike,

Thank you for the update on this case, and the additional feedback on how
you were successful in resolving this issue. I believe that other customers
who experience similar issues will also benefit from the solution.

For other break/fix based issue, you are welcome to post here.

Have a nice day!

Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->Thread-Topic: Changing Server IP Address
--->thread-index: Ach+F6V4lgX2ssYoQxSY98deoCnLgw==
--->X-WBNR-Posting-Host: 207.46.19.168
--->From: =?Utf-8?B?QmlnTW8=?= <>
--->References: <>
<>
<>
<>
<>
<>
<>
<>
<>
<>
--->Subject: Re: Changing Server IP Address
--->Date: Tue, 4 Mar 2008 08:49:00 -0800
--->Lines: 311
--->Message-ID: <>
--->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.2992
--->Newsgroups: microsoft.public.windows.server.networking
--->Path: TK2MSFTNGHUB02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:11155
--->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->X-Tomcat-NG: microsoft.public.windows.server.networking
--->
--->Morgan,
--->
--->I found the problem. Didn't have anything to do with firewalls. There
was
--->an old_ip address entry in the host file.
--->Once I removed it and rebooted the server things were o.k. Windows
2003
--->server must use that file even if you have configured the system not to
use
--->it.
--->
--->Thanks...
--->"Morgan che(MSFT)" wrote:
--->
--->> Dear Mike,
--->>
--->> Thanks for the collected information and your efforts.
--->>
--->> Analysis:
--->> =========
--->>
--->> After checking MPSreport logs, I found the following entries in
--->> ETDCPDWY_DCDIAG log and also enclosed below for your reference:
--->>
--->> <<Performing initial setup:
--->> * Verifying that the local machine etdspdwy, is a DC.
--->> * Connecting to directory service on server etdspdwy.
--->> *** Warning: could not confirm the identity of this server in
--->> the directory versus the names returned by DNS servers.
--->> If there are problems accessing this directory server
then
--->> you may need to check that this server is correctly
registered
--->> with DNS
--->> [etdspdwy] Directory Binding Error 1722:
--->> The RPC server is unavailable.
--->> This may limit some of the tests that can be performed.
--->> * Collecting site info.
--->> * Identifying all servers.
--->> * Identifying all NC cross-refs.
--->> * Found 3 DC(s). Testing 1 of them.
--->> Done gathering initial info.>>
--->>
--->> These messages indicate this issue might be related to RPC traffic,
which
--->> is critical to DCs communication, like DC replication etc. I suppose
the
--->> related firewalls would not be adjusted after IP address is changed.
--->>
--->> Suggestion:
--->> =========
--->>
--->> To further troubleshoot RPC issues, you may use "Portqry" to isolate
it.
--->> Here, I also listed some articles about how to troubleshoot RPC
issues for
--->> your reference.
--->>
--->> About RPC:
--->>
http://technet2.microsoft.com/WindowsServer/en/library/4dbc4c95-935b-4617-b4
--->> f8-20fc947c72881033.mspx?mfr=true
--->>
--->> How to troubleshoot RPC Endpoint Mapper errors
--->> http://support.microsoft.com/?kbid=839880
--->>
--->> Below is an article about the PORTTQRY tool
--->> http://support.microsoft.com/?kbid=310099
--->>
--->> Below is a link to download the PORTQRY tool
--->>
http://www.microsoft.com/downloads/details.aspx?familyid=89811747-C74B-4638-
--->> A2D5-AC828BDC6983&displaylang=en
--->>
--->> If possible, you can also disable the all firewalls on the DCs and
between
--->> the DCs and test the result. Besides, please check the site and
subnet
--->> information in Active Directory Sites and Services to verify whether
it
--->> complies with your actual environment.
--->>
--->> If this symptom persists, please send me the Userenv.log file. Please
note
--->> Userenv.log will generate after completing the necessary setting in
--->> registry and rebooting the computer.
--->>
--->> I look forward to your reply.
--->>
--->> Thanks and have a nice day!
--->>
--->>
--->>
--->> Sincerely
--->> Morgan Che
--->> Microsoft Online Support
--->> Microsoft Global Technical Support Center
--->>
--->> 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.
--->>
--->>
--->> --------------------
--->> --->Thread-Topic: Changing Server IP Address
--->> --->thread-index: Ach6NkCoPrURPn6CQ+GkKnDgMASacA==
--->> --->X-WBNR-Posting-Host: 207.46.19.197
--->> --->From: =?Utf-8?B?QmlnTW8=?= <>
--->> --->References: <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> <>
--->> --->Subject: Re: Changing Server IP Address
--->> --->Date: Thu, 28 Feb 2008 10:18:01 -0800
--->> --->Lines: 306
--->> --->Message-ID: <>
--->> --->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.2992
--->> --->Newsgroups: microsoft.public.windows.server.networking
--->> --->Path: TK2MSFTNGHUB02.phx.gbl
--->> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->> microsoft.public.windows.server.networking:11038
--->> --->NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
--->> --->X-Tomcat-NG: microsoft.public.windows.server.networking
--->> --->
--->> --->I've sent the info you request via e-mail
--->> --->
--->> --->Thanks...
--->> --->
--->> --->"Morgan che(MSFT)" wrote:
--->> --->
--->> --->> Dear Customer,
--->> --->>
--->> --->> Thanks for posting back.
--->> --->>
--->> --->> Before we go any further, I'd like to explain more about
newsgroup
--->> service.
--->> --->> Newsgroup only focuses on the break/fix based and non-urgent
--->> technical
--->> --->> issues. Our response is usually within 24 hours excluding
weekend.
--->> --->>
--->> --->> If you are experiencing a business critical situation and
prefer a
--->> real
--->> --->> time communication, please consider Microsoft Customer Support
--->> Service
--->> --->> (CSS) for further assistance so that this problem can be
resolved
--->> --->> efficiently. To obtain the phone numbers for specific
technology
--->> request
--->> --->> please take a look at the web site listed below:
--->> --->>
--->> --->>
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
--->> --->>
--->> --->> If you are outside the US please see
http://support.microsoft.com
--->> for
--->> --->> regional support phone numbers.
--->> --->>
--->> --->> However, if you are glad to continue working with me here, I
will try
--->> my
--->> --->> best to assist you with this issue.
--->> --->>
--->> --->> Based on my research, event ID 1868 and 1655 may be caused by
the
--->> following
--->> --->> factors:
--->> --->>
--->> --->> 1) When communicating with the GC, it returns either that it's
not a
--->> GC
--->> --->> (ie, not publishing itself - which can occur during normal
--->> replication
--->> --->> process) or returned some bad information to the local machine.
--->> --->>
--->> --->> 2) If the GC is out of its site, it will invalidate the
information
--->> by a
--->> --->> background task that cleans the cache of old unused GCs.
--->> --->>
--->> --->> 3) The DsCrackNames (which is used to convert from one naming
syntax
--->> to
--->> --->> another, ie, Cn=Bob, OU=Users, DC=domain, dc=my to Domain\Bob)
--->> returns an
--->> --->> error from the GC .
--->> --->>
--->> --->> Please user command ipconfig/flushdns to clear the DNS cache
and
--->> nbtstat -R
--->> --->> to clear the Netbios cache. And try to manually modify SRV
record of
--->> GC in
--->> --->> DNS server according to you environment, then use NSlookup tool
to
--->> text if
--->> --->> your client can retrieve the correct record for the domain.
--->> --->>
--->> --->> On the client, please use NSlookup tool to retrieve the SRV
record of
--->> GC:
--->> --->>
--->> --->> Run nslookup. Make sure the server is correct.
--->> --->>
--->> --->> Type the following command one by one:
--->> --->>
--->> --->> set type=SRV
--->> --->>
--->> --->> _ladp._tcp.gc._msdcs.<DomainName>
--->> --->>
--->> --->> Please replace <DomainName> by the actual domain name.
--->> --->>
--->> --->> And check if the retrieved information is consistent with the
actual
--->> GC in
--->> --->> your LAN.
--->> --->>
--->> --->> "Dcdiag didn't complain about not being able to find Old_IP
after
--->> adding
--->> --->> the GC back onto Server1. It now complains about not being able
to
--->> contact
--->> --->> Server1, like it can't find it's SRV record. It also fails at
the
--->> --->> ForestDNSzone test with RPC unavailable. All of the others
Schema,
--->> Config,
--->> --->> etc, pass."
--->> --->>
--->> --->> [Morgan]:
--->> --->>
--->> --->> I suggest you check these SRV on Server 1 records on DNS and
manually
--->> --->> adjust them to the correct ones. Besides, verify the site
settings in
--->> the
--->> --->> DCs if they coincide with your actual environment.
--->> --->>
--->> --->> And if this issue still persists, please send Userenv.log, MPS
--->> --->> report(Microsoft Product Support's Report) of DS and the
detailed
--->> --->> description of your network environment to me by
--->> for
--->> --->> further troubleshooting.
--->> --->>
--->> --->> About Userenv.log
--->> --->> =============
--->> --->>
--->> --->> Location: %Systemroot%\Debug\UserMode\Userenv.log
--->> --->>
--->> --->> Enable by:
--->> --->>
--->> --->> Use Registry Editor to add or to modify the following registry
entry:
--->> --->>
--->> --->> Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
--->> --->> NT\CurrentVersion\Winlogon
--->> --->> Entry: UserEnvDebugLevel
--->> --->> Type: REG_DWORD
--->> --->> Value data: 10002 (Hexadecimal)
--->> --->>
--->> --->> UserEnvDebugLevel can have the following values:
--->> --->> NONE 0x00000000
--->> --->> NORMAL 0x00000001
--->> --->> VERBOSE 0x00000002
--->> --->> LOGFILE 0x00010000
--->> --->> DEBUGGER 0x00020000
--->> --->>
--->> --->> The default value is NORMAL|LOGFILE (0x00010001)
--->> --->>
--->> --->> About MPS report:
--->> --->> ================
--->> --->>
--->> --->> Microsoft Product Support's Reporting to get more information
about
--->> our
--->> --->> computer situation. This tool facilitates the gathering of
critical
--->> system
--->> --->> and logging information used in troubleshooting support issues.
After
--->> this
--->> --->> tool stops automatically, navigate to the folder "
--->> --->> %SYSTEMROOT%\MPSReports\DirSvc\Logs " and please send all these
files
--->> back
--->> --->> to me.
--->> --->>
--->> --->> You can get this tool from the link:
--->> --->>
--->> --->> Microsoft Product Support's Reporting Tools
--->> --->>
--->>
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
--->> --->> 88B7-F9C79B7306C0&displaylang=en
--->> --->> Please download MPSRPT_DirSvc.EXE and collect MPSReport of all
DCs
--->> and send
--->> --->> to me.
--->> --->>
--->> --->> You can also get more information about how to use it in the
same
--->> page (the
--->> --->> readme.txt)
--->> --->>
--->> --->> I look forward to your reply.
--->> --->>
--->> --->> Thanks.
--->> --->>
--->> --->> Sincerely
--->> --->> Morgan Che
--->> --->> Microsoft Online Support
--->> --->> Microsoft Global Technical Support Center
--->> --->>
--->> --->> 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.
--->> --->>
--->> --->>
--->> --->> --------------------
--->> --->> --->Thread-Topic: Changing Server IP Address
--->> --->> --->thread-index: Ach5mRhw0XMgT8riQBG1W9i9UDDTmQ==
--->> --->> --->X-WBNR-Posting-Host: 207.46.19.168
--->> --->> --->From: =?Utf-8?B?QmlnTW8=?= <>
--->> --->> --->References:
<>
--->> --->> <>
--->> --->> <>
--->> --->> <>
--->> --->> <>
--->> --->> <>
--->> --->> --->Subject: Re: Changing Server IP Address
--->> --->> --->Date: Wed, 27 Feb 2008 15:33:02 -0800
--->> --->> --->Lines: 293
--->