Re: Network authentication

From: Steven (sthomason@shurtape.com)
Date: 04/04/03


From: "Steven" <sthomason@shurtape.com>
Date: Fri, 4 Apr 2003 11:33:57 -0800


No we are not running sms. I will try the vb script above
to fix the problem.
Thanks,
>-----Original Message-----
>Do you run Systems Management Server (SMS)? There is a
known issue with this
>if you do run an old version of SMS.
>
>--
>
>Rajkumar Mohanram [MSFT]
>Windows Security - Kerberos Authentication Protocol
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>..
>"Steven" <sthomason@shurtape.com> wrote in message
>news:054501c2f921$bcda8630$a601280a@phx.gbl...
>> We are having intermittant problems with authentication
on
>> our network, especially when connecting through a MS
proxy
>> 2.0 server of to a IIS server and accessing files. When
>> accessing the MS Proxy server, the user will not be able
>> to connect with his username/password. Looking in the
>> event log on the proxy server you see that the user
>> account is locked out. If you look in Active Directory,
>> the account is not locked out.
>>
>> There seems to be something as in a SID history from the
>> NT upgrade that occasionally causes a users to enter his
>> username and password. The problem only seems to occur
on
>> computers and/or computer accounts that were original to
>> the NT 4 domain. If you create a new user and log onto a
>> computer created after the upgrade, there does not seem
to
>> be a problem.
>>
>> Using a sniffer, it appears that the computer tries to
>> authenticate several times before giving/rejecting
access
>> to any resource. Using the "new" user, authentication
>> happens right away.
>>
>> Is there something i should be doing to "clean-up" my
sid
>> history? We upgrade to AD last February.
>>
>
>
>.
>



Relevant Pages

  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: Client not reporting into SCCM
    ... Therefore you can't upgrade to ConfigMgr until they upgrade first. ... If you don't want to report to them any more then use a new site code. ... If you rebuild SMS 2k3 then you will still need to update the security on the System Management Container. ... SCCM Server on a seperate server SQL ...
    (microsoft.public.sms.misc)
  • Re: Post Windows 2003 Update Errors
    ... > down to a member server later). ... > Everything appears to be fine following the upgrade except that the SMS ... > or local security authority server was in the wrong state to perform ...
    (microsoft.public.sms.setup)
  • Re: Failed upgrade to SCCM
    ... but I've done an SMS restore to new ... I had during the upgrade would prevent the new install / site repair from ... I recently started the upgrade our SMS 2003 SP3 Server to SCCM. ...
    (microsoft.public.sms.setup)
  • Re: SMS upgrade question(s)
    ... an Exsiting Installation of SMS 2.0 part of the document available at ... for execution details). ... server (please refer to page 32 the Swapping the Computer of a Site Server ... > upgrade current site then move to new box or move site to ...
    (microsoft.public.sms.admin)