OVH Cloud OVH Cloud

IPC$ pb with W98 and member server

1 réponse
Avatar
Alex
Hi

I have some W98 client that log on a NT4 Domain. I have too an Active
Directory domain with a Domain Controler and a member server (this server is
W2K Server, member of the AD but AD is not installed on it). There is a
bidirectional trust relationship between the NT4 and the AD.

The W98 clients logged to the NT4 domain can connect to the NT4 PDC, BDC,
the AD Domain Controler but not to the 2000 Member Server.

Besides the W98 clients there are some NT4 client logged on the NT4 Domain
and they can access both the AD DC and the W2K member server.

Why my W98 clients can not access this member server, though they can access
the AD Domain Controler ? On the client side I am prompted for IPC$ password
and on the member server side I have a security event error (wrong user
name/pwd).

Here is the error message I get on the member server:
__
The logon to account: ACLA by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from
workstation: \\AC1. failed
. The error code was: 3221225572
__
and below
__
USERNAME: ACLA
DOMAIN: NTDOMAIN ; name of the NT4 DOM
Session Type : 3
NTLMSP
Authentication: NTML
Workstation: \\AC1
__

If I enter the user name/pwd of the W98 user on the member server, it works.
But it is not a solution, of course...

Thanks for any help...

Alex

1 réponse

Avatar
Smain
Hi Alex

Note that the Authentication authority is the NT Lan Manager (NTLM)
protocol.

I understand that you are using Windows 98 clients within NT4 domain to
which a server 2000 is a member. Windows 98 clients can connect to the
domain NT4 but not to the member server 2000. First, this is because
computers with Windows 3.11, Windows 95, Windows 98, or Windows NT 4.0 use
the NTLM protocol for network authentication in Windows 2000 domains.
Second, your Windows 2000 machine uses NTLM when authenticating to servers
with Windows NT 4.0 and when accessing resources in Windows NT 4.0 domains.

So long as the NTLM protocol is in use, your clients 98 will have to
authenticate themselves with a valid username/password to connect to the
member server 2000.

NB: AD is not a Windows NT4 environment built-in.

The only thing I can suggest is to enable NTLM v.2. Please take a look at
this KB for more information as to how you can do it.

http://support.microsoft.com/?id#9869

Regards

Smain

"Alex" wrote in message
news:
| Hi
|
| I have some W98 client that log on a NT4 Domain. I have too an Active
| Directory domain with a Domain Controler and a member server (this server
is
| W2K Server, member of the AD but AD is not installed on it). There is a
| bidirectional trust relationship between the NT4 and the AD.
|
| The W98 clients logged to the NT4 domain can connect to the NT4 PDC, BDC,
| the AD Domain Controler but not to the 2000 Member Server.
|
| Besides the W98 clients there are some NT4 client logged on the NT4 Domain
| and they can access both the AD DC and the W2K member server.
|
| Why my W98 clients can not access this member server, though they can
access
| the AD Domain Controler ? On the client side I am prompted for IPC$
password
| and on the member server side I have a security event error (wrong user
| name/pwd).
|
| Here is the error message I get on the member server:
| __
| The logon to account: ACLA by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from
| workstation: AC1. failed
| . The error code was: 3221225572
| __
| and below
| __
| USERNAME: ACLA
| DOMAIN: NTDOMAIN ; name of the NT4 DOM
| Session Type : 3
| NTLMSP
| Authentication: NTML
| Workstation: AC1
| __
|
| If I enter the user name/pwd of the W98 user on the member server, it
works.
| But it is not a solution, of course...
|
| Thanks for any help...
|
| Alex