RE: Exchange 2003 server problems after login.
- From: Brian Delaney <BrianDelaney@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 16:12:27 -0800
Absolutely, you could also try disabling checksum offloading on the NIC
before rolling back the driver.
--
Brian Delaney, MCSE
"JKR" wrote:
One other thing I just noticed in the event logs. I updated my NIC driver.
late one afternoon and then the next day the problems started occuring. Can
a flakey NIC driver cause this?
"Brian Delaney" wrote:
I would try two things. First of all install the hotfix from
http://support.microsoft.com/?id=898060 on the Exchange Server and the DCs if
running SP1. This corrects a problem with the tcpip.sys file that was
released in SP1 which can cause some odd authentication issues as you will
see in the article above.
Secondly, I would configure the exchange server to use Kerberos over TCP.
By default Kerberos uses UDP and on some networks the packets can get
fragmented and occasionally you will see Netlogon 5719's along with LSASRV
40960 and/or 40961. To configure Kerberos to use TCP follow the article
http://support.microsoft.com/?id=244474
--
Brian Delaney, MCSE
"JKR" wrote:
This whole sad story of woe started when my GFI faxmaker service wouldn't
start after I rebooted my exchange 2003 server (thats runs windows 2003 sp1
server..aka the most reliable windows ever). Once I logged in I could
manually start my faxserver and it works fine. DNS seems fine...I can ping
the domain controllers by name. If I reboot the mail server and run
RSOP.msc the user policies apply fine but not the computer has a big red X in
it and says:
Group Policy Infrastructure failed due to the error listed below.
The specified domain either does not exist or could not be contacted.
Note: Due to the GP Core failure, none of the other Group Policy components
processed their policy. Consequently, status information for the other
components is not available. Additional Information: Windows cannot
determine the user or computer name. (The specified domain either does not
exist or could not be contacted. ). Group Policy processing aborted.
Now I can wait awhile and re-run rsop.msc and the computer policies will
apply fine.
Anyone have any ideas besides a large sledge hammer applied firmly on the
server box?
Source: Service Control Manager
Type: ERROR
Computer: MAIL
Time: 3/17/2006 12:25:02 AM ID: 7038
The FAXmaker MTA Service service was unable to log on as corp\administrator
with the currently configured password due to the following error:
There are currently no logon servers available to service the logon request.
App Log:
Event ID: 1053
Source: Userenv
Windows cannot determine the user or computer name. (The specified domain
either does not exist or could not be contacted. ). Group Policy processing
aborted.
System Log:
Event ID: 5719
Source: NETLOGIN
This computer was not able to set up a secure session with a domain
controller in domain CORP 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.
- References:
- RE: Exchange 2003 server problems after login.
- From: Brian Delaney
- RE: Exchange 2003 server problems after login.
- From: JKR
- RE: Exchange 2003 server problems after login.
- Prev by Date: RE: Exchange 2003 server problems after login.
- Next by Date: Re: 'Managed By' tab
- Previous by thread: RE: Exchange 2003 server problems after login.
- Index(es):
Relevant Pages
|
