X.25 Support with Windows for Workgroups 3.11 RASLast reviewed: August 17, 1995Article ID: Q113239 |
The information in this article applies to:
Microsoft does not encourage nor support changes to .INF files; therefore, Microsoft Product Support Services (PSS) does not support the procedure in this article. Although we have tested the following procedure and it appears to function as described, we recommend that you make a backup copy of your .INF file before you proceed.
SUMMARYThe Remote Access Services (RAS) client that ships with Microsoft Windows for Workgroups supports the packet-switching protocol X.25. The X.25 protocol is used to gain access to vendor-provided wide area networks (WANs) by modem or direct connections from terminals and computers.
MORE INFORMATIONRAS can be set up as a client to dial Packet Assembly/Disassembly (PAD) services that are supplied by X.25 carriers. Windows for Workgroups RAS clients support X.25 networking if the PAD.INF file is set up with the correct X.25 command scripts. The default PAD entries in the PAD.INF file include InfoNet, SprintNet Alternate, and SprintNet Standard. In some cases, you may need to manually enter the specific PAD command scripts in the PAD.INF file. These command scripts allow you to automate communication with your vendor's X.25 dial-up PAD, however, you have the option to log on interactively to the dial-up PAD by using the Windows For Workgroups RAS Terminal feature. For additional information refer to the section titled "CONFIGURING WINDOWS RAS TO USE RAS TERMINAL AFTER DIALING" in the following article:
ARTICLE-ID:Q125975 TITLE :Automating Remote RAS Logons Using SWITCH.INF ScriptsThe following steps may allow you to connect to an X.25 provider through Windows for Workgroups RAS:
|
KBCategory: kbnetwork kb3rdparty
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |