NetDDE and RAS Connections

 Last reviewed: May 13, 1997
Article ID: Q110315
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SUMMARY

When you attempt to use NetDDE over a Windows NT Remote Access Service (RAS) connection, the session can be started only by one of the systems. The system that can start the session is usually the one who dials into a RAS server. On the other system, a "Machine Name Not Found" error message appears.

MORE INFORMATION

NetDDE requires that a NCB.LISTEN be posted for the NetBIOS name of the clients. RAS for Windows NT defaults to not posting NCB.LISTEN for remote connections, but you can modify this in the registry. The registry entry is: 

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess
   \Parameters\NetbiosGateway\RemoteListen
The default value is 1 for enabling Messenger and Server services only. Change the value to 2 to include NCB.LISTEN for all remote client NetBIOS names.

Warning: Enabling NCB.LISTEN require the RAS server to post all NetBIOS names from remote connections to the network. With a 64-port RAS server and an average of 5 or 6 names per Windows NT client, this can mean at least 320 NetBIOS names. This can exceed the 254 NetBIOS name limit per protocol/NIC on Windows NT.

Additional query words: adapter prodnt chat clipbook one way
Keywords : kbnetwork ntnetserv
Version : 3.1
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.