MSDOS client

Not sure if this is the right group or not but here goes.

I have an old DOS workstation that I need to connect to my
Windows Server 2003 domain. I have done this once at
another location and it worked. This time, I keep getting
access denied. I followed article 811497 but still can't
login.

Any help would be great!!

Thanks

Jim

"Jim" <(E-Mail Removed)> wrote in message
news:4fcd01c49111$a142fd10$(E-Mail Removed)...
> Not sure if this is the right group or not but here goes.
>
> I have an old DOS workstation that I need to connect to my
> Windows Server 2003 domain. I have done this once at
> another location and it worked. This time, I keep getting
> access denied. I followed article 811497 but still can't
> login.
>
> Any help would be great!!
>
> Thanks
>
> Jim


On your Windows Server 2003 machine you probably need to lighten the
security to allow LanManager authentication. Start secpol.msc and go to
Local Policies/Security Options and find 'Network Security: LAN Manager
authentication level'. If this server is a member of a domain and this
setting is being forced through Group Policy, then your changes will be
overwritten the next time the policy is applied.

Thanks for the reply,
It was working yesterday fine. This morning, I'm getting
an invalid password error. As far as I know, nothing has
changed. I made the change that you suggested, but it did
not help.

Anything else to try?

Jim
>-----Original Message-----
>
>"Jim" <(E-Mail Removed)> wrote in
message
>news:4fcd01c49111$a142fd10$(E-Mail Removed)...
>> Not sure if this is the right group or not but here
goes.
>>
>> I have an old DOS workstation that I need to connect to
my
>> Windows Server 2003 domain. I have done this once at
>> another location and it worked. This time, I keep
getting
>> access denied. I followed article 811497 but still can't
>> login.
>>
>> Any help would be great!!
>>
>> Thanks
>>
>> Jim
>
>
>On your Windows Server 2003 machine you probably need to
lighten the
>security to allow LanManager authentication. Start
secpol.msc and go to
>Local Policies/Security Options and find 'Network
Security: LAN Manager
>authentication level'. If this server is a member of a
domain and this
>setting is being forced through Group Policy, then your
changes will be
>overwritten the next time the policy is applied.
>
>
>
>.
>

In the event log, security, I see the user logon and then
immediatly get logged off
>-----Original Message-----
>Thanks for the reply,
>It was working yesterday fine. This morning, I'm getting
>an invalid password error. As far as I know, nothing has
>changed. I made the change that you suggested, but it did
>not help.
>
>Anything else to try?
>
>Jim
>>-----Original Message-----
>>
>>"Jim" <(E-Mail Removed)> wrote in
>message
>>news:4fcd01c49111$a142fd10$(E-Mail Removed)...
>>> Not sure if this is the right group or not but here
>goes.
>>>
>>> I have an old DOS workstation that I need to connect
to
>my
>>> Windows Server 2003 domain. I have done this once at
>>> another location and it worked. This time, I keep
>getting
>>> access denied. I followed article 811497 but still
can't
>>> login.
>>>
>>> Any help would be great!!
>>>
>>> Thanks
>>>
>>> Jim
>>
>>
>>On your Windows Server 2003 machine you probably need to
>lighten the
>>security to allow LanManager authentication. Start
>secpol.msc and go to
>>Local Policies/Security Options and find 'Network
>Security: LAN Manager
>>authentication level'. If this server is a member of a
>domain and this
>>setting is being forced through Group Policy, then your
>changes will be
>>overwritten the next time the policy is applied.
>>
>>
>>
>>.
>>
>.
>

I found the issue, Not sure of the fix.
I edited the registry yesterday at
Localmachine\system\currentcontrolset\services\lan manserver
\parameters and set the value of requirescuritysignature
to 0 (zero) This moring, it is back to 1 When I set it
back to zero, things work. I set the digitally sign always
group policy to disabled yesterday.

Any idea why it would change?

Jim

>-----Original Message-----
>Thanks for the reply,
>It was working yesterday fine. This morning, I'm getting
>an invalid password error. As far as I know, nothing has
>changed. I made the change that you suggested, but it did
>not help.
>
>Anything else to try?
>
>Jim
>>-----Original Message-----
>>
>>"Jim" <(E-Mail Removed)> wrote in
>message
>>news:4fcd01c49111$a142fd10$(E-Mail Removed)...
>>> Not sure if this is the right group or not but here
>goes.
>>>
>>> I have an old DOS workstation that I need to connect
to
>my
>>> Windows Server 2003 domain. I have done this once at
>>> another location and it worked. This time, I keep
>getting
>>> access denied. I followed article 811497 but still
can't
>>> login.
>>>
>>> Any help would be great!!
>>>
>>> Thanks
>>>
>>> Jim
>>
>>
>>On your Windows Server 2003 machine you probably need to
>lighten the
>>security to allow LanManager authentication. Start
>secpol.msc and go to
>>Local Policies/Security Options and find 'Network
>Security: LAN Manager
>>authentication level'. If this server is a member of a
>domain and this
>>setting is being forced through Group Policy, then your
>changes will be
>>overwritten the next time the policy is applied.
>>
>>
>>
>>.
>>
>.
>

"Jim" <(E-Mail Removed)> wrote in message
news:09f601c491c6$04c15df0$(E-Mail Removed)...
> I found the issue, Not sure of the fix.
> I edited the registry yesterday at
> Localmachine\system\currentcontrolset\services\lan manserver
> \parameters and set the value of requirescuritysignature
> to 0 (zero) This moring, it is back to 1 When I set it
> back to zero, things work. I set the digitally sign always
> group policy to disabled yesterday.
>
> Any idea why it would change?
>
> Jim
>


There could be more than one group policy defined on the domain or OU, and
the policy that you changed is being overridden.