Event: 5719 occurs and no Network Connectivity
by Francois » Wed, 12 May 2004 17:25:48 GMT
My exchange server looses it's connection with the
Primary Domain Controller every 15minutes. In the event
log the first error that occurs is 5719.
When I restart the server the exchange is back up for
15mins and then fails again.
What can we try to resolve this problem.
We are running Windows 2003 standard as the AD server and
Exchange 2003.
Regards
Re: Event: 5719 occurs and no Network Connectivity
by Ruwan Dissanayake » Wed, 12 May 2004 18:09:21 GMT
Hey,
I think this problem occurs because of another problem. Please check that
you have an error on NetLogOn service in the Event Viewer.
Ruwan Dissamayake
Similar Threads:
1.Event ID 5719, Source: NETLOGON
2.Exchange Front End Server Getting Event ID 5719
I am running an Exchange 2003 SP1 front end server in the dmz with a
clustered backend. We have been noticing that lately once a day we have been
getting Event Log 5719, it can't authenticate to a domain controller. This
only happens once a day and it is always on the hour, a different hour each
time but it is on the hour. We are running a Pix between the DMZ and inside.
It isn't a port issue because it works all of the time except that one time a
day. Anyone seen this before?
3.NETLOGON 5719 on Windows 2003 after Exchange 2003 was installed
I am getting a NETLOGON 5719 error in my event log, this just happened after
Exchange 2003 was installed on this new server. The OS is Windows 2003.
What could be the cause of this error? This is a brand new server and
installation.
--
Eric Sabo
NT Administrator
4.NetLogon 5719
I'm getting this error because the XXXX domain no longer exists.....I
removed the domain when I migrated the exchange servers. How do I fix this?
This computer was not able to set up a secure session with a domain
controller in domain XXXX 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.
--
Wack
----
This message will self destruct.
5.Exchange and network connectivity
Question re: Exchange and network connectivity.
Exchange
Exchange server 2003 SP2 is located physically in a different location in a
colocation facility. It is on a different domain that hosts the company web
presence. DNS forwarders are set to the hosting company DNS servers.
LAN
One internal domain that forwards to an ISP's DNS. Internally PCs have a
host table entry that points to the colocation Exchange server internal IP
(192.168.1.X). It is located on a different subnet address and connected via
VPN.
The problem is that some laptops users cannot connect to email when working
remotely due to the internal IP address entry in Hosts. That's because from
outside there is a public interface. The work around is to have them use the
public IP address. This works, but seems clumsy. Surely, others have
encountered this.
Any ideas? Is there a DNS solution to this?
6. Strange networking/connectivity problem ...
7. Which tool to use to test network connectivity?