Event errors and login problems

[Guest]

Hello, I'm getting the below errors in my server 2003 event logs, anyone any
ideas?

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 8/11/2004
Time: 12:25:42 PM
User: N/A
Computer: SERVER
Description:
This computer was not able to set up a secure session with a domain
controller in domain BIG due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your domain
administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À
_________________________________________________________________

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 8/11/2004
Time: 3:51:40 PM
User: N/A
Computer: SERVER
Description:
This computer was not able to set up a secure session with a domain
controller in domain BIG due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your domain
administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the specified
domain. Otherwise, this computer sets up the secure session to any domain
controller in the specified domain.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 17 00 02 c0 ...À

 

[Stanley Jones [MSFT]]

Verify that your computer is physically connected to the network like it
should be (cables plugged in to ports which are actually live). Then try
using a command prompt to "ping" the name or ipaddress of another box on the
network which you should be able to connect to. If the ping fails then you
something is not wired like it should be somewhere. If you get replies from
the ping then you are connected and need to talk to whoever is the domain
admin for BIG about being assigned an IP address and any appropriate
credentials.