1. Manuals
  2. Brands
  3. Bay Networks Manuals
  4. Software
  5. FastLink II
  6. User manual

Bay Networks FastLink II User Manual

Nortel fastlink ii network: user guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Enlarged version
FastLink II
Client Pack
Copyright © 1994-1996 Bay Networks, Inc. and Funk Software, Inc.
3rd Edition, October 1996.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FastLink II and is the answer not in the manual?

Questions and answers

Related Manuals for Bay Networks FastLink II

Summary of Contents for Bay Networks FastLink II

  • Page 1 FastLink II Client Pack Copyright © 1994-1996 Bay Networks, Inc. and Funk Software, Inc. 3rd Edition, October 1996.
  • Page 2 6100, Remote Annex 6300, MSX 5390, MSX 5391, and MSX 5393 are trademarks of Bay Networks, Inc. FastLink II © 1994-1996 Bay Networks, Inc. and Funk Software, Inc. All rights reserved. Proxy © 1992-1996 Funk Software, Inc. All rights reserved.

  • Page 3: Table Of Contents

    Overview ... 5 System Requirements/Compatibility... 7 About The Documentation ... 8 Technical Support ... 9 FastLink II Client Pack Diskettes and Licensing ... 10 I-2 Installing the FastLink II Client Pack Overview ... 11 Windows Installation... 12 DOS Installation ... 21 II-1 FastLink II Concepts Clients and Servers...

  • Page 4: Iii-1 Supported Ip Stacks

    Before Running Windows ...70 Connecting to the Remote Access Server ...71 Connecting to NetWare File Servers...71 Using Custom Windows Icons ...72 II-A FastLink II Connection Errors Connection Error Messages...77 III-1 Supported IP Stacks Introduction...81 Beame & Whiteside (BW-TCP 3.2) ...82 Frontier (SuperTCP for Windows) ...86...

  • Page 5: Introducing The Fastlink Ii Client Pack

    Overview Welcome to the world of remote network access. With the FastLink II Client Pack, you’ll be able to reach your network from anywhere via modem, and connect to all its resources just as if you were on premises — so you can do your work without being at work.

  • Page 6: System Requirements/Compatibility

    Proxy Remote Control One of the most important things that your FastLink II connection allows you to do is run the powerful Proxy Remote Control software included in this package. By installing the Proxy Master on your remote PC and the Proxy Host on your PC at work, you can take over and operate your PC at work from your home or from the road.
  • Page 7 16550A-based serial COM port add-in card that contains a co-processor such as a Hayes ESP card. For a discussion of the different types of serial ports, see the “FastLink II Concepts” chapter. To determine which type you have, use the Comm Port Test feature described in the “FastLink II User Interface”...

  • Page 8: About The Documentation

    Š Part I includes this introductory material plus instructions on installing the FastLink II Client Pack. Š Part II describes how to use the FastLink II Client to establish a connection to a network over a phone line. Š Part III documents the IP Stacks.

  • Page 9: Technical Support

    Technical Support If you have any problems installing or using the FastLink II Client or Proxy, there are various resources available to help you: Š This manual and the README.TXT files on your diskettes may contain the information you need to solve the problem you are having Š...

  • Page 10: Fastlink Ii Client Pack Diskettes And Licensing

    Remote PC diskettes You are provided with a master copy of the following two diskettes used to install FastLink II on the remote PC. You may freely distribute and copy either of these diskettes for use in connecting to Bay Networks’ remote access server: Š...

  • Page 11: Windows Installation

    I-2 Installing the FastLink II Client Pack Overview These instructions describe how to install the FastLink II Client Pack on your PC. You can install either from DOS or from Windows: Š The Windows installation process installs all the software you need to run FastLink II with either DOS or Windows.

  • Page 12: Windows Installation

    To install the FastLink II Client and the Proxy remote control Master: Run SETUP.EXE from the FastLink II Client diskette. To do so, insert the FastLink II Client diskette in drive A or B, issue the File Run command from Program Manager, then enter:...
  • Page 13 Master Installation Directory The default is to install the FastLink II Dial-in Client, the Novell NetWare Files, Novell TCP/IP Stack and the Proxy Master — these are the modules you’ll want to have on the PC that you’ll be using remotely.
  • Page 14 For each of these prompts, answer [Yes] to overwrite the existing file, or [No] to keep the previous version. If you answer [Yes], the file will be backed up. The FastLink II files will now be copied to the destination directories.
  • Page 15 A file copy progress indicator will now appear: Figure 4: Copy Progress Dialog To cancel the copy operation hit the [Cancel] key; this will prompt you to abort the installation operation. After the file copy, you will be asked to select one of the two supported connection types for your Remote Annex Software.
  • Page 16 You will now be asked if you wish to configure the FastLink II client settings. The following prompt will now appear: Figure 5: Initialization Confirmation Prompt If you answer [Yes] to configure the settings now, the FastLink II client will be started with the Setup dialog chosen for you.
  • Page 17 Concepts” and “The FastLink II User Interface” for more information on configuring FastLink II. If you installed the NetWare Client you will get a message stating that VLMs are installed on your system. This screen includes information on the batch files to load your dial-up stack for NetWare and/or TCP/IP.
  • Page 18 Installing Proxy Host on the network PC The Proxy Host can be installed from Windows or Windows 95. There are some differences between the Windows and Windows 95 installation; however, the installation steps are identical. Before installing the Proxy Host, make sure that you close all other applications that you have running.
  • Page 19 During installation from Windows, certain modifications will be made to your system files: Š When the FastLink II Client is installed, a line is added to your AUTOEXEC.BAT that loads a Novell program called DPMS.EXE, if it is not there already.

  • Page 20: Dos Installation

    This section describes how to install the FastLink II Client on your PC in DOS. To install the FastLink II Client, start from the DOS prompt and: Insert the FastLink II Client diskette in drive A or B, then make that drive current by typing either A: or B:, then pressing .
  • Page 21 NOTE: DPMS is a Novell extended memory driver that allows the FastLink II ODI driver to reduce its DOS footprint dramatically. Before running FastLink II, reboot your PC.

  • Page 22: Ii-1 Fastlink Ii Concepts

    A Bay Networks’ Remote Annex server is an example of such a server. The Remote Annex server accepts calls from the FastLink II Client. The FastLink II client and Remote Annex server communicate using a standard protocol called Point to Point Protocol (PPP). Most modern remote access systems use PPP as the underlying basis for communication.

  • Page 23: The Remote Access Administrator

    A password to allow the Remote Annex server to authenticate your identity. Š The phone number of the Remote Annex server. Your Administrator can also help you configure the FastLink II Client software, make sure your modem works correctly, and provide you with ongoing support as you need it.

  • Page 24: Serial Ports

    Your PC and modem communicate with each other over a serial port. The type of serial port you have and the speed (baud rate) you set it to affect the performance of your FastLink II connection. The most common type of serial port is based on the 8250 and, more recently, the 16450 Universal Asynchronous Receiver Transmitter (UART).

  • Page 25: The Fastlink Ii Odi Driver

    Remote Annex server that uses Point-to-Point protocol (PPP), a standard data-link level protocol. The FastLink II ODI driver allows both IPX and IP protocols to run over the PPP connection. FastLink II includes Novell’s IPX and LAN Workplace IP stack. There are also numerous vendors that supply IP stacks which are also compatible with FastLink II.

  • Page 26: The Fastlink Ii User Interface

    The FastLink II User Interface runs whether or not the FastLink II ODI driver has been loaded; if it is not loaded you won’t be able to connect to a server, though you will be able to change settings.
  • Page 27 To return to DOS from any dialog Running the FastLink II User Interface from Windows To run the FastLink II User Interface from Windows, use the File Run command and type the following: C:\FLINK\FLINKW You can also double-click the FastLink II Client icon in your FastLink II Windows group. Either way, the FastLink II User Interface appears with the Connections dialog displayed.

  • Page 28: The Connections Dialog

    The Connections Dialog The Connections dialog is the focal point of activity in FastLink II. It is from this dialog that you connect and disconnect from servers, and save the characteristics of connections for future use. Specifically, you can: Š...
  • Page 29 To display the Connections dialog, check the Connections button at the left of the screen. A dialog similar to the following appears: Editing Connection Settings To edit the settings for a connection: Highlight the Connection drop-down box, and select the connection whose settings you want to edit. Edit any of the individual settings, as described in the sections below.
  • Page 30 This is the phone number of the server. Your Administrator can supply you with this number. Your modem uses this number to gain access to the network. To specify the phone number, highlight the Phone number field and enter the phone number of your server. If any special access codes or modem controls (such as pauses) are required, be sure to include them.
  • Page 31 Remote Annex server. Checking this box will automatically start Terminal Mode in the following situations: Š When you click Connect, FastLink II will pop up the Terminal Mode screen, which is equivalent to pressing [Terminal]. Š...
  • Page 32 Network and Node Address When you connect, you will be assigned an IPX address that combines the Remote Annex server’s network number with a node address. FastLink II gives you a choice as to how your network and/or node address gets assigned: Š...
  • Page 33 IPX address has already dialed in, you will get an error when you try to connect. If you use FastLink II’s node address that was generated at installation, the odds of this happening are very small. If it does happen to you, go to the Setup Dialog and generate a new random node address to resolve the conflict.

  • Page 34: Ip Protocol Settings

    The IP Protocol Settings dialog lets you configure the use of IP over the connection. When you click on the [IP Protocol Settings] button, a dialog similar to the following appears: FastLink II gives you two choices as to how your IP address gets assigned: Š...

  • Page 35: Adding A Connection

    NOTE: If you use DHCP, ensure that you have a DHCP server on your network. IP Stack Configuration FastLink II uses ETHERNET_II for its default frame type. Do not change this frame type in the NET.CFG file or FastLink II will not work with IP.

  • Page 36: Connecting To A Server

    Highlight the Connection drop-down box, and select the appropriate connection. Press [Connect]. FastLink II activates the modem and dials the server. Once the phone link is created between the two modems, FastLink II and the server exchange the information necessary to establish the connection.
  • Page 37 The following table describes the information returned in the message box: Item Description Modem reports ... If your modem returned a CONNECT string, it will be displayed along with the speed of the modem-to-modem connection over the telephone line in bits/second. ( NOTE: some modems may only display the baud rate between the PC and modem.) Baud rate ...
  • Page 38 The following shows a typical error message: Figure 5: Connection Failure Message Box If you have repeated or unexplained connection failures, see Appendix A “FastLink II Connection Errors” for recommended actions. Disconnecting Once you’ve completed your work, press [Disconnect] to terminate your connection with the server.

  • Page 39: Terminal Mode

    Terminal Mode Terminal Mode provides a full-screen display that permits you to monitor FastLink II’s interaction with the modem, and lets you type directly into the modem as well. You might use Terminal Mode for the following reasons: Š To view modem result strings Š...

  • Page 40: Port Settings

    To display the Setup dialog, check the Setup button at the left of the screen. A dialog similar to the following appears: You can now edit any of the items shown. When you are through editing, press [Save] to make your changes permanent.

  • Page 41: Serial Port

    COM1 through COM4. Either your modem is connected to one of these ports by cable, or you have an internal modem with a built-in serial port. In either case, you need to select the correct serial port for FastLink II to operate.

  • Page 42: Node Address

    This node address is used as your IPX node address if you selected client-assigned IPX address. When you first install FastLink II, it will automatically generate a random node address for you. We recommend that you use the node address that you get upon installation. However, you can change the value if you like.

  • Page 43: The Modems Dialog

    Edit the settings for any modem FastLink II comes preconfigured with a list of the modems you are most likely to encounter. The settings for each modem consist of a set of strings that FastLink II will use to operate that modem.
  • Page 44 A result string is a string sent back from the modem to indicate the result of an operation. When FastLink II initiates a call to a server, it first sends three command strings in succession: Reset, Init, and Additional. It then sends the Dial string, followed by the phone number.

  • Page 45: Adding A Modem

    Response Strings The modem response strings have the following meanings: Š The OK string is returned by the modem to indicate success. Ordinarily, this string is set to OK. Š The Connect string is returned by the modem to indicate a successful connection. Ordinarily, this string is set to CONNECT.

  • Page 46: The Scripts Dialog

    Press [Save] to make your changes permanent. The Scripts Dialog The Scripts dialog lets you create and edit scripts, which are used when you create FastLink II connections in the Connections dialog. Scripts allow you to easily automate connections to a Remote Annex server with front-end security.

  • Page 47: Adding A Script

    FastLink II comes preconfigured with a Standard script, which works for many terminal servers and Internet access providers. To display the Scripts dialog, check the Scripts button at the left of the screen. A dialog similar to the following appears:...

  • Page 48: Editing Scripts

    Removing a Script To remove a script from the list: Highlight the Script Name drop-down box, and select the script you’d like to remove. Press [Remove] to remove the script from the list. Editing Scripts You can edit the selected script using the buttons to the right of the Script Window: Š...
  • Page 49 For example, if you selected expect, entered “Login:” as the String, and checked the nocase option, you would see the following display: Figure 9: Script Command Dialog When you press [OK], the command, argument, and option settings are formulated into a single script line and placed in the script.

  • Page 50: Displaying Port Statistics

    FastLink II’s Port Statistics display provides statistics on data traffic to help diagnose any problems that you may have. Note that the statistics are cleared each time you reload the FastLink II ODI driver, and they are cumulative over all connection sessions.
  • Page 51 To view the Port Statistics display, check the Port Statistics button at the left of the screen. A display similar to the following appears: Figure 10: FastLink II Statistics Screen The following table describe these statistics.
  • Page 52 Statistic Character Driver Statistics Rx total Rx errors Rx buffer overruns Rx flow off Tx total Packet Statistics Total packets sent Total packets received Checksum errors Send packet too small Send packet too big No ECB available Receive packet overflow Receive packet too big Receive packet too small Send packet miscellaneous...

  • Page 53: Housekeeping

    The Comm Port Test option displays a list of available serial ports and determines the UART type for each. NOTE: The Comm Port Test must be performed from the DOS version of the FastLink II interface; that is, from FLINK.EXE run from the DOS command line. This is because this test must access hardware directly;...
  • Page 54 The Comm Port Test displays information about the serial ports that are available on your PC. To display this information: From the main menu, select Housekeeping. From the Housekeeping menu, select Comm Port Test. FastLink II surveys your serial ports and display the following information about each: Š The COM port number Š...

  • Page 55: Flink.exe Command Line Options

    FLINK.EXE Command Line Options The FLINK.EXE command (the FastLink II DOS User Interface) offers several command line options that let you: Š Connect and disconnect without running the full-screen interface. Š Run the Comm Port Test option without running the full-screen interface.

  • Page 56: Flinkw.exe Command Line Options

    However, many laptops have gray-scale displays that represent different colors with various shades of gray. Sometimes the result is that some have inadequate contrast or are indistinguishable from each other. If you find such problems when you run the FastLink II User Interface, try specifying monochrome mode using the /M switch: FLINK /M FLINKW.EXE Command Line Options...
  • Page 57 FLINKW /D Automatic Program or Batch File Launch When you run the FastLink II User Interface with a connection name on the command line, you can also specify one or more programs to launch once the connection has been established.
  • Page 58 Then, you can use the macro rather than the PROXY command line after the vertical bar in the FLINKW command line: FLINKW MYOFFICE | RC FLINK.INI Settings The FLINK.INI file contains a [Settings] section with parameters that affect the programs’ operation. The following table explains these parameters:...
  • Page 59 FastLink II is disconnected with the /D option. If disabled, no message box is displayed. SuccessAction Determines what to do with the FastLink II client if a successful connection is made from the user interface or the command line. The default (0) is to have FLINKW remain active in both cases.

  • Page 60: Ii-3 Connecting From Dos

    Overview This chapter describes how to connect to the network from the DOS environment. It covers not only FastLink II, but also the other TSRs and programs you need to build an IPX stack and login to NetWare file servers. You’ll find out: Š...

  • Page 61: Making A Connection Manually

    Load LSL (the Link Support Layer): Load the FastLink II ODI driver: FLODI Run the FastLink II User Interface with the connection name on the command line: FLINK connectionname For example, to make connect to a remote access server, type: FLINK SAMPLE FastLink II initiates the connection, and notifies you when your PC is connected.
  • Page 62 NETX is Novell’s older shell program. While it works fine over FastLink II, it lacks some of the features that the VLM shell has that are useful for remote access. To use VLM, type:...
  • Page 63 Be sure to include the drive and full pathname of the local login script. Creating a Local Login Script Your FastLink II Administrator can help you set up a local login script. Most login scripts consist primarily of ATTACH commands to connect to additional file servers, MAP commands to create network drives, and CAPTURE commands to redirect printer ports to network printers.

  • Page 64: Breaking The Connection

    Log out from any NetWare file servers you are attached to: LOGOUT Break the FastLink II connection to the Remote Annex server: FLINK /D You’ve now disconnected, but all modules are still loaded. If you’d like to reconnect, just re-establish your FastLink II connection and log in again.

  • Page 65: Making And Breaking Connections With Batch Files

    Š It lets you keep local copies of programs you normally run from the network, and automatically runs the local copy even when the remote copy of the program is called for. You might use FLCACHE for...
  • Page 66 How FLCACHE Works FLCACHE intercepts requests to run DOS programs from network drives, and prompts you either to run the program, to download it, or to cancel the operation. By intercepting these requests, FLCACHE provides a warning that you may be accidentally running a program over a relatively slow dial-up connection.
  • Page 67 The default is the FLCACHE directory off the current directory Unloads FLCACHE from memory Sets the file size threshold in kilobytes. Smaller files will be loaded normally over the network. Default: /S=5 Disables FLCACHE notification Enables FLCACHE notification after using /D Provides the warning only.

  • Page 68: Ii-4 Connecting From Windows

    This chapter describes how to connect to the network from the Windows environment. It covers not only FastLink II, but also the other TSRs and programs you need to build an IPX stack and login to NetWare file servers. You’ll find out: Š...

  • Page 69: Before You Connect

    If you requested Novell NetWare Files installation, then the last line of your AUTOEXEC.BAT should be: CALL C:\FLINK\LOADVLM This will load all the required drivers you need to run FastLink II from Windows. If you don’t have this line in your AUTOEXEC.BAT, you can invoke LOADVLM.BAT with the following command: LOADVLM Alternatively, you can load each driver manually.

  • Page 70: Connecting To The Remote Access Server

    Connecting to NetWare File Servers Once you have made a FastLink II connection, you can log into NetWare file servers, map drives, capture printers, then log out when you’re done. All these operations can be performed from Novell’s NetWare User Tools (NWUSER.EXE).

  • Page 71: Using Custom Windows Icons

    These icons use the FLINKW.EXE command line for connecting to a Remote Annex server and launching programs or batch files once connected. See the section “FLINKW Command Line Options” in the “FastLink II User Interface” chapter for a description of how these options work.
  • Page 72 Use Program Manager’s File New command to create a new Program Item in the group of your choice. Set the Command Line field to run the FastLink II User Interface and specify a connection name as an argument. For example, to create a FastLink II icon that uses the DIAL connection, you would enter: C:\FLINK\FLINKW.EXE SAMPLE...
  • Page 73 Use Program Manager’s File New command to create a new Program Item in the group of your choice. Set the Command Line field to run the FastLink II User Interface with a connection name as an argument, followed by a vertical bar and the name of the .PIF file you just created.
  • Page 74 For example, to create a FastLink II icon that uses the DIAL connection and then runs a batch file specified in MYLOGIN.PIF, enter the following in the Command Line field: C:\FLINK\FLINKW.EXE SAMPLE | C:\FLINK\MYLOGIN.PIF Click OK and the new icon is ready for use.

  • Page 75: Ii-A Fastlink Ii Connection Errors

    II-A FastLink II Connection Errors Connection Error Messages The following messages may appear on screen when your system encounters an error, either while trying to establish a connection, or while connected.
  • Page 76 Check the hardware and modem configuration. Try the call again later. Are you running the PPP Client, instead of the FastLink II Client? Contact the system administrator. Contact the system administrator. Contact the system administrator.
  • Page 77 Modem Error: There is no dialtone; there No dialtone may be a problem with your local connection. No network You have not connected protocols with either an IPX or an IP enabled protocol Not a dial-in port...

  • Page 78: Supported Ip Stacks

    NetManage (Chameleon 4.01) Novell (LAN Workplace for DOS/Windows 4.2, 5.1) Wall Data (Rumba for Internet 1.0) Wollongong (Pathway Access 3.1) WRQ (Reflection 2, 4.01) Information on installation and configuration of these stacks with FastLink II is provided in this document.

  • Page 79: Beame & Whiteside (Bw-Tcp 3.2)

    Beame & Whiteside (BW-TCP 3.2) Product Company Address Telephone Technical Support Telephone Installation Directions Beame & Whiteside (BW-TCP 3.2) To configure SuperTCP do the following: Run the standard BW-TCP installation. Follow the standard installation instructions. When asked to supply Driver Type, respond ODI. Now, configure your stack based on whether you want a static or dynamic IP address.
  • Page 80 Static IP Address Configuration Configuring BW-TCP for a static IP address requires configuring both BW-TCP and FastLink II for the same static IP address. To configure BW-TCP for a static IP address: Run the BW-TCP configuration utility by clicking on the Customize icon in the BW-Apps Windows group.
  • Page 81 To configure FastLink II for a dynamic IP address: Run FastLink II, and select the Connections button at the left of the screen. Highlight the Connect drop-down box, and select the connection whose settings you want to set for your IP connection.
  • Page 82 System File Requirements Your AUTOEXEC.BAT (or the file you use to load your network stack) should contain lines like these: C:\FLINK\LSL C:\FLINK\FLODI C:\BEAME\STARTNET However, if you are going to use dynamic addressing (and RARP protocol), you must defer execution of STARTNET until you have connected.

  • Page 83: Frontier (Supertcp For Windows)

    Frontier (SuperTCP for Windows) Product Company Address Telephone Technical Support Telephone Installation Directions Frontier Technologies Corporation. - SuperTCP for Windows version 4.00 To configure SuperTCP do the following: Run the standard SuperTCP installation. Follow the standard installation instructions. Configure your stack based on whether you want a static or dynamic IP address (see instructions below).
  • Page 84 Static IP Address Configuration Configuring SuperTCP for a static IP address requires configuring both SuperTCP and FastLink II for the same static IP address. To configure SuperTCP for a static IP address: Run the SuperTCP configuration utility by clicking on the SetupTCP icon in the SuperTCP Windows group Select the Interfaces icon in the left-hand side list box.
  • Page 85 Dynamic IP Address Configuration Configuring SuperTCP for a dynamic IP address requires BOOTP or RARP protocol; BOOTP provides you with the most flexibility and is what we recommend. FastLink II should be configured for dynamic IP address. To configure SuperTCP for BOOTP: Run the SuperTCP configuration utility by clicking on the SetupTCP icon in the SuperTCP Windows group.
  • Page 86 Link Driver FLODI Frame Ethernet_II Protocol IP 800 Ethernet_II Protocol ARP 806 Ethernet_II Protocol RARP 8035 Ethernet_II Make sure that your AUTOEXEC.BAT (or the file you use to load your network stack) contains lines similar to this: SET TZ=est5edt SET SUPERTCP=C:\WINDOWS\SUPERTCP.INI C:\FLINK\LSL...

  • Page 87: Ftp (Onnet V2.1 For Windows)

    To install OnNet, or configuring an existing installation of OnNet, do the following: Make sure that you have loaded the FastLink II driver (FLODI) into memory from the DOS prompt. If you need to load FastLink II, exit Windows, run FLODI from the FastLink II directory, and then run Windows again.

  • Page 88: Automatic Ip Address Configuration

    Enter your remote access server gateway address in the Router field. Static IP Address Configuration Since FastLink II will replace the OnNet IP stack values at connect time, it is not normally required to use a Static IP address. To configure FastLink II for a static IP address: Run FastLink II, and select the Connections button at the left of the screen.
  • Page 89 System File Requirement Make sure that your AUTOEXEC.BAT (or the file you use to load your network stack) contains lines similar to this: SET PCTCP=C:\PCTCP\PCTCP.INI C:\FLINK\LSL C:\FLINK\FLODI C:\PCTCP\ODIPKT C:\PCTCP\ETHDRV (for DOS applications) C:\PCTCP\VXDINIT (for Windows applications) Make sure that your NET.CFG contains the statement:...

  • Page 90: Microsoft Tcp/Ip-32 3.11 (Wfw 3.11)

    Run Network Setup from the Network group in WFW. Get to the Drivers section and select your network card. Select [Add Protocol] to add the TCP/IP protocol (which may be obtained from Microsoft). Follow the instructions for "Static IP Address Configuration" below.
  • Page 91 Static IP Address Configuration Configuring TCP/IP-32 for a static IP address requires configuring both TCP/IP-32 and FastLink II to use the same static IP address. NOTE: Before you setup WFW for TCP/IP support, you must already have configured Windows for Workgroups for basic network connectivity. If you have not done this, refer to your WFW documentation, or the README.TXT file supplied with FastLink II.
  • Page 92 Link Driver FLODI Frame Ethernet_II Note that FastLink II will not work properly if any frame statement other than Frame Ethernet_II appears after the Link Driver line. Make sure your AUTOEXEC.BAT (or the file you use to load your network stack) contains lines like these:...

  • Page 93: Netmanage (Chameleon 4.01)

    To install Chameleon do the following: Make sure that you have loaded the FastLink II driver (FLODI) into memory from the DOS prompt. If you need to load FastLink II, exit Windows, run FLODI from the FastLink II directory, and then run Windows again.
  • Page 94 To configure FastLink II for a static IP address: Run FastLink II, and select the Connections button at the left of the screen. Highlight the Connect drop-down box, and select the connection whose settings you want to set for your IP connection.
  • Page 95 To configure FastLink II for a dynamic IP address: Run FastLink II, and select the Connections button at the left of the screen. Highlight the Connect drop-down box, and select the connection whose settings you want to set for your IP connection.

  • Page 96: Novell (Lan Workplace For Dos/Windows 4.2, 5.1)

    Installation Directions Novell, Inc. - LAN Workplace Version 4.2 and 5.1 To install the LAN Workplace stack you can use the FastLink II client install and select the Novell TCP/IP Stack option. If you install the LAN Workplace product (which includes TCP/IP applications), or to configure an existing installation of LAN Workplace, do the following: Run the standard LAN Workplace installation.
  • Page 97 0.0.0.0. Static IP Address Configuration Since FastLink II will replace the LAN Workplace IP stack values at connect time, it is not normally required to use a Static IP address. To configure FastLink II for a static IP address: Run FastLink II, and select the Connections button at the left of the screen.
  • Page 98 NET.CFG built by the stack install program is sometimes placed in an NWCLIENT subdirectory underneath the stack root directory. Move the NET.CFG to the FastLink II directory. Make sure your NET.CFG contains the following lines (in addition to the Protocol TCPIP lines generated by the...

  • Page 99: Wall Data (Rumba For Internet 1.0)

    To configure RUMBA do the following: Run the RUMBA installation, and follow the standard installation instructions. When prompted for your adapter driver enter the name of the FastLink II ODI driver using the whole path as in the following line: NOTE: Make sure you provide the full path name, or the installation will not work properly.
  • Page 100 Static IP Address Configuration Configuring RUMBA for a static IP address requires configuring both RUMBA and FastLink II for the same static IP address. To configure RUMBA for a static IP address: Run the RUMBA configuration utility by clicking on the TCP/IP Configuration icon in the RUMBA Windows group.
  • Page 101 Dynamic IP Address Configuration You cannot configure RUMBA for RARP or BOOTP. However, if you need to connect to a server that requires the use of a dynamic IP address, you can manually set the address in RUMBA following the FastLink II connection.
  • Page 102 C:\FLINK\FLODI.COM PATH C:\RUMBA\TCPIP;%PATH% Check to see that FLODI.COM is executed in the FastLink II directory. The stack install program may generate a reference to FLODI.COM in a RUMBA subdirectory. You cannot correct this by simply moving FLODI.COM to the referenced directory. Instead, you should change the directory reference, as in the lines above.

  • Page 103: Wollongong (Pathway Access 3.1)

    To install PathWay Access do the following: Make sure that you have loaded the FastLink II driver (FLODI) into memory from the DOS prompt. If you need to load FastLink II, exit Windows, run FLODI from the FastLink II directory, and then run Windows again.
  • Page 104 To configure FastLink II for a static IP address: Run FastLink II, and select the Connections button at the left of the screen. Highlight the Connect drop-down box, and select the connection whose settings you want to set for your IP connection.
  • Page 105 To configure FastLink II for a dynamic IP address: Run FastLink II, and select the Connections button at the left of the screen. Highlight the Connect drop-down box, and select the connection whose settings you want to set for your IP connection.
  • Page 106 PWCONFIG -N:65 ODI -I:3 Note: this interrupt setting may be different PWTCP NOTE: Be sure that the NET.CFG is moved to the same directory where you are executing LSL.

  • Page 107: Wrq (Reflection 2, 4.01)

    WRQ (Reflection 2, 4.01) Product Company Address Telephone Technical Support Telephone Installation Directions Walker Richer & Quinn, Inc. - Reflection Version 2, 4.01 To install WRQ Reflection, or configuring an existing installation of Reflection, do the following: Run the standard Reflection installation. Follow the standard installation instructions. Configure your stack based on whether you want a static or dynamic IP address (see instructions below).
  • Page 108 Static IP Address Configuration Configuring Reflection for a static IP address requires configuring both Reflection and FastLink II for the same static IP address. To configure Reflection for a static IP address: Click on the Network Configuration icon in the TCP/IP Windows group. Select the TCP/IP category button on the left-hand side.
  • Page 109 Dynamic IP Address Configuration Configuring Reflection for a dynamic IP address requires configuring Reflection for BOOTP or RARP protocol; we recommend BOOTP, since it provides for a simpler configuration. Configure FastLink II for a dynamic IP address. To configure Reflection for BOOTP: Click on the Network Configuration icon in the TCP/IP Windows group.
  • Page 110 System File Requirements Make sure that your AUTOEXEC.BAT (or the file you use to load your network stack) contains lines similar to this: C:\FLINK\LSL C:\FLINK\FLODI C:\WRQNET\RODI /STACKS=8 Make sure that your NET.CFG file contains the following lines: Link Driver FLODI...
  • Page 111 —A— Additional string, 45 Auto-answer string, 45 automated login scripts creating, 73 —B— BOOTP, 36 Busy string, 46 —C— COM ports displaying information about, 55 command line options FLINKW, 68 Connect string, 46 connection re-establishing a broken, 42 —D— DHCP, 36 Dial string, 45 DPMS.EXE, 22 drives...
  • Page 112 —R— RARP, 36 Receive RIP/SAP, 34 Request dialback, 31 Reset string, 45 Reverse Address Resolution Protocol, 36 RIP/SAP broadcast, 34 —S— Seconds between redials, 43 Seconds to wait before redial, 43 serial port specifying for DOS and Windows, 42 software requirements FastLink, 7 Proxy, 7 —T—...

This manual is also suitable for:

Fastlink ii client pack

Table of Contents