missing authentication tab on DC under server 2003

In my AD domain following strange behaviour was noticed lately

I have 2 DC's DC1 and DC2, running server 2003, both up-to-date
patched.

Opening the lan panel of the active connection shows an authentication
tab DC1, but NOT on DC2.

I tried to find out why, but have no clue. I saw posting referring to
wlan problems, but I have no wlan.

Any help is appreciated,

Yves

What LAN Panel? Are these servers replicating with each other?

--
Todd J Heron, MCSE
Windows 2003/2000/NT

"Yves" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> In my AD domain following strange behaviour was noticed lately
>
> I have 2 DC's DC1 and DC2, running server 2003, both up-to-date
> patched.
>
> Opening the lan panel of the active connection shows an authentication
> tab DC1, but NOT on DC2.
>
> I tried to find out why, but have no clue. I saw posting referring to
> wlan problems, but I have no wlan.
>
> Any help is appreciated,
>
> Yves

I don't know exactly what you are referring to but if you thing you are having a
problem check Event Viewer for any pertinent errors and run first the support tool
netdiag and then dcdiag on your domain controllers to see if any problems exist such
as dns, network connectivity, and/or replication.. --- Steve


"Yves" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> In my AD domain following strange behaviour was noticed lately
>
> I have 2 DC's DC1 and DC2, running server 2003, both up-to-date
> patched.
>
> Opening the lan panel of the active connection shows an authentication
> tab DC1, but NOT on DC2.
>
> I tried to find out why, but have no clue. I saw posting referring to
> wlan problems, but I have no wlan.
>
> Any help is appreciated,
>
> Yves

Thank you both for responding so fast. I am unable to post an answer
to each of you separately, so this is the answer to both:

Let me try to be more specific first.

I open Start->Network Connection -> Team 0 lan adapter -> properties.

On DC1, 3 tabs appear : General authentication and advanced
(DC1 is also the certificate server of the domain)
On DC2, 2 tabs appear : General and advanced. (No authentication)

I use the authentication to set the smart card or certificate
properties,
which I cannot do on the DC2.

I wonder what is wrong.

I check the event logs daily. No no networking related error messages
on the DC's. I have policy replication troubles on the XP SP2
workstations, though and this was how I found out that this strange
behavior occurs

That authentication tab is for the use of 802.1X wireless or wired authentication
for computer authentication which requires the use of an IAS server. 802.1x
compatible switches/access points, and computer certificates on all computers. I am
not sure why it would not appear on one computer. If the computer that is missing
from is a Windows 2000 Server you will need to install the latest service pack -SP4
or an update for 802.1x. If you are not configuring your network for 801.1x then
that is not the place to configure certificates for a computer. You can use the mmc
certificate snapin for certificates [user or computer] to install certificates on a
computer. --- Steve

http://support.microsoft.com/default...b;en-us;313664


"Yves" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Thank you both for responding so fast. I am unable to post an answer
> to each of you separately, so this is the answer to both:
>
> Let me try to be more specific first.
>
> I open Start->Network Connection -> Team 0 lan adapter -> properties.
>
> On DC1, 3 tabs appear : General authentication and advanced
> (DC1 is also the certificate server of the domain)
> On DC2, 2 tabs appear : General and advanced. (No authentication)
>
> I use the authentication to set the smart card or certificate
> properties,
> which I cannot do on the DC2.
>
> I wonder what is wrong.
>
> I check the event logs daily. No no networking related error messages
> on the DC's. I have policy replication troubles on the XP SP2
> workstations, though and this was how I found out that this strange
> behavior occurs