Netlogon error 5783 after SP4

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello group,

I recently rolled out service pack 4 to about 150 windows 2000 professional
clients on my windows 2003 AD domain using group policy software installation.

Immediately following the update (2-4 hours) a good number of these clients
started showing a Netlogon error in the system event log. The txt of the log
follows:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5783
Date: 1/11/2006
Time: 9:34:38 AM
User: N/A
Computer: COMPUTER
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller
\\server.domain.com for the domain domain is not responsive. The current RPC
call from Netlogon on \\computer to \\server.domain.com has been cancelled.

An exhaustive search of the event logs on these machines reveals that the
error, in all cases, occurs directly after installing SP4 with the GPO. There
doesn't seem to be a pattern for the errors but they are consistent and
seemingly directly a result of the SP install. A reboot allows the client to
continue to work but the error crops up again within a couple of hours.
Clients are still able to connect to the Exchange server using Outlook 200x
but attempts to access network resources like mapped drives and shares fail.
Most users report that they see the offline icon in the system tray when the
problem happens. That would seem to point to the networking client or the
TCP/IP protocol stack but that's a guess

The Netlogon error seems to spawn numerous UserEnv 1000 errors to do with
failing to process policy objects in SYSVOL.

I've found a host of information on the www about the error but none of it
seems to apply to this particular situation. Most often it relates to Citrix
and Norton AV 2002 both of which we don't use.

I tried reinstalling the SP locally but the error ultimately returns.

This hasn't happened in all cases (perhaps 25%) and we are using a standard
image on identical hardware in a 100% packet switched environment.

Since SP4 is not an optional component (KB912919 requires it) I need to get
this corrected so I can make the lambs stop screaming so to speak.

Any advice and/or direction from users or MS PSS professionals cruising
these forums will really save my bacon.

Best,

JPenrose MCSE MCSA
 
it could be the DNS issue. any errors if using this command line: dcdiag /test:registerindns /dnsdomain ?


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hello group,

I recently rolled out service pack 4 to about 150 windows 2000 professional
clients on my windows 2003 AD domain using group policy software installation.

Immediately following the update (2-4 hours) a good number of these clients
started showing a Netlogon error in the system event log. The txt of the log
follows:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5783
Date: 1/11/2006
Time: 9:34:38 AM
User: N/A
Computer: COMPUTER
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller
\\server.domain.com for the domain domain is not responsive. The current RPC
call from Netlogon on \\computer to \\server.domain.com has been cancelled.

An exhaustive search of the event logs on these machines reveals that the
error, in all cases, occurs directly after installing SP4 with the GPO. There
doesn't seem to be a pattern for the errors but they are consistent and
seemingly directly a result of the SP install. A reboot allows the client to
continue to work but the error crops up again within a couple of hours.
Clients are still able to connect to the Exchange server using Outlook 200x
but attempts to access network resources like mapped drives and shares fail.
Most users report that they see the offline icon in the system tray when the
problem happens. That would seem to point to the networking client or the
TCP/IP protocol stack but that's a guess

The Netlogon error seems to spawn numerous UserEnv 1000 errors to do with
failing to process policy objects in SYSVOL.

I've found a host of information on the www about the error but none of it
seems to apply to this particular situation. Most often it relates to Citrix
and Norton AV 2002 both of which we don't use.

I tried reinstalling the SP locally but the error ultimately returns.

This hasn't happened in all cases (perhaps 25%) and we are using a standard
image on identical hardware in a 100% packet switched environment.

Since SP4 is not an optional component (KB912919 requires it) I need to get
this corrected so I can make the lambs stop screaming so to speak.

Any advice and/or direction from users or MS PSS professionals cruising
these forums will really save my bacon.

Best,

JPenrose MCSE MCSA
 
Hi Bob,

Thank you for the reply.

The issue is unique to Win2K clients and only then after SP4. The Windows
Server 2003 Domain Controllers are clean and the dcdiag/netdiag tests I ran
on them checked out 100%.

Are you suggesting that this command will reveal registration problems for
clients when run on the DC? The client is connecting to the exchange 2003
server which needs contact with a DC for global catalog so I'm not sure I
have a DNS issue. An IPconfig /all on the client shows all the correct
information including both DNS servers and WINS servers. It appears to be RPC
communications that fail.

I'm wondering if the SP rewrites portions of the IP stack and/or the network
client which has hosed some of the computers? Maybe ripping out the protocol
and MS client and reinstalling them would do it. The SP deployed over the
network via a GPO so that may have caused the issue if the connection wasn't
stable through the whole process.

The crappy thing about this is the lack of relevant info about netlogon 5783
and SP4. If I'm having the issue then surely someone else has too.

I'm almost ready to breakdown and call PSS.

Best,
J Penrose MCSE MCSA
 
If this is not DNS issue, then use rpcping to troubleshoot RPC issues.


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi Bob,

Thank you for the reply.

The issue is unique to Win2K clients and only then after SP4. The Windows
Server 2003 Domain Controllers are clean and the dcdiag/netdiag tests I ran
on them checked out 100%.

Are you suggesting that this command will reveal registration problems for
clients when run on the DC? The client is connecting to the exchange 2003
server which needs contact with a DC for global catalog so I'm not sure I
have a DNS issue. An IPconfig /all on the client shows all the correct
information including both DNS servers and WINS servers. It appears to be RPC
communications that fail.

I'm wondering if the SP rewrites portions of the IP stack and/or the network
client which has hosed some of the computers? Maybe ripping out the protocol
and MS client and reinstalling them would do it. The SP deployed over the
network via a GPO so that may have caused the issue if the connection wasn't
stable through the whole process.

The crappy thing about this is the lack of relevant info about netlogon 5783
and SP4. If I'm having the issue then surely someone else has too.

I'm almost ready to breakdown and call PSS.

Best,
J Penrose MCSE MCSA
 
Back
Top