Can't join Win2k Pro Client to Domain after SUS Update

  • Thread starter Thread starter David Reed
  • Start date Start date
D

David Reed

Hello,

I have a user who did an update today from the SUS server. After the system
rebooted, she could no longer "connect to the internet".

Some examination on my part found out that she couldn't access the network
either, that even though she thought she was logging into the network, no
actual network connections were being made, and the login script (and hence,
the mapped folders on the Win2k Server with Active Directory server) wasn't
running. If I go to the RUN command and type:

\\servername\folder

I am then prompted for username and login, and I can access the folders on
the network, however.

Trying to fix this problem I reinstalled the NIC drivers. I also removed
the computer from the Domain and removed the DNS entry from the Forward
Lookup Zone.

Then I tried to re-join the Domain on the client computer.

I receive the following error:

"The following error occured validating the name 'srdcorp". This condition
mayb e caused by a DNS lookup problem. For information about
troubleshooting common DNS lookup problems, please see the following
Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=5171
The specified domain either does not exist or could not be contacted."

As described here
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp ) I have
also run the following commands on the client computer:

Right-click My Network Places, and then click Properties.
1.. Right-click Local Area Connection, and then click Properties.
2.. Click Internet Protocol (TCP/IP), and then click Properties.
3.. Click Advanced, and then click the DNS tab. Configure the DNS server
addresses to point to the DNS server that you configured in previous steps.
4.. Force the registration of the host (A) records. At a command prompt,
type ipconfig /flushdns and then press ENTER to purge the DNS resolver
cache. Type ipconfig /registerdns and then press ENTER to register the DNS
resource records.
If the ipconfig /registerdns command generates the following error message
Error: The system cannot find the file specified. : Refreshing DNS names
start and turn on the DHCP Client service on this computer, and then run the
ipconfig /registerdns command again.
I can't figure out why this computer can't find the domain, so I can join
it.

Can anyone offer some suggestions?

Thanks,
 
In
David Reed said:
Hello,

I have a user who did an update today from the SUS
server. After the system rebooted, she could no longer
"connect to the internet".

Some examination on my part found out that she couldn't
access the network either, that even though she thought
she was logging into the network, no actual network
connections were being made, and the login script (and
hence, the mapped folders on the Win2k Server with Active
Directory server) wasn't running. If I go to the RUN
command and type:

\\servername\folder

I am then prompted for username and login, and I can
access the folders on the network, however.

Trying to fix this problem I reinstalled the NIC drivers.
I also removed the computer from the Domain and removed
the DNS entry from the Forward Lookup Zone.

Then I tried to re-join the Domain on the client computer.

I receive the following error:

"The following error occured validating the name
'srdcorp". This condition mayb e caused by a DNS lookup
problem. For information about troubleshooting common
DNS lookup problems, please see the following Microsoft
Web site:
http://go.microsoft.com/fwlink/?LinkId=5171
The specified domain either does not exist or could not
be contacted."

As described here
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp
) I have also run the following commands on the client
computer:

Right-click My Network Places, and then click
Properties.
1.. Right-click Local Area Connection, and then click
Properties.
2.. Click Internet Protocol (TCP/IP), and then click
Properties.
3.. Click Advanced, and then click the DNS tab.
Configure the DNS server addresses to point to the DNS
server that you configured in previous steps.
4.. Force the registration of the host (A) records. At
a command prompt, type ipconfig /flushdns and then press
ENTER to purge the DNS resolver cache. Type ipconfig
/registerdns and then press ENTER to register the DNS
resource records. If the ipconfig /registerdns command
generates the following error message Error: The system
cannot find the file specified. : Refreshing DNS names
start and turn on the DHCP Client service on this
computer, and then run the ipconfig /registerdns command
again.
I can't figure out why this computer can't find the
domain, so I can join it.

Can anyone offer some suggestions?
Click to expand...

post results ipconfig /all and net start command
 
Host Name r0169-lcyr
Primary DNS Suffix srdcorp.com
Node type hybrid
IP routing enabled No
WINS Proxy Enabled No
DNS Suffic Search List srdcorp.com

Connection specific DNS Suffix srdcorp.com
Description 3Com 3c920 Integrated
FAst Etehrnet Controller (3C905C-TX Compatable)
DHCP Enabled Yes
Autoconifugration Enabled Yes
IP Address 172.16.4.54
Subnet Mask 255.255.0.0
Default Gateway 172.16.0.1
DHCP Server 172.16.1.1
DNS Servers 172.16.1.3
172.16.1.1
Lease Obtained Thursday, September 29, 2004
5:13:40 PM
Lease Expires Friday, October 01, 2004
5:13:40 PM

And when running NET START NETLOGON I receive the following:

The Net Logon service is starting.
The Net Logon service could not be started.
A service specific error occured: 3095.
More help is available by typing NET HELPMSG 3547

Thank-you,

David
 
In
David Reed said:
Host Name r0169-lcyr
Primary DNS Suffix srdcorp.com
Node type hybrid
IP routing enabled No
WINS Proxy Enabled No
DNS Suffic Search List srdcorp.com

Connection specific DNS Suffix srdcorp.com
Description 3Com
3c920 Integrated FAst Etehrnet Controller (3C905C-TX
Compatable)
DHCP Enabled Yes
Autoconifugration Enabled Yes
IP Address
172.16.4.54
Subnet Mask 255.255.0.0
Default Gateway 172.16.0.1
DHCP Server 172.16.1.1
DNS Servers 172.16.1.3 172.16.1.1
Click to expand...

Do both of these DNS servers have Zones for the AD Domain?



And when running NET START NETLOGON I receive the
following:

The Net Logon service is starting.
The Net Logon service could not be started.
A service specific error occured: 3095.
More help is available by typing NET HELPMSG 3547
Click to expand...

Wrong command, the command is 'net start' this lists the running services.
 
I don't know, but I would be happy to check and see.

I know 172.16.1.1 is the primary domain controller, and so I was suprised to
see that the DNS Server listed first (below) was 172.16.1.3, which is
supposed to function more as a backup.

If you can guide me on how to check that, I would be happy to do it. :)

Thank-you,

David
 
Although I do have to say I don't know why there might be a problem with the
server end of things. At this time, all other computers are on the network
and working fine. The only change that I know of is that the user installed
this update from the SUS server (which one I don't know, since they didn't
write down the update name before doing it), and it was immediately after
that that this computer wouldn't connect to the domain. :(

Thanks,

David
 
In
David Reed said:
I don't know, but I would be happy to check and see.

I know 172.16.1.1 is the primary domain controller, and
so I was suprised to see that the DNS Server listed first
(below) was 172.16.1.3, which is supposed to function
more as a backup.

If you can guide me on how to check that, I would be
happy to do it. :)
Click to expand...

What is the DNS at that address?
If it does not have a zone for the AD domain, you must remove it.
You _cannot_ use an external DNS in any position on any interface on a
member of an AD domain. All DNS servers must have a zone for the AD domain.

I'm going to be out for an hour or so we'll continue this conversation when
I return.
 
David Reed said:
I don't know, but I would be happy to check and see.

I know 172.16.1.1 is the primary domain controller, and so I was
suprised to see that the DNS Server listed first (below) was 172.16.1.3,
which is supposed to function more as a backup.
Click to expand...

If both DNS servers are running on DCs they more than likely have zones for
your domain.
Is there anything appearing in the system event log on the workstation that
would indicate a problem?

PS: AD domains don't have PDC's or BDC's anymore. They are all just DC's now
and are all equal, with the exception of a few specific roles.
 
Hi Kevin,

I appreciate that, and the note that you would be out an hour.

I'm sorry I didn't understand what you said, when you asked me what is the
DNS at that address. Do you mean what is the DNS server on our network? If
so, then 172.16.1.1 and 172.16.1.3 are the correct IPs for the primary and
backup DNS (in that order).

Thanks,

David
 
Hi Andrew,

hehehe...I knew someone would tag me on that. :) I know that, but I
continue to fall back on the phrase anyway. <LOL>

I don't see anything that jumps right out to me, but starting late yesterday
afternoon, about the time the update was done, I notice a lot of errors with
the Event ID #3034, and listing the source as MrxSmb...quite a lot of them
actually.

Maybe that has something to do with it?

David
 
David Reed said:
Hi Andrew,

hehehe...I knew someone would tag me on that. :) I know that, but I
continue to fall back on the phrase anyway. <LOL>

I don't see anything that jumps right out to me, but starting late
yesterday afternoon, about the time the update was done, I notice a lot
of errors with the Event ID #3034, and listing the source as
MrxSmb...quite a lot of them actually.

Maybe that has something to do with it?
Click to expand...

Most probably. Would you be able to provide the last D-Word value that
appears in the data of the error? (just provide the complete data if you are
not sure)

Is replication working ok between your 2 DNS servers ?
 
Now that everyone is scurrying around,...I have to ask,...since this all
worked before the update, and since the update is not very likely to have
changed any of these things,...the question is,...Is this machine an XP
machine?,...and did the update involve SP2?...and if so did you remember to
disable the Personal Firewall that the SP2 enables by default?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
 
Hello,

My apologies. No, it's a Windows 2000 Pro SP4 machine.

David

Phillip Windell said:
Now that everyone is scurrying around,...I have to ask,...since this all
worked before the update, and since the update is not very likely to have
changed any of these things,...the question is,...Is this machine an XP
machine?,...and did the update involve SP2?...and if so did you remember to
disable the Personal Firewall that the SP2 enables by default?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


David Reed said:
Hi Kevin,

I appreciate that, and the note that you would be out an hour.

I'm sorry I didn't understand what you said, when you asked me what is the
DNS at that address. Do you mean what is the DNS server on our network? If
so, then 172.16.1.1 and 172.16.1.3 are the correct IPs for the primary and
backup DNS (in that order).

Thanks,

David
Click to expand...
Click to expand...
 
Hi Andrew,

I probably could do that, if I knew how, or what to do to do that?

How do I check the replication between the 2 DNS servers?

David
 
Ok, I just wanted to check. I'm not sure about the possible cause other
than what already has been suggested.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

David Reed said:
Hello,

My apologies. No, it's a Windows 2000 Pro SP4 machine.

David

Phillip Windell said:
Now that everyone is scurrying around,...I have to ask,...since this all
worked before the update, and since the update is not very likely to have
changed any of these things,...the question is,...Is this machine an XP
machine?,...and did the update involve SP2?...and if so did you remember to
disable the Personal Firewall that the SP2 enables by default?


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


David Reed said:
Hi Kevin,

I appreciate that, and the note that you would be out an hour.

I'm sorry I didn't understand what you said, when you asked me what is the
DNS at that address. Do you mean what is the DNS server on our
Click to expand...
network?
If
so, then 172.16.1.1 and 172.16.1.3 are the correct IPs for the primary and
backup DNS (in that order).

Thanks,

David

In David Reed <[email protected]> commented
Then Kevin replied below:
I don't know, but I would be happy to check and see.

I know 172.16.1.1 is the primary domain controller, and
so I was suprised to see that the DNS Server listed first
(below) was 172.16.1.3, which is supposed to function
more as a backup.

If you can guide me on how to check that, I would be
happy to do it. :)

What is the DNS at that address?
If it does not have a zone for the AD domain, you must remove it.
You _cannot_ use an external DNS in any position on any interface on a
member of an AD domain. All DNS servers must have a zone for the AD
domain.

I'm going to be out for an hour or so we'll continue this conversation
when
I return.
Click to expand...
Click to expand...
Click to expand...
 
Phillip,

Okay.

I'm still dead in the water here.

I don't understand it, because I've got complete network connectivity. I
could even NET SEND a message from another computer on the network, and it
worked fine. It just won't let me join the domain.

ARGH!

HELP! :(

David
 
Here is a copy of the System Log, from the time the problems started until a
few minutes ago. :( The problem started right after the update at 2:58pm
on 09/23/04. It rebooted, and from then on wouldn't join the domain. :(

David
=====================

Type Date Time Source Category Event User Computer
Error 9/24/2004 11:58:14 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 11:58:14 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 11:58:14 AM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/24/2004 11:58:13 AM eventlog None 6005 N/A R0169-LCYR
Information 9/24/2004 11:58:13 AM eventlog None 6009 N/A R0169-LCYR
Information 9/24/2004 11:57:09 AM eventlog None 6006 N/A R0169-LCYR
Warning 9/24/2004 11:46:29 AM Dnsapi None 11185 N/A R0169-LCYR
Information 9/24/2004 11:46:18 AM Browser None 8033 N/A R0169-LCYR
Information 9/24/2004 11:26:21 AM Application Popup None 26 N/A R0169-LCYR
Error 9/24/2004 10:17:01 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 10:17:01 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 10:17:01 AM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/24/2004 10:17:00 AM eventlog None 6005 N/A R0169-LCYR
Information 9/24/2004 10:17:00 AM eventlog None 6009 N/A R0169-LCYR
Information 9/24/2004 10:16:01 AM eventlog None 6006 N/A R0169-LCYR
Error 9/24/2004 9:59:52 AM DCOM None 10010 Administrator R0169-LCYR
Error 9/24/2004 9:59:22 AM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/24/2004 9:59:22 AM DCOM None 10010 Administrator R0169-LCYR
Error 9/24/2004 9:58:53 AM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/24/2004 9:41:53 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 9:41:52 AM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/24/2004 9:41:52 AM eventlog None 6005 N/A R0169-LCYR
Information 9/24/2004 9:41:52 AM eventlog None 6009 N/A R0169-LCYR
Error 9/24/2004 9:41:52 AM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/24/2004 8:40:18 AM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/24/2004 8:40:18 AM Netlogon None 3095 N/A R0169-LCYR
Error 9/24/2004 3:52:53 AM DCOM None 10010 Administrator R0169-LCYR
Error 9/24/2004 3:52:23 AM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/24/2004 3:52:23 AM DCOM None 10010 Administrator R0169-LCYR
Error 9/24/2004 3:51:54 AM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/23/2004 9:52:52 PM DCOM None 10010 Administrator R0169-LCYR
Error 9/23/2004 9:52:22 PM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/23/2004 9:52:22 PM DCOM None 10010 Administrator R0169-LCYR
Error 9/23/2004 9:51:53 PM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/23/2004 5:12:36 PM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/23/2004 5:12:36 PM Netlogon None 3095 N/A R0169-LCYR
Error 9/23/2004 4:56:09 PM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/23/2004 4:56:09 PM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/23/2004 4:56:09 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 4:56:09 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 4:55:21 PM eventlog None 6006 N/A R0169-LCYR2
Information 9/23/2004 4:52:04 PM Browser None 8033 N/A R0169-LCYR2
Error 9/23/2004 4:40:02 PM Service Control Manager None 7000 N/A R0169-LCYR2
Error 9/23/2004 4:40:02 PM Service Control Manager None 7000 N/A R0169-LCYR2
Information 9/23/2004 4:40:01 PM eventlog None 6005 N/A R0169-LCYR2
Information 9/23/2004 4:40:01 PM eventlog None 6009 N/A R0169-LCYR2
Information 9/23/2004 4:36:11 PM eventlog None 6006 N/A R0169-LCYR2
Error 9/23/2004 4:23:49 PM Service Control Manager None 7000 N/A R0169-LCYR2
Error 9/23/2004 4:23:49 PM Service Control Manager None 7000 N/A R0169-LCYR2
Information 9/23/2004 4:23:49 PM eventlog None 6005 N/A R0169-LCYR2
Information 9/23/2004 4:23:49 PM eventlog None 6009 N/A R0169-LCYR2
Information 9/23/2004 4:23:06 PM eventlog None 6006 N/A R0169-LCYR2
Information 9/23/2004 4:22:32 PM Browser None 8033 N/A R0169-LCYR2
Error 9/23/2004 4:18:28 PM Service Control Manager None 7000 N/A R0169-LCYR2
Error 9/23/2004 4:18:28 PM Service Control Manager None 7000 N/A R0169-LCYR2
Information 9/23/2004 4:18:27 PM eventlog None 6005 N/A R0169-LCYR2
Information 9/23/2004 4:18:27 PM eventlog None 6009 N/A R0169-LCYR2
Information 9/23/2004 4:17:41 PM eventlog None 6006 N/A R0169-LCYR2
Error 9/23/2004 4:13:33 PM Service Control Manager None 7000 N/A R0169-LCYR2
Error 9/23/2004 4:13:33 PM Service Control Manager None 7000 N/A R0169-LCYR2
Information 9/23/2004 4:13:32 PM eventlog None 6005 N/A R0169-LCYR2
Information 9/23/2004 4:13:32 PM eventlog None 6009 N/A R0169-LCYR2
Information 9/23/2004 4:12:47 PM eventlog None 6006 N/A R0169-LCYR
Warning 9/23/2004 4:12:18 PM Dnsapi None 11184 N/A R0169-LCYR
Error 9/23/2004 4:10:40 PM Netlogon None 5719 N/A R0169-LCYR
Error 9/23/2004 4:10:31 PM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/23/2004 4:10:31 PM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/23/2004 4:10:30 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 4:10:30 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 4:09:28 PM eventlog None 6006 N/A R0169-LCYR
Warning 9/23/2004 4:09:21 PM Dnsapi None 11184 N/A R0169-LCYR
Warning 9/23/2004 4:09:19 PM Dnsapi None 11184 N/A R0169-LCYR
Warning 9/23/2004 4:07:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 4:07:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 4:07:47 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 4:07:47 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 4:07:47 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 4:07:47 PM MrxSmb None 3034 N/A R0169-LCYR
Error 9/23/2004 4:06:25 PM Netlogon None 5719 N/A R0169-LCYR
Error 9/23/2004 4:06:16 PM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/23/2004 4:06:16 PM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/23/2004 4:06:15 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 4:06:15 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 4:05:28 PM eventlog None 6006 N/A R0169-LCYR
Information 9/23/2004 4:05:15 PM NtServicePack None 4382 Administrator
R0169-LCYR
Error 9/23/2004 3:59:27 PM Service Control Manager None 7023 N/A R0169-LCYR
Error 9/23/2004 3:59:09 PM Netlogon None 5719 N/A R0169-LCYR
Error 9/23/2004 3:58:59 PM Service Control Manager None 7000 N/A R0169-LCYR
Error 9/23/2004 3:58:59 PM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/23/2004 3:58:59 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 3:58:59 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 3:57:58 PM eventlog None 6006 N/A R0169-LCYR
Information 9/23/2004 3:57:46 PM NtServicePack None 4382 Administrator
R0169-LCYR
Warning 9/23/2004 3:53:12 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:12 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:09 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:09 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:09 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:53:07 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:58 PM MrxSmb None 3034 N/A R0169-LCYR
Error 9/23/2004 3:51:47 PM DCOM None 10010 Administrator R0169-LCYR
Error 9/23/2004 3:51:17 PM Service Control Manager None 7024 N/A R0169-LCYR
Error 9/23/2004 3:51:17 PM DCOM None 10010 Administrator R0169-LCYR
Warning 9/23/2004 3:51:16 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:16 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:51:12 PM MrxSmb None 3034 N/A R0169-LCYR
Error 9/23/2004 3:50:47 PM Service Control Manager None 7024 N/A R0169-LCYR
Information 9/23/2004 3:36:48 PM Windows File Protection None 64004 N/A
R0169-LCYR
Warning 9/23/2004 3:34:37 PM Dnsapi None 11180 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:55 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:54 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:53 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:53 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:53 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:27:46 PM Dnsapi None 11184 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:59 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:58 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:57 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:57 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:57 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:26:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:27 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:23 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:22 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:21 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:21 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:21 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:21 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:23:13 PM Dnsapi None 11184 N/A R0169-LCYR
Information 9/23/2004 3:20:32 PM Windows File Protection None 64004 N/A
R0169-LCYR
Information 9/23/2004 3:19:13 PM Windows File Protection None 64004 N/A
R0169-LCYR
Warning 9/23/2004 3:16:51 PM W32Time None 11 N/A R0169-LCYR
Error 9/23/2004 3:16:46 PM Service Control Manager None 7023 N/A R0169-LCYR
Error 9/23/2004 3:16:13 PM Netlogon None 5719 N/A R0169-LCYR
Error 9/23/2004 3:16:08 PM Service Control Manager None 7000 N/A R0169-LCYR
Information 9/23/2004 3:16:08 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 3:16:08 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 3:15:25 PM eventlog None 6006 N/A R0169-LCYR
Warning 9/23/2004 3:14:44 PM Dnsapi None 11180 N/A R0169-LCYR
Error 9/23/2004 3:13:26 PM Server None 2505 N/A R0169-LCYR
Warning 9/23/2004 3:13:16 PM Dnsapi None 11184 N/A R0169-LCYR
Error 9/23/2004 3:13:11 PM Server None 2504 N/A R0169-LCYR
Warning 9/23/2004 3:13:00 PM Dnsapi None 11184 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:29 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:28 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:27 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:27 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:12:27 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:09:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:09:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:09:13 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:09:13 PM MrxSmb None 3034 N/A R0169-LCYR
Error 9/23/2004 3:09:02 PM Service Control Manager None 7023 N/A R0169-LCYR
Error 9/23/2004 3:08:41 PM Netlogon None 5719 N/A R0169-LCYR
Information 9/23/2004 3:08:31 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 3:08:31 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 3:07:43 PM eventlog None 6006 N/A R0169-LCYR
Warning 9/23/2004 3:05:51 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:05:51 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:05:48 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:05:48 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:04:06 PM MrxSmb None 3034 N/A R0169-LCYR
Warning 9/23/2004 3:04:06 PM MrxSmb None 3034 N/A R0169-LCYR
Error 9/23/2004 3:01:38 PM Service Control Manager None 7023 N/A R0169-LCYR
Error 9/23/2004 3:01:19 PM Netlogon None 5719 N/A R0169-LCYR
Information 9/23/2004 3:01:09 PM eventlog None 6005 N/A R0169-LCYR
Information 9/23/2004 3:01:09 PM eventlog None 6009 N/A R0169-LCYR
Information 9/23/2004 3:00:04 PM eventlog None 6006 N/A R0169-LCYR
Information 9/23/2004 2:58:34 PM Automatic Updates Installation 21 N/A
R0169-LCYR
Information 9/23/2004 2:58:34 PM Automatic Updates Installation 19 N/A
R0169-LCYR
Information 9/23/2004 2:53:31 PM Automatic Updates Installation 17 N/A
R0169-LCYR
Information 9/23/2004 12:35:18 PM Application Popup None 26 N/A R0169-LCYR
Information 9/23/2004 12:35:17 PM Application Popup None 26 N/A R0169-LCYR
Information 9/23/2004 12:35:16 PM Application Popup None 26 N/A R0169-LCYR
Information 9/23/2004 12:35:14 PM Application Popup None 26 N/A R0169-LCYR
Information 9/23/2004 11:41:34 AM Application Popup None 26 N/A R0169-LCYR
 
I also checked the Words, and it said the following:

0000: c000005e - Event ID 5719 Source: Net Logon (and)
0000: 000000ff - Event ID 6006

David
 
That last time it happened to me it was just a simple DNS setting. I had to
run only one DNS setting on the client and it had to be the AD/DNS. Once
the machine is "joined" there is a little bit more flexability, but it is
really picky before you get it joined. I also used a WINS Server that the
DC/DNS and the client both pointed to.
 
Back
Top