This is a situation that started a couple of days ago.

It started first with DHCP attempting to assign a dynamic IP address to a
second NIC in my Exchange 2000 server with SP4 and Exchange SP3 and all
patches. I deleted the IP address in the leased DHCP list and the
corresponding address in DNS and disabled the second NIC and all was well.

The next day, out of the blue, the IP address of the Exchange server was
missing from the list. Again, I manually placed it back in the DNS list and
all was well.

I did not set this server up from the beginning and discovered that DNS
scavenging is disabled. I have not enabled it because everything was fine for
a lengthy time. I have a single AD domain with Windows 2000 domain
controllers. I have a Primary and Secondary DNS server both running Windows
2000. Please advise.
--
sputnik

In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
sputnik <(E-Mail Removed)> typed:
> This is a situation that started a couple of days ago.
>
> It started first with DHCP attempting to assign a dynamic IP address
> to a second NIC in my Exchange 2000 server with SP4 and Exchange SP3
> and all patches. I deleted the IP address in the leased DHCP list and
> the corresponding address in DNS and disabled the second NIC and all
> was well.
>
> The next day, out of the blue, the IP address of the Exchange server
> was missing from the list. Again, I manually placed it back in the
> DNS list and all was well.
>
> I did not set this server up from the beginning and discovered that
> DNS scavenging is disabled. I have not enabled it because everything
> was fine for a lengthy time. I have a single AD domain with Windows
> 2000 domain controllers. I have a Primary and Secondary DNS server
> both running Windows 2000. Please advise.

If you run ipconfig /registerdns on the Exchange box, does it work?
Event logs giving you any errors?

Lanwench,

I haven't tried this yet. Is there any impact on the box if I do? Typically,
this is transparent to the user, however, I want to avoid unneccessary
disconnects. I have seen some interesting issues lately. I'll wait to hear
from you. Thanks a million!
--
sputnik


"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
> sputnik <(E-Mail Removed)> typed:
> > This is a situation that started a couple of days ago.
> >
> > It started first with DHCP attempting to assign a dynamic IP address
> > to a second NIC in my Exchange 2000 server with SP4 and Exchange SP3
> > and all patches. I deleted the IP address in the leased DHCP list and
> > the corresponding address in DNS and disabled the second NIC and all
> > was well.
> >
> > The next day, out of the blue, the IP address of the Exchange server
> > was missing from the list. Again, I manually placed it back in the
> > DNS list and all was well.
> >
> > I did not set this server up from the beginning and discovered that
> > DNS scavenging is disabled. I have not enabled it because everything
> > was fine for a lengthy time. I have a single AD domain with Windows
> > 2000 domain controllers. I have a Primary and Secondary DNS server
> > both running Windows 2000. Please advise.
>
> If you run ipconfig /registerdns on the Exchange box, does it work?
> Event logs giving you any errors?
>
>
>
>

In news:330236AD-DA47-4A47-BF1E-(E-Mail Removed),
sputnik <(E-Mail Removed)> typed:
> Lanwench,
>
> I haven't tried this yet. Is there any impact on the box if I do?

Shouldn't, at least no negative one.

> Typically, this is transparent to the user, however, I want to avoid
> unneccessary disconnects. I have seen some interesting issues lately.
> I'll wait to hear from you. Thanks a million!

What symptoms/problems are your users experiencing now?


>
>>
>>
>> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
>> sputnik <(E-Mail Removed)> typed:
>>> This is a situation that started a couple of days ago.
>>>
>>> It started first with DHCP attempting to assign a dynamic IP address
>>> to a second NIC in my Exchange 2000 server with SP4 and Exchange SP3
>>> and all patches. I deleted the IP address in the leased DHCP list
>>> and the corresponding address in DNS and disabled the second NIC
>>> and all was well.
>>>
>>> The next day, out of the blue, the IP address of the Exchange server
>>> was missing from the list. Again, I manually placed it back in the
>>> DNS list and all was well.
>>>
>>> I did not set this server up from the beginning and discovered that
>>> DNS scavenging is disabled. I have not enabled it because everything
>>> was fine for a lengthy time. I have a single AD domain with Windows
>>> 2000 domain controllers. I have a Primary and Secondary DNS server
>>> both running Windows 2000. Please advise.
>>
>> If you run ipconfig /registerdns on the Exchange box, does it work?
>> Event logs giving you any errors?

I ran the ipconfig/registerdns. I'll provide an update as the issue unfolds.
Your feedback is much appreciated.
--
sputnik


"sputnik" wrote:

> This is a situation that started a couple of days ago.
>
> It started first with DHCP attempting to assign a dynamic IP address to a
> second NIC in my Exchange 2000 server with SP4 and Exchange SP3 and all
> patches. I deleted the IP address in the leased DHCP list and the
> corresponding address in DNS and disabled the second NIC and all was well.
>
> The next day, out of the blue, the IP address of the Exchange server was
> missing from the list. Again, I manually placed it back in the DNS list and
> all was well.
>
> I did not set this server up from the beginning and discovered that DNS
> scavenging is disabled. I have not enabled it because everything was fine for
> a lengthy time. I have a single AD domain with Windows 2000 domain
> controllers. I have a Primary and Secondary DNS server both running Windows
> 2000. Please advise.
> --
> sputnik

The problem that the end-user experiences is simply that the server host
record suddenly dissappears and the users are disconnected from the Exchange
Server. I have to intervene at this stage.
--
sputnik


"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:330236AD-DA47-4A47-BF1E-(E-Mail Removed),
> sputnik <(E-Mail Removed)> typed:
> > Lanwench,
> >
> > I haven't tried this yet. Is there any impact on the box if I do?
>
> Shouldn't, at least no negative one.
>
> > Typically, this is transparent to the user, however, I want to avoid
> > unneccessary disconnects. I have seen some interesting issues lately.
> > I'll wait to hear from you. Thanks a million!
>
> What symptoms/problems are your users experiencing now?
>
>
> >
> >>
> >>
> >> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
> >> sputnik <(E-Mail Removed)> typed:
> >>> This is a situation that started a couple of days ago.
> >>>
> >>> It started first with DHCP attempting to assign a dynamic IP address
> >>> to a second NIC in my Exchange 2000 server with SP4 and Exchange SP3
> >>> and all patches. I deleted the IP address in the leased DHCP list
> >>> and the corresponding address in DNS and disabled the second NIC
> >>> and all was well.
> >>>
> >>> The next day, out of the blue, the IP address of the Exchange server
> >>> was missing from the list. Again, I manually placed it back in the
> >>> DNS list and all was well.
> >>>
> >>> I did not set this server up from the beginning and discovered that
> >>> DNS scavenging is disabled. I have not enabled it because everything
> >>> was fine for a lengthy time. I have a single AD domain with Windows
> >>> 2000 domain controllers. I have a Primary and Secondary DNS server
> >>> both running Windows 2000. Please advise.
> >>
> >> If you run ipconfig /registerdns on the Exchange box, does it work?
> >> Event logs giving you any errors?
>
>
>

In news:CFBD806E-1155-47FE-A479-(E-Mail Removed),
sputnik <(E-Mail Removed)> typed:
> The problem that the end-user experiences is simply that the server
> host record suddenly dissappears and the users are disconnected from
> the Exchange Server. I have to intervene at this stage.

OK, yes, I reckon that's not good. Did you try /registerDNS ?
>
>>
>>
>> In news:330236AD-DA47-4A47-BF1E-(E-Mail Removed),
>> sputnik <(E-Mail Removed)> typed:
>>> Lanwench,
>>>
>>> I haven't tried this yet. Is there any impact on the box if I do?
>>
>> Shouldn't, at least no negative one.
>>
>>> Typically, this is transparent to the user, however, I want to avoid
>>> unneccessary disconnects. I have seen some interesting issues
>>> lately. I'll wait to hear from you. Thanks a million!
>>
>> What symptoms/problems are your users experiencing now?
>>
>>
>>>
>>>>
>>>>
>>>> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
>>>> sputnik <(E-Mail Removed)> typed:
>>>>> This is a situation that started a couple of days ago.
>>>>>
>>>>> It started first with DHCP attempting to assign a dynamic IP
>>>>> address to a second NIC in my Exchange 2000 server with SP4 and
>>>>> Exchange SP3 and all patches. I deleted the IP address in the
>>>>> leased DHCP list and the corresponding address in DNS and
>>>>> disabled the second NIC and all was well.
>>>>>
>>>>> The next day, out of the blue, the IP address of the Exchange
>>>>> server was missing from the list. Again, I manually placed it
>>>>> back in the DNS list and all was well.
>>>>>
>>>>> I did not set this server up from the beginning and discovered
>>>>> that DNS scavenging is disabled. I have not enabled it because
>>>>> everything was fine for a lengthy time. I have a single AD domain
>>>>> with Windows 2000 domain controllers. I have a Primary and
>>>>> Secondary DNS server both running Windows 2000. Please advise.
>>>>
>>>> If you run ipconfig /registerdns on the Exchange box, does it work?
>>>> Event logs giving you any errors?

Lanwench,

I tried registerDNS and so far so good! I'll keep you posted. You are kind.
--
sputnik


"Lanwench [MVP - Exchange]" wrote:

>
>
> In news:CFBD806E-1155-47FE-A479-(E-Mail Removed),
> sputnik <(E-Mail Removed)> typed:
> > The problem that the end-user experiences is simply that the server
> > host record suddenly dissappears and the users are disconnected from
> > the Exchange Server. I have to intervene at this stage.
>
> OK, yes, I reckon that's not good. Did you try /registerDNS ?
> >
> >>
> >>
> >> In news:330236AD-DA47-4A47-BF1E-(E-Mail Removed),
> >> sputnik <(E-Mail Removed)> typed:
> >>> Lanwench,
> >>>
> >>> I haven't tried this yet. Is there any impact on the box if I do?
> >>
> >> Shouldn't, at least no negative one.
> >>
> >>> Typically, this is transparent to the user, however, I want to avoid
> >>> unneccessary disconnects. I have seen some interesting issues
> >>> lately. I'll wait to hear from you. Thanks a million!
> >>
> >> What symptoms/problems are your users experiencing now?
> >>
> >>
> >>>
> >>>>
> >>>>
> >>>> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
> >>>> sputnik <(E-Mail Removed)> typed:
> >>>>> This is a situation that started a couple of days ago.
> >>>>>
> >>>>> It started first with DHCP attempting to assign a dynamic IP
> >>>>> address to a second NIC in my Exchange 2000 server with SP4 and
> >>>>> Exchange SP3 and all patches. I deleted the IP address in the
> >>>>> leased DHCP list and the corresponding address in DNS and
> >>>>> disabled the second NIC and all was well.
> >>>>>
> >>>>> The next day, out of the blue, the IP address of the Exchange
> >>>>> server was missing from the list. Again, I manually placed it
> >>>>> back in the DNS list and all was well.
> >>>>>
> >>>>> I did not set this server up from the beginning and discovered
> >>>>> that DNS scavenging is disabled. I have not enabled it because
> >>>>> everything was fine for a lengthy time. I have a single AD domain
> >>>>> with Windows 2000 domain controllers. I have a Primary and
> >>>>> Secondary DNS server both running Windows 2000. Please advise.
> >>>>
> >>>> If you run ipconfig /registerdns on the Exchange box, does it work?
> >>>> Event logs giving you any errors?
>
>
>

In news:02B1DA60-BC5A-435F-B0D0-(E-Mail Removed),
sputnik <(E-Mail Removed)> typed:
> Lanwench,
>
> I tried registerDNS and so far so good!

Glad to hear it....

> I'll keep you posted. You are
> kind.

Kind of what? ;-)

..
>
>>
>>
>> In news:CFBD806E-1155-47FE-A479-(E-Mail Removed),
>> sputnik <(E-Mail Removed)> typed:
>>> The problem that the end-user experiences is simply that the server
>>> host record suddenly dissappears and the users are disconnected from
>>> the Exchange Server. I have to intervene at this stage.
>>
>> OK, yes, I reckon that's not good. Did you try /registerDNS ?
>>>
>>>>
>>>>
>>>> In news:330236AD-DA47-4A47-BF1E-(E-Mail Removed),
>>>> sputnik <(E-Mail Removed)> typed:
>>>>> Lanwench,
>>>>>
>>>>> I haven't tried this yet. Is there any impact on the box if I do?
>>>>
>>>> Shouldn't, at least no negative one.
>>>>
>>>>> Typically, this is transparent to the user, however, I want to
>>>>> avoid unneccessary disconnects. I have seen some interesting
>>>>> issues lately. I'll wait to hear from you. Thanks a million!
>>>>
>>>> What symptoms/problems are your users experiencing now?
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> In news:C0060CBA-218F-4040-BDCA-(E-Mail Removed),
>>>>>> sputnik <(E-Mail Removed)> typed:
>>>>>>> This is a situation that started a couple of days ago.
>>>>>>>
>>>>>>> It started first with DHCP attempting to assign a dynamic IP
>>>>>>> address to a second NIC in my Exchange 2000 server with SP4 and
>>>>>>> Exchange SP3 and all patches. I deleted the IP address in the
>>>>>>> leased DHCP list and the corresponding address in DNS and
>>>>>>> disabled the second NIC and all was well.
>>>>>>>
>>>>>>> The next day, out of the blue, the IP address of the Exchange
>>>>>>> server was missing from the list. Again, I manually placed it
>>>>>>> back in the DNS list and all was well.
>>>>>>>
>>>>>>> I did not set this server up from the beginning and discovered
>>>>>>> that DNS scavenging is disabled. I have not enabled it because
>>>>>>> everything was fine for a lengthy time. I have a single AD
>>>>>>> domain with Windows 2000 domain controllers. I have a Primary
>>>>>>> and Secondary DNS server both running Windows 2000. Please
>>>>>>> advise.
>>>>>>
>>>>>> If you run ipconfig /registerdns on the Exchange box, does it
>>>>>> work? Event logs giving you any errors?