IP Change for DC

We change the IP's of both our DC, they are also the DNS server for the domain.
Now some time when we try to open Users and Computers for AD, this message
shows up " Naming information cannot be located for the following reason: The
server is not operational.". After you say OK the user screen comes up with
no information and every thing is blank. We have to restart the machine and
every thing comes back, which will last for a day or two and it happens
again. This happens on both DC's. We are running Windows server 2003,
Standard edition, service pack 2. Any suggestions. Thanks.

Sarfraz Malik schrieb:
> We change the IP's of both our DC, they are also the DNS server for the domain.
> Now some time when we try to open Users and Computers for AD, this message
> shows up " Naming information cannot be located for the following reason: The
> server is not operational.". After you say OK the user screen comes up with
> no information and every thing is blank. We have to restart the machine and
> every thing comes back, which will last for a day or two and it happens
> again. This happens on both DC's. We are running Windows server 2003,
> Standard edition, service pack 2. Any suggestions. Thanks.

Have you changed the DNS configuration, too? When changing the IP
addresses of the DCs, make sure that you also change their settings for
"Primary" and "Secondary" DNS server so they are able to reach each other.

also, have you checked whether you can successfully ping the FQDNs of
the DCs as well as the domain name? Have you checked whether DNS has old
IP references and clean them up?

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste

"Sarfraz Malik" <> wrote in message
news:75831FAB-CAC1-4A3C-8859-...
> We change the IP's of both our DC, they are also the DNS server for the
> domain.
> Now some time when we try to open Users and Computers for AD, this message
> shows up " Naming information cannot be located for the following reason:
> The
> server is not operational.". After you say OK the user screen comes up
> with
> no information and every thing is blank. We have to restart the machine
> and
> every thing comes back, which will last for a day or two and it happens
> again. This happens on both DC's. We are running Windows server 2003,
> Standard edition, service pack 2. Any suggestions. Thanks.


Did you also change the DNS setting on the DC to the new IP address? That
must be done for all client machines, too, and if using DHCP, it must be
changed in Option 006.

Also, make sure you do not use the ISP DNS, the router as a DNS address, or
any other external DNS that does not have reference to AD's zone.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

I check the configuration of DNS. On one DC the order was reverse. The
primary was the other DC and sec. as itself. I fix that, the other DC was
fine. I was able to ping all the things you requested. Hopefully this change
will stabilize it.
Will this cause the error I was getting for Users and conputer screen. Thanks.

"Florian Frommherz [MVP]" wrote:

> Sarfraz Malik schrieb:
> > We change the IP's of both our DC, they are also the DNS server for the domain.
> > Now some time when we try to open Users and Computers for AD, this message
> > shows up " Naming information cannot be located for the following reason: The
> > server is not operational.". After you say OK the user screen comes up with
> > no information and every thing is blank. We have to restart the machine and
> > every thing comes back, which will last for a day or two and it happens
> > again. This happens on both DC's. We are running Windows server 2003,
> > Standard edition, service pack 2. Any suggestions. Thanks.
>
> Have you changed the DNS configuration, too? When changing the IP
> addresses of the DCs, make sure that you also change their settings for
> "Primary" and "Secondary" DNS server so they are able to reach each other.
>
> also, have you checked whether you can successfully ping the FQDNs of
> the DCs as well as the domain name? Have you checked whether DNS has old
> IP references and clean them up?
>
> Cheers,
> Florian
> --
> Microsoft MVP - Group Policy
> eMail: prename [at] frickelsoft [dot] net.
> blog: http://www.frickelsoft.net/blog.
> Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
>

Did you point all of your clients at the new location of your dc (Via the
dns settings on the clients)? If using dhcp just change the scope.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Sarfraz Malik" <> wrote in message
news:B9774212-2093-4D92-AC0C-...
>I check the configuration of DNS. On one DC the order was reverse. The
> primary was the other DC and sec. as itself. I fix that, the other DC was
> fine. I was able to ping all the things you requested. Hopefully this
> change
> will stabilize it.
> Will this cause the error I was getting for Users and conputer screen.
> Thanks.
>
> "Florian Frommherz [MVP]" wrote:
>
>> Sarfraz Malik schrieb:
>> > We change the IP's of both our DC, they are also the DNS server for the
>> > domain.
>> > Now some time when we try to open Users and Computers for AD, this
>> > message
>> > shows up " Naming information cannot be located for the following
>> > reason: The
>> > server is not operational.". After you say OK the user screen comes up
>> > with
>> > no information and every thing is blank. We have to restart the machine
>> > and
>> > every thing comes back, which will last for a day or two and it happens
>> > again. This happens on both DC's. We are running Windows server 2003,
>> > Standard edition, service pack 2. Any suggestions. Thanks.
>>
>> Have you changed the DNS configuration, too? When changing the IP
>> addresses of the DCs, make sure that you also change their settings for
>> "Primary" and "Secondary" DNS server so they are able to reach each
>> other.
>>
>> also, have you checked whether you can successfully ping the FQDNs of
>> the DCs as well as the domain name? Have you checked whether DNS has old
>> IP references and clean them up?
>>
>> Cheers,
>> Florian
>> --
>> Microsoft MVP - Group Policy
>> eMail: prename [at] frickelsoft [dot] net.
>> blog: http://www.frickelsoft.net/blog.
>> Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
>>

Yes, but I am still getting thsi error message on the DC. It happen again
today on both DC's. " Naming information cannot be located for the following
reason: The
server is not operational."
I do not know what this error means.

"Paul Bergson [MVP-DS]" wrote:

> Did you point all of your clients at the new location of your dc (Via the
> dns settings on the clients)? If using dhcp just change the scope.
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Sarfraz Malik" <> wrote in message
> news:B9774212-2093-4D92-AC0C-...
> >I check the configuration of DNS. On one DC the order was reverse. The
> > primary was the other DC and sec. as itself. I fix that, the other DC was
> > fine. I was able to ping all the things you requested. Hopefully this
> > change
> > will stabilize it.
> > Will this cause the error I was getting for Users and conputer screen.
> > Thanks.
> >
> > "Florian Frommherz [MVP]" wrote:
> >
> >> Sarfraz Malik schrieb:
> >> > We change the IP's of both our DC, they are also the DNS server for the
> >> > domain.
> >> > Now some time when we try to open Users and Computers for AD, this
> >> > message
> >> > shows up " Naming information cannot be located for the following
> >> > reason: The
> >> > server is not operational.". After you say OK the user screen comes up
> >> > with
> >> > no information and every thing is blank. We have to restart the machine
> >> > and
> >> > every thing comes back, which will last for a day or two and it happens
> >> > again. This happens on both DC's. We are running Windows server 2003,
> >> > Standard edition, service pack 2. Any suggestions. Thanks.
> >>
> >> Have you changed the DNS configuration, too? When changing the IP
> >> addresses of the DCs, make sure that you also change their settings for
> >> "Primary" and "Secondary" DNS server so they are able to reach each
> >> other.
> >>
> >> also, have you checked whether you can successfully ping the FQDNs of
> >> the DCs as well as the domain name? Have you checked whether DNS has old
> >> IP references and clean them up?
> >>
> >> Cheers,
> >> Florian
> >> --
> >> Microsoft MVP - Group Policy
> >> eMail: prename [at] frickelsoft [dot] net.
> >> blog: http://www.frickelsoft.net/blog.
> >> Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste
> >>
>
>
>

Post an ipconfig /all from both dc's. feel free to modify the first couple
of octets

Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> ntfrsutl ds your_dc_name > c:\sysvol.log
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take into
account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045


--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Sarfraz Malik" <> wrote in message
news:7D52A3B5-913C-494C-A24A-...
> Yes, but I am still getting thsi error message on the DC. It happen again
> today on both DC's. " Naming information cannot be located for the
> following
> reason: The
> server is not operational."
> I do not know what this error means.
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> Did you point all of your clients at the new location of your dc (Via the
>> dns settings on the clients)? If using dhcp just change the scope.
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>> Microsoft's Thrive IT Pro of the Month - June 2009
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>> "Sarfraz Malik" <> wrote in message
>> news:B9774212-2093-4D92-AC0C-...
>> >I check the configuration of DNS. On one DC the order was reverse. The
>> > primary was the other DC and sec. as itself. I fix that, the other DC
>> > was
>> > fine. I was able to ping all the things you requested. Hopefully this
>> > change
>> > will stabilize it.
>> > Will this cause the error I was getting for Users and conputer screen.
>> > Thanks.
>> >
>> > "Florian Frommherz [MVP]" wrote:
>> >
>> >> Sarfraz Malik schrieb:
>> >> > We change the IP's of both our DC, they are also the DNS server for
>> >> > the
>> >> > domain.
>> >> > Now some time when we try to open Users and Computers for AD, this
>> >> > message
>> >> > shows up " Naming information cannot be located for the following
>> >> > reason: The
>> >> > server is not operational.". After you say OK the user screen comes
>> >> > up
>> >> > with
>> >> > no information and every thing is blank. We have to restart the
>> >> > machine
>> >> > and
>> >> > every thing comes back, which will last for a day or two and it
>> >> > happens
>> >> > again. This happens on both DC's. We are running Windows server
>> >> > 2003,
>> >> > Standard edition, service pack 2. Any suggestions. Thanks.
>> >>
>> >> Have you changed the DNS configuration, too? When changing the IP
>> >> addresses of the DCs, make sure that you also change their settings
>> >> for
>> >> "Primary" and "Secondary" DNS server so they are able to reach each
>> >> other.
>> >>
>> >> also, have you checked whether you can successfully ping the FQDNs of
>> >> the DCs as well as the domain name? Have you checked whether DNS has
>> >> old
>> >> IP references and clean them up?
>> >>
>> >> Cheers,
>> >> Florian
>> >> --
>> >> Microsoft MVP - Group Policy
>> >> eMail: prename [at] frickelsoft [dot] net.
>> >> blog: http://www.frickelsoft.net/blog.
>> >> Maillist (german):
>> >> http://frickelsoft.net/cms/index.php?page=mailingliste
>> >>
>>
>>
>>

Here is the Ipconfig from both DC's.


Windows IP Configuration



Host Name . . . . . . . . . . . . : ssb21

Primary Dns Suffix . . . . . . . : vcsa.uic.edu

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : vcsa.uic.edu

ssbclient.uic.edu

uic.edu



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : ssbclient.uic.edu

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet

Physical Address. . . . . . . . . : 00-06-5B-F3-89-21

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : xxx.xxx.121.11

Subnet Mask . . . . . . . . . . . : 255.255.252.0

Default Gateway . . . . . . . . . : xxx.xxx.120.1

DHCP Server . . . . . . . . . . . : xxx.xxx.155.124

DNS Servers . . . . . . . . . . . : xxx.xxx.121.11

Primary WINS Server . . . . . . . : xxx.xxx.121.8

Secondary WINS Server . . . . . . : xxx.xxx.121.45

Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:05:34 AM

Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:21:34 AM




Windows IP Configuration



Host Name . . . . . . . . . . . . : ssb26

Primary Dns Suffix . . . . . . . : vcsa.uic.edu

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : vcsa.uic.edu

ssbclient.uic.edu

uic.edu



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . : ssbclient.uic.edu

Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2

Physical Address. . . . . . . . . : 00-0F-1F-67-78-32

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : xxx.xxx.121.25

Subnet Mask . . . . . . . . . . . : 255.255.252.0

Default Gateway . . . . . . . . . : xxx.xxx.120.1

DHCP Server . . . . . . . . . . . : xxx.xxx.155.124

DNS Servers . . . . . . . . . . . : xxx.xxx.121.25

Primary WINS Server . . . . . . . : xxx.xxx.121.8

Secondary WINS Server . . . . . . : xxx.xxx.121.45

Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:10:09 AM

Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:26:09 AM

Thanks.



"Paul Bergson [MVP-DS]" wrote:

> Post an ipconfig /all from both dc's. feel free to modify the first couple
> of octets
>
> Run diagnostics against your Active Directory domain.
>
> If you don't have the support tools installed, install them from your server
> install disk.
> d:\support\tools\setup.exe
>
> Run dcdiag, netdiag and repadmin in verbose mode.
> -> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
> -> netdiag.exe /v > c:\netdiag.log (On each dc)
> -> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
> -> ntfrsutl ds your_dc_name > c:\sysvol.log
> -> dnslint /ad /s "ip address of your dc"
>
> **Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
> in the forest. If you have significant numbers of DC's this test could
> generate significant detail and take a long time. You also want to take into
> account slow links to dc's will also add to the testing time.
>
> If you download a gui script I wrote it should be simple to set and run
> (DCDiag and NetDiag). It also has the option to run individual tests without
> having to learn all the switch options. The details will be output in
> notepad text files that pop up automagically.
>
> The script is located on my website at
> http://www.pbbergs.com/windows/downloads.htm
>
> Just select both dcdiag and netdiag make sure verbose is set. (Leave the
> default settings for dcdiag as set when selected)
>
> When complete search for fail, error and warning messages.
>
> Description and download for dnslint
> http://support.microsoft.com/kb/321045
>
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
> Microsoft's Thrive IT Pro of the Month - June 2009
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Sarfraz Malik" <> wrote in message
> news:7D52A3B5-913C-494C-A24A-...
> > Yes, but I am still getting thsi error message on the DC. It happen again
> > today on both DC's. " Naming information cannot be located for the
> > following
> > reason: The
> > server is not operational."
> > I do not know what this error means.
> >
> > "Paul Bergson [MVP-DS]" wrote:
> >
> >> Did you point all of your clients at the new location of your dc (Via the
> >> dns settings on the clients)? If using dhcp just change the scope.
> >>
> >> --
> >> Paul Bergson
> >> MVP - Directory Services
> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> >> 2008, 2003, 2000 (Early Achiever), NT4
> >> Microsoft's Thrive IT Pro of the Month - June 2009
> >>
> >> http://www.pbbergs.com
> >>
> >> Please no e-mails, any questions should be posted in the NewsGroup This
> >> posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >> "Sarfraz Malik" <> wrote in message
> >> news:B9774212-2093-4D92-AC0C-...
> >> >I check the configuration of DNS. On one DC the order was reverse. The
> >> > primary was the other DC and sec. as itself. I fix that, the other DC
> >> > was
> >> > fine. I was able to ping all the things you requested. Hopefully this
> >> > change
> >> > will stabilize it.
> >> > Will this cause the error I was getting for Users and conputer screen.
> >> > Thanks.
> >> >
> >> > "Florian Frommherz [MVP]" wrote:
> >> >
> >> >> Sarfraz Malik schrieb:
> >> >> > We change the IP's of both our DC, they are also the DNS server for
> >> >> > the
> >> >> > domain.
> >> >> > Now some time when we try to open Users and Computers for AD, this
> >> >> > message
> >> >> > shows up " Naming information cannot be located for the following
> >> >> > reason: The
> >> >> > server is not operational.". After you say OK the user screen comes
> >> >> > up
> >> >> > with
> >> >> > no information and every thing is blank. We have to restart the
> >> >> > machine
> >> >> > and
> >> >> > every thing comes back, which will last for a day or two and it
> >> >> > happens
> >> >> > again. This happens on both DC's. We are running Windows server
> >> >> > 2003,
> >> >> > Standard edition, service pack 2. Any suggestions. Thanks.
> >> >>
> >> >> Have you changed the DNS configuration, too? When changing the IP
> >> >> addresses of the DCs, make sure that you also change their settings
> >> >> for
> >> >> "Primary" and "Secondary" DNS server so they are able to reach each
> >> >> other.
> >> >>
> >> >> also, have you checked whether you can successfully ping the FQDNs of
> >> >> the DCs as well as the domain name? Have you checked whether DNS has
> >> >> old
> >> >> IP references and clean them up?
> >> >>
> >> >> Cheers,
> >> >> Florian
> >> >> --
> >> >> Microsoft MVP - Group Policy
> >> >> eMail: prename [at] frickelsoft [dot] net.
> >> >> blog: http://www.frickelsoft.net/blog.
> >> >> Maillist (german):
> >> >> http://frickelsoft.net/cms/index.php?page=mailingliste
> >> >>
> >>
> >>
> >>
>
>
>

"Sarfraz Malik" <> wrote in message
news:1903F251-9F99-4222-838A-...
> Here is the Ipconfig from both DC's.
>
>
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : ssb21
> Primary Dns Suffix . . . . . . . : vcsa.uic.edu
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : vcsa.uic.edu
> ssbclient.uic.edu
> uic.edu
>
> Ethernet adapter Local Area Connection
>
> Connection-specific DNS Suffix . : ssbclient.uic.edu
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> Physical Address. . . . . . . . . : 00-06-5B-F3-89-21
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : xxx.xxx.121.11
> Subnet Mask . . . . . . . . . . . : 255.255.252.0
> Default Gateway . . . . . . . . . : xxx.xxx.120.1
> DHCP Server . . . . . . . . . . . : xxx.xxx.155.124
> DNS Servers . . . . . . . . . . . : xxx.xxx.121.11
> Primary WINS Server . . . . . . . : xxx.xxx.121.8
> Secondary WINS Server . . . . . . : xxx.xxx.121.45
> Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:05:34
> AM
> Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:21:34
> AM
>
>
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : ssb26
> Primary Dns Suffix . . . . . . . : vcsa.uic.edu
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : vcsa.uic.edu
> ssbclient.uic.edu
> uic.edu
>
> Ethernet adapter Local Area Connection 2:
> Connection-specific DNS Suffix . : ssbclient.uic.edu
> Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> #2
> Physical Address. . . . . . . . . : 00-0F-1F-67-78-32
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : xxx.xxx.121.25
> Subnet Mask . . . . . . . . . . . : 255.255.252.0
> Default Gateway . . . . . . . . . : xxx.xxx.120.1
> DHCP Server . . . . . . . . . . . : xxx.xxx.155.124
> DNS Servers . . . . . . . . . . . : xxx.xxx.121.25
> Primary WINS Server . . . . . . . : xxx.xxx.121.8
> Secondary WINS Server . . . . . . : xxx.xxx.121.45
> Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:10:09
> AM
> Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:26:09
> AM
>
> Thanks.
>

What I don't understand, is why are the DCs using DHCP??? DCs MUST be set to
a static configuration and never to use DHCP. If you set them with a static
configuration, do the problems disappear?

I would also suggest for each DC's DNS settings, to point to themselves
first (which they show, and is good), but to add the partner DC as the
second entry.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

They are getting the IP from DHCP but it is a fix IP, and never changes. In
DHCP server base on their mac address it gets a fix IP which never changes.
Will that make any difference. Thanks.

"Ace Fekay [MCT]" wrote:

> "Sarfraz Malik" <> wrote in message
> news:1903F251-9F99-4222-838A-...
> > Here is the Ipconfig from both DC's.
> >
> >
> > Windows IP Configuration
> > Host Name . . . . . . . . . . . . : ssb21
> > Primary Dns Suffix . . . . . . . : vcsa.uic.edu
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : vcsa.uic.edu
> > ssbclient.uic.edu
> > uic.edu
> >
> > Ethernet adapter Local Area Connection
> >
> > Connection-specific DNS Suffix . : ssbclient.uic.edu
> > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> > Physical Address. . . . . . . . . : 00-06-5B-F3-89-21
> > DHCP Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IP Address. . . . . . . . . . . . : xxx.xxx.121.11
> > Subnet Mask . . . . . . . . . . . : 255.255.252.0
> > Default Gateway . . . . . . . . . : xxx.xxx.120.1
> > DHCP Server . . . . . . . . . . . : xxx.xxx.155.124
> > DNS Servers . . . . . . . . . . . : xxx.xxx.121.11
> > Primary WINS Server . . . . . . . : xxx.xxx.121.8
> > Secondary WINS Server . . . . . . : xxx.xxx.121.45
> > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:05:34
> > AM
> > Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:21:34
> > AM
> >
> >
> >
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : ssb26
> > Primary Dns Suffix . . . . . . . : vcsa.uic.edu
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : vcsa.uic.edu
> > ssbclient.uic.edu
> > uic.edu
> >
> > Ethernet adapter Local Area Connection 2:
> > Connection-specific DNS Suffix . : ssbclient.uic.edu
> > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
> > #2
> > Physical Address. . . . . . . . . : 00-0F-1F-67-78-32
> > DHCP Enabled. . . . . . . . . . . : Yes
> > Autoconfiguration Enabled . . . . : Yes
> > IP Address. . . . . . . . . . . . : xxx.xxx.121.25
> > Subnet Mask . . . . . . . . . . . : 255.255.252.0
> > Default Gateway . . . . . . . . . : xxx.xxx.120.1
> > DHCP Server . . . . . . . . . . . : xxx.xxx.155.124
> > DNS Servers . . . . . . . . . . . : xxx.xxx.121.25
> > Primary WINS Server . . . . . . . : xxx.xxx.121.8
> > Secondary WINS Server . . . . . . : xxx.xxx.121.45
> > Lease Obtained. . . . . . . . . . : Thursday, September 03, 2009 9:10:09
> > AM
> > Lease Expires . . . . . . . . . . : Thursday, September 03, 2009 9:26:09
> > AM
> >
> > Thanks.
> >
>
> What I don't understand, is why are the DCs using DHCP??? DCs MUST be set to
> a static configuration and never to use DHCP. If you set them with a static
> configuration, do the problems disappear?
>
> I would also suggest for each DC's DNS settings, to point to themselves
> first (which they show, and is good), but to add the partner DC as the
> second entry.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
>