home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
osinntsp.txt
< prev
next >
Wrap
Text File
|
1997-06-01
|
6KB
|
126 lines
OSINNTSP - INSTALLING NETSCAPE 2.02 FOR OS/2
01/28/97
=======================================================================
Installing Netscape 2.02 for OS/2
=======================================================================
Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------
DESCRIPTION
This document provides tips for configuring Netscape Navigator 2.02 for
OS/2 using Proxy and Socks Servers.
RESOLUTION
Upgrading WebExplorer to Netscape
---------------------------------
When installing Netscape Navigator for OS/2 over WebExplorer, you can
choose to migrate your WebExplorer quicklist to the Netscape list of
bookmarks. However, Netscape will not retain the settings for your
Socks Server or your Proxy Server.
To configure Socks and Proxies:
1. Open WebExplorer and select Configure from the menu.
Select Servers. Make note of the Proxy Gateway and
Socks Server fields. Close the WebExplorer.
2. Open Netscape and select Options from the menu; select
Network Preferences.
3. Select the Proxies tab on the Netscape Network Preferences
notebook.
4. Select Manual Proxy Configuration, then View.
5. Enter the following:
HTTP Proxy: Proxy Gateway from Web Explorer
SOCKS Host: Socks Server from Web Explorer
You should then have access beyond the firewall.
Netscape Handbook Help Section
------------------------------
Ordinarily, Netscape does not require proxies to interact with the
network services of external sources. However, in some network
configurations, the connection between Netscape and a remote server is
blocked by a firewall. Firewalls protect information in internal
computer networks from external access. In doing so, firewalls might
limit Netscape's ability to exchange information with external sources.
To overcome this limitation, Netscape can interact with proxy software.
A proxy server sits atop a firewall and acts as a conduit, providing a
specific connection for each network service protocol. If you are
running Netscape on an internal network from behind a firewall, your
system administrator can provide the names and associated port numbers
for the server running proxy software for each network service. Proxy
software retains the ability to communicate with external sources, yet
is trusted to communicate with the internal network.
Select No Proxies, Manual Proxy Configuration, or Automatic Proxy
Configuration to designate the conduit between your computer and the
Internet. Users with a direct connection to the Internet should use the
default, No Proxies. To customize a proxy configuration, choose Manual
Configuration and press the View button to display a dialog box. If you
have a configuration file designed expressly for your proxy server,
choose Automatic Configuration and type the file's URL in the adjacent
text field.
A single computer can run multiple servers, each server connection
identified with a port number. A proxy server, like an HTTP server or
an FTP server, occupies a port. Typically, a connection uses
standardized port numbers for each protocol (for example, HTTP = 80 and
FTP = 21). However, unlike common server protocols, the proxy server
has no default port. Netscape requires that for each proxy server you
specify in a Proxy text field, you also specify its port number in the
Port field.
Text in each Proxy field designates the host name of each protocol's
proxy server. (Often, a single proxy server handles the three major
protocols: HTTP, FTP, and Gopher.) This can also be a numeric IP
address of the proxy server.
A number in each adjacent Port field identifies the port number used by
the proxy server.
Text fields for proxies and ports are offered for FTP (File Transfer
Protocol), Gopher, HTTP (HyperText Transfer Protocol), Security (Secure
Sockets Layer protocol), WAIS (Wide Area Information System), and SOCKS
(firewall bypass software).
The text field No Proxy for:, available when viewing the Manual Proxy
Configuration windows, allows you to bypass the proxy server for one or
more specified local domains. For example, if you specify
HTTP Proxy: aserver.netscape.com Port: 8080
No Proxy for: adomain,bdomain,netscape.com
then all HTTP requests for the adomain, bdomain, and netscape.com host
servers go from Netscape directly to the host (not using any proxy).
All HTTP requests for other servers go from Netscape through the proxy
server aserver on port 8080, then to the host. A proxy that runs on a
host server outside a firewall cannot connect to server inside the
firewall. To bypass the firewall's restriction, you must set the No
Proxy for: field to include any internal server you're using. If you
use local hostnames without the domain name, you should list them the
same way. Multiple hostnames are delimited by commas and the wildcard
character (*) cannot be used.
______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including
without limitation, warranties of fitness and merchantability with
respect to the information in this document. By furnishing this
document, IBM grants no licenses to any related patents or copyrights.
Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark
information.