Unsolved
This post is more than 5 years old
3 Posts
0
8321
September 16th, 2004 18:00
PowerEdge 2600 Windows 2003 Server - Netlogin Errors Event ID 5719
I just setup a Windows 2003 member server on our current domain, with
multiple W2k domain controllers. It is a brand new Dell PowerEdge 2600, with
a Intel Pro 1000XT NIC with auto-sensing. Since installing the NIC drivers
and adding it to the domain, I get the same errors in the event logs every
time the server is booted up.
Source: NETLOGIN
TYPE: ERROR
EVENT ID: 5719
This computer was not able to set up a secure session with a domain
controller in domain ***** 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.
SOURCE: W32TIME
TYPE: Warning
EVENT ID: 14
The time provider NtpClient was unable to find a domain controller to use as
a time source. NtpClient will try again in 15 minutes.
Source: W32TIME
TYPE: ERROR
EVENT ID: 29
The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 15 minutes. NtpClient has no
source of accurate time.
SOURCE: MRxSmb
TYPE: ERROR
EVENT ID: 8003
The master browser has received a server announcement from the computer
TWB-OSP that believes that it is the master browser for the domain on
transport NetBT_Tcpip_{DB034500-5BC7-494B-A. The master browser is stopping
or an election is being forced.
In the application log:
Source: WMSERVER
TYPE: ERROR
EVENT ID: 323
Plug-in 'WMS WMI Event Handler' on the server failed with the following
information: Error code = 0x8004100a, Error text = 'The WMI event plugin
failed to start.'.
Source: USERENV
TYPE: ERROR
Event ID: 1054
Windows cannot obtain the domain controller name for your computer network.
(The specified domain either does not exist or could not be contacted. ).
Group Policy processing aborted.
Of all the research I've done, everything seems to point back to a problem
with the ethernet card and some sort of incompatibility with the "Media
sensing" feature of Windows 2003. Some articles have stated to update the
driver (only one driver is available that I can find, and I have the most
current). Others talk about editing the registry to disable "Media Sensing".
Everything I tried I get the same results.
Then a lightbulb when off in my head, and I changed an option of the NIC
driver that did in fact fix the error. I changed the Link Speed and Duplex
settings from "Auto Negotiate best speed" to "100MBPS Full Duplex" Believe
it or not this made all off the errors go away. The only problem with this
being, that with that setting in place, the NIC gets horrible packet loss and
dropped frames. So of course I had to put the setting back to auto-negotiate.
Does anyone have a clue where to go from here? I appreciate it.
multiple W2k domain controllers. It is a brand new Dell PowerEdge 2600, with
a Intel Pro 1000XT NIC with auto-sensing. Since installing the NIC drivers
and adding it to the domain, I get the same errors in the event logs every
time the server is booted up.
Source: NETLOGIN
TYPE: ERROR
EVENT ID: 5719
This computer was not able to set up a secure session with a domain
controller in domain ***** 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.
SOURCE: W32TIME
TYPE: Warning
EVENT ID: 14
The time provider NtpClient was unable to find a domain controller to use as
a time source. NtpClient will try again in 15 minutes.
Source: W32TIME
TYPE: ERROR
EVENT ID: 29
The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 15 minutes. NtpClient has no
source of accurate time.
SOURCE: MRxSmb
TYPE: ERROR
EVENT ID: 8003
The master browser has received a server announcement from the computer
TWB-OSP that believes that it is the master browser for the domain on
transport NetBT_Tcpip_{DB034500-5BC7-494B-A. The master browser is stopping
or an election is being forced.
In the application log:
Source: WMSERVER
TYPE: ERROR
EVENT ID: 323
Plug-in 'WMS WMI Event Handler' on the server failed with the following
information: Error code = 0x8004100a, Error text = 'The WMI event plugin
failed to start.'.
Source: USERENV
TYPE: ERROR
Event ID: 1054
Windows cannot obtain the domain controller name for your computer network.
(The specified domain either does not exist or could not be contacted. ).
Group Policy processing aborted.
Of all the research I've done, everything seems to point back to a problem
with the ethernet card and some sort of incompatibility with the "Media
sensing" feature of Windows 2003. Some articles have stated to update the
driver (only one driver is available that I can find, and I have the most
current). Others talk about editing the registry to disable "Media Sensing".
Everything I tried I get the same results.
Then a lightbulb when off in my head, and I changed an option of the NIC
driver that did in fact fix the error. I changed the Link Speed and Duplex
settings from "Auto Negotiate best speed" to "100MBPS Full Duplex" Believe
it or not this made all off the errors go away. The only problem with this
being, that with that setting in place, the NIC gets horrible packet loss and
dropped frames. So of course I had to put the setting back to auto-negotiate.
Does anyone have a clue where to go from here? I appreciate it.
No Events found!
lny
3 Posts
0
October 6th, 2004 11:00
Do you use Cisco switch?
/Lny
lny
3 Posts
0
October 6th, 2004 11:00
You have to change the switch settings to match the card settings of your client then you use 100Mbit FD.
I belive you have Auto negotiate in the switch end and 100Mbit FD in the server end.
We have problem with Startup scipts and Dell Optiplex with Intel 1000T card but a newer Intel driver fixes our problem.
/Lny
Troy Thompson
3 Posts
0
October 6th, 2004 11:00
lny
3 Posts
0
October 6th, 2004 12:00
If we suppose everything is configured right in the Cisco swith, I know there is Intel Pro/100 or Pro/1000 fixes in the IOS.
I´m working with our servers and not with the Cisco products directly but we updated our Cisco IOS to solve some Intel problems.
Please read the Cisco update bulletins and try to find Intel related fixes.
Sorry, can´t give you more information than that.
/Lny
Troy Thompson
3 Posts
0
October 6th, 2004 12:00
didierhayoz
1 Message
0
October 7th, 2004 21:00
I just had the problem.
Turns out that the file server had two DNS servers defined in the TCP/IP settings. The first one defined was a domain controller that was just demoted, so it did not have any of the zones for our domain anymore. Therefore, the file server could not locate any info about the domain, including the time server. It refused any connection coming from the domain.
I changed the DNS settings to point to a current domain controller, flushed the DNS cache (ipconfig /flushdns) and it started working.
Hope this helps.
pevou
2 Posts
0
October 14th, 2004 09:00
Try
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"DisableDHCPMediaSense"=dword:00000001
elvish
2 Intern
•
33 Posts
0
October 25th, 2004 18:00
:) Sounds familar...
On boot or reboot: when the Intel LOM driver loads, it commands the NIC ASIC to reset. This drops link, and if STP is enabled on the switch or if the system boots fast enough; the OS may be looking for network resources before the LOM can actually pass traffic. OOps..
We ran into this ourselves. We disabled STP and experimented with hardsetting the switch and the LOM. This worked for us..