Copyright: RideWay


ITServ RideWay

Help Index

Overview

Introduction

Dialer

Server

BreezeWay

Installation Guide

System Requirements

Network Configuration

Software Installation

RideWay Dialer Setup

RideWay Server Setup

Using BreezeWay

Browser Setup

Telnet Application Setup

RealPlayer Setup

FTP Application Setup

Email Application Setup

TCP Mapping Setup

UDP Mapping Setup

Access the Internet from Home via the Office LAN

Menus

RideWay Window

Dialer Menu

Server Menu

Tools Menu

Help Menu

Frequently Asked Questions

General Information

Setup Questions

Application Specifics

Registration

Troubleshooting


Index Command (Help Menu)

Displays the opening screen of Help from which step-by-step instructions for using RideWay as well as reference information can be found.

Once you open Help, you can click the Contents button at any time to return to the opening screen.


Using Help Command (Help Menu)

Displays instructions for using Help.


About Command (Help Menu)

Displays the version number and copyright information of RideWay.


Help Using Help Command

Context Help Command

Displays help on some portion of RideWay. Selecting the Toolbar's Context Help button changes the mouse pointer to an arrow and question mark. Clicking anywhere in the RideWay window, such as another Toolbar button displays the Help for that particular topic.

Shortcut

Keys:	SHIFT+F1


Title Bar

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

Located along the top of a window, the Title Bar contains the name of the application and document.

Move the window by dragging 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 bars indicate the vertical and horizontal location within the document. The mouse can be used 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)

This command displays a four-headed arrow so that the active window can be sized 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)

Displays a four-headed arrow that moves 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)

Enlarges 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)

Switches 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)

Switches to the previous open document window. RideWay determines which window is previous according to the order in which the windows were opened.

Shortcut

Keys:	SHIFT+CTRL+F6


Close Command (Control Menus)

Closes the active window or dialog box.

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

Note: If multiple windows are open for a single document, the Close command on the document Control menu closes only one window at a time. All windows can be closed 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)

Returns the active window to its previous size and position before the Maximize or Minimize command was used.


Switch to Command (Application Control Menu)

Displays 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 e-mail (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/98 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, 98 or 3.1 to:

•	browse the WWW (World-Wide Web),

•	send and receive e-mails,

•	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 e-mails using e-mail 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/98/98 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:

•	Office: With RideWay, 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/98, a connection to the Internet, and a LAN, other machines (Windows 95/NT/98, Macintosh, Windows 3.1) can simultaneously access the Internet.

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


Dialer

Any Windows 95/NT/98 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/98’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:

•	E-mail 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 non-SOCKS e-mail applications to send and receive Internet e-mails. Please refer to BreezeWay Setup and E-mail Application Setup When Using BreezeWay for detailed setup instructions.

The FTP proxy service provided by BreezeWay allows all non-SOCKS FTP applications 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 non-SOCKS Telnet applications 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 non-SOCKS browsers 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 offices and homes, PCs must first be connected by a LAN in order to allow more than one computer to simultaneously access the Internet using one shared connection. The PC on which RideWay is installed acts as the Server PC while other PCs are considered Client PC(s).

The Server PC must:

•	run Windows 95/NT/98 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/98 PC to the Windows 95/NT/98 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/98 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/98: 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/98:

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/98 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/98 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/98 '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. This three-user trial version is fully enabled for 30 days from the date of installation. After the evaluation period has expired, you must register RideWay with ITServ Inc. to unlock the software. The 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/98 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/98’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/98:

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, E-mail, 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, E-mail, 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, E-mail, 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, E-mail, 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/98 PC) is connected to the LAN,

•	the Windows 95/NT/98’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 that provides proxy services for non-SOCKS compliant applications to access the Internet via RideWay.

The Internet e-mail proxy provided by BreezeWay includes both SMTP and POP3 proxy services. E-mail applications running on Client PCs will all use the same SMTP server specified in BreezeWay for sending Internet e-mails. 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 e-mails. POP3 server’s information is specified in each e-mail application running on Client PCs. Please refer to E-mail 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 use 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 E-mail 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 (Without 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 (with 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.


E-mail Application Setup on Client PC

E-mail Application Setup

Before trying to setup an e-mail 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 e-mail application supports SMTP and POP3 protocols for Internet e-mails.

Use the following step-by-step instructions to configure popular e-mail applications. You need to configure both BreezeWay on the Server PC and the e-mail 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 e-mail address is user@company.com.  To use E-mail 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 E-mail 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 e-mail 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 e-mail 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: Microsoft uses many different names for its e-mail programs on both Windows 95 and NT. All of the above Microsoft e-mail 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 e-mail 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 e-mail 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 e-mail applications on Client PCs:

For all other non-SOCKS compliant e-mail 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 e-mail 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 Identify,

5.	Enter Your name,

6.	Enter your E-mail address, for example user@company.com,

7.	Click Mail Server,

8.	Enter 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 e-mail applications on Client PCs:

For all other SOCKS compliant e-mail 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 95/NT/98 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 95/NT/98 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 e-mail 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:

Dialer Menu	Commands to control Dialer.
Server Menu	Commands to control Server.
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 displays 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 contains the following commands:

Connect	Dials to an ISP.
Disconnect	Hangs up and terminates the Internet connection.
Dialer Control	Displays setup of the Dial-Up Networking dialer.
Dial-Up Networking	Opens Microsoft’s Dial-Up Networking window.
Clear Dialer  Log	Clears the Dialer Log file.
Exit	Exits RideWay.


Dialer Connect command

Connect Command (Dialer Menu)

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)

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)

Opens the Dialer Control Dialog Box, where the RideWay Dial-Up Networking Dialer settings can be configured.

See Also:

Dialer

Dialer Setup


Dialer Control Dialog Box

The following options specifies the Default Connection, Redialing parameters, and Reconnection parameters:

Automatically Connect

Check this box to automatically dial and establish an Internet connection when RideWay starts. A connection can be manually dialed by using the Connect command under Dialer Menu.

Automatically Disconnect

Check this box to automatically disconnect the Internet connection when RideWay closes. Disconnecting can be accomplished manually by using the Disconnect command under Dialer Menu.

Default Connection

Displays the default dial-up connection. The 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/98, where the properties of the Internet connection can be configured. Click on this button to change the properties of the Default Connection.

Redial Control

For Windows 95/98

Click here to have RideWay automatically redial when it is unable to establish an Internet connection. The number of redial attempts and the interval time between each attempt are user-defined.

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

Enables the 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 connection time.

Enable On-demand dialing

including DNS requests

Disconnect after ____ minutes of inactivity

Checking Enable On-demand dialing allows the RideWay Dialer to dial/connect to the ISP specified by the Default Connection. 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 environments, the client PCs issue DNS requests to resolve computer names even when they are not accessing the Internet. In this case, make sure the box including DNS requests is unchecked so that the Dialer will not be triggered by these unnecessary DNS requests. When the including DNS requests box 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)

Opens the Dial-Up Networking window of Windows 95/NT/98

See Also:

Dialer

Dialer Setup


Clear Dialer Log command

Clear Dialer Log Command (Dialer Menu)

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)

Terminates the current RideWay session. The session can also be terminated by using 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 contains 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.
Clear Server Log	Clear the Server Log file.
Clear DNS cache	Clears the stored DNS files.


Start Server command

Start Command (Server Menu)

Starts the Proxy Server of RideWay. If On-demand dialing is enabled, the Proxy Server will run automatically when RideWay starts. Otherwise, an Internet connection made either through a LAN or with the Connect command under Dialer Menu must be established before starting RideWay.

Shortcuts

Keys:	Ctrl+S

See Also:

Server

Stop command


Stop Server command

Stop Command (Server Menu)

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)

Opens the Server Control Dialog Box where the Proxy Server properties are configured.

See Also:

Server

Server Setup


Server Control Dialog Box

Automatically starts SOCKS proxy server when RideWay starts

Check here to automatically start the SOCKS proxy server when RideWay starts. Manually start the SOCKS proxy server with the Start command.

SOCKS proxy server port

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

DNS proxy

Check here to enable DNS proxy server. This box should be checked for users not running their own DNS servers. DNS proxy server is required when using SOCKS proxy server.

DNS port

Defines the port used by the DNS proxy server. Since almost all applications use port 53 for DNS requests, users should select port 53.

DNS Servers

Shows the DNS servers that have been manually entered. Clicking the Add or Remove button will specify the DNS Servers. Note: Users who do not want to manually specify the DNS servers can ignore this box. RideWay will automatically attempt to find the DNS servers from the Control Panel  when starting the server.

BreezeWay… Button

Opens the BreezeWay Dialog Box that contains the following:

•	enables/disables HTTP and Security/Secure proxy and specifies its proxy port

•	enables/disables Telnet proxy and specifies its proxy port

•	enables/disables RealPlayer proxy and specifies its proxy port

•	enables/disables FTP proxy and specifies its Control port and Data port

•	enables/disables E-mail (SMTP/POP3) proxy and specifies its SMTP server

•	enables/disables TCP mapping and specifies its local ports and remote servers and ports

•	enables/disables UDP mapping and specifies its local ports and remote servers and ports

See Also:

BreezeWay

BreezeWay Setup

See Also:

Server

Server Setup


Server Control Dialog Box

BreezeWay (Non-Socks Proxies) Dialog Box

Enable HTTP and Security/Secure proxy

Enables HTTP and Security/Secure proxy. This should be unchecked if the server PC runs its own HTTP server. 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 browsers to use RideWay’s HTTP and Security/Secure proxy.

0	HTTP proxy port

If there is port conflict when the HTTP and Security/Secure proxy is entered, change the HTTP and Security/Secure proxy port in this box. The default value for this port is 80.

Enable Telnet proxy

Enables Telnet proxy. Refer to Telnet Application Setup When Using BreezeWay for detailed instructions for setting up Telnet applications to use RideWay’s Telnet proxy.

0	Telnet proxy port

1	If there is port conflict when the Telnet proxy is entered, change the Telnet proxy port in this box. The default value for this port is 23. Changing the default value is not recommended.

2	Enable RealPlayer proxy

Enables Realplayer proxy. Refer to Realplayer Setup When Using BreezeWay for detailed instructions for setting up RealPlayer to use RideWay’s Realplayer proxy.

0	RealPlayer proxy port

If there is port conflict when the Realplayer proxy is entered, change the Realplayer proxy port in this box. The default value for this port is 1090.

Enable FTP proxy

Enables FTP proxy. This should be left unchecked if the server PC runs its own FTP proxy. Refer to FTP Application Setup When Using BreezeWay for detailed instructions for setting up FTP applications to use RideWay’s FTP proxy.

0	Control port

1	If there is port conflict when the FTP proxy is enabled, change the FTP proxy Control port in this box. The default value for the Control port is 21. Changing the default value is not recommended.

2	Data port

3	If there is port conflict when the FTP proxy is enabled, change the FTP proxy Data port in this box. The default value for the Data port is 21. Changing the default value is not recommended.

4	Enable Email Proxy (SMTP/POP3)

Enables Email proxy. If the server PC runs its own e-mail proxy, do not enable Email proxy. Refer to Email Application Setup When Using BreezeWay for detailed instructions for setting up email applications to use RideWay’s Email proxy.

SMTP server

0	Enter the SMTP server’s host name or IP address in this box. Please contact your ISP. for the information if not known.

1	Enable TCP mapping

Enables TCP mapping. Refer to TCP Mapping Setup When Using BreezeWay for detailed setup instructions.

0	Local port    Remote server : port

1	Local port refers to the TCP port that RideWay opens 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 this connection. For example, Internet News uses NNTP (which is a TCP protocol) and Client PCs receive News from the same NNTP server. Set up TCP mapping for Internet News proxy by setting Local port to 119 and Remote server to the ISP’s NNTP server and Remote port to 119.

Enable UDP mapping

Enables UDP mapping. Refer to UDP Mapping Setup When Using BreezeWay  for detailed setup instructions.

0	Local port    Remote server : port

1	Local port refers to the port that RideWay opens 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. 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


Server Menu Command

Security Administration Command (Server Menu)

Opens the Access Control Box where the RideWay proxy server permissions are controlled.

See Also:

Server


Server Security Administration dialog

Access Control Dialog Box

Enable Access Control

Check here to impose access restrictions to both internal and external computers. If this box is checked, only those computers explicitly specified in under Full access and Conditional access have access permissions and all other computers have no access permission. If this box is not checked there are no access restrictions for internal computers. In other words, every internal computer has full access to the Internet. By default this box is not checked.

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. Computers can be entered individually or as complete subnets.

Computers with no access

Networks and/or computers defined in this box have no access to the Internet. These computers are denied access to any computer in the Internet. When an entire subnet is listed in full access, it is still possible to assign individual computers no access. In other words, no access takes precedence over conditional access and full access.

Computers with conditional access

Networks and/or computers defined in this box are permitted or denied access to some Internet addresses. When Permit connections is selected, all the computers listed in the From: window have access to only those addresses in the To: window. When Deny connections is selected, all the computers listed in the From: window will be unable to access those addresses in the To: window. If a network and/or computer is listed in both conditional access and full access windows, it will be assigned conditional access.

Add button

Displays a dialog box enabling you to add a computer or network into the associated box.

Remove Button.

Deletes the selected computer or network from the associated box.

See Also:

Server


Clear Server Log command

Clear Server Log Command (Server Menu)

Empties the log file of Proxy Server.

See Also:

Clear Dialer Log command


Server Menu Commands

Clear DNS Cache (Server Menu)

Empties the DNS cache file. If for some reasons, the cached DNS entries don’t keep up to date, use this command to refresh cache buffer.


Tools menu

Tools Menu Commands

The Tools Menu offers the following commands:

Ping	Pings a remote computer.
DNS Lookup	Looks up a computer name or an IP address.
Trace Route	Traces the route to a remote computer.
IP Configuration	Shows the IP configuration of the local computer.
Dialer Log	Generates the Dialer Report
Server Log	Generates the Server Report
Log Options	Shows Log Level Selections and Log size settings
Stay in SysTray when start	Controls the position of RideWay when minimized


Ping command

Ping Command (Tools Menu)

The “Ping" command sends several probe messages to the specified remote computer. The remote computer simply echoes each probe message. If a message is successfully echoed back and matches the transmitted one with no error, the computer prints out a successful probe.

The ping utility can be used 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, a name resolution problem exists. In this case, be sure that the computer name being queried 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 the 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

Starts pinging the remote computer.

Help Button

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 ‘Request timed out’ will be displayed.

•	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)

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 a 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

Looks up the remote computer name or IP address.

Help Button

Displays online help information.

The following shows sample output for DNS Lookup:

DNS lookup for	"www.itserv.com"

IP address(s):	207.196.61.6

DNS 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 trace packets 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. Consistently high numbers of traversing time or time-out associated to certain nodes could indicate a congested network segment along the path.

The detailed explanation and a sample output for Trace Route is 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

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

•	The last field is the name of the intermediate gateway

•	A * (star) indicates that a packet was lost and did not come back to the local computer. This is called a "packet drop". Packets are dropped because some gateways fail to return the appropriate message requested by Trace Route. Other times, firewalls use packet filters which block packets used by Trace Route. Finally, packets may be lost as a result of network congestion. One or two stars per line indicate that performance is poor and data is being lost. A line full of stars means that the target computer is unreachable.

•	Sometimes 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, Internet routing tables are incomplete or conflict with the target computer. If looping occurs within a user's internal network or between the routers on either end of a customer link, the user’s routing has been setup improperly.

0	Trace Route described line-by-line

1	Trace Route shows the path packets take from the computer in use to the destination. Each hop is a port on a router somewhere in the Internet. A detailed line-by-line analysis:

2	Starting Point

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

4	"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!

5	First Hop

6	  1      2 ms       1 ms       1 ms  	207.196.61.1

7	There are three things to notice here:

•	There are three different sets of numbers, with each representing one of the three packets that Trace Route sends out (it's possible that these packets can take different routes)

•	The numbers measure the round-trip time (in milliseconds) of each packet from the starting point to the IP address

•	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 where the packets enter the router

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 that there is no name and only an IP number. This 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)

Displays the IP Configuration Dialog Box where the user can 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 any changes are made, such as disconnecting from the network, the IP Configuration utility must be restarted. To run the IP Configuration utility, click the Refresh  button.

See Also:

IP Configuration Dialog Box


IP Configuration dialog

IP Configuration Dialog Box

Refresh Button

Shows the IP Configuration of the local computer.

Help Button

Displays online help information.

See Also:

IP Configuration command


Report for Dialer command

Dialer Log (Tools Menu)

Displays the Report for Dialer Dialog Box that generates a report for the RideWay Dialer.

See Also:

Dialer


Report for Dialer dialog

Report for Dialer Dialog Box

Starting from

Specifies the starting time of the report. If unchecked, RideWay will generate the report by scanning the log from the beginning.

Ending at

Specifies 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

Selects the style of the report to be generated. Check ‘Summary’ to view statistical

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

See Also:

Dialer


Report for Server command

Server Log (Tools Menu)

Displays the Report for Server Dialog Box that generates a report for the RideWay Proxy Server.

See Also:

Server


Report for Server dialog

Report for Server Dialog Box

Starting from

Specifies the starting time of the report. If unchecked, RideWay will generate the report by scanning the log from the beginning.

Ending at

Specifies 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 machines are displayed in the report. Selecting [All Systems] displays the connections of all machines in the report. Otherwise, the connection information of systems specified by the [These System] edit box will be showed. The [Add] [Remove] [Change] are used to select systems.

What to report

Select Access permitted by Socks proxy server to view restrictions for outbound connections. Select Access denied by Socks proxy server to view restrictions for inbound connections.

Internet access permission settings for any computer can be set using the Security Administration Command under Server Menu.

Detail level of the report

Selects 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


Server Log Options command

Log Options Command (Tools Menu)

Displays the Log Options Dialog Box that enables users to specify Log Options for the RideWay proxy server.

See Also:

Clear Server Log command


Server Log Options command

Log Options Dialog Box

Log Level Selection

Selects the Log Level of RideWay Proxy Server. There are three log levels: 0, 1, and 2. The default is set to Level 1, which records Error and Connection Messages into log files. Log level 2 is used for debugging purposes. The Server Log can be generated from the log file by using the Server Log command under the Tools Menu.

Note: It is recommended that Level 2 only be used when debugging the system, as this detailed logging may affect network performance.

Limit disk space for log

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

See Also:

Clear Server Log command


Tools Menu Commands

Stay in SysTray when start (Tools Menu)

Controls the position of the RideWay icon when minimized. If checked, the RideWay icon will stay in the system tray when RideWay starts.


Help menu

Help Menu Commands

The Help Menu contains the following commands:

Help Topics	Displays an index of searchable help topics
Register RideWay	Registers this software.
ITServ Home Page	Links to the ITServ home page
About RideWay	Displays the version number of this application.


Register RideWay command

Register RideWay Command (Help Menu)

Displays the Registration Dialog Box enabling users to register RideWay. Refer to How to Register RideWay for the registration procedure. When registering the product with ITServ, please have the Serial Number ready.

See Also:

ITServ Home Page command


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


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. Once the order is processed, a License ID will be delivered via e-mail within one business day (this may take longer if the user wishes to have the ID delivered through the mail).

Step 3: After receiving the License ID, please run RideWay, click on Help and Register RideWay. In the RideWay Registration window, enter your User Name, License Type, and License ID 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, feel free to contact us in any of the following ways:

ITServ Inc.

One Bank Street, Suite 220

Gaithersburg, MD 20878

USA

Customer Service

E-mail: support@itserv.com

Web: Error! Reference source not found.

See Also:

Registration Dialog Box


ITServ home page command

ITServ Home Page Command (Help Menu)

Starts the default browser and connects to the ITServ home page automatically. The ITServ home page handles registration, provides technical support, and contains additional product information.

See Also:

Register RideWay command


DNS

Domain Name Service is an Internet service that resolves host names into IP addresses, and vice versa.


DNS Server

DNS Server is a server of Domain Name Service that resolves host names into IP addresses, and vice versa.


ISP

Internet Service Provider or Internet Access Provider. The company that provides Internet connections.


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. The most common protocol for TCP/IP routers and PCs to communicate over dial-up and leased-line connections.


Proxy Server

RideWay is a Proxy Server that acts as a gateway between the internal users of a LAN and the Internet. Since all Internet traffic passes through RideWay, it also acts as a firewall, effectively shielding the rest of the LAN from the Internet.


SOCKS

SOCKS is a networking proxy protocol that enables hosts on one side of the SOCKS server to gain full access to hosts on the other side of the SOCKS server without requiring direct IP address reachability. 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. It is characterized by its 'open standards' that allow 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 an award-winning . SOCKS 4 compliant Proxy Server that enables multiple users to access the Internet simultaneously through one shared Internet connection. RideWay is both simple and cost-effective: the software is installed on a single Windows 95/NT/98 machine and no additional hardware or software is required for the Client PCs (Win 95/NT/98, 3.1, Macintosh, etc.).

Q.	Why use RideWay?

A.	RideWay saves money. By eliminating the need to pay for multiple phone lines, Internet accounts, modems and additional network security, the cost-savings resulting from the utilization of RideWay are tremendous! In addition, RideWay offers many convenient features that allows users to maximize the performance of their network.

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

•	BreezeWay supports Internet e-mail, FTP, Telnet, RealAudio/Video, Http//Https, TCP/UDP mappings for all PCs on a LAN

•	Bandwidth management control can assign higher priorities to specific clients (boss vs. secretary; parents doing work vs. children playing games)

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

•	Provides different permission settings to control Internet usage: full, conditional (limit workers to certain sites or restrict children from viewing inappropriate sites), or none

•	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 user-specified period of inactivity

•	Captures DNS settings in accordance with the DNS configuration of the PC; DNS caching increases browsing speed

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

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

1	A.	At the minimum, you will need:

•	A Windows 95/NT/98 PC with a 486 processor and 16 MB RAM

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

•	A Dial-Up access line or LAN connection to the Internet

Q.	Does RideWay support all types of modems?

A.	Yes. RideWay will work with any type of modem, supporting both analog modems (14.4 kps, 28.8, 33.6, 56 kps) and ISDN (64-128kps) modems. In addition, RideWay is perfect for high-speed connections such as cable modems and with wireless modems.

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 previous versions of RideWay before installing updated versions?

A.	Yes. If previous versions are not uninstalled, RideWay may not be able to run. They can be removed from the ‘Add/Remove Programs’ icon found on the ‘Control Panel’.

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. Once dial-up networking connects to the ISP and establishes the PPP connection by using the default setting of username and password, there’s no need for the scripting tool: just select the ISP as the default connection in the Dialer Control dialog box. Users that cannot connect to their ISP with this method can use their own dial-up tool to reach the ISP and then start the RideWay server by choosing “start” under the Server menu. However, the features of the RideWay dialer such as On-demand dialing will be disabled.

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

A.	The Server PC is the Windows 95/NT/98 PC with the Internet connection on which RideWay is installed. The Client PCs are those (Win 95/NT/98/3.1/3.11, Unix, Macintosh, etc.) that will connect to the Internet through the Server PC.

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

A.	No. RideWay should be installed on a single Windows 95/NT/89 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, the TCP/IP protocol settings on the Server PC and Clients PC’s will need to be properly configured. Detailed step-by-step instructions can be found on-line at Error! Reference source not found., and users with difficulties can always contact ITServ for assistance.

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 each 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. Can I still use RideWay?

A.	Yes. RideWay supports peer-to-peer networking. Please refer to the Network Configuration section.

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

A.	No. RideWay uses the existing dial-up account. However, to take full advantage of RideWay's features, it is recommended that users 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. Once the On-demand dialing feature is enabled, any Client PC can trigger the Server PC to dial out and establish an Internet connection.

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.	Either some proxy entries other than the SOCKS are entered in the browser under the proxy settings.

2.	A Client PC running a Windows 3.xx operating system does not have a name 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.

2.	If the Client PC is indeed using Windows 3.xx, search for the Host definition or Host file associated with the TCT/IP package and enter a Client PC hostname (machine name) and IP address. For example, in NetManage TCT/IP for Windows, this information can be entered on the Service tab within Custom icon. Those using Trumpet will 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.	An FTP server, for example, Windows NT FTP server on Server PC will occupy port 21, which serves as the default FTP control port BreezeWay needs. To resolve this conflict, 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. If the control port of the BreezeWay FTP proxy is changed, similar port specifications will be necessary for the FTP client software as well.


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/98. It is compatible with all SOCKS 4 compliant browsers, e-mail, ftp, news, and telnet packages such as Netscape Navigator 2.0 or higher. BreezeWay (included in version 2.0 and higher) supports non-SOCKS applications such RealPlayer, Microsoft Outlook, and ICQ.

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

A.	For each application the configuration will be different. In general, the applications will have to run with a 'Proxy' configuration or a 'SOCKS' firewall or host. The Server PC would be entered for the SOCKS address and ‘1080’ would be entered for the SOCKS Port. (See Enable SOCKS proxy for Internet Software for more information.)

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

A.	Yes. For step-by-step instructions, see the on-line manual.

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 e-mail/ News Reader functions which come with Netscape Navigator work very well with RideWay. Once Netscape Navigator is properly configured to run through the 'SOCKS Host' in 'Manual Proxy Mode', users will be able to browse, ftp, e-mail, and read news from Client PCs.

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

A.	Yes. RideWay includes a feature called BreezeWay that provides Internet e-mail proxy service for non-SOCKS complaint e-mail application such as Eudora to send/receive Internet e-mails. Please refer to  BreezeWay Setup and E-mail Application Setup When Using BreezeWay for detailed setup instructions.

Q.	Can I use RealPlayer with RideWay?

A.	Yes. The BreezeWay feature supports 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, granting customers 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), live technical support (as well as via e-mail and web, and e-mail update notices.

Q.	How do I register RideWay?

A.	Registration forms are on-line at the ITServ home page. ITServ processes credit card orders online on a secure SSL server and also accepts checks and money orders made out to ITServ, Inc. Contact us at info@itserv.com for further questions. When registering RideWay, please have the Serial Number ready (found under Help->Register RideWay).

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, a subscriber who purchased a RideWay 1.83 three user license (without BreezeWay) for $50 and then later wanted a RideWay 2.0 eight user license would pay $195 (i.e., the difference between an eight user license and a three-user license = $170. 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.

Troubleshooting

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

A.	RideWay can generate several types of reports. A detailed report for troubleshooting the system can be created by following these steps:

•	Choose Clear Server Log under Server menu.

•	Choose Log Options under the Tools menu. A Log Options for Server dialog box will appear. Select Level 2: Error, Connection, and Debugging and click OK.

•	Run the RideWay server until the error happens again.

•	Choose Server Log under the Tools menu.

•	Click the Create button to generate a detailed report for troubleshooting.

Note: When not troubleshooting, keep the Log Level on Level 0 to maximize the efficiency of RideWay (Level 2 causes a heavy burden on the RideWay server).

Q.	Why can’t I start the RideWay server?

A.	There are several reasons why the RideWay server does not start. Creating a detailed report of the RideWay server often reveals the exact problem. In most cases, the solutions can be found from RideWay help documentation, but if you continued to experience problems, please contact our customer support at Error! Reference source not found. and provide the detailed report log.

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 another proxy server has been installed, please uninstall it and try RideWay again (some proxy servers automatically run their engines in the background during system boots). Another solution would be to change the SOCKS proxy server port of RideWay to another port (this can be done in the Server control dialog box). However, we don’t suggest this way since applications on Client PCs would need to be reconfigured.

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 the server PC is running the DNS server on Windows NT, port 53 will be occupied by the DNS server. In this case, the DNS proxy of RideWay is not necessary and should be disabled in the following manner:

•	Choose Server Control under Server menu.

•	Make sure Enable DNS proxy is unchecked. Click OK.

Q.	My Server PC dials when I click Network Neighborhood on the Client machines. Why?

. 	This situation is caused by some unnecessary DNS requests issued by the Client PCs. When On-demand dialing is enabled, DNS requests and SOCKS requests will trigger the connection to the ISP. In some cases, the Client PC will attempt to resolve names when it boots or browses the Network Neighborhood. To solve this problem, go to the Dial-on demand dialing window under Dialer Control and make sure the box including DNS requests is unchecked. Refer to Dialer Control Dialog Box for details.

Q.	I cannot connect to the 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 there is a problem with the Client PC configuration. Please refer to Applications Setup on a Client PC for details.