Copyright: RideWay 1.84


ITServ RideWay

Help Index

Overview

Introduction

Dialer

Server

BreezeWay

Installation Guide

System Requirements

Network Configuration

Software Installation

RideWay Dialer Setup

RideWay Server Setup

BreezeWay Setup

Browser Setup When NOT Using BreezeWay

Browser Setup When Using BreezeWay

Telnet Application Setup When Using BreezeWay

Realplayer Setup When Using BreezeWay

FTP Application Setup When Using BreezeWay

Email Application Setup When Using BreezeWay

TCP Mapping Setup When Using BreezeWay

UDP Mapping Setup When Using BreezeWay

Access the Internet from Home via the Office LAN

Menus

RideWay Window

Dialer Menu

Server Menu

Report Menu

Tools Menu

Help Menu

Frequently Asked Questions

General Information

Setup Questions

Application Specifics

Registration

Troubleshooting


Index Command (Help Menu)

This command displays the opening screen of Help.  From the opening screen, you can jump to step-by-step instructions for using RideWay and various types of reference information.

Once you open Help, you can click the Contents button whenever you want to return to the opening screen.


Using Help Command (Help Menu)

This command displays instructions for using Help.


About Command (Help Menu)

This command displays the copyright notice and version number of your copy of RideWay.


Help Using Help Command

Context Help Command

Use the Context Help command to obtain help on some portion of RideWay.  When you choose the Toolbar's Context Help button, the mouse pointer will change to an arrow and question mark.  Then click somewhere in the RideWay window, such as another Toolbar button.  The Help topic will be shown for the item you clicked.

Shortcut

Keys:	SHIFT+F1


Title Bar

<< Show your application's title bar here. >>

The title bar is located along the top of a window.  It contains the name of the application and document.

To move the window, drag the title bar.  Note: You can also move dialog boxes by dragging their title bars.

A title bar may contain the following elements:

Application Control-menu button

Document Control-menu button

Maximize button

Minimize button

Name of the application

Name of the document

Restore button


Scroll Bars

Displayed at the right and bottom edges of the document window.  The scroll boxes inside the scroll bars indicate your vertical and horizontal location in the document.  You can use the mouse to scroll to other parts of the document.

<< Describe the actions of the various parts of the scrollbar, according to how they behave in your application. >>


Size Command (System Menu)

Use this command to display a four-headed arrow so you can size the active window with the arrow keys.

After the pointer changes to the four-headed arrow:

1.	Press one of the DIRECTION keys (left, right, up, or down arrow key) to move the pointer to the border you want to move.

2.	Press a DIRECTION key to move the border.

3.	Press ENTER when the window is the size you want.

Note:  This command is unavailable if you maximize the window.

Shortcut

Mouse:	Drag the size bars at the corners or edges of the window.


Move Command (Control Menu)

Use this command to display a four-headed arrow so you can move the active window or dialog box with the arrow keys.

Note:  This command is unavailable if you maximize the window.

Shortcut

Keys:	CTRL+F7


System Minimize Command

Minimize Command (Application Control Menu)

Use this command to reduce the RideWay window to an icon.

Shortcut

Mouse:	Click the minimize icon [image] on the title bar.

Keys:	ALT+F9


Maximize Command (System Menu)

Use this command to enlarge the active window to fill the available space.

Shortcut

Mouse:	Click the maximize icon [image] on the title bar; or double-click the title bar.

Keys:	CTRL+F10 enlarges a document window.


Next Window Command (Document Control Menu)

Use this command to switch to the next open document window.  RideWay determines which window is next according to the order in which you opened the windows.

Shortcut

Keys:	CTRL+F6


Previous Window Command (Document Control Menu)

Use this command to switch to the previous open document window.  RideWay determines which window is previous according to the order in which you opened the windows.

Shortcut

Keys:	SHIFT+CTRL+F6


Close Command (Control Menus)

Use this command to close the active window or dialog box.

Double-clicking a Control-menu box is the same as choosing the Close command.

Note:  If you have multiple windows open for a single document, the Close command on the document Control menu closes only one window at a time.  You can close all windows at once with the Close command on the File menu.

Shortcuts

Keys: 	CTRL+F4 closes a document window

ALT+F4 closes the <<YourType>> window or dialog box


Restore command (Control menu)

Use this command to return the active window to its size and position before you chose the Maximize or Minimize command.


Switch to Command (Application Control Menu)

Use this command to display a list of all open applications.  Use this "Task List" to switch to or close an application on the list.

Shortcut

Keys:	CTRL+ESC

Dialog Box Options

When you choose the Switch To command, you will be presented with a dialog box with the following options:

Task List

Select the application you want to switch to or close.

Switch To

Makes the selected application active.

End Task

Closes the selected application.

Cancel

Closes the Task List box.

Cascade

Arranges open applications so they overlap and you can see each title bar.  This option does not affect applications reduced to icons.

Tile

Arranges open applications into windows that do not overlap.  This option does not affect applications reduced to icons.

Arrange Icons

Arranges the icons of all minimized applications across the bottom of the screen.


Overview

Introduction

RideWay consists of three components:

•	Dialer : controls the dialing and connection to a Internet access provider (or Internet Service Provider, ISP)

•	Server : provides DNS proxy service and SOCKS (version 4) proxy service.

•	BreezeWay : provides Internet email (for both SMTP and POP3), FTP, RealPlayer, Telnet, and HTTP, Security/Secure proxy services and TCP/UDP mappings for non-SOCKS compliant applications.

The Dialer component allows a PC running Windows 95/NT to:

•	dial and connect to an Internet access provider(ISP),

•	redial if the telephone line is busy,

•	establish a PPP connection to the Internet access provider(ISP).

The Server component allows Client PCs running Windows NT, 95 or 3.1 to:

•	browse the WWW (World-Wide Web),

•	send and receive emails,

•	read and post news,

•	telnet to any host in the Internet,

•	transfer files to/from any hosts in the Internet, and

•	resolve computer names.

The BreezeWay component allows Client PCs to:

•	send and receive Internet emails using email applications which are not SOCKS-compliant, such as Eudora,  Microsoft Outlook, and Microsoft Exchange Client.

•	transfer files using FTP applications which are not SOCKS-compliant, such as Windows FTP applet, WS_FTP, and CuteFTP.

•	access your shell account or read posts from BBS by Telnet software, such as Microsoft Telnet, NetTerm.

•	listen to RealAudio and view RealVideo via RealPlayer.

•	browse the WWW using non-SOCKS-compliant browsers.

•	read Internet News and chat.

RideWay is installed and run on a Windows 95/NT PC designated as the Server PC for a LAN. All other PCs connected to the LAN will access the Internet through this Server PC. These PCs are Client PCs of the Server PC. RideWay should only be installed on the Server PC. All Client PCs should be configured to access the Internet through the Server PC.

There are two typical usage scenarios for RideWay:

•	Small Office: With RideWay, small offices and home-based businesses can perform the same Internet communication functions (browsing, e-mail, file transfer) as large organizations. With a PC running Windows 95/NT, a connection to the Internet, and a LAN, other machines (Windows 95/NT, Macintosh, Windows 3.1) can simultaneously access the Internet.

•	Home: With RideWay installed on a Windows 95/NT computer at work, users can dial into that PC to access the Internet from Home via the Office LAN.


Dialer

Any Windows 95/NT PC equipped with a modem, ‘Dial-Up Networking’, and Dial-Up Scripting Tool may serve as the Server PC. A Server PC uses RideWay’s Dialer to establish a connection to the Internet. The Dialer is seamlessly integrated with the Windows 95/NT’s Dial-Up Networking.


Server

The Server component provides two services:

•	DNS proxy service and

•	SOCKS proxy service

When accessing the Internet, an application can use IP addresses directly or use computer names and rely on the DNS service to resolve the computer names. The DNS proxy service of RideWay provides this name resolution function for all PCs connected to the LAN.

The SOCKS proxy service provided by RideWay allows all PCs to access the Internet via the Server PC.


BreezeWay

The BreezeWay component provides:

•	Email proxy service which includes SMTP and POP3 proxy,

•	FTP proxy service,

•	Telnet proxy service,

•	RealPlayer proxy service,

•	HTTP and Security/Secure proxy service,

•	TCP mapping, and

•	UDP mapping.

The SMTP and POP3 proxy services provided by BreezeWay allows all email applications which are not supporting SOCKS protocol to send and receive Internet emails. Please refer to BreezeWay Setup and Email Application Setup When Using BreezeWay for detailed setup instructions.

The FTP proxy service provided by BreezeWay allows all FTP applications which are not supporting SOCKS protocol to transfer files. Please refer to BreezeWay Setup and FTP Application Setup When Using BreezeWay for detailed setup instructions.

The Telnet proxy service provided by BreezeWay allows all Telnet applications which are not supporting SOCKS protocol to telnet to remote computers. Please refer to BreezeWay Setup and Telnet Application Setup When Using BreezeWay for detailed setup instructions.

The RealPlayer proxy service provided by BreezeWay allows RealPlayer to listen to RealAudio and view RealVideo. Please refer to BreezeWay Setup and RealPlayer Setup When Using BreezeWay for detailed setup instructions.

The HTTP and Security/Secure proxy services provided by BreezeWay allows browsers which are not supporting SOCKS protocol to surf the WWW. Please refer to BreezeWay Setup and Browser Setup When Using BreezeWay for detailed setup instructions.

The TCP mapping service provided by BreezeWay maps a local port of the Server PC to a remote server and port, effectively creating a data pipe between a Client PC and a remote server. TCP mapping service can provide proxy services for many applications, such as Internet News. Please refer to BreezeWay Setup and TCP Mapping Setup When Using BreezeWay for detailed setup instructions.

The UDP mapping service provided by BreezeWay maps a local port of the Server PC to a remote server and port, effectively creating a data pipe between a Client PC and a remote server. UDP mapping service can provide proxy services for many applications, such as ICQ. Please refer to BreezeWay Setup and UDP Mapping Setup When Using BreezeWay for detailed setup instructions.


System Requirements

Scenario 1:

In a small office or home to allow more than one computer to simultaneously access the Internet using one phone line, one modem with RideWay, you will need to configure one Server PC and some Client PC(s), all connected by a LAN.

The Server PC must:

•	run Windows 95/NT with Dial-Up Networking component installed,

•	have a modem and an account provided by an ISP to access to the Internet,

•	have the TCP/IP protocol installed,

•	have RideWay installed, and

•	have a Network Interface Card connecting to the Client PCs via a LAN.

The Client PC(s) must:

•	have the TCP/IP protocol installed and

•	connect to the Server PC via a LAN.

Scenario 2 :

For users who want to access the Internet by dialing from

his or her home Windows 95/NT PC to the Windows 95/NT PC at work the following is required:

The Server PC at office must:

•	be able to access Internet through the LAN of your office,

•	run Windows 95/NT with Dial-Up Networking component installed,

•	have the TCP/IP protocol installed,

•	have RideWay installed,

•	have a modem, and

•	have the Dial-Up Networking Server installed.

For Windows 95: Dial-Up Networking Server is a part of the Microsoft Plus! For Windows 95.

For Windows NT: You can activate this server from the Control Panel.

The Client PC at home must:

•	have the TCP/IP protocol installed,

•	have a modem for dialing to the Server PC,

•	Dial-Up Networking installed.


Network Configuration

Note: Also see our extensive online help section with detailed step-by-step installation instructions at: ‘http://www.itserv.com/rideway’.

RideWay uses the TCP/IP protocol to communicate with Internet and your Clients PC. The following shows how to configure the TCP/IP on both the Server PC and Client PCs in this section. The IP address of the Server PC on the LAN side is set to the same subnet as that of Client PCs’. We recommend that you use a private IP subnet, such as 192.168.1.0. Pick IP address 192.168.1.1 and subnet mask 255.255.255.0 for the Server PC and 192.168.1.2, 192.168.1.3, ... etc. for the Client PCs.

PC	IP Address	Subnet Mask	DNS
Server PC	192.168.1.1	255.255.255.0	DNS Server Address of ISP
Client PC 1	192.168.1.2	255.255.255.0	192.168.1.1
Client PC 2	192.168.1.3	255.255.255.0	192.168.1.1
Client PC 3	192.168.1.4	255.255.255.0	192.168.1.1

We will use these IP addresses and subnet masks in our example.

Note: The IP address assigned to the network card should be different from the IP address assigned by your ISP for you modem.

Please make sure that your LAN has been installed correctly. You may double-click the ‘Network Neighborhood’ icon on your desktop to see if the Server PC and the Client PC(s) can be found on the list. If not, please read the documents in Windows NT/95 Help relating to Network Troubleshooting to fix the problem.

Install/Setup TCP/IP on the Server/Client PC

Please follow these instructions to install and setup the TCP/IP protocol on the Server PC and each Client PC:

For Windows 95:

1.	Go into the Control Panel.

2.	Double click the Network icon.

3.	Verify that following network components

TCP/IP

Dial-Up Adapter

TCP/IP -> (name of your network card)

are listed. If yes, you have installed the TCP/IP protocol. Go to step 9.

4.	Click Add.

5.	Select the Protocol icon and then click Add.

6.	Under Manufacturers, select Microsoft.

7.	Under Network Protocols, select TCP/IP and click OK.

8.	Both TCP/IP -> Dial-Up Adapter and TCP/IP -> (name of your network acrd) should now appear in the network component list.

9.	Click Properties.

10.	Click IP Address tab.

11.	Click Specify an IP Address from the IP Address tab in the IP Address box, if there is no IP address already, input an address such as 192.168.1.1 for Server PC, and 192.168.1.2 for a Client PC.

12.	In the Subnet Mask box, enter 255.255.255.0.

13.	Click the DNS tab, click Enable DNS radio, and then, in the Host and Domain boxes, type your host name and domain name, respectively. These names identify you on the Internet.

14.	In the DNS Server Search Order box, input the IP address of the DNS server of your LAN. If your network has more than one DNS server, input the IP address of each DNS server and then click Add. If you have no DNS server on your LAN, already use the Server PC as your DNS server.

Note: DNS settings are currently global across all interfaces of TCP/IP. This allows you to rely on a secondary DNS server if the primary DNS server is down. The first server listed is the first one searched

15.	Click OK.

16.	Restart Windows 95.

Note: The IP address of the Server PC is specified by you for your internal LAN. The IP address assigned by your ISP for the modem/PPP connection has no role in the configuration of RideWay.

For Windows NT:

1.	Go into the Control Panel.

2.	Double click the Network icon.

3.	If TCP/IP Protocol is not listed, then do the following steps.

4.	click Add.

5.	Double-click TCP/IP Protocol to add the TCP/IP protocol and then click OK.

6.	TCP/IP Protocol should appear in the list.

7.	Click Properties.

8.	Click IP Address tab.

9.	Click Specify an IP Address from the IP Address tab in the IP Address box, if there is no IP address already, input an address such as 192.168.1.1 for the Server PC, and 192.168.1.2 for the a Client PC.

10.	In the Subnet Mask box, enter 255.255.255.0.

11.	Click DNS tab, In the DNS Server Search Order box, input the IP address of your LAN’s DNS server. If your network has more than one DNS server, input the IP Address of each DNS server and then click Add. If you have no DNS server on your LAN already, use the Server PC as your DNS server.

12.	Click OK.

Network Configuration Test

Please follow these instructions to verify that your network is properly configured:

1.	On the Server PC, open a DOS Command Prompt window (Start->Programs->MS-DOS Prompt)

2.	Use the ping utility by typing ‘ping 192.168.1.2’ (the IP address of Client PC). Press Enter key in the Command Prompt window to check if the Server PC can communicate with the Client PC. Try to ping the IP address of each Client PC from the Server PC.

3.	From each Client PC, try to ping the Server PC by typing ‘ping 192.168.1.1’.


Installation

Software Installation

RideWay should be installed only on a PC (the Server PC) that has direct access to the Internet via a LAN or a dial-up connection. Do not install RideWay on PCs (Client PCs) which will access the Internet through RideWay.

RideWay is distributed as either

•	rideway-setup.exe: a self-extract executable file or

•	rideway-setup.zip: a ZIP file

If you download 'rideway-setup.exe', run this executable either at a DOS prompt or from Windows 95/NT Explorer to start the installation.

If you download 'rideway-setup.zip', please unzip this file and extract the 2 unzipped files ('Setup.exe' and 'Readme.txt') to a directory of your choice.  Run the executable ('Setup.exe') either at a DOS prompt or from Windows 95/NT Explorer to start the installation.

The installation process is straight-forward and is guided by InstallShield(TM). You need only supply your name and company name during the installation process. If you have an earlier version of RideWay installed on your system, you should install the new version to a different directory. Otherwise the installation will not complete correctly. When installation is finished, you can find RideWay in the RideWay ...' group in the Windows 95/NT 'Start' menu.

RideWay can be un-installed through 'Control Panel->Add/Remove Programs'. Select RideWay ...' and doubly-click the 'Add/Remove' button. You will then be asked for a confirmation before RideWay is removed.

When RideWay is run the first time after the installation it will check if there is an earlier version on your system. If so it will ask if you want to copy the settings from the earlier version. So if you want to keep your old settings you should un-install the old version after you have installed the new version and run the new version for at least one time.

RideWay will be installed initially as an evaluation copy. It is runable for 30 days from the date of installation. After the evaluation period has expired, you have to register RideWay with ITServ Inc.  in order to run it again. Registered copy and evaluation copy of RideWay are exactly the same except that the registered copy will not expire. Please refer to How to Register RideWay for the online registration procedure.


Dialer Setup

RideWay Dialer Setup

Any Windows 95/NT PC equipped with a modem, Dial-Up Networking, and Dial-Up Scripting Tool may serve as the Server PC. The Server PC uses RideWay Dialer to establish a connection to the Internet. The Dialer is seamlessly integrated with Windows 95/NT’s Dial-Up Networking. Dial-Up Scripting Tool enables you to establish the Internet connection without having to input your name, password or choose the connection protocol manually. If your ISP accepts the User name and Password saved in a Dial-Up Networking entry, you don’t have to use a script.

In August 1996 Microsoft released the ISDN 1.1 Accelerator Pack that simplified the setup of dial-up scripts. We recommend the installation of the ISDN 1.1 Accelerator Pack on the Server PC. The ISDN 1.1 Accelerator Pack may be downloaded from Microsoft (http://premium.microsoft.com/support/downloads/dp2281.asp).

Note: If you do not know how to use the scripting tool, manually initiate the PPP connection (connect to the Internet like normal) and then start the RideWay Server. However, you will not be able to take advantage of  on-demand dialing feature of RideWay.

To Setup the Dialer

For Windows 95:

1.	Choose the Dial-Up Networking command from the Dialer menu.

2.	Doubly-click Make New Connection icon to create a Dial-Up connection entry for your Internet access provider (ISP) if you have not done so yet.

3.	Create a script for the Dial-Up connection.

4.	Choose Dialer Control command of the ‘Dialer’ menu or Toolbar

5.	Select your Internet access provider (ISP) as the Default Connection from the drop-down list box.

6.	Check Enable On-demand dialing if you want RideWay Dialer to dial/connect to the ISP specified by the Default Connection. As default, all requests, including DNS, SOCKS, Email, FTP, HTTP, RealPlayer, Telnet, TCP mapping, and UDP mapping requests will trigger the Dialer to connect to the Default Connection. In some environment, client PCs issues DNS requests to resolve computer names even when they are not accessing the Internet. In this case, you should uncheck including DNS requests box so that the Dialer won’t be triggered by these unnecessary DNS requests. When the  including DNS requests is unchecked a client application can trigger the Dialer by sending SOCKS, Email, FTP, HTTP, RealPlayer, Telnet, TCP mapping, and UDP mapping requests with IP addresses instead of a domain names. For example, you should type http://207.196.61.6 instead of http://www.itserv.com in your browser on a client PC to trigger the Dialer to connect to the Default Connection. After the connection is established domain names can be used.

7.	Specify the value for Disconnect after --- minutes of inactivity. RideWay will terminate the connection to the Default Connection after the specified period of inactivity from client PCs.

8.	Click OK.

For Windows NT:

To Create a new Dial-Up Networking entry if you do not have one for your ISP:

1.	Select the Dial-Up Networking command from the Dialer menu.

2.	Click New and follow the instructions to make a new entry for your Internet access provider if you have not done so already.

3.	Click More and choose Edit entry and modem property to open the Edit Phonebook Entry window. Click the Script tab and click Edit script to make a script if necessary.

4.	From the drop down menu, choose the script you have created and click the Run this script radio button.

To Select a Dial-Up Networking entry as your Default Connection:

1.	Select the Dialer Control command of Dialer menu or Toolbar.

2.	Select your Internet access provider as the Default Connection from the drop-down list box.

To initiate automatic redialing when a connection attempt fails:

1.	Click on the Redial Control button.

2.	Click More and then Choose preferences.

3.	In the Dialing tab, specify a positive number in Number of redial attempts.

4.	Check Redial on link failure.

5,	In the Appearances tab, uncheck Always prompt before auto-dialing.

6. 	Click OK and then the Close button.

To Setup the On-demand dialing:

1.	Check Enable On-demand dialing if you want RideWay Dialer to dial/connect to the ISP specified by the Default Connection. As default, all requests, including DNS, SOCKS, Email, FTP, HTTP, RealPlayer, Telnet, TCP mapping, and UDP mapping requests will trigger the Dialer to connect to the Default Connection. In some environment, client PCs issues DNS requests to resolve computer names even when they are not accessing the Internet. In this case, you should uncheck including DNS requests box so that the Dialer won’t be triggered by these unnecessary DNS requests. When the  including DNS requests is unchecked a client application can trigger the Dialer by sending SOCKS, Email, FTP, HTTP, RealPlayer, Telnet, TCP mapping, and UDP mapping requests with IP addresses instead of a domain names. For example, you should type http://207.196.61.6 instead of http://www.itserv.com in your browser on a client PC to trigger the Dialer to connect to the Default Connection. After the connection is established domain names can be used.

2.	Specify the value for Disconnect after --- minutes of inactivity. RideWay will terminate the connection to the Default Connection after the specified period of inactivity from client PCs.

3.	Click the Redial Control button.

4.	Click More and then Choose preferences.

5.	In the Appearances tab, uncheck Always prompt before auto-dialing.

6. 	Click OK and then the Close button.

7.	Click OK to save the setup information you have given.


Server Setup

RideWay Server Setup

Note: Also see our online help section with detailed step-by-step instructions at : ‘http://www.itserv.com/rideway’.

The RideWay Proxy Server needs to know the IP address of your DNS server. Before trying to setup the Server make sure

•	the Server PC (a Windows 95/NT PC) is connected to the LAN,

•	the Windows 95/NT’s TCP/IP protocol is installed,

•	the IP address of the Server PC on the LAN side is set to the same subnet as that of Client PCs’. We recommend that you use a private IP subnet address for your LAN, such as 192.168.1.0 with subnet mask 255.255.255.0.

To setup the Server

1.	Choose the Server Control command under Server Menu or Toolbar.

2.	You may need to enter DNS server’s IP address. Ask your ISP for the DNS server’s IP address or connect to your ISP and then choose Tools and then IP configuration to check your DNS server’s IP address.

3.	Follow the instructions in BreezeWay Setup to set up BreezeWay.

4.	Choose Start command to start the SOCKS Proxy Server.


BreezeWay Setup

BreezeWay is a component of RideWay, which provides proxy services for non-SOCKS compliant applications to access the Internet via RideWay.

The Internet email proxy provided by BreezeWay includes both SMTP and POP3 proxy services. Email applications running on Client PCs will all use the same SMTP server specified in BreezeWay for sending Internet emails. You may specify the SMTP server by its host name or IP address. Each Client PC can specifies a different POP3 server for retrieving Internet emails. POP3 server’s information is specified in each email application running on Client PCs. Please refer to Email Application Setup When Using BreezeWay for detailed setup instructions.

FTP destination is specified in each FTP application running on Client PCs. Please refer to FTP Application Setup When Using BreezeWay for detailed setup instructions.

Telnet destination is entered interactively in each Telnet application running on Client PCs. Please refer to Telnet Application Setup When Using BreezeWay for detailed setup instructions.

RealAudio/Video server’s information is specified in RealPlayer running on Client PCs. Please refer to RealPlayer Setup When Using BreezeWay for detailed setup instructions.

Browser’s proxy information is specified in browsers running on Client PCs. Please refer to Browser Setup When Using BreezeWay for detailed setup instructions.

In order to use TCP mapping applications running on Client PCs need to be set up. Please refer to TCP Mapping Setup When Using BreezeWay for detailed setup instructions.

In order to use UDP mapping applications running on Client PCs need to be set up. Please refer to UDP Mapping Setup When Using BreezeWay for detailed setup instructions.

To setup the BreezeWay:

1.	Choose the BreezeWay command from Server Menu or Toolbar to open the BreezeWay Dialog Box,

2.	Check ‘Enable BreezeWay’,

3.	Check ‘Enable HTTP and Security/Secure proxy’ and use the provided HTTP proxy port value,

4.	Check ‘Enable Telnet proxy’ and use the provided Telnet port value,

5.	Check ‘Enable RealPlayer proxy’ and use the provided RealPlayer proxy port value,

6.	Check ‘Enable FTP proxy’ and use the provided Control port and Data port values,

7.	Check ‘Enable Email proxy (SMTP/POP3)’, enter SMTP server’s host name or IP address in the box provided, and used the provided SMTP and POP3  port values,

8.	Check ‘Enable TCP mapping’ and enter mapping proxies,

9.	Check ‘Enable UDP mapping’ and enter mapping proxies,

10.	Click OK button, and

11.	Click OK button again to restart the server if it is currently running.


Browsers Setup When NOT Using BreezeWay

Browser Setup When NOT Using BreezeWay

Before trying to setup a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

Use the following step-by-step instructions to configure Netscape Navigator/Communicator and Microsoft Internet Explorer to access the Internet through RideWay. You need to configure both RideWay on the Server PC and the Navigator/Communicator or Internet Explorer on Client PCs.

RideWay on Server PC:

1.	Choose the Server Control command under Server Menu or Toolbar.

2.	You may need to enter DNS server’s IP address. Ask your ISP for the DNS server’s IP address or connect to your ISP and then choose Tools and then IP configuration to check your DNS server’s IP address.

3.	Choose Start command  under Server Menu or Toolbar to start the SOCKS Proxy Server.

Netscape Navigator/Communicator 4.x on Client PCs:

1.	Click Edit, then choose Preferences,

2.	Click Advanced,

3.	Click the Proxies tab,

4.	Select Manual Proxy Configuration,

5.	Press the View button to display a dialog box,

6.	Enter the Server PC’s IP Address (e.g. 192.168.1.1) for Socks and 1080 for Port,

7.	Make sure all other proxy fields are blank,

8.	Click OK,

9.	Click OK again

Microsoft Internet Explorer 4.x on Client PCs:

Some distributions of the Internet Explorer 4.0 do not correctly install a necessary .DLL file supporting Socks 4 proxy (wsock32n.dll). This makes it difficult to work with RideWay or any other proxy server. In order to make IE4 to talk to any Socks 4 proxy server, including RideWay, you need to manually extract the DLL from one of the IE4 distribution files and copy it into Windows system directory. If your version of IE4 has difficulties working with RideWay please follow the steps below to extract the DLL. Otherwise follow the Setup Instructions below.

1.	Start MS-DOS,

2.	Change Directories (Type 'cd') to the directory where Internet Explorer  4's distribution files are located. If you do not know the directory, find the file IE4_S4.CAB from the Start button. The directory that contains the file is the directory you want to change directories to,

3.	Run the following commands in sequence:

•	> extract ie4_s4.cab

•	> extract ie4_4.cab wsock32n.dll

•	> copy wsock32n.dll <Windows system directory> where <Windows system directory> is the system directory under the Windows root, normally it is \Windows\system.

•	Restart your computer.

Setup instructions:

1.	Select View and then choose the Internet Options menu item.

2.	Click the Connection tab.

3.	Check the Access the Internet using a proxy server box.

4.	Click Advanced.

5.	Enter the Server PC’s IP Address (e.g. 192.168.1.1) for Socks and 1080 for Port,

6.	Make sure all other Proxy fields are blank and the Use the same proxy server for all protocols box is NOT checked.

7.	Click OK.

8.	Click OK again


Browser Application Setup on Client PC

Browser Setup When Using BreezeWay

Before setting a browser on a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

•	the host name(or IP address) and port numbers of SOCKS, HTTP and Security/Secure proxies where RideWay is running.

Use the following step-by-step instructions to configure Netscape Navigator/Communicator and Microsoft Internet Explorer to access the Internet through RideWay. You need to configure both BreezeWay on the Server PC and the Navigator/Communicator or Internet Explorer on Client PCs.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable HTTP and Security/Secure proxy box and enter 80 in the HTTP proxy port.

3.	Click OK.

Netscape Navigator/Communicator 4.x on Client PCs:

1.	Click Edit,

2.	Click Preferences,

3.	Double click on Advanced in Category box,

4.	Click Proxies,

5.	Check radio button by Manual proxy configuration,

6.	Click View button and Manual Proxy Configuration dialog box is shown up,

7.	Enter Server PC’s IP address (e.g. 192.168.1.1) into the Address of proxy server to use box for these services: HTTP, Security, FTP, Socks. For the Port enter 80 for both HTTP and Security, 21 for FTP, and 1080 for Socks.

8.	Click OK button on Manual Proxy Configuration dialog box,

9.	Click OK button on Proxies dialog box.

Microsoft Internet Explorer 4.x on Client PCs:

Some distributions of the Internet Explorer 4.0 do not correctly install a necessary .DLL file supporting Socks 4 proxy (wsock32n.dll). This makes it difficult to work with RideWay or any other proxy server. In order to make IE4 to talk to any Socks 4 proxy server, including RideWay, you need to manually extract the DLL from one of the IE4 distribution files and copy it into Windows system directory. If your version of IE4 has difficulties working with RideWay please follow the steps below to extract the DLL. Otherwise follow the Setup Instructions below.

1.	Start MS-DOS.

2.	Change Directories (Type 'cd') to the directory where Internet Explorer  4's distribution files are located. If you do not know the directory, find the file IE4_S4.CAB from the Start button. The directory that contains the file is the directory you want to change directories to.

3.	Run the following commands in sequence:

•	> extract ie4_s4.cab

•	> extract ie4_4.cab wsock32n.dll

•	> copy wsock32n.dll <Windows system directory> where <Windows system directory> is the system directory under the Windows root, normally it is \Windows\system.

•	Restart your computer.

Setup instructions:

1.	Click View,

2.	Click Internet Options and Internet Options dialog box is shown up,

3.	Click Connection tab,

4.	Click on check box by Access the Internet using a proxy server,

5.	Click Advanced button and Proxy Settings dialog box is shown up,

7.	Enter Server PC’s IP address (e.g. 192.168.1.1) into the Address of proxy to use box for these services: HTTP, Secure, FTP, Socks. For the Port enter 80 for both HTTP and Secure, 21 for FTP, and 1080 for Socks.

7.	Click OK button Proxy Settings dialog window,

8.	Click OK button Internet Options dialog window.


Email Application Setup on Client PC

Email Application Setup When Using BreezeWay

Before trying to setup an email application on a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

•	the email application supports SMTP and POP3 protocols for Internet emails.

Use the following step-by-step instructions to configure popular email applications. You need to configure both BreezeWay on the Server PC and the email applications on Client PCs.

For the example in the following instructions assumes the POP3 account that your ISP assigned to you is pop3user, the POP3 server at your ISP is pop3server.isp.com, the SMTP server at your ISP is smtpserver.isp.com, the IP address of the Server PC (which is running RideWay/BreezeWay) is 192.168.1.1, and your Internet email address is user@company.com.  To use Email proxy, you must specify the Server PC as your SMTP and POP3 servers and use pop3user#pop3server.isp.com as your account name. “#pop3server.isp.com” gives the real POP3 server information to BreezeWay. The following table shows the setting changes when using BreezeWay:

Original	Using BreezeWay

----------------------------------------------------------------------------------------------

POP3 server	pop3server.isp.com	192.168.1.1

Account name:	pop3user	pop3user#pop3server.isp.com

Password	password	password

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable Email proxy box, enter 25 in the SMTP port, 110 in the POP3 port, and smtpserver.isp.com in the SMTP server box.

3.	Click OK.

Eudora 1.x on Client PCs:

1.	Click Tools,

2.	Click Options,

3.	Click Getting Started and enter your POP account information as

<POP3 account>#<POP3 server>@<Server PC>

where <POP3 account> is the POP3 account that your ISP assigned to you,

<POP3 server> is the computer name or IP address of a POP3 server at your ISP,

<Server PC> is the IP address of the PC which is running RideWay/BreezeWay.

For example, pop3user#pop3server.isp.com@192.168.1.1.

4.	Click Personal Information and enter your email address into the ‘Return address’ box,

For example, user@company.com.

5.	Click Hosts and enter Server PC’s IP address into the ‘SMTP’ box, For example, 192.168.1.1.

6.	Click OK,

Eudora Pro 4.x on Client PCs:

1.	Click Tools,

2.	Click Options,

3.	Click Getting Started and enter your email address into the ‘Return address’ box,

For example, user@company.com.

4.	Enter Server PC’s IP address into the Mail Server (Incoming) box. For example, 192.168.1.1.

5.	Enter <POP3 account>#<POP3 server> into Login Name box, For example, pop3user#pop3server.isp.com,

6.	Click Sending Mail and enter Server PC’s IP address into the ‘SMTP Server’ box, For example, 192.168.1.1.

7.	Click OK,

Microsoft Outlook 97

Microsoft Exchange 4.x

Windows Messaging 4.x

Inbox icon on Client PCs:

Note: Micorsoft uses many different names for its email programs on both Windows 95 and NT. All of the above Microsoft email programs use the same Internet Mail mailbox and share the same configuration.

1.	Click Tools,

2.	Click Services,

3.	If Internet Mail appears in the Services box, click Internet Mail, and then Properties. Otherwise click Add…, then Internet Mail, and finally OK,

4.	Enter your full name into Full name box,

5.	Enter your email address into E-mail address box, For example, user@company.com.

6.	Enter Server PC’s IP address into Internet Mail server box, For example, 192.168.1.1,

7.	Enter <POP3 account>#<POP3 server> into Account name, For example, pop3user#pop3server.isp.com,

8.	Enter POP3 account password into Password,

9.	Click OK,

Microsoft Outlook Express 4.x on Client PCs:

1.	Click Tools and then choose Accounts,

2.	Click Mail,

3.	Click Add and then choose Mail,

4.	Type in a Display name and then click Next,

5.	Enter your email address into E-mail address box, For example, user@company.com

and then click Next,

6.	Choose POP3 for My incoming mail server,

7.	Enter Server PC’s IP address into Incoming mail (POP3 or IMAP) server box, For example, 192.168.1.1

8.	Enter Server PC’s IP address into Outgoing mail (SMTP) server box, For example, 192.168.1.1,  and then click Next,

9.	Click Log on using,

10.	Enter <POP3 account>#<POP3 server> into POP account name, For example, pop3user#pop3server.isp.com,

11.	Enter POP3 account password into Password, and then click Next,

12.	Type a name for the Internet mail account name, and then click Next,

13.	Click Connect using my local area network (LAN), and then click Next,

14.	Click Finish,

All other non-SOCKS compliant email applications on Client PCs:

For all other non-SOCKS compliant email applications that supports SMTP and POP3 protocols you need to find the place where you can enter the following information:

1.	Your E-mail address (or Return address),

2.	Server PC’s IP address

3.	POP3 Server’s name or IP address,

4.	POP3 Account name, and

then enter

1.	Your E-mail address (or Return address), For example, user@company.com,

2.	Server PC’s IP address as both SMTP and POP3 servers, For example, 192.168.1.1,

3.	<POP3 account>#<POP3 server> name into Account name, For example, pop3user#pop3server.isp.com,

Netscape Communicator 4.x on Client PCs:

Netscape Communicator is a SOCKS-compliant email application which means you don’t need to set up anything special in order to use it with RideWay/BreezeWay. Just follow the instructions in the previous section to set up SOCKS server and follow the instructions below to set up  POP3 and SMTP information:

1.	Click Edit,

2.	Click Preferences,

3.	Doubly-click Mail & Groups,

4.	Click Identy,

5.	Enter Your name,

6.	Enter your Email address, for example user@company.com,

7.	Click Mail Server,

8.	Enetr your POP3 account name into Mail server user name, for example, pop3user,

9.	Enter SMTP server into Outgoing mail (SMTP) server box, For example, smtpserver.isp.com,

10.	Enter POP3 server into Incoming mail server box, For example, pop3server.isp.com,

11.	Click POP3 under Mail Server Type,

12.	Click OK,

All other SOCKS compliant email applications on Client PCs:

For all other SOCKS compliant email applications that supports SMTP and POP3 protocols you need to find the place where you can enter the following information:

1.	Your E-mail address (or Return address),

2.	SMTP Server’s name or IP address

3.	POP3 Server’s name or IP address,

4.	POP3 Account name, and

then enter

1.	Your E-mail address (or Return address), For example, user@company.com,

2.	SMTP Server’s name or IP address, For example, smtpserver.isp.com,

3.	POP3 Server’s name or IP address, For example, pop3server.isp.com,

4.	POP3 Account name, For example, pop3user


FTP Application Setup on Client PC

FTP Application Setup When Using BreezeWay

Before trying to setup a FTP application on a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

Use the following step-by-step instructions to configure popular FTP applications to FTP through BreezeWay. You need to configure both BreezeWay on the Server PC and FTP applications on Client PCs.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable FTP proxy box, enter 21 in the Control port and 20 in the Data port.

3.	Click OK.

For the example in the following instructions assume that the FTP server that you want to connect to is ftp.server.addr, your account name on that server is myusername, and the address of the Server PC is 192.168.1.1. To use FTP proxy, you should specify the Server PC as your FTP server and use myusername#ftp.server.com as your account name. “#server.ftp.com” gives the real FTP server information to BreezeWay. The following table shows the setting changes when using BreezeWay:

Original	Using BreezeWay

----------------------------------------------------------------------------------------------

FTP server	server.ftp.addr	192.168.1.1

User name:	myusername	myusername#ftp.server.addr

Password	mypassword	mypassword

Windows NT/95 FTP applet on Client PCs:

1.	Click Start and choose Run,

2.	Type ftp 192.168.1.1,

3.	Click Open, then the system will pop up a MS-DOS Prompt window.

4.	At the prompt, input your user name as myusername#ftp.server.addr. You should use your real user name and server address rather than myusername and ftp.server.addr

5.	The server will prompt you for password. Input the real password of this account.

6.	If you pass the authentication, the FTP server will reply to you with a “230 User … logged in” message.

Note: 	If you changed the Control Port of FTP proxy of BreezeWay to another port, say 3000, you should type only ftp in step 2, and then type open 192.168.1.1 3000 at the ftp prompt.

Unix FTP on Client PCs:

FTP client applications on UNIX systems are very similar to Windows FTP applet. What you have to do is type ftp 192.168.1.1 and then follow the above instructions from step 4.

WS_FTP Pro & LE 4.1 and later on Client PCs:

1.	Click Connect.

2.	Click General in the Session Properties dialog box,

3.	Click New, then type BreezeWay or any other name you prefer for Profile Name.

4.	Enter the Server PC’s IP address, for example, 192.168.1.1 in Host Name/Address box,

5.	Enter myusername#ftp.server.addr in User ID box, where myusername is your login name on the FTP server: ftp.server.addr,

6.	Enter your password in the Password box.

7.	Click OK.

Note:	If you change your BreezeWay FTP control port to another port, for example 3000, you should also change the setting of WS-FTP by the following steps:

1.	Click Advanced in Session Properties property sheet.

2.	Enter 3000 or whatever you set for BreezeWay FTP proxy server as your Remote Port.

3.	Click OK


Telnet Application Setup on Client PC

Telnet Application Setup When Using BreezeWay

Before trying to setup a Telnet application on a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

Use the following step-by-step instructions to configure popular Telnet applications with BreezeWay. You need to configure both BreezeWay on the Server PC and the Telnet applications on Client PCs.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable Telnet proxy box and enter 23 in the Telnet proxy port.

3.	Click OK.

For the example in the following instructions assuming that the Telnet server that you want to connect to is bbs.server.addr, and the address of the Server PC is 192.168.1.1. To use Telnet proxy, you should specify the Server PC as your Telnet server and give the real destination after the prompt.

The following instructions show how to use popular Telnet applications with BreezeWay:

Windows NT/95 Telnet applet on Client PCs:

1.	Click Start and choose Run,

2.	Type telnet 192.168.1.1

3.	BreezeWay Telnet Proxy will respond you with

Welcome to RideWay Telnet

Connect to >

4.	At the prompt, enter the host name or IP address of the server you want to connect to, for example, bbs.server.addr, and then press Enter.

5.	The real server will prompt you for login information at this point.

Note: 	If you have changed the port of BreezeWay Telnet Proxy to another port, say 3500, you should type telnet 192.168.1.1 3500 in Step 2.

Unix Telnet on Client PCs:

1.	Type telnet 192.168.1.1 under a Unix shell

2.	BreezeWay Telnet Proxy will respond you

Welcome to RideWay Telnet

Connect to >

3.	At the prompt, enter the host name or IP address of the server you want to connect to, for example, bbs.server.addr, and then press Enter.

4.	The real server will prompt you for login information at this point.

Note: 	If you have changed the port of BreezeWay Telnet Proxy to another port, say 3500, you should type telnet 192.168.1.1 3500 in Step 1.

NetTerm 3.2 on Client PCs:

1.	Click Phone Directory…. under File menu,

2.	Click Add button to create a new entry in the phone directory,

3.	Enter BreezeWay or any other name you prefer for Host Name,

4.	Enter the IP address of the Server PC, for example, 192,168.1.1 in Host/IP box,

5.	Click Change to save the setting,

6.	Click Connect,

7.	BreezeWay Telnet Proxy server will respond you

Welcome to RideWay Telnet

Connect to >

8.	At the prompt, enter the host name or IP address of the server you want to connect to, for example, bbs.server.addr, and then press Enter.

9.	The real server will prompt you for login information at this point.

Note: 	If you have changed the port of BreezeWay Telnet Proxy to another port, say 3500, you should set 3500 in the Telnet port field in Step 4.


RealPlayer Application Setup on Client PC

RealPlayer Setup When Using BreezeWay

Before setting the RealPlayer on a Client PC make sure

•	the client is connected to the same LAN as the Server PC.

•	a TCP/IP package is installed,

•	the IP address of the Client PC is on the same subnet as that of the Server PC.

Use the following step-by-step instructions to configure the RealPlayer to receive RealAudio and RealVideo contents through BreezeWay. You need to configure both BreezeWay on the Server PC and the RealPlayers on Client PCs.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable HTTP and Security/Secure proxy box and enter 80 in the HTTP proxy port.

3.	Check the Enable RealPlayer proxy box and enter 1090 in the RealPlayer proxy port.

4.	Click OK.

RealPlayer 5.0 on Client PCs:

1.	Select Preferences under the View menu.

2.	Click Proxy tab on the Preferences dialog box.

3.	Check Use Proxy box.

4.	In RealPlayer Proxy box, enter the host name or IP address of the Server PC (for example 192.168.1.1) and in Port box, enter port number set in BreezeWay Dialog Box, for example 1090.

5.	In Http Proxy box, enter the host name or IP address of the Server PC (for example 192.168.1.1) and in Port box, enter port number set in BreezeWay Dialog Box, for example 80.

6.	Click OK button to finish the setting.


TCP Mapping Setup on Client PC

TCP Mapping Setup When Using BreezeWay

TCP mapping can be set up for different applications running on Client PCs. As long as an application uses TCP protocol to query the same server for information every time it may be set up to use TCP mapping proxy to access the Internet. For example, you can set up a TCP mapping for Client PCs to telnet to a remote computer in the Internet. Internet News is also a good candidate for TCP mapping.

This section provides step-by-step instructions for setting up Netscape Communicator v4.x, Microsoft Outlook Express 4.x, and Forte Free Agent 1.11 on Client PCs to use RideWay’s TCP mapping proxy for reading the Internet News. You need to configure both BreezeWay on the Server PC and the applications on Client PCs. Refer to  BreezeWay Dialog Box for more configuration instructions.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable TCP mapping box.

3.	Click Add.

4.	In Local Port, enter 119.

5.	In Remote Server, enter your ISP’s NNTP server. Ask your ISP if you don’t have the NNTP server’s information.

6.	In Remote Port, enter 119.

7.	Click OK.

8.	Click OK again.

Netscape Communicator 4.x on Client PCs:

1.	Click Communicator, then select Collabra Discussion Groups or Message Center,

2.	Click File, then select New Discussion Group Server,

3.	Enter Server PC’s IP address into Server box, For example, 192.168.1.1,

4.	Click OK,

Microsoft Outlook Express 4.x on Client PCs:

1.	From Internet Explorer click Go, then select News, and go to Step 4,

From Outlook Express click Tools, then choose Accounts, and continue to Step 2,

2.	Click News,

3.	Click Add and then choose News,

4.	Type in a Display name,

5.	Enter your email address into E-mail address box, For example, user@company.com.

6.	Enter Server PC’s IP address into News (NNTP) server box, For example, 192.168.1.1,

7.	Type a name for the Internet news account name,

8.	Click Connect using my local area network (LAN),

9.	Click Finish,

Forte Free Agent 1.11 on Client PCs:

1.	Click Options.

2.	Click General Preferences.

3.	Click System.

4.	In the News Server, enter Server PC’s IP address, for example, 192.168.1.1.

5.	Click OK.


UDP Mapping Setup on Client PC

UDP Mapping Setup When Using BreezeWay

UDP mapping can be set up for different applications running on Client PCs. As long as an application uses UDP protocol to query the same server every time it may use UDP mapping to access the Internet. This section provides step-by-step instructions for setting up Mirabilis’ ICQ Version 98a to use RideWay’s UDP mapping proxy. You need to configure both BreezeWay on the Server PC and the ICQ on Client PCs. Refer to  BreezeWay Dialog Box for more configuration instructions.

NOTE: UDP mapping and SOCKS 4 proxy together provides partial support for ICQ to operate in a private LAN, i.e. ICQ users in the private LAN are able to initiate communication to ICQ users in the Internet but ICQ users in the Internet can not initiate communication to ICQ users in the private LAN.

BreezeWay on Server PC:

1.	Select BreezeWay under the Server menu.

2.	Check the Enable UDP mapping box.

3.	Click Add.

4.	In Local Port, enter 4000.

5.	In Remote Server, enter the IP address or hostname of an ICQ server, e.g. 204.91.243.115 or icq.mirabilis.com.

6.	In Remote Port, enter 4000.

7.	Click OK.

8.	Click OK again.

Mirabilis’ ICQ Version 98a on Client PCs:

When running the ICQ Registration Wizard please follow these steps:

1.	Check New ICQ# if you are a new user or Existing ICQ# if you are a registered user and then click Next

2.	On the Connection Type, check LAN User, click I am behind a firewall or proxy, and click Next,

3.	On the Specify what SOCKS Proxy server you use, click I am using a SOCKS4 proxy server,

4.	Click Next,

5.	Enter the Server PC’s IP address in SOCKS4 Host box, for example, 192.168.1.1,

6.	Enter 1080 in SOCKS4 Port box,

7.	Click Use a mapped port on a Proxy,

8.	Enter the Server PC’s IP address in Proxy Server Host box, for example, 192.168.1.1,

9.	Enter port value in Proxy Server Port box, for example 4000,

10.	Click Next

11.	Enter other information which are not related to Proxy Server setup.

If you need to change proxy settings after registration please follow these steps:

1.	Click Menu, and then select Preferences,

2.	Click Connection,

3.	Check I am using a permanent Internet connection (LAN),

4.	Check I am behind a firewall or proxy,

5.	Click Firewall Settings,

6.	Check I am using a SOCKS4 proxy server,

7.	Click Next,

8.	Enter the Server PC’s IP address in SOCKS4 Host box, for example, 192.168.1.1,

9.	Enter 1080 in SOCKS4 Port box,

10.	Check Use a mapped port on Proxy,

11.	Enter the Server PC’s IP address in Proxy Server Host box, for example, 192.168.1.1,

12.	Enter port value in Proxy Server Port box, for example 4000,

13.	Click Next,

14.	Click Done,

15.	Click OK.


Access the Internet from Home via the Office LAN

Follow these steps to setup your configuration:

1.	Connect a modem to the Server PC,

2.	Install the Microsoft Dial-Up Adapter on the Server PC,

3.	Assign 192.168.1.1/255.255.255.0 as the IP address/mask to TCP/IP  Dial-Up Adapter,

4.	Install Dial-Up Server on the Server PC. The Dial-Up Server is part of the Microsoft Plus! for Windows 95 and a built-in server on Windows NT.

5.	Install RideWay on the Server PC,

6.	Follow the instructions in RideWay Proxy Server Setup section to setup DNS and SOCKS Proxy Server,

7.	Connect a modem to the Client PC,

8.	Install the Microsoft Dial-Up adapter on the Server PC ,

9.	Create a Dial-Up Networking icon for your connection to the Server PC and assign 192.168.1.2/255.255.255.0 as the IP address/mask for this connection.

10.	Follow the instructions in the Applications Setup on a Client PC section to point to the client’s DNS server and SOCKS server to the Server PC.


RideWay Window

The RideWay window offers the following menus and server status and statistics:

Status and Statistics	Shows Dialer and Server status and statistics.
Dialer Menu	Commands to control Dialer.
Server Menu	Commands to control Server.
Report Menu	Commands to generate report for Server and Dialer on the fly.
Tools Menu	Commands to launch diagnostic tools.
Help Menu	Commands to get online help.


Server Statistics

RideWay Window - Server Statistics

When RideWay is started, the RideWay window shows the connection status of the Dialer and running status of the Server. When the Server is started, the RideWay window shows the following Server statistics:

Number of Active Users:	Shows the number of users who are currently using the RideWay Server. This number will not exceed the number of user licenses you have purchased.
Number of Active Connections:	Shows the number of connections currently established between RideWay Server and all clients. A client can establish as many connections to the Server as it wishes.
Total Number of Bytes Received:	Shows the total number of bytes that the RideWay Server received from all clients and all application servers since the server last started. The RideWay Server receives requests from clients and replies from application servers. This number is the sum of bytes in all replies and requests that RideWay Server received. This number will always greater than or equal to the Total Number of Bytes Sent. If clients do not reset any connections, such as with the ‘Stop’ button for Netscape Navigator, this number will be equal to the Total Number of Bytes Sent.
Total Number of Bytes Sent:	Shows the total number of bytes that RideWay Server sent to all clients and all application servers since the server last started. The RideWay Server sends replies to clients and requests to application servers. This number is the sum of bytes in all replies and requests that RideWay Server sent. This number will always less than or equal to the Total Number of Bytes Received. If clients do not reset any connection, such as with the ‘Stop’ button for Netscape Navigator, this number will be equal to the Total Number of Bytes Received.
Total Number of Connections:	Shows the total number of connections established between the RideWay Server and all clients since the server last started.


Dialer menu

Dialer Menu Commands

The Dialer Menu offers the following commands:

Connect	Dial up to an ISP.
Disconnect	Hang-up and terminate the Internet connection.
Dialer Control	Setup the Dial-Up Networking dialer.
Dial-Up Networking	Open Microsoft’s Dial-Up Networking window.
Clear Dialer  Log	Clear the Dialer Log file.
Exit	Exits RideWay.


Dialer Connect command

Connect Command (Dialer Menu)

This command dials/connects to the ISP specified in the Dialer Control’s Default Connection box.

_______________________________________________________________________________

Shortcuts

Keys:	Ctrl+C

See Also:

Dialer

Disconnect command


Dialer Disconnect command

Disconnect Command (Dialer Menu)

This command terminates the connection to the ISP specified in the Dialer Control’s Default Connection box.

_______________________________________________________________________________

Shortcuts

Keys:	Ctrl+D

See Also:

Dialer

Connect command


Dialer Control command

Dialer Control Command (Dialer Menu)

The Dialer Control command opens Dialer Control Dialog Box enabling you to set or modify the parameters of the RideWay Dial-Up Networking Dialer.

_______________________________________________________________________________

See Also:

Dialer

Dialer Setup


Dialer Control Dialog Box

The following options allow you to specify the Default Connection, Redialing parameters, and Reconnection parameters:

Automatically Connect

Check this box if you want to automatically dial and establish an Internet connection when RideWay starts. You may manually dial and establish the connection by using the Connect command under Dialer Menu.

Automatically Disconnect

Check this box if you want RideWay to automatically disconnect the Internet connection when it exits. You may manually disconnect by using the Disconnect command under Dialer Menu.

Default Connection

Set the default dial-up connection. RideWay Dialer will connect to this Default Connection when the Connect command is issued and disconnect from this Default Connection when the Disconnect command is issued.

Setup Button

Opens the Dial-Up Networking window of Windows 95/NT allowing you to set or modify the properties of your Internet connection. Clicking on this button to change the property of the Default Connection.

Redial Control

For Windows 95

Check here if you want RideWay to automatically redial when unable to establish an Internet connection. You may specify the number of redial attempts and the interval time between each attempt.

For Windows NT:

1.	Click Redial Control button to open the Dial-up Networking dialog,

2.	Click More button,

3.	Choose User preferences menu item,

4.	Click Dialing tab, and

5.	Set redial parameters.

6.	Check Redial on link failure if you want Dial-up Networking to automatically redial if the connection is terminated unexpectedly.

On-demand Dialing

On-demand dialing feature enable RideWay Dialer to automatically dial to the Default Connection when the RideWay Proxy Server receives a request to access the Internet from a client application and terminate the connection to the Default Connection after a specified period of inactivity. This feature is cost-effective if Internet access charges are based on the connection time.

Enable On-demand dialing

including DNS requests

Disconnect after ____ minutes of inactivity

Check Enable On-demand dialing if you want RideWay Dialer to dial/connect to the ISP specified by the Default Connection. As default, all requests, including DNS, SOCKS, Email, FTP, HTTP, Telnet, RealPlayer, and TCP and UDP mapping requests will trigger the Dialer to connect to the Default Connection. In some environment, client PCs issues DNS requests to resolve computer names even when they are not accessing the Internet. In this case, you should uncheck including DNS requests box so that the Dialer won’t be triggered by these unnecessary DNS requests. When the  including DNS requests is unchecked a client application can trigger the Dialer by sending SOCKS, Email, FTP, Telnet, HTTP, RealPlayer, and TCP and UDP mapping requests with an IP address instead of a domain name. For example, you should type http://207.196.61.6 instead of http://www.itserv.com in your browser on a client PC to trigger the Dialer to connect to the Default Connection. After the connection is established domain names can be used. Specify the value for Disconnect after ___ minutes of inactivity. RideWay will terminate the connection to the Default Connection after the specified period of inactivity from client PCs.

______________________________________________________________________________

See Also:

Dialer

Dialer Setup


Dial-Up Networking command

Dial-Up Networking Command (Dialer Menu)

This command opens the Dial-Up Networking window of Windows 95/NT

_______________________________________________________________________________

See Also:

Dialer

Dialer Setup


Clear Dialer Log command

Clear Dialer Log Command (Dialer Menu)

This command empties RideWay Dialer’s log file. This Log file stores information for RideWay’s Dial-Up Networking Dialer.

_______________________________________________________________________________

See Also:

Clear Server Log command


Dialer Exit command

Exit Command (Dialer Menu)

This command terminates the current RideWay session. You may also use the Close command on the application Control Menu.

_______________________________________________________________________________

Shortcuts

Mouse:	Double-click the application's Control menu button.

Keys:	ALT+F4


Server menu

Server Menu Commands

The Server Menu offers the following commands:

Start	Start the RideWay Proxy Server.
Stop	Stop the RideWay Proxy Server.
Server Control	Setup the RideWay Proxy Server.
Security Administration	Setup the network security administration options.
Log Options	Setup Log levels and Log file length.
Clear Server Log	Clear the Server Log file.
BreezeWay	Setup BreezeWay.


Start Server command

Start Command (Server Menu)

This command starts the Proxy Server of RideWay. If On-demand dialing is enabled, Proxy Server will run automatically when RideWay starts. Otherwise before starting the server, you should first make an Internet connection either through a LAN or with the Connect command under Dialer Menu.

_______________________________________________________________________________

Shortcuts

Keys:	Ctrl+S

See Also:

Server

Stop command


Stop Server command

Stop Command (Server Menu)

This command terminates the Proxy Server of RideWay. When On-demand dialing is enabled the Proxy Server can not be stopped. The Proxy Server will automatically stop when RideWay exits.

_______________________________________________________________________________

Shortcuts

Keys:	Ctrl+P

See Also:

Server

Start command


Server Control command

Server Control Command (Server Menu)

This command opens the Server Control Dialog Box allowing you to specify the properties of Proxy Server.

_______________________________________________________________________________

See Also:

Server

Server Setup


Server Control Dialog Box

Automatically start SOCKS proxy server when RideWay starts

Check here if you want to automatically start the SOCKS proxy server when RideWay starts. You may manually start the SOCKS proxy server with the Start command.

SOCKS proxy server port

Define the port used for the RideWay proxy server. This should be the same port as specified in your client applications’(for instance, Netscape Navigator) SOCKS port. The default value of 1080 is recommended.

DNS proxy

Check here to enable DNS proxy server. If you are not running your own DNS server you should check this box. DNS proxy server is required when using SOCKS proxy server.

DNS port

Define the port used by the DNS proxy server. Almost all applications use port 53 for DNS requests so always use the value of 53 for this port.

DNS Servers

Show the DNS servers that you entered manually. Clicking the Add or Remove button will allow you to specify your DNS Servers. Note: You may skip this setup if you do not want to manually specify the DNS servers. RideWay will try to find your DNS servers from the Control Panel automatically when starting the server.

______________________________________________________________________________

See Also:

Server

Server Setup


Security Administration command

Security Administration Command (Server Menu)

This command opens the Security Administration Dialog Box allowing you to control access to RideWay proxy server.  There are two tabs under the Security Administration dialog box. The Internal to External tab defines Internet access control for internal computers and the External to Internal tab defines the access permission from external computers to internal computers.

_______________________________________________________________________________

See Also:

Server


Server Security Administration dialog

Security Administration Dialog Box

Internal to External

Internet access control for internal computers

Check here to impose access restrictions to internal computers. If this box is checked then only those computers explicitly specified have access permission and all other computers have no access permission. If this box is not checked there are no access restrictions for internal computers, i.e. every internal computers has full access to the Internet. By default this box is not checked.

Internal computers with full access

Networks and/or computers defined in this box have full access to the Internet. These computers can access any computer in the Internet without restrictions.

Internal computers with no access

Networks and/or computers defined in this box have no access to the Internet. These computers can not access any computer in the Internet.

Internal computers with conditional access

Networks and/or computers defined in this box are permitted or denied to access some computers in the Internet.

Permit internal computers access to external computers

Click this button if you want to permit the internal computers to access the external computers.

Deny internal computers access to external computers

Click this button if you want to deny the internal computers to access the external computers.

Internal computers

The above permit/deny access applies to these Internal computers.

External computers

The above permit/deny access applies to these External computers.

Add button

Clicking this button will display a dialog box enabling you to add a computer or network into the associated box.

Remove Button.

Clicking this button will delete the selected computer or network from the associated box.

External to Internal

Permit external computers access to internal computers

Check here to permit external computers to access internal computers. If this box is checked then the specified external computers can only access those specified internal computers but not other internal computers. If this box is not checked  no external computers can access any internal computer. By default this box is not checked.

External computers with access to internal computers

These external computers and/or networks can access the internal computers specified below.

Internal computers accessible by external computers

These internal computers are accessible by the external computers specified above.

Add button

Clicking this button will display a dialog box enabling you to add a computer or network into the associated box.

Remove Button.

Clicking this button will delete the selected systems from the associated box.

_______________________________________________________________________________

See Also:

Server


Server Log Options command

Log Options Command (Server Menu)

This command displays the Log Options Dialog Box enabling users to specify Log Options for the RideWay proxy server. There are three log levels: 0, 1, and 2. The default log level is 1 which will log Error and Connection Messages into log files. The Report commands use information in log files to generate reports. Log level 2 is used for debugging purpose. If there is a need to change to Log Level 2 for debugging, please change it back to either Log Level 0 or 1 immediately after the testing.

Note: choosing Log Level 2 may severely hurt the performance of RideWay proxy server.

_______________________________________________________________________________

See Also:

Clear Server Log command


Server Log Options command

Log Options Dialog Box

Log Level Selection

Select the Log Level of RideWay Proxy Server. You may generate the Report for Server from the log file by using the Report for Server command under the Report Menu.

Limit disk space for log

Limit the size (in Kbytes) of the log file. The number must be between 1 and 9999.

_______________________________________________________________________________

See Also:

Clear Server Log command


Clear Server Log command

Clear Server Log Command (Server Menu)

This command empties the log file of Proxy Server.

_______________________________________________________________________________

See Also:

Clear Dialer Log command


BreezeWay command

BreezeWay Command (Server Menu)

This command opens the BreezeWay Dialog Box allowing you to

•	enable/disable HTTP and Security/Secure proxy and specify the proxy port.

•	enable/disable Telnet proxy and specify the proxy port.

•	enable/disable RealPlayer proxy and specify RealPlayer proxy port.

•	enable/disable FTP proxy and specify the Control port and Data port,

•	enable/disable Email (SMTP/POP3) proxy and specify a SMTP server,

•	enable/disable TCP mapping, and

•	enable/disable UDP mapping.

_______________________________________________________________________________

See Also:

BreezeWay

BreezeWay Setup


Server Control Dialog Box

BreezeWay Dialog Box

Enable BreezeWay

Check this box if you want to enable BreezeWay option.

Enable HTTP and Security/Secure proxy

Check this box if you want to enable HTTP and Security/Secure proxy. If you are running your own HTTP server on the Server PC you should leave this box unchecked. Otherwise the RideWay Server will not be able to start. Security/Secure refers to the SSL (Secure Socket Layer) protocol.  Refer to Browser Setup When Using BreezeWay for detailed instructions for setting up browser to use RideWay’s HTTP and Security/Secure proxy.

HTTP proxy port

If there is port conflict when you enable the HTTP and Security/Secure proxy you may change the HTTP and Security/Secure proxy port. Enter new port number into this box. The default value for this port is 80.

Enable Telnet proxy

Check this box if you want to enable Telnet proxy. Refer to Telnet Application Setup When Using BreezeWay  for detailed instructions for setting up Telnet applications to use RideWay’s Telnet proxy.

Telnet proxy port

If there is port conflict when you enable the Telnet proxy you may change the Telnet proxy port. Enter new port number into this box. The default value for this port is 23. It is not recommended to change the default value.

Enable RealPlayer proxy

Check this box if you want to enable Realplayer proxy. Refer to Realplayer Setup When Using BreezeWay for detailed instructions for setting up RealPlayer to use RideWay’s Realplayer proxy.

RealPlayer proxy port

If there is port conflict when you enable the Realplayer proxy you may change the Realplayer proxy port. Enter new port number into this box. The default value for this port is 1090.

Enable FTP proxy

Check this box if you want to enable FTP proxy. Do not enable FTP proxy when you are running your own FTP server on the Server PC. Refer to FTP Application Setup When Using BreezeWay for detailed instructions for setting up FTP applications to use RideWay’s FTP proxy.

Control port

If there is port conflict when you enable the FTP proxy you may change the FTP proxy Control port. Enter new port number into this box. The default value for Control port is 21. It is not recommended to change the default value.

Data port

If there is port conflict when you enable the FTP proxy you may change the FTP proxy Data port. Enter new port number into this box. The default value for Data port is 20. It is not recommended to change the default value.

Enable Email Proxy (SMTP/POP3)

Check this box if you want to enable Email proxy. Do not enable Email proxy when you are running your own email server on the Server PC. Refer to Email Application Setup When Using BreezeWay for detailed instructions for setting up email applications to use RideWay’s Email proxy.

SMTP server

Enter SMTP server’s host name or IP address in this box. If you do not have information of your SMTP server, please ask your ISP.

Enable TCP mapping

Check this box if you want to enable TCP mapping. Refer to TCP Mapping Setup When Using BreezeWay  for detailed instructions of setting up applications on Client PCs to use RideWay’s TCP mapping proxy.

Local port    Remote server : port

Local port refers to the TCP port that RideWay has opened to receive requests from Client PCs. When RideWay receives the first request from a Client PC it establishes a connection to the remote server:port. Subsequent requests are relayed to the remote server through the connection. For example, the Internet News uses NNTP (which is a TCP protocol) and Client PCs can get News from the same NNTP server. You may set up TCP mapping for Internet News proxy by setting Local port to 119 and Remote server to your ISP’s NNTP server and Remote port to 119.

Enable UDP mapping

Check this box if you want to enable UDP mapping. Refer to UDP Mapping Setup When Using BreezeWay  for detailed instructions of setting up applications on Client PCs to use RideWay’s UDP mapping.

Local port    Remote server : port

Local port refers to the port that RideWay has opened to receive UDP requests from Client PCs. When RideWay receives a request from a Client PC it relays the request to the remote server:port. For example, the Mirabilis’ ICQ uses UDP protocol (port 4000) to communicate with ICQ servers. You may set up a UDP mapping for Mirabilis’ ICQ by setting Local port to 4000, Remote server to icq.mirabilis.com, and Remote port to 4000.

_______________________________________________________________________________

See Also:

BreezeWay

BreezeWay Setup


Report menu

Report Menu Commands

The Report Menu offers the following commands:

Report for Dialer	Generate the Dialer Report.
Report for Server	Generate the Server Report.


Report for Dialer command

Report for Dialer Command (Report Menu)

This command displays the Report for Dialer Dialog Box enabling users to generate a report for the RideWay Dialer.

_______________________________________________________________________________

See Also:

Dialer


Report for Dialer dialog

Report for Dialer Dialog Box

Starting from

Check here to set the starting time of the report.  If unchecked, RideWay will generate the report by scanning the log from the beginning.

Ending at

Check here to set the ending time of report.  If unchecked, RideWay will generate the report by scanning the log file to the end.

Detail level of the Report

Select the style of the report you want to generate. Check ‘Summary’ to view statistical

information and check ‘Details’ to see both chronological and statistical information.

_______________________________________________________________________________

See Also:

Dialer


Report for Server command

Report for Server Command (Report Menu)

This command displays the Report for Server Dialog Box enabling users to generate a report for the RideWay Proxy Server.

_______________________________________________________________________________

See Also:

Server


Report for Server dialog

Report for Server Dialog Box

Starting from

Check here to specify the starting time of the report. If unchecked, RideWay will generate the report by scanning the log from the beginning.

Ending at

Check here to specify the ending time of the report. If unchecked, RideWay will generate the report by scanning the log file to the end.

Systems to be included in report

Specifies which machine you want to see on the report. If [All Systems] selected, the report will show all connections of any machine. Otherwise, the connection information of systems specified by the [These System] edit box will be showed. You could use [Add] [Remove] [Change] buttons to choose systems.

What to report

Check the first box to view restrictions for outbound connections.

Check the second box to view restrictions for inbound connections.

You may give permission to any system to access Internet from your internal systems or any internal system to access Internet by Security Administration Command under Server Menu.

Detail level of the report

Select the style of the report you want to generate. Check ‘Summary’ to view statistical information and check ‘Details’ to view both chronological and statistical information.

_______________________________________________________________________________

See Also:

Server


Tools menu

Tools Menu Commands

The Tools Menu offers the following commands:

Ping	Ping a remote computer.
DNS Lookup	Lookup a computer name or an IP address.
Trace Route	Trace route to a remote computer.
IP Configuration	Show the IP configuration of the local computer.


Ping command

Ping Command (Tools Menu)

When you "ping" some computer, you are sending several probe messages to the specified remote computer. The remote computer simply echoes each probe message back to your computer. If a message is successfully echoed back and matches the transmitted one with no error, the computer prints out a successful probe.

You can use the ping utility to test both the computer name and the IP address of the computer. If the IP address is verified but the computer name is not, you may have a name resolution problem. In this case, be sure that the computer name you are querying is in either the local HOSTS file or in the DNS database.

This command displays the Ping Dialog Box enabling the user to verify connection to a remote computer. The Ping Dialog Box also shows sample output for Ping command.


Ping dialog

Ping Dialog Box

Enter a computer or IP address:

A computer name or an IP address is required to run the Ping command. Enter a computer name or an IP address in this field and then click the ‘Start’ button to run the command.

Start Button

Click this button to start pinging the remote computer.

Help Button

Click this button to get online help information.

Output for ping command is shown in the box below the ‘Start’ button. The following shows sample output for ping:

Pinging www.itserv.com [207.196.61.6] with 32 bytes of data:

Reply from 207.196.61.6: bytes=32 time=101ms TTL=64

Reply from 207.196.61.6: bytes=32 time=100ms TTL=64

Reply from 207.196.61.6: bytes=32 time=120ms TTL=64

Request timed out.

Reply from 207.196.61.6: bytes=32 time=130ms TTL=64

Ping complete.

•	The first field shows either ‘Reply’ from remote computer or ‘Request timed out.’ If the local computer does not receive reply within 1 second it will show ‘Request timed out.’

•	The ‘bytes’ field shows the amount of data sent to the remote computer.

•	The ‘time’ field shows the round trip time in milliseconds for the packet traveling from the local computer to the remote computer.

•	The ‘TTL’ field shows the maximum number of intermediate gateways the packet allowed to travel before reaching the remote computer.

_______________________________________________________________________________

See Also:

Ping command


DNS Lookup command

DNS Lookup Command (Tools Menu)

This command enables the user to identify the computer names associated with a specified IP address or to resolve all the IP addresses assigned for a specified computer name.

The DNS Lookup Dialog Box gives more detailed explanation on how to use the command and shows sample output for DNS Lookup.


DNS Lookup dialog

DNS Lookup Dialog Box

Enter a computer or IP address:

A computer name or an IP address is required to run the DNS Lookup command. Enter a computer name or an IP address in this field and then click the ‘Start’ button to run the command.

Start Button

Click this button to start looking up the remote computer name or IP address.

Help Button

Click this button to get online help information.

Output for ping command is shown in the box below the ‘Start’ button. The following shows sample output for DNS Lookup:

DNS lookup for	"www.itserv.com"

IP address(s):	207.196.61.6

NS lookup for	"207.196.61.6"

DNS name(s):	byron.itserv.com

www.itserv.com

•	The first line shows the computer name or IP address to lookup.

•	The rest of lines show the corresponding IP address or computer names.

_______________________________________________________________________________

See Also:

DNS Lookup command


Trace Route command

Trace Route Command (Tools Menu)

Trace Route is the most useful tool to troubleshoot network problems. It shows the path (a list of gateway or router nodes) that the trace packets will take from your computer to the specified remote computer. Each node is displayed along with the round trip time for each of three trace packets to reach the indicated node and return. These intervals may vary widely as a function of network load or network condition. A consistent high numbers of traversing time or time-out associated to certain node could indicate a congested network segment along the path.

The detailed explanation and a sample output for Trace Route are shown at Trace Route Dialog Box.


Trace Route dialog

Trace Route Dialog Box

Enter a computer or IP address:

A computer name or an IP address is required to run the Trace Route command. Enter a computer name or an IP address in this field and then click the ‘Start’ button to run the command.

Start Button

Click this button to start tracing route to the remote computer.

Help Button

Click this button to get online help information.

Output for Trace Route command is shown in the box below the ‘Start’ button. The following shows sample output for Trace Route:

Tracing route to www.microsoft.com [207.68.156.49]

over a maximum of 30 hops:

  1      2 ms       1 ms       1 ms  	207.196.61.1

  2   178 ms     35 ms     35 ms  	Rockville-P50-34.clark.net [207.22.117.34]

  3   126 ms     39 ms     37 ms  	e0.rockcreek.clark.net [207.22.117.1]

  4     48 ms     39 ms     40 ms  	s2-5.gaithersburg.mae-east.clark.net [207.97.14.57]

  5     51 ms     69 ms     73 ms  	s1-3mae-east.noc.clark.net [207.97.14.62]

  6    250 ms   349 ms   253 ms 	sl-dc-17-S1/5-T1.sprintlink.net [144.228.4.1]

  7    186 ms   128 ms   164 ms 	sl-dc-1-F0/0.sprintlink.net [144.228.20.1]

  8   326 ms     *          259 ms  	sl-kc-1-H3/0-T3.sprintlink.net [144.228.10.74]

  9   226 ms   216 ms   198 ms  	sl-kc-2-P4/0/0-155M.sprintlink.net [144.232.2.66]

 10  327 ms   410 ms   402 ms  	sl-chi-15-H2/0-T3.sprintlink.net [144.228.10.69]

 11     *          172 ms       *        	sl-chi-20-P4/0/0-150M.sprintlink.net [144.232.0.137]

 12  269 ms       *             *        	sl-chi-20-H1/0-T3.sprintlink.net [144.228.10.61]

 13     *          233 ms   186 ms  	sl-sea-5-F0/0.sprintlink.net [144.228.90.5]

 14  232 ms   215 ms       *        	sl-mic-2-H-T3.sprintlink.net [144.228.95.10]

 15  490 ms       *         252 ms  	207.68.145.54

 16     *          546 ms   285 ms  	www.microsoft.com [207.68.156.49]

Trace complete.

•	The first field shows the hop number of the intermediate gateway, which is shown in the last field.

•	The following 3 fields show the round trip time in milliseconds from local computer to the gateway.

•	A * (star) indicates that a packet did not come back to local computer. This is called a "packet drop". It got lost or thrown away. There are several factors responsible for lost packets. Some gateways don't return the appropriate message requested by Trace Route. Some firewalls use packet filters which block packets used by Trace Route. Finally, packets may be lost as a result of network congestion. If you get one or two stars on a line, it means that performance is bad and data is being lost. If you get nothing but stars on a line, your target computer is unreachable.

•	Sometimes you'll see the packets bounce back and forth between two routers or even do a big loop through the Internet and come back to where it started. In this case, the Internet routing tables are incomplete or in conflict for your target computer. If the loop happens within a customer's internal network or between the routers on either end of a customer link, the customer has not setup their routing correctly.

Trace Route described line-by-line

Trace Route shows the path packets take from the computer you are using to the destination. Each hop is a port on a router somewhere in the Internet. Let's take this one line at a time:

Starting Point

Tracing route to www.microsoft.com [207.68.156.49] over a maximum of 30 hops:

"30 hops" means that the Trace Route will only hop 30 times and then it will stop. You should be able get to where you're trying to go within 30 hops!

First Hop

  1      2 ms       1 ms       1 ms  	207.196.61.1

There are three things to notice here:

•	There are three different sets of numbers; this is because Trace Route sends out 3 packets. It's possible that these packets can take different routes.

•	The numbers give the time that each packet took to get to that IP address and return to the starting point. (Sort of like little messengers coming back yelling "it's there! It's there!")

•	It gives a router name and an IP address. The IP address indicates a particular port on the router (serial port or Ethernet port). The IP number will always be the number of the port that the packets enter the router by.

Second hop

  2   178 ms     35 ms     35 ms  	Rockville-P50-34.clark.net [207.22.117.34]

The packets have left 207.196.61.1 to Rockville-P50-34.clark.net [207.22.117.34].

The final (16th) hop

 16     *          546 ms   285 ms  	www.microsoft.com [207.68.156.49]

This is the 16th and final hop. The packets have traveled across another link and entered another router (the customer's router) with the IP address 207.68.145.54. Notice: There is no name, only IP number; this just means that there is no DNS name assigned to this IP address.

_______________________________________________________________________________

See Also:

Trace Route command


IP Configuration command

IP Configuration Command (Tools Menu)

This command displays the IP Configuration Dialog Box enabling the user to verify the IP configuration of the local computer. The IP Configuration utility is a troubleshooting utility that displays all current TCP/IP network configuration values for any computer running Microsoft TCP/IP. Network configuration values include the current IP address allocated to the computer and other useful data about the TCP/IP allocation. This utility is particularly useful for networks using DHCP, allowing users to determine which TCP/IP configuration values have been configured by DHCP. The IP Configuration utility does not, however, dynamically update information. If you make any changes, such as disconnecting from the network, you must exit the IP Configuration utility and restart it again. To run IP Configuration utility, click the Refresh  button.

See Also:

IP Configuration Dialog Box


IP Configuration dialog

IP Configuration Dialog Box

Refresh Button

Click this button to show the IP Configuration of the local computer.

Help Button

Click this button to get online help information.

_______________________________________________________________________________

See Also:

IP Configuration command


Help menu

Help Menu Commands

The Help Menu offers the following commands, which will provide you assistance with this application:

Help Topics	Displays an index of topics from which you can get help.
Register RideWay	Register this software.
ITServ Home Page	Go to the ITServ home page
About RideWay	Displays the version number of this application.


Register RideWay command

Register RideWay Command (Help Menu)

This command displays the Registration Dialog Box enabling users to register RideWay. Refer to How to Register RideWay for the registration procedure.

_______________________________________________________________________________

See Also:

ITServ Home Page command


How to Register RideWay

Please follow the steps below to register RideWay:

Step 1: Click the ITServ logo or the URL on the Registration Dialog Box to access our registration webpage.

Step 2: Follow the instructions on the webpage to purchase this software online. Your order will be processed and we will send you a License ID via email, normally, within one business day.

Step 3: After receiving the License ID from us, please run RideWay and go to the Registration Dialog Box under the Help Menu. Fill in the User Name, License Type, and License ID fields and then click the Register button to register your copy of RideWay

Please save registration information in the event that you need to reinstall or upgrade RideWay in the future.

If you need any assistance, please contact us in the following ways:

ITServ Inc.

One Bank Street, Suite 220

Gaithersburg, MD 20878

USA

Customer Service

E-mail: support@itserv.com

Web: http://www.itserv.com

_______________________________________________________________________________

See Also:

Registration Dialog Box


Registration Dialog Box

Serial Number

This is the serial number associated with your copy of RideWay. You will need this number to register RideWay.

User Name

The user’s name registered for this software. You must use the same name as you specified when you purchased the software online. The User Name is case-sensitive.

License Type

Choose the license type you have purchased. License type indicates how many users could access Internet through RideWay simultaneously.

License ID

Enter the License ID into this box. The License ID is case-sensitive.

Register Button

Click this button to register this software on your machine.

Cancel Button

Click this button to cancel the registration and exit this dialog box.

Help Button

Click this button to get help information.

_______________________________________________________________________________

See Also:

How to Register RideWay


ITServ home page command

ITServ Home Page Command(Help Menu)

This command will start your default browser and connect to ITServ home page automatically. You could register your software, get technical support, or get more information about our products at ITServ home page.

_______________________________________________________________________________

See Also:

Register RideWay command


DNS

Domain Name Service is an Internet service to resolve the host names into IP addresses, and vice versa.


DNS Server

DNS Server is a server of Domain Name Service to resolve the host names into IP addresses, and vice versa.


ISP

Internet Service Provider or Internet Access Provider. The company that provides you the Internet connection.


LAN

LAN is an acronym for Local Area Network. A local area network refers to a group of connected computers.


PPP

Point-to-Point Protocol. A protocol for (most commonly) TCP/IP routers and PCs to communicate over dial-up and leased-line  connections.


Proxy Server

A Proxy Server acts as a gateway between the internal users of a LAN and the Internet. All Internet traffic goes through the proxy server, effectively shielding (firewall) the rest of the LAN from the Internet.


SOCKS

SOCKS is a networking proxy protocol that enables hosts on one side of SOCKS server to gain full access to hosts in the other side of the SOCKS server without requiring direct IP address reachable. SOCKS redirects connection requests from hosts on opposite sides of a SOCKS server. The SOCKS server authenticates and authorizes the requests, establishes a proxy connection, and relays data. SOCKS is commonly used as a network firewall that enables hosts behind a SOCKS server to gain full access to the Internet, while preventing unauthorized access from the Internet to the internal hosts.


TCP/IP

TCP/IP stands for Transmission Control Protocol/Internet Protocol. This is a computer 'language' available for almost every computer system and network type and is characterized by its 'open standards' allowing just about any 2 systems to talk to one another. Most Internet Applications (for example, Netscape Navigator, Internet Explorer) are Winsock compliant and need TCP/IP.


Winsock

Windows Sockets. The standard API (often called the socket interface) between Microsoft Windows (3.1, 95, NT) application software and TCP/IP protocol software( often called a protocol stack)


SMTP

SMTP : Simple Mail Transfer Protocol, an Internet standard protocol which is used for sending Internet emails.


POP3

POP3 : Post Office Protocol Version 3, an Internet standard protocol which is used for retrieving Internet emails from email server.


FAQ General Information

General Information

Q.	What is RideWay?

A.	RideWay is a SOCKS 4 compliant Proxy Server for Windows 95/NT which allows multiple users from several Client PCs (Win 95/NT, 3.1, Macintosh, etc.) to simultaneously access the Internet using only one modem, phone line, and Internet access account.

Q.	Why use RideWay?

A.	RideWay will save you a lot of money. By eliminating the need to pay for multiple phone lines, Internet accounts, and modems, the cost-savings resulting from the utilization of RideWay are tremendous!

Q.	What are the features of RideWay?

A.

•	Provides simultaneous access to the Internet from any networked computer using only one modem and phone line

•	Acts as a secure firewall protecting your internal network from outside intruders

•	Permits/Denies access to specified sites

•	Logs server information and generates customized reports for the network usage

•	Provides an easy-to-use interface for setting up the network and customizing it for your needs

•	Reduces on-line connection fees with the On-Demand dialing feature which automatically dials to the Internet when the first request is received and disconnects after a specified period of inactivity

•	Captures DNS settings in accordance with the DNS configuration of the PC (makes setting up RideWay that much easier!)

•	Provides diagnostic tools for trouble-shooting network connectivity, examining traffic flow conditions, and looking up computer name and Internet address information

Q.	What kind of setup is needed to utilize RideWay?

A.	At the minimum, you will need:

•	A Windows 95/NT PC with access to the Internet

•	A Network adapter card and TCT/IP installed on each computer which desires to simultaneously access the Internet.

Q.	Does RideWay support all types of modems?

A.	RideWay will work with analog modems (14.4 kps, 28.8, 33.6, 56 kps) and ISDN (64-128kps) modems as well! Also cable modems, available in some regions (offering up to 300 times the bandwidth available in a regular telephone line) will work with RideWay!

Q.	Is RideWay easy to install and setup?

A.	Absolutely. Thousands of RideWay users, with virtually no experience with LAN and TCT/IP networking, have successfully downloaded and installed our software. ITServ is also willing to help with general PC/networking issues (setup of TCT/IP, dialer, dial-up-networking) which are not related to RideWay itself. With ITServ's detailed step-by-step instructions and great technical support team, setting up RideWay is a breeze!

Q.	What applications does RideWay support?

A.	RideWay supports any application that supports SOCKS Version 4. Many popular applications support SOCKS Version 4, such as Netscape Navigator, Internet Explorer, and NetTerm.


FAQ Setup

Setup Questions

Note: Also see our extensive online help section with detailed step-by-step instructions at : ‘http://www.itserv.com/rideway’.

Q.	Do I have to uninstall RideWay before re-installing it?

A.	Yes, you should uninstall it from ‘Control Panel’’Add/Remove Program’. If you do not uninstall it first, RideWay may not be able to run.

Q.	Can I use RideWay if I have no Dial-Up Scripting Tool or I don’t know how to write a script.

A.	Yes. If you could use Dial-up networking to dial up to the ISP and establish the PPP connection by the default setting of username and password, you don’t need the scripting tool. Just choose the ISP as your default connection in the Dialer Control dialog box. If you could not connect to your ISP by this way, you could use your own dial-up tool to connect to the ISP and then start the RideWay server by choosing “start” under the Server menu. However, you could not use the features of RideWay Dialer such as on-demand dialing on this case.

Q.	I don't understand the references to Server PC and Client PC?

A.	You can think of the Server PC as:

•	the Windows 95/NT PC with RideWay installed with an Internet Connection.

You can think of the Client PC as:

•	the PC (Win 95, NT, 3.1, 3.11, Unix, etc..) which will use the Server PC to connect to the Internet.

Q.	Do I need to install RideWay on each of the PCs in my LAN?

A.	No. RideWay should be installed on one Windows 95/NT PC (Server PC) . Other computers (Client PCs) on the LAN will then be able to utilize RideWay’s many features.

Q.	Does RideWay run on a Novell LAN?

A.	Yes, RideWay can run on a Novell LAN. However, you have to configure TCP/IP protocol on the Server PC and Clients PC’s. If you contact ITServ, they will provide you with more information on the software you need and how to configure it.

Q.	My LAN runs the IPX protocol. Can I also run TCT/IP at the same time?

A.	Yes.

Q.	I have a PC connected to the Internet via a SLIP connection, and I have a UNIX box connected to the PC via an Ethernet connection. Can I give the UNIX box Internet access through the PC with RideWay?

A.	Yes. TCT/IP will need to be configured for the two machines to speak to one another. Also, your browser and any other Internet applications (e.g. telnet, e-mail, chat, news reader, etc.) on the UNIX box will need to be SOCKS-Compliant.

Q.	I have 2 computers at home, but have not setup a LAN yet. How do I set it up?

A.	Please refer to Network Configuration.

Q.	Do I need to modify my current dial-up account settings to work with RideWay?

A.	No. RideWay allows you to use your existing dial-up account. However, to take full advantage of RideWay's features, it is recommended that you create Windows 95's Dial-Up Networking entries to initiate calls to the Internet Access Provider.

Q. 	Does RideWay have the 'On-demand dialing' feature? Namely, can I have the Server PC dial out and make an Internet connection by making an Internet request from a Client PC?

A. 	Yes.

Q.	My Client PC seems to connect to the RideWay server, but it gets disconnected shortly. Why is this?

A.	There are most likely two causes for this problem.

1.	The browser is set to proxy mode, but some proxy entries other than the SOCKS are filled out; or

2.	If the client is a Windows 3.xx operating system, the Client PC's machine name is not defined in the TCT/IP Host file.

Possible Solutions:

1.	In Netscape Navigator, set the 'SOCKS Host' to the IP of the Server PC and set 'port' to 1080. Remember to leave all other proxy entries in blank; or

2.	If indeed you are using Windows 3.xx, search for the Host definition or Host file associated with your TCT/IP package and enter your Client PC hostname (machine name) and IP address. For example, if you are using NetManage TCT/IP for Windows, you should be able to enter these information in the Service tab within Custom icon. If you are using Trumpet, you have to search for the Host file and use an editor to add this line of information (please follow the line format shown in the file).

Q.	I could not start BreezeWay FTP Proxy on my Server PC. What should I do?

A.	If you are running a FTP server, for example, Windows NT FTP server on Server PC, it will occupy port 21 which is the default FTP control port BreezeWay needs. To solve this conflict, you should either change the control port of BreezeWay FTP proxy to another unused port or just disable it. Please refer to BreezeWay Setup and FTP Application Setup When Using BreezeWay for detailed setup instructions. Note that if you change the control port of BreezeWay FTP proxy, you should also specify the port on your FTP client software.


FAQ Application Specifics

Application Specifics

Q.	Which Internet applications work with RideWay?

A.	RideWay is a SOCKS 4 compliant Proxy Server for Windows 95/NT. It is compatible with all SOCKS 4 compliant browsers, email, ftp, news, and telnet packages such as Netscape Navigator 2.0 or higher.

Q.	How do I make SOCKS compliant Internet applications work with RideWay ?

A.	For each application the configuration will be different. In general, you need to look for an option to set either the 'Proxy' configuration or a 'SOCKS' firewall or host. You would input your Server PC's IP for the SOCKS address and '1080' for the SOCKS Port. (See Enable SOCKS proxy for Internet Software for more information.)

Q.	Which EMAIL applications supporting SOCKS 4 can I use with RideWay?

A.	Netscape Mail. Or you can use BreezeWay provided in RideWay version 1.6, as your Internet email proxy server. Please read BreezeWay Setup and Email Application Setup When Using BreezeWay for configuration instructions.

Q.	Which TELNET applications supporting SOCKS 4 can I use with RideWay?

A.	NetTerm, CRT

Q.	Which CHAT applications supporting SOCKS 4 can I use with RideWay?

A.	MIRC

Q.	Which FTP applications supporting SOCKS 4 can I use with RideWay?

A.	eFTP, Netscape Navigator, Internet Explorer

Q.	Can I FTP from the Server PC via RideWay?

A.	No, you can NOT. It’s a limitation of Socks4 protocol. However, you could use FTP application on the Server PC without passing through RideWay since the Server PC could access Internet directly.

Q.	How do I FTP from the Netscape Navigator browser?

A.	If you wish to make an anonymous FTP transfer, simply use the following format "ftp://<site address>" for the 'location' box. For non-anonymous FTP transfers, use the format "ftp://<username>@<site address>" and the browser will prompt you for your password. For instance, to make an FTP connection to 'host.fictional.edu' with username 'example', enter "ftp://example@host.fictional.edu" in the location box.

Q.	How do I FTP from the Internet Explorer browser?

A.	If you wish to make an anonymous FTP transfer, simply use the following format "ftp://<site address>" for the 'address' box. For non-anonymous FTP transfers, use the format "ftp://<username>:<password>@<site address>". For instance, to make an FTP connection to 'host.fictional.edu' with username 'example' and password 'secret', enter "ftp://example:secret@host.fictional.edu" in the address box.

Q.	How do I get Netscape Mail and Netscape News to work with Netscape Navigator on the Client machines?

A.	The Email/ News Reader functions which come with Netscape Navigator work very well with RideWay. Once you have properly configured Netscape Navigator to run through the 'SOCKS Host' in 'Manual Proxy Mode', you will be able to browse, ftp, email, and read news from your Client PCs.

Q.	If my email application does not support SOCKS, can I use it with RideWay?

A.	Yes. RideWay Release 1.6 includes an add-on feature called BreezeWay which provides Internet email proxy service for non-SOCKS complaint email application like Eudora to send/receive Internet emails. Please refer to  BreezeWay Setup and Email Application Setup When Using BreezeWay for detailed setup instructions.

Q.	Can I use RealPlayer with RideWay?

A.	Yes. RideWay Release 1.7 with BreezeWay options support RealPlayer proxy service. Please refer to  BreezeWay Setup and RealPlayer Setup When Using BreezeWay for detailed setup instructions.


FAQ Registration

Registration

Q.	What do I get for registering RideWay?

A.	Registering RideWay removes all limitations from the program, giving you the right to use the product for as long as you own it. Registered users of RideWay are eligible for free upgrades (minor version releases), technical support via email and web, and email update notices.

Q.	How do I register RideWay?

A.	Go to the ITServ registration page and follow the instructions from there. We process credit card orders online on a secure SSL server and also accept checks and money orders made out to ITServ, Inc. Contact us at info@itserv.com if you have any questions.

Q.	What is a "user" as referred to in the price table above?

A.	A user refers to any PC which is set to "proxy" (i.e. manual proxy for Netscape) or "socks" mode and connects to the Internet through the RideWay.

Q.	Do Internet connections from the Server PC count as an additional "user"?

A.	If the Server PC's Internet applications use the "proxy" or "socks" mode, then the Server PC does count as an additional user. Enabling the "proxy" or "socks" feature for Internet applications allows the Server PC to take advantage of useful features such as access control and log generating

Q.	How do I upgrade my registered version to allow for additional users?

A.	Users seeking to add additional users after purchasing a lower user license can do so by paying the difference plus a $25 service fee. For example, if you purchased a three user-license for $50 and then later decided to add four more users, you would pay $125 (i.e., the difference between a multi-user license and a three-user license = $100. Add $25 service fee.)

Q.	I purchased RideWay and received a License ID. How do I register RideWay with this license?

A.	To register RideWay with the License ID you have received, you would follow the procedure below:

1.	Run RideWay.

2.	Under the 'Help' menu, go to the 'Register RideWay' option.

3.	Fill in the 3 fields: User Name, License Type, License ID. Everything is case-sensitive.

4.	Click OK.

Q.	Do I need to purchase BreezeWay in addition to RideWay?

A.	Yes, when you purchase RideWay you need to specify if you want to purchase BreezeWay. If you do not purchase BreezeWay license, BreezeWay will be disabled after you registered RideWay.

Note: To register RideWay, you will need Version 1.0 or greater. If your version of RideWay has expired already, please download the latest version of RideWay from our web site.


FAQ Troubleshooting

Troubleshooting

Q.	How to get a detailed report of RideWay server for troubleshooting?

A.	RideWay could generate several types of reports. If you need a detailed report for troubleshooting your system, please follow these steps:

•	Choose Clear Server Log under Server menu.

•	Choose Log Options under Server menu. It pop up a Log Options for Server dialog box. Then choose Level 2 radio, and click OK.

•	Run the RideWay server until the error happens again.

•	Choose Report for Server under Report menu.

•	Click Create button. Then you will get a detail report for trouble shooting.

Note: Please undo the change of Log Options after the troubleshooting. Choosing Level 2 of Log option causes a heavy burden on RideWay server.

Q.	I could not start the server of RideWay. Why?

A.	There are several reasons prevent the starting of RideWay server. Please create a detail report of RideWay server and figure out the exact problem. In most cases, you could find the solution from RideWay help documentation, especially, in this section. If you could not solve the problem, please mail the detail report to our customer support at support@itserv.com.

Q.	I got a Error message, Error(10048): bind: SOCKS port 1080: Address already in use. Why?

A.	WSA error message 10048 means the port is used by another program. By convention, port 1080 is used for SOCKS proxy server. If you have installed another proxy server, please uninstall it and try RideWay again. Some proxy server runs its engine at background while your system boots up even you don’t want to use it. Or you could change the SOCKS proxy server port of RideWay to another port under the Server control dialog box. However, we don’t suggest this way since you have to reconfigure the applications on Client PCs.

Q.	I got a Error message, Error(10048): bind: DNS port 53: Address already in use. Why?

A.	RideWay features a DNS proxy for those systems without a DNS server on the server machine. If your server PC is running the DNS server on NT, the port 53 will be occupied by the DNS server. Since you don’t need the DNS proxy of RideWay in this case, please disable the function of the DNS proxy by:

•	Choose Server Control under Server menu.

•	Check Disable DNS proxy and click OK.

Q.	My server PC dial up when I click Network Neighborhood on the Client machines. Why?

. 	This situation is caused by some unnecessary DNS requests issued by your Client PCs. When you enable the function of On-demand dialing, DNS requests and SOCKS requests will trigger the connection to your ISP. In same cases, the Client PC will try to resolve names when it boots, browse the Network Neighborhood.  If you have this problem, just enable On-demand dialing for only SOCKS requests. Refer to  Dialer Control Dialog Box for details.

Q.	I cannot connect to Internet from the Client PC. There is an error message Error(20004): Invalid Socks version (71)((0x47) in the detail report. Why?

A.	Your application on the Client PC is not SOCKS-compliant or you miss something on the configuration of it. Please refer to Applications Setup on a Client PC for details.