Microsoft KB Archive/172450: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 12: Line 12:
<div id="TitleRow">
<div id="TitleRow">


= <span id="KB172450"></span>NetDDE Connections Fail When &quot;Logon to&quot; Restrictions Apply =
= <span id="KB172450"></span>NetDDE Connections Fail When "Logon to" Restrictions Apply =




Line 56: Line 56:
== CAUSE ==
== CAUSE ==


&quot;Logon to&quot; restrictions are implemented such that user A can only log on to workstation A. User B logs on to workstation B, but no &quot;Logon to&quot; restrictions are placed on this user. A network DDE application is then started on both workstations. When workstation A attempts to dial workstation B through the network DDE application, User A is prompted for a password. If any valid non-administrative user and password is used, the connection fails with an &quot;Invalid Password&quot; pop-up error message.<br />
"Logon to" restrictions are implemented such that user A can only log on to workstation A. User B logs on to workstation B, but no "Logon to" restrictions are placed on this user. A network DDE application is then started on both workstations. When workstation A attempts to dial workstation B through the network DDE application, User A is prompted for a password. If any valid non-administrative user and password is used, the connection fails with an "Invalid Password" pop-up error message.<br />
<br />
<br />
When the network DDE client connects to the network DDE server, the server will impersonate the client. Because of this security restriction, the server portion of the network DDE application is responding with the password dialog box.
When the network DDE client connects to the network DDE server, the server will impersonate the client. Because of this security restriction, the server portion of the network DDE application is responding with the password dialog box.
Line 65: Line 65:
== RESOLUTION ==
== RESOLUTION ==


Remove &quot;Logon To&quot; account restrictions for the user account that originates the connection.<br />
Remove "Logon To" account restrictions for the user account that originates the connection.<br />
<br />
<br />
-or-<br />
-or-<br />

Latest revision as of 11:06, 21 July 2020

Knowledge Base


NetDDE Connections Fail When "Logon to" Restrictions Apply

Article ID: 172450

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q172450

SYMPTOMS

You are prompted for a password when connecting to a Windows NT computer while using a network dynamic data exchange (DDE) application.

CAUSE

"Logon to" restrictions are implemented such that user A can only log on to workstation A. User B logs on to workstation B, but no "Logon to" restrictions are placed on this user. A network DDE application is then started on both workstations. When workstation A attempts to dial workstation B through the network DDE application, User A is prompted for a password. If any valid non-administrative user and password is used, the connection fails with an "Invalid Password" pop-up error message.

When the network DDE client connects to the network DDE server, the server will impersonate the client. Because of this security restriction, the server portion of the network DDE application is responding with the password dialog box.

RESOLUTION

Remove "Logon To" account restrictions for the user account that originates the connection.

-or-

Add netdde to the list of workstations the user can log on from.

-or-

From the originating computer, perform the following steps:

  1. Use the Domain Administrator's account.
  2. Use the answering computer's Administrator account.
  3. Enable the domain Guest account and use it to originate the connection.


STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT versions 3.51 and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.



Additional query words: prodnt chat hearts

Keywords: KB172450