No Logon Server Available

I have a network consisting of one server and five machines... all
Win2K Pro and server is win2K Server Pro.

One and only one of the machines seems to lose connectivity to network
shares throughout the day. When she logs on in the morning, all is
fine, but within a couple hours, she can't see the share, and can't
remap a connection.

Any suggestions?

TIA,

Jason

Hi,

Are there any errors in Event logs (System and Applications logs)? Where
does preferred DNS server point to on this computer? Does it point to Active
Directory DNS server?

--
Mike
Microsoft MVP - Windows Security

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have a network consisting of one server and five machines... all
> Win2K Pro and server is win2K Server Pro.
>
> One and only one of the machines seems to lose connectivity to network
> shares throughout the day. When she logs on in the morning, all is
> fine, but within a couple hours, she can't see the share, and can't
> remap a connection.
>
> Any suggestions?
>
> TIA,
>
> Jason

These are two of the errors from the local machine...

Adapter-specific Domain Suffix : bcmb.ab.ca
DNS server list :
64.59.184.13, 64.59.184.15, 64.59.184.13
Sent update to server : None
IP Address(es) :
192.168.2.7

The reason the DNS update request could not be completed was
because of a system problem. You can manually retry DNS registration
of the network adapter and its settings by typing
"ipconfig /registerdns" at the command prompt. If problems
still persist, contact your DNS server or network systems
administrator. For specific error code information, see the
record data displayed below.

The system failed to register pointer (PTR) resource records (RRs)
for network adapter
with settings:

Adapter Name : {F9842BE3-CDC1-4516-8587-E9D12BB5D37E}
Host Name : bcmb-qm9tb96nx3
Adapter-specific Domain Suffix : bcmb.ab.ca
DNS server list :
64.59.184.13, 64.59.184.15, 64.59.184.13
Sent update to server : 192.175.48.1
IP Address : 192.168.2.7

The reason that the system could not register these RRs was because
the DNS server refused the update request. The cause of this could be
(a) your computer is not allowed to update the adapter-specified DNS
domain name, or (b) because the DNS server authoritative for the
specified name does not support the DNS dynamic update protocol.

To register the DNS pointer (PTR) resource records using the specific
DNS domain name and IP addresses for this adapter, contact your DNS
server or network systems administrator.

Hope this helps, thanks.

On Mon, 7 Nov 2005 19:36:01 +0100, "Miha Pihler [MVP]"
<mihap-(E-Mail Removed)> wrote:

>Hi,
>
>Are there any errors in Event logs (System and Applications logs)? Where
>does preferred DNS server point to on this computer? Does it point to Active
>Directory DNS server?

Hi,

Are your computers members of Active Directory domain?

If I am not mistaken IP addresses 64.59.184.13, 64.59.184.15, 64.59.184.13
point to your ISP DNS servers?

If your computers are member of Active Directory domain they should point to
your internal Active Directory DNS server and not your ISP. Computers that
are members of domain use DNS server to locate domain controllers on the
network. Since you told your clients to use your ISP DNS and your ISP
doesn't know anything about your domain controllers -- your clients fail to
find Logon Servers...

--
Mike
Microsoft MVP - Windows Security

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> These are two of the errors from the local machine...
>
> Adapter-specific Domain Suffix : bcmb.ab.ca
> DNS server list :
> 64.59.184.13, 64.59.184.15, 64.59.184.13
> Sent update to server : None
> IP Address(es) :
> 192.168.2.7
>
> The reason the DNS update request could not be completed was
> because of a system problem. You can manually retry DNS registration
> of the network adapter and its settings by typing
> "ipconfig /registerdns" at the command prompt. If problems
> still persist, contact your DNS server or network systems
> administrator. For specific error code information, see the
> record data displayed below.
>
> The system failed to register pointer (PTR) resource records (RRs)
> for network adapter
> with settings:
>
> Adapter Name : {F9842BE3-CDC1-4516-8587-E9D12BB5D37E}
> Host Name : bcmb-qm9tb96nx3
> Adapter-specific Domain Suffix : bcmb.ab.ca
> DNS server list :
> 64.59.184.13, 64.59.184.15, 64.59.184.13
> Sent update to server : 192.175.48.1
> IP Address : 192.168.2.7
>
> The reason that the system could not register these RRs was because
> the DNS server refused the update request. The cause of this could be
> (a) your computer is not allowed to update the adapter-specified DNS
> domain name, or (b) because the DNS server authoritative for the
> specified name does not support the DNS dynamic update protocol.
>
> To register the DNS pointer (PTR) resource records using the specific
> DNS domain name and IP addresses for this adapter, contact your DNS
> server or network systems administrator.
>
> Hope this helps, thanks.
>
> On Mon, 7 Nov 2005 19:36:01 +0100, "Miha Pihler [MVP]"
> <mihap-(E-Mail Removed)> wrote:
>
>>Hi,
>>
>>Are there any errors in Event logs (System and Applications logs)? Where
>>does preferred DNS server point to on this computer? Does it point to
>>Active
>>Directory DNS server?

Mike,

Thanks for the response.

I am unsure if you respond to your e-mail account listed here, but
will ask my question here as well.

Excuse my ignorance, but I am fairly new to active directory. I
believe I have disovered the name of the active directory dns server,
but it is a name server. The only place I can find to change dns on
local machine asks for an ip address...

If you could quickly explain, I would be indebted.

Thanks,

Jason

On Tue, 8 Nov 2005 08:35:10 +0100, "Miha Pihler [MVP]"
<mihap-(E-Mail Removed)> wrote:

>Hi,
>
>Are your computers members of Active Directory domain?
>
>If I am not mistaken IP addresses 64.59.184.13, 64.59.184.15, 64.59.184.13
>point to your ISP DNS servers?
>
>If your computers are member of Active Directory domain they should point to
>your internal Active Directory DNS server and not your ISP. Computers that
>are members of domain use DNS server to locate domain controllers on the
>network. Since you told your clients to use your ISP DNS and your ISP
>doesn't know anything about your domain controllers -- your clients fail to
>find Logon Servers...

Hi,

Sorry for my ignorance, but I appreciate the help, but how do I change where
the dns points to....
> From the local computer, I should select properties from Network
> Neighborhood right click and change in TCP/IP settings?

Yes, if these are not your Active Directory DNS servers "64.59.184.13,
64.59.184.15, 64.59.184.13" you will have to change thes IP addresses
(preferred DNS servers) on the client under TCP/IP settings to point to your
AD DNS servers.

If you are using DHCP server to configure the clients with IP address,
subnet masks and DNS settings -- you can change configuration that clients
get there...

--
Mike
Microsoft MVP - Windows Security

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Mike,
>
> Thanks for the response.
>
> I am unsure if you respond to your e-mail account listed here, but
> will ask my question here as well.
>
> Excuse my ignorance, but I am fairly new to active directory. I
> believe I have disovered the name of the active directory dns server,
> but it is a name server. The only place I can find to change dns on
> local machine asks for an ip address...
>
> If you could quickly explain, I would be indebted.
>
> Thanks,
>
> Jason
>
> On Tue, 8 Nov 2005 08:35:10 +0100, "Miha Pihler [MVP]"
> <mihap-(E-Mail Removed)> wrote:
>
>>Hi,
>>
>>Are your computers members of Active Directory domain?
>>
>>If I am not mistaken IP addresses 64.59.184.13, 64.59.184.15, 64.59.184.13
>>point to your ISP DNS servers?
>>
>>If your computers are member of Active Directory domain they should point
>>to
>>your internal Active Directory DNS server and not your ISP. Computers that
>>are members of domain use DNS server to locate domain controllers on the
>>network. Since you told your clients to use your ISP DNS and your ISP
>>doesn't know anything about your domain controllers -- your clients fail
>>to
>>find Logon Servers...