Sign in with
Sign up | Sign in
Your question

Why doesnt this w2k client register in DNS?

Last response: in Windows 2000/NT
Share
Anonymous
December 25, 2004 11:56:49 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi all:


Merry Christmas to all the great people here,
and a thousand thanks for all the support
I have received in the past here!



w2k adv server, w2k pro client

Why doesn't this client register in dns?


event ID 11151

Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11151
Date: 12/22/2004
Time: 10:23:12 PM
User: N/A
Computer: HAL9000
Description:
The system failed to register network adapter with settings:

Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
Host Name : hal9000
Adapter-specific Domain Suffix : jewelconsulting.org
DNS server list :
64.233.217.3, 64.233.217.2
Sent update to server : None
IP Address(es) :
10.0.0.10

The cause of this DNS registration failure was because of DNS server
failure. This may be due to a zone transfer that has locked the DNS server
for the applicable zone that your computer needs to register itself with.

(The applicable zone should typically correspond to the Adapter-specific
Domain Suffix that was indicated above.) You can manually retry registration
of the network adapter and its settings by typing "ipconfig /registerdns" at
the command prompt. If problems still persist, contact your network systems
administrator to verify network conditions.
Data:
0000: 2a 23 00 00 *#..



ipconfig/all:

C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : hal9000
Primary DNS Suffix . . . . . . . : jewelconsulting.org
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jewelconsulting.org

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 64.233.217.3
64.233.217.2

C:\Documents and Settings\Administrator.JEWELCONSULTING>


Thank you in advance!

James W. Long
Anonymous
December 26, 2004 1:17:25 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com,
James W. Long <JamesLong@wowway.com> made a post then I commented below
:: Hi all:
::
::
:: Merry Christmas to all the great people here,
:: and a thousand thanks for all the support
:: I have received in the past here!
::
::
::
:: w2k adv server, w2k pro client
::
:: Why doesn't this client register in dns?
::
::
:: event ID 11151
::
:: Event Type: Warning
:: Event Source: DnsApi
:: Event Category: None
:: Event ID: 11151
:: Date: 12/22/2004
:: Time: 10:23:12 PM
:: User: N/A
:: Computer: HAL9000
:: Description:
:: The system failed to register network adapter with settings:
::
:: Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
:: Host Name : hal9000
:: Adapter-specific Domain Suffix : jewelconsulting.org
:: DNS server list :
:: 64.233.217.3, 64.233.217.2
:: Sent update to server : None
:: IP Address(es) :
:: 10.0.0.10
::
:: The cause of this DNS registration failure was because of DNS server
:: failure. This may be due to a zone transfer that has locked the DNS
:: server for the applicable zone that your computer needs to register
:: itself with.
::
:: (The applicable zone should typically correspond to the
:: Adapter-specific Domain Suffix that was indicated above.) You can
:: manually retry registration of the network adapter and its settings
:: by typing "ipconfig /registerdns" at the command prompt. If problems
:: still persist, contact your network systems administrator to verify
:: network conditions.
:: Data:
:: 0000: 2a 23 00 00 *#..
::
::
::
:: ipconfig/all:
::
:: C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all
::
:: Windows 2000 IP Configuration
::
:: Host Name . . . . . . . . . . . . : hal9000
:: Primary DNS Suffix . . . . . . . : jewelconsulting.org
:: Node Type . . . . . . . . . . . . : Broadcast
:: IP Routing Enabled. . . . . . . . : No
:: WINS Proxy Enabled. . . . . . . . : No
:: DNS Suffix Search List. . . . . . : jewelconsulting.org
::
:: Ethernet adapter Local Area Connection:
::
:: Connection-specific DNS Suffix . :
:: Description . . . . . . . . . . . : Marvell Yukon 88E8053
:: PCI-E Gigabit Ethernet Controller
:: Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
:: DHCP Enabled. . . . . . . . . . . : No
:: IP Address. . . . . . . . . . . . : 10.0.0.10
:: Subnet Mask . . . . . . . . . . . : 255.255.255.0
:: Default Gateway . . . . . . . . . : 10.0.0.1
:: DNS Servers . . . . . . . . . . . : 64.233.217.3
:: 64.233.217.2
::
:: C:\Documents and Settings\Administrator.JEWELCONSULTING>
::
::
:: Thank you in advance!
::
:: James W. Long



Merry Christmas to you too James!! Hope you had a nice one.

Nice to see you in the group again.

As for your issue, the reason why you are getting this problem, and I know
we've discussed this thoroughly in the past, is because you are using your
ISP's DNS servers in your machines. It's sending the updates to them.

I know we've discussed this and why you cannot use your ISP's DNS. Remove
them and configure a forwarder, PLEASE!!!!!

Ace
Anonymous
December 26, 2004 2:24:26 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Ace has it right.
> DNS server list : 64.233.217.3, 64.233.217.2
> IP Address: 10.0.0.10

You should (must) use only the INTERNAL DNS
server on the INTERNAL DNS client machines
(NIC->IP properties).

You will likely want to FORWARD from your
internal DNS servers to that ISP DNS you are
incorrectly using on the internal machine.

DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:

nltest /dsregdns /server:D C-ServerNameGoesHere

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

The only people/machines which can (safely) use
the ISP DNS server directly are those machines
which have no internal DNS servers -- i.e., which
have no NEED to resolve or register internal names.

--
Herb Martin


"James W. Long" <JamesLong@wowway.com> wrote in message
news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com...
> Hi all:
>
>
> Merry Christmas to all the great people here,
> and a thousand thanks for all the support
> I have received in the past here!
>
>
>
> w2k adv server, w2k pro client
>
> Why doesn't this client register in dns?
>
>
> event ID 11151
>
> Event Type: Warning
> Event Source: DnsApi
> Event Category: None
> Event ID: 11151
> Date: 12/22/2004
> Time: 10:23:12 PM
> User: N/A
> Computer: HAL9000
> Description:
> The system failed to register network adapter with settings:
>
> Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
> Host Name : hal9000
> Adapter-specific Domain Suffix : jewelconsulting.org
> DNS server list :
> 64.233.217.3, 64.233.217.2
> Sent update to server : None
> IP Address(es) :
> 10.0.0.10
>
> The cause of this DNS registration failure was because of DNS server
> failure. This may be due to a zone transfer that has locked the DNS server
> for the applicable zone that your computer needs to register itself with.
>
> (The applicable zone should typically correspond to the Adapter-specific
> Domain Suffix that was indicated above.) You can manually retry
registration
> of the network adapter and its settings by typing "ipconfig /registerdns"
at
> the command prompt. If problems still persist, contact your network
systems
> administrator to verify network conditions.
> Data:
> 0000: 2a 23 00 00 *#..
>
>
>
> ipconfig/all:
>
> C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : hal9000
> Primary DNS Suffix . . . . . . . : jewelconsulting.org
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : jewelconsulting.org
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E
> Gigabit Ethernet Controller
> Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.0.0.10
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.0.0.1
> DNS Servers . . . . . . . . . . . : 64.233.217.3
> 64.233.217.2
>
> C:\Documents and Settings\Administrator.JEWELCONSULTING>
>
>
> Thank you in advance!
>
> James W. Long
>
>
>
>
>
Related resources
Anonymous
December 26, 2004 3:59:54 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

Dear Ace and Herb:

Hope yours was good as well!


I cant believe this again again again, its a new install and either I put
those
in to to do a ms windows update before I joined the domain
I think, or, I put them in because the dc was not up after I had it joined,
either way, I forgot all about them.

geez.

Lets see if that clears up a couple other thingz too. AD will be hapier.

Thank you guys

"dont break the cardinal rule - only 1 dns server "

James





"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:o SOy3lv6EHA.1596@tk2msftngp13.phx.gbl...
> In news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com,
> James W. Long <JamesLong@wowway.com> made a post then I commented below
> :: Hi all:
> ::
> ::
> :: Merry Christmas to all the great people here,
> :: and a thousand thanks for all the support
> :: I have received in the past here!
> ::
> ::
> ::
> :: w2k adv server, w2k pro client
> ::
> :: Why doesn't this client register in dns?
> ::
> ::
> :: event ID 11151
> ::
> :: Event Type: Warning
> :: Event Source: DnsApi
> :: Event Category: None
> :: Event ID: 11151
> :: Date: 12/22/2004
> :: Time: 10:23:12 PM
> :: User: N/A
> :: Computer: HAL9000
> :: Description:
> :: The system failed to register network adapter with settings:
> ::
> :: Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
> :: Host Name : hal9000
> :: Adapter-specific Domain Suffix : jewelconsulting.org
> :: DNS server list :
> :: 64.233.217.3, 64.233.217.2
> :: Sent update to server : None
> :: IP Address(es) :
> :: 10.0.0.10
> ::
> :: The cause of this DNS registration failure was because of DNS server
> :: failure. This may be due to a zone transfer that has locked the DNS
> :: server for the applicable zone that your computer needs to register
> :: itself with.
> ::
> :: (The applicable zone should typically correspond to the
> :: Adapter-specific Domain Suffix that was indicated above.) You can
> :: manually retry registration of the network adapter and its settings
> :: by typing "ipconfig /registerdns" at the command prompt. If problems
> :: still persist, contact your network systems administrator to verify
> :: network conditions.
> :: Data:
> :: 0000: 2a 23 00 00 *#..
> ::
> ::
> ::
> :: ipconfig/all:
> ::
> :: C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all
> ::
> :: Windows 2000 IP Configuration
> ::
> :: Host Name . . . . . . . . . . . . : hal9000
> :: Primary DNS Suffix . . . . . . . : jewelconsulting.org
> :: Node Type . . . . . . . . . . . . : Broadcast
> :: IP Routing Enabled. . . . . . . . : No
> :: WINS Proxy Enabled. . . . . . . . : No
> :: DNS Suffix Search List. . . . . . : jewelconsulting.org
> ::
> :: Ethernet adapter Local Area Connection:
> ::
> :: Connection-specific DNS Suffix . :
> :: Description . . . . . . . . . . . : Marvell Yukon 88E8053
> :: PCI-E Gigabit Ethernet Controller
> :: Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
> :: DHCP Enabled. . . . . . . . . . . : No
> :: IP Address. . . . . . . . . . . . : 10.0.0.10
> :: Subnet Mask . . . . . . . . . . . : 255.255.255.0
> :: Default Gateway . . . . . . . . . : 10.0.0.1
> :: DNS Servers . . . . . . . . . . . : 64.233.217.3
> :: 64.233.217.2
> ::
> :: C:\Documents and Settings\Administrator.JEWELCONSULTING>
> ::
> ::
> :: Thank you in advance!
> ::
> :: James W. Long
>
>
>
> Merry Christmas to you too James!! Hope you had a nice one.
>
> Nice to see you in the group again.
>
> As for your issue, the reason why you are getting this problem, and I know
> we've discussed this thoroughly in the past, is because you are using your
> ISP's DNS servers in your machines. It's sending the updates to them.
>
> I know we've discussed this and why you cannot use your ISP's DNS. Remove
> them and configure a forwarder, PLEASE!!!!!
>
> Ace
>
>
Anonymous
December 26, 2004 3:59:55 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

"James W. Long" <JamesLong@wowway.com> wrote in message
news:eYOdne97i7fUzlPcRVn-3A@wideopenwest.com...
> Dear Ace and Herb:
>
> Hope yours was good as well!

We're all good. Thanks.

> I cant believe this again again again, its a new install and either I
put
> those
> in to to do a ms windows update before I joined the domain

Not a good reason -- there is no requirement to be a
domain member to use the DNS server. Just put the
correct (internal one) in anyway.

> I think, or, I put them in because the dc was not up after I had it
joined,
> either way, I forgot all about them.

Well, that makes sense -- send yourself an email when
you do such stuff or write it down if you are prone to
forget (and especially if you haven't pretty much
memorize AND more importantly UNDERSTOOD what
is happening here.)

After you understand it you can fix it almost without
thinking.

It will be one of the first things you will think to check.

(BTW, that is how Ace and I know even though we cannot
touch or see your system. We know how it has to work and
how it is easily fouled up.)

> geez.
>
> Lets see if that clears up a couple other thingz too. AD will be hapier.
>
> Thank you guys
>
> "dont break the cardinal rule - only 1 dns server "


--
Herb Martin


>
> James
>
>
>
>
>
> "Ace Fekay [MVP]"
> <PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
> message news:o SOy3lv6EHA.1596@tk2msftngp13.phx.gbl...
> > In news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com,
> > James W. Long <JamesLong@wowway.com> made a post then I commented below
> > :: Hi all:
> > ::
> > ::
> > :: Merry Christmas to all the great people here,
> > :: and a thousand thanks for all the support
> > :: I have received in the past here!
> > ::
> > ::
> > ::
> > :: w2k adv server, w2k pro client
> > ::
> > :: Why doesn't this client register in dns?
> > ::
> > ::
> > :: event ID 11151
> > ::
> > :: Event Type: Warning
> > :: Event Source: DnsApi
> > :: Event Category: None
> > :: Event ID: 11151
> > :: Date: 12/22/2004
> > :: Time: 10:23:12 PM
> > :: User: N/A
> > :: Computer: HAL9000
> > :: Description:
> > :: The system failed to register network adapter with settings:
> > ::
> > :: Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
> > :: Host Name : hal9000
> > :: Adapter-specific Domain Suffix : jewelconsulting.org
> > :: DNS server list :
> > :: 64.233.217.3, 64.233.217.2
> > :: Sent update to server : None
> > :: IP Address(es) :
> > :: 10.0.0.10
> > ::
> > :: The cause of this DNS registration failure was because of DNS server
> > :: failure. This may be due to a zone transfer that has locked the DNS
> > :: server for the applicable zone that your computer needs to register
> > :: itself with.
> > ::
> > :: (The applicable zone should typically correspond to the
> > :: Adapter-specific Domain Suffix that was indicated above.) You can
> > :: manually retry registration of the network adapter and its settings
> > :: by typing "ipconfig /registerdns" at the command prompt. If problems
> > :: still persist, contact your network systems administrator to verify
> > :: network conditions.
> > :: Data:
> > :: 0000: 2a 23 00 00 *#..
> > ::
> > ::
> > ::
> > :: ipconfig/all:
> > ::
> > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all
> > ::
> > :: Windows 2000 IP Configuration
> > ::
> > :: Host Name . . . . . . . . . . . . : hal9000
> > :: Primary DNS Suffix . . . . . . . : jewelconsulting.org
> > :: Node Type . . . . . . . . . . . . : Broadcast
> > :: IP Routing Enabled. . . . . . . . : No
> > :: WINS Proxy Enabled. . . . . . . . : No
> > :: DNS Suffix Search List. . . . . . : jewelconsulting.org
> > ::
> > :: Ethernet adapter Local Area Connection:
> > ::
> > :: Connection-specific DNS Suffix . :
> > :: Description . . . . . . . . . . . : Marvell Yukon 88E8053
> > :: PCI-E Gigabit Ethernet Controller
> > :: Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
> > :: DHCP Enabled. . . . . . . . . . . : No
> > :: IP Address. . . . . . . . . . . . : 10.0.0.10
> > :: Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > :: Default Gateway . . . . . . . . . : 10.0.0.1
> > :: DNS Servers . . . . . . . . . . . : 64.233.217.3
> > :: 64.233.217.2
> > ::
> > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>
> > ::
> > ::
> > :: Thank you in advance!
> > ::
> > :: James W. Long
> >
> >
> >
> > Merry Christmas to you too James!! Hope you had a nice one.
> >
> > Nice to see you in the group again.
> >
> > As for your issue, the reason why you are getting this problem, and I
know
> > we've discussed this thoroughly in the past, is because you are using
your
> > ISP's DNS servers in your machines. It's sending the updates to them.
> >
> > I know we've discussed this and why you cannot use your ISP's DNS.
Remove
> > them and configure a forwarder, PLEASE!!!!!
> >
> > Ace
> >
> >
>
>
Anonymous
December 26, 2004 3:59:55 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

"James W. Long" <JamesLong@wowway.com> wrote in message
news:eYOdne97i7fUzlPcRVn-3A@wideopenwest.com...
> Dear Ace and Herb:
>
> Hope yours was good as well!

We're all good. Thanks.

> I cant believe this again again again, its a new install and either I
put
> those
> in to to do a ms windows update before I joined the domain

Not a good reason -- there is no requirement to be a
domain member to use the DNS server. Just put the
correct (internal one) in anyway.

> I think, or, I put them in because the dc was not up after I had it
joined,
> either way, I forgot all about them.

Well, that makes sense -- send yourself an email when
you do such stuff or write it down if you are prone to
forget (and especially if you haven't pretty much
memorize AND more importantly UNDERSTOOD what
is happening here.)

After you understand it you can fix it almost without
thinking.

It will be one of the first things you will think to check.

(BTW, that is how Ace and I know even though we cannot
touch or see your system. We know how it has to work and
how it is easily fouled up.)

> geez.
> Lets see if that clears up a couple other thingz too. AD will be hapier.
> Thank you guys
> "dont break the cardinal rule - only 1 dns server "

I don't believe that is a cardinal rule or even a rule at
all.

The real rule would be:

Make sure your DNS service is RELIABLE.

IF that means 2 or more then that is what you must do,
but if you make the MAIN DNS server reliable that
can work also.

We (me at least) keep wondering why your DC/DNS
server is down so much. There is the REAL problem
to overcome.

It should not be down more than it takes to reboot
after updates or VERY SELDOM to put in a new
piece of hardware (memory etc.)

Think about this: You likely only have ONE connection
to the Internet and it that goes down you are basically
out of service too.

If service is/were critical, that would also be an issue.

--
Herb Martin


>
> James
>
>
>
>
>
> "Ace Fekay [MVP]"
> <PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
> message news:o SOy3lv6EHA.1596@tk2msftngp13.phx.gbl...
> > In news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com,
> > James W. Long <JamesLong@wowway.com> made a post then I commented below
> > :: Hi all:
> > ::
> > ::
> > :: Merry Christmas to all the great people here,
> > :: and a thousand thanks for all the support
> > :: I have received in the past here!
> > ::
> > ::
> > ::
> > :: w2k adv server, w2k pro client
> > ::
> > :: Why doesn't this client register in dns?
> > ::
> > ::
> > :: event ID 11151
> > ::
> > :: Event Type: Warning
> > :: Event Source: DnsApi
> > :: Event Category: None
> > :: Event ID: 11151
> > :: Date: 12/22/2004
> > :: Time: 10:23:12 PM
> > :: User: N/A
> > :: Computer: HAL9000
> > :: Description:
> > :: The system failed to register network adapter with settings:
> > ::
> > :: Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
> > :: Host Name : hal9000
> > :: Adapter-specific Domain Suffix : jewelconsulting.org
> > :: DNS server list :
> > :: 64.233.217.3, 64.233.217.2
> > :: Sent update to server : None
> > :: IP Address(es) :
> > :: 10.0.0.10
> > ::
> > :: The cause of this DNS registration failure was because of DNS server
> > :: failure. This may be due to a zone transfer that has locked the DNS
> > :: server for the applicable zone that your computer needs to register
> > :: itself with.
> > ::
> > :: (The applicable zone should typically correspond to the
> > :: Adapter-specific Domain Suffix that was indicated above.) You can
> > :: manually retry registration of the network adapter and its settings
> > :: by typing "ipconfig /registerdns" at the command prompt. If problems
> > :: still persist, contact your network systems administrator to verify
> > :: network conditions.
> > :: Data:
> > :: 0000: 2a 23 00 00 *#..
> > ::
> > ::
> > ::
> > :: ipconfig/all:
> > ::
> > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig /all
> > ::
> > :: Windows 2000 IP Configuration
> > ::
> > :: Host Name . . . . . . . . . . . . : hal9000
> > :: Primary DNS Suffix . . . . . . . : jewelconsulting.org
> > :: Node Type . . . . . . . . . . . . : Broadcast
> > :: IP Routing Enabled. . . . . . . . : No
> > :: WINS Proxy Enabled. . . . . . . . : No
> > :: DNS Suffix Search List. . . . . . : jewelconsulting.org
> > ::
> > :: Ethernet adapter Local Area Connection:
> > ::
> > :: Connection-specific DNS Suffix . :
> > :: Description . . . . . . . . . . . : Marvell Yukon 88E8053
> > :: PCI-E Gigabit Ethernet Controller
> > :: Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
> > :: DHCP Enabled. . . . . . . . . . . : No
> > :: IP Address. . . . . . . . . . . . : 10.0.0.10
> > :: Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > :: Default Gateway . . . . . . . . . : 10.0.0.1
> > :: DNS Servers . . . . . . . . . . . : 64.233.217.3
> > :: 64.233.217.2
> > ::
> > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>
> > ::
> > ::
> > :: Thank you in advance!
> > ::
> > :: James W. Long
> >
> >
> >
> > Merry Christmas to you too James!! Hope you had a nice one.
> >
> > Nice to see you in the group again.
> >
> > As for your issue, the reason why you are getting this problem, and I
know
> > we've discussed this thoroughly in the past, is because you are using
your
> > ISP's DNS servers in your machines. It's sending the updates to them.
> >
> > I know we've discussed this and why you cannot use your ISP's DNS.
Remove
> > them and configure a forwarder, PLEASE!!!!!
> >
> > Ace
> >
> >
>
>
Anonymous
December 26, 2004 5:04:50 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:u1jX5Qx6EHA.1404@TK2MSFTNGP11.phx.gbl,
Herb Martin <news@LearnQuick.com> made a post then I commented below
:: (BTW, that is how Ace and I know even though we cannot
:: touch or see your system. We know how it has to work and
:: how it is easily fouled up.)

Yep, I agree. A quick peek at the config usually shows it right away.
Anonymous
December 26, 2004 6:31:21 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

Dear Herb:


ok,

> We (me at least) keep wondering why your DC/DNS
> server is down so much. There is the REAL problem
> to overcome.

I have a couple different networks,
one at home, one at work, both domains.
so theres been a couple different situations I ask about here.

The first time I ever did a win2k dc upgrade from winnt 4.0 server
I did not know any better, so that was that issue,. this past spring.
everything was different even the dns mmc. wow big change.
I did not know about SRV records and forwarders and dynamic updates,
and single name domains. I was still back in winnt 4.0 server land
which I had running great for about 5 years on the same PDC box.
It's incredible what I learned from you guys.


On the lan at work the clients were not properly configged to use
one dns server, (thier dc) when I became employed there this past summer.
They were configged to use multiple dns servers that went
around thier dc by dhcp. so I fixed that. even thier MS Exchange
was configged to use mult DNS servers and that too is a NO-NO.
That was that issue, and the dc never goes down except for a reboot or hw
install
as you say. that dns server is reliable. its a dell 2650 with raid and
backed up by (tape,well backed up) with Gold support and its
mission crittical, so it stays up.

on that note- at work there is no secondary dns server
and I have it scheduled to config an existing member dc
for that purpose.

The upgraded lan at home was fine till recently I toasted (a client)
hal9000's mobo and let the smoke out. It had to be reloaded and just
got configged wrong. I ASSUMED the Repaired system was
ALREADY straight. (because it USED to BE) LOL, and I forgot I changed it!
This is my home workstation from which I test alot of stuff.
It also happens to have all the latest greatest stuff on it,
and is interfaced to my Ham Radios, Midi Keyboards
Digital Communications gear, Digital Camera, I have a few
hobbies......

I turn off that domain controller at home every nite.
so, thats why that dc is not up all the time at home.
once in a while I might elect to bypass the dc
like now when I needed internet to reload this puppy.

I am lucky in that I have have a domain at home
to check stuff out on, and its no mistake that I planned
it that way. its a tool I use to learn stuff for my profession,
and if you guys werent here I'd be totally LOST.
I can't thank you all enough!


James W. Long

"Herb Martin" <news@LearnQuick.com> wrote in message
news:o IxR1Ux6EHA.2012@TK2MSFTNGP15.phx.gbl...
> "James W. Long" <JamesLong@wowway.com> wrote in message
> news:eYOdne97i7fUzlPcRVn-3A@wideopenwest.com...
> > Dear Ace and Herb:
> >
> > Hope yours was good as well!
>
> We're all good. Thanks.
>
> > I cant believe this again again again, its a new install and either I
> put
> > those
> > in to to do a ms windows update before I joined the domain
>
> Not a good reason -- there is no requirement to be a
> domain member to use the DNS server. Just put the
> correct (internal one) in anyway.

yes, I did noticed that. that is cool that a workstation can use
the domain dns server without being a member of the domain.


>
> > I think, or, I put them in because the dc was not up after I had it
> joined,
> > either way, I forgot all about them.
>
> Well, that makes sense -- send yourself an email when
> you do such stuff or write it down if you are prone to
> forget (and especially if you haven't pretty much
> memorize AND more importantly UNDERSTOOD what
> is happening here.)
>
> After you understand it you can fix it almost without
> thinking.
>
> It will be one of the first things you will think to check.
>
> (BTW, that is how Ace and I know even though we cannot
> touch or see your system. We know how it has to work and
> how it is easily fouled up.)
>
> > geez.
> > Lets see if that clears up a couple other thingz too. AD will be hapier.
> > Thank you guys
> > "dont break the cardinal rule - only 1 dns server "
>
> I don't believe that is a cardinal rule or even a rule at
> all.
>
> The real rule would be:
>
> Make sure your DNS service is RELIABLE.
>
> IF that means 2 or more then that is what you must do,
> but if you make the MAIN DNS server reliable that
> can work also.
>
> We (me at least) keep wondering why your DC/DNS
> server is down so much. There is the REAL problem
> to overcome.
>
> It should not be down more than it takes to reboot
> after updates or VERY SELDOM to put in a new
> piece of hardware (memory etc.)
>
> Think about this: You likely only have ONE connection
> to the Internet and it that goes down you are basically
> out of service too.
>
> If service is/were critical, that would also be an issue.
>
> --
> Herb Martin
>
>
> >
> > James
> >
> >
> >
> >
> >
> > "Ace Fekay [MVP]"
> > <PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
> > message news:o SOy3lv6EHA.1596@tk2msftngp13.phx.gbl...
> > > In news:D _-dnU3N0NPah1PcRVn-gA@wideopenwest.com,
> > > James W. Long <JamesLong@wowway.com> made a post then I commented
below
> > > :: Hi all:
> > > ::
> > > ::
> > > :: Merry Christmas to all the great people here,
> > > :: and a thousand thanks for all the support
> > > :: I have received in the past here!
> > > ::
> > > ::
> > > ::
> > > :: w2k adv server, w2k pro client
> > > ::
> > > :: Why doesn't this client register in dns?
> > > ::
> > > ::
> > > :: event ID 11151
> > > ::
> > > :: Event Type: Warning
> > > :: Event Source: DnsApi
> > > :: Event Category: None
> > > :: Event ID: 11151
> > > :: Date: 12/22/2004
> > > :: Time: 10:23:12 PM
> > > :: User: N/A
> > > :: Computer: HAL9000
> > > :: Description:
> > > :: The system failed to register network adapter with settings:
> > > ::
> > > :: Adapter Name : {76E87BCB-41A8-440C-95C4-8586665FE1BF}
> > > :: Host Name : hal9000
> > > :: Adapter-specific Domain Suffix : jewelconsulting.org
> > > :: DNS server list :
> > > :: 64.233.217.3, 64.233.217.2
> > > :: Sent update to server : None
> > > :: IP Address(es) :
> > > :: 10.0.0.10
> > > ::
> > > :: The cause of this DNS registration failure was because of DNS
server
> > > :: failure. This may be due to a zone transfer that has locked the DNS
> > > :: server for the applicable zone that your computer needs to register
> > > :: itself with.
> > > ::
> > > :: (The applicable zone should typically correspond to the
> > > :: Adapter-specific Domain Suffix that was indicated above.) You can
> > > :: manually retry registration of the network adapter and its settings
> > > :: by typing "ipconfig /registerdns" at the command prompt. If
problems
> > > :: still persist, contact your network systems administrator to verify
> > > :: network conditions.
> > > :: Data:
> > > :: 0000: 2a 23 00 00 *#..
> > > ::
> > > ::
> > > ::
> > > :: ipconfig/all:
> > > ::
> > > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>ipconfig
/all
> > > ::
> > > :: Windows 2000 IP Configuration
> > > ::
> > > :: Host Name . . . . . . . . . . . . : hal9000
> > > :: Primary DNS Suffix . . . . . . . : jewelconsulting.org
> > > :: Node Type . . . . . . . . . . . . : Broadcast
> > > :: IP Routing Enabled. . . . . . . . : No
> > > :: WINS Proxy Enabled. . . . . . . . : No
> > > :: DNS Suffix Search List. . . . . . : jewelconsulting.org
> > > ::
> > > :: Ethernet adapter Local Area Connection:
> > > ::
> > > :: Connection-specific DNS Suffix . :
> > > :: Description . . . . . . . . . . . : Marvell Yukon 88E8053
> > > :: PCI-E Gigabit Ethernet Controller
> > > :: Physical Address. . . . . . . . . : 00-11-2F-4E-65-9A
> > > :: DHCP Enabled. . . . . . . . . . . : No
> > > :: IP Address. . . . . . . . . . . . : 10.0.0.10
> > > :: Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > :: Default Gateway . . . . . . . . . : 10.0.0.1
> > > :: DNS Servers . . . . . . . . . . . : 64.233.217.3
> > > :: 64.233.217.2
> > > ::
> > > :: C:\Documents and Settings\Administrator.JEWELCONSULTING>
> > > ::
> > > ::
> > > :: Thank you in advance!
> > > ::
> > > :: James W. Long
> > >
> > >
> > >
> > > Merry Christmas to you too James!! Hope you had a nice one.
> > >
> > > Nice to see you in the group again.
> > >
> > > As for your issue, the reason why you are getting this problem, and I
> know
> > > we've discussed this thoroughly in the past, is because you are using
> your
> > > ISP's DNS servers in your machines. It's sending the updates to them.
> > >
> > > I know we've discussed this and why you cannot use your ISP's DNS.
> Remove
> > > them and configure a forwarder, PLEASE!!!!!
> > >
> > > Ace
> > >
> > >
> >
> >
>
>
>
Anonymous
December 26, 2004 9:42:36 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

> > We (me at least) keep wondering why your DC/DNS
> > server is down so much. There is the REAL problem
> > to overcome.
>
> I have a couple different networks,
> one at home, one at work, both domains.
> so theres been a couple different situations I ask about here.
>
> The first time I ever did a win2k dc upgrade from winnt 4.0 server
> I did not know any better, so that was that issue,. this past spring.
> everything was different even the dns mmc. wow big change.

I was focusing on the seeming lack of reliability of
your DC once you had it working correctly.

> I did not know about SRV records and forwarders and dynamic updates,
> and single name domains. I was still back in winnt 4.0 server land
> which I had running great for about 5 years on the same PDC box.
> It's incredible what I learned from you guys.

Pretty much no one does at first. (Including me.)

> On the lan at work the clients were not properly configged to use
> one dns server, (thier dc) when I became employed there this past summer.

Remember the key word is not "one" but rather the "INTERNAL"
DNS server (set).

> They were configged to use multiple dns servers that went
> around thier dc by dhcp. so I fixed that. even thier MS Exchange
> was configged to use mult DNS servers and that too is a NO-NO.

Again, it is not the "multiple" that makes it wrong but rather
that they are not part of the INTERNAL SET of DNS servers.
One or more, but only from the correct set.

> That was that issue, and the dc never goes down except for a reboot or hw
> install
> as you say. that dns server is reliable. its a dell 2650 with raid and
> backed up by (tape,well backed up) with Gold support and its
> mission crittical, so it stays up.

Then using only the Internal -- even only one -- DNS server
will be no big deal since it will (practically) always be
available for forwarding for Internet resolution.

> on that note- at work there is no secondary dns server
> and I have it scheduled to config an existing member dc
> for that purpose.

And this is still a good practice to make it more reliable.

> The upgraded lan at home was fine till recently I toasted (a client)
> hal9000's mobo and let the smoke out. It had to be reloaded and just
> got configged wrong. I ASSUMED the Repaired system was
> ALREADY straight. (because it USED to BE) LOL, and I forgot I changed it!

This is what I was trying to point out -- not to say "we know"
but rather to try to call to your attention that when you have
such problems YOU have the information and know the tools
to straighten it out.

This is not because we don't like helping either -- obviously
we spend a lot of time and effort just reading and typing
comments -- but because I personally believe the greatest
help we can give you is to to show you how to work it out.

It's an example of the old saying: Give a man a fish and
you feed him for a day; teach him to fish and you feed him
for a lifetime.

> This is my home workstation from which I test alot of stuff.
> It also happens to have all the latest greatest stuff on it,
> and is interfaced to my Ham Radios, Midi Keyboards
> Digital Communications gear, Digital Camera, I have a few
> hobbies......

Don't we all <grin>

> I turn off that domain controller at home every nite.
> so, thats why that dc is not up all the time at home.
> once in a while I might elect to bypass the dc
> like now when I needed internet to reload this puppy.

Maybe a cheapo DC or even just an extra DNS
server would be useful on your net. A couple of
hundred dollars buys an amazing machine of just
a few years ago that most people will sneer at
today -- I have a handful of those things for testing
and such and they really are quite good machines.
(300Mhz Pentiums with 128 Meg is about average.)

> I am lucky in that I have have a domain at home
> to check stuff out on, and its no mistake that I planned
> it that way. its a tool I use to learn stuff for my profession,
> and if you guys werent here I'd be totally LOST.
> I can't thank you all enough!

This also argues for very frequent system state backups.
(Maybe even automated on a scheduled task backup.)
Anonymous
December 27, 2004 1:57:49 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:HIidneteytngglLcRVn-pw@wideopenwest.com,
James W. Long <JamesLong@wowway.com> made a post then I commented below
:: I am lucky in that I have have a domain at home
:: to check stuff out on, and its no mistake that I planned
:: it that way. its a tool I use to learn stuff for my profession,
:: and if you guys werent here I'd be totally LOST.
:: I can't thank you all enough!
::

I'm glad we were able to help you out. As for the DC at home, maybe as Herb
said, use a low end PC for that function, especially since you'll need it up
all the time for DNS, and that you are really not using it for anything
else. I leave my machines at home on all the time. Save the powerful
workstation for yourself.

:-)

Ace
Anonymous
December 27, 2004 10:48:26 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

Dear Ace:

Oh yes definately. My DC is a Dell GX1 P3 running 500 MHZ,
and my workstation is a P5 3GHZ Asus with I gig ram.
The DC just puts along but then it doesnt have any other
services on it.

I put another w2k Adv DC on a Dell dimension 266 with 128 meg ram
running DNS and it still works fine. not a problem for messing with.
but in either case If I were putting serious services on either,
I would need more thoughtput as in ram/drives/cpu etc.

James

"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:u44XAh86EHA.1300@TK2MSFTNGP14.phx.gbl...
> In news:HIidneteytngglLcRVn-pw@wideopenwest.com,
> James W. Long <JamesLong@wowway.com> made a post then I commented below
> :: I am lucky in that I have have a domain at home
> :: to check stuff out on, and its no mistake that I planned
> :: it that way. its a tool I use to learn stuff for my profession,
> :: and if you guys werent here I'd be totally LOST.
> :: I can't thank you all enough!
> ::
>
> I'm glad we were able to help you out. As for the DC at home, maybe as
Herb
> said, use a low end PC for that function, especially since you'll need it
up
> all the time for DNS, and that you are really not using it for anything
> else. I leave my machines at home on all the time. Save the powerful
> workstation for yourself.
>
> :-)
>
> Ace
>
>
Anonymous
December 28, 2004 3:02:01 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:eGZzd.3655$7g7.2624@newssvr31.news.prodigy.com,
James W. Long <JamesLong@Dunhamshq.com> made a post then I commented below
:: Dear Ace:
::
:: Oh yes definately. My DC is a Dell GX1 P3 running 500 MHZ,
:: and my workstation is a P5 3GHZ Asus with I gig ram.
:: The DC just puts along but then it doesnt have any other
:: services on it.
::
:: I put another w2k Adv DC on a Dell dimension 266 with 128 meg ram
:: running DNS and it still works fine. not a problem for messing with.
:: but in either case If I were putting serious services on either,
:: I would need more thoughtput as in ram/drives/cpu etc.
::
:: James

Sounds good. Then it doesn't matter if you leave the machine running so DNS
is always up.

Ace
Anonymous
December 28, 2004 3:49:40 AM

Archived from groups: microsoft.public.win2000.dns (More info?)

> :: I put another w2k Adv DC on a Dell dimension 266 with 128 meg ram
> :: running DNS and it still works fine. not a problem for messing with.
> :: but in either case If I were putting serious services on either,
> :: I would need more thoughtput as in ram/drives/cpu etc.
> ::
> :: James
>
> Sounds good. Then it doesn't matter if you leave the machine running so
DNS
> is always up.

Yes, and you would be surprised how well
some of these "little old" machines will do
when they only have 3 clients. <grin>


--
Herb Martin


"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@hotmail.com> wrote in
message news:eqQzjpJ7EHA.3416@TK2MSFTNGP09.phx.gbl...
> In news:eGZzd.3655$7g7.2624@newssvr31.news.prodigy.com,
> James W. Long <JamesLong@Dunhamshq.com> made a post then I commented below
> :: Dear Ace:
> ::
> :: Oh yes definately. My DC is a Dell GX1 P3 running 500 MHZ,
> :: and my workstation is a P5 3GHZ Asus with I gig ram.
> :: The DC just puts along but then it doesnt have any other
> :: services on it.
> ::
> :: I put another w2k Adv DC on a Dell dimension 266 with 128 meg ram
> :: running DNS and it still works fine. not a problem for messing with.
> :: but in either case If I were putting serious services on either,
> :: I would need more thoughtput as in ram/drives/cpu etc.
> ::
> :: James
>
> Sounds good. Then it doesn't matter if you leave the machine running so
DNS
> is always up.
>
> Ace
>
>
Anonymous
December 28, 2004 9:18:25 PM

Archived from groups: microsoft.public.win2000.dns (More info?)

In news:eTtphqK7EHA.2700@TK2MSFTNGP14.phx.gbl,
Herb Martin <news@LearnQuick.com> made a post then I commented below
::: Sounds good. Then it doesn't matter if you leave the machine
::: running so DNS is always up.
::
:: Yes, and you would be surprised how well
:: some of these "little old" machines will do
:: when they only have 3 clients. <grin>

True!
!