Re: Event Warning 40961 LSASRV
- From: "Todd J Heron" <todd_heron(delete)@hotmail.com>
- Date: Sat, 29 Oct 2005 16:18:35 -0400
Now that you've set the primary and secondary DNS servers in TCP/IP settings
on the NIC to be your own DNS servers, you will not see the LSASRV errors
(as you've confirmed). The reason is the system whether a DC or not will
attempt to register it's computer name into the DNS zone of it's primary DNS
suffix (which will be it's AD domain). Your ISP's server will not hold a
zone for your AD domain therefore the registration will fail.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
"The Vogon" <TheVogon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:13B44657-BCC8-4A3B-853A-B6D31DA9C792@xxxxxxxxxxxxxxxx
Thanks for the reply Todd...
Ok, but I'm curious now :-)
....the servers throwing the LSASRV error were in fact, amongst other things,
my primary and secondary DNS servers... and are on the same physical network
and subnet as my provider's DNS servers... I've set the primary and
secondary
DNS servers in TCP/IP settings on the NIC to be my own DNS servers, and as
yet haven't seen the LSASRV error... but why? Please note my servers are NOT
DC's and NOT using ADS :-S
The Vogon
.
- Follow-Ups:
- Re: Event Warning 40961 LSASRV
- From: The Vogon
- Re: Event Warning 40961 LSASRV
- References:
- Re: Event Warning 40961 LSASRV
- From: Todd J Heron
- Re: Event Warning 40961 LSASRV
- Prev by Date: After VPN conn. i am not able to ping local comp by NAME
- Next by Date: Re: VPN client adds wrong route to local route table
- Previous by thread: Re: Event Warning 40961 LSASRV
- Next by thread: Re: Event Warning 40961 LSASRV
- Index(es):
Relevant Pages
|
|