SolarNet PC-NFSpro Configuration

Use the Configuration program to create an initial configuration profile, to make changes to a configuration profile, or to create alternate configuration profiles.

Introduction

What Is Configuration?

How To...

Tip: Use Express Config for first-time configuration. Then configure additional Applications and Services as needed.  Click on Use Express Config:

To Set Up Your PC to..	Click on...
Connect to the Internet	Configure TCP/IP
Connect to a LAN	Configure a LAN Connection
Dial in to another computer	Configure a Serial Connection
Manage user accounts	Configure User Information
Share files	Configure an NFS Client
Print	Configure Printing
Use NetBIOS	Configure NetBIOS
Be a file server	Configure Services
Define a Printer Queue	Define a Print Queue
Set up your PC as a print server	Configure an LPD Server
Set up an SNMP Agent	Configure SNMP
Work with NetWare over ODI	Configure for NetWare Over an ODI Driver
Work with NetWare over WFW	Configure for NetWare Over Windows for Workgroups
Store multiple configurations	Work with Multiple Configuration Profiles
Enable PC-Admin client	Enable PC-Admin Client


What Is Configuration?

The Configuration program creates and changes configuration profiles. You can use alternate configuration profiles in different settings. For example, you might create one profile to configure your notebook computer for use in the office, when it is connected to a network locally, and another profile for use when you are on the road and want to connect to your network through a modem.

To use a particular configuration, make sure the Configuration program updates the system startup files to match the configuration that you want. The Configuration program will offer to perform this update whenever you choose Save or Save As, or if you choose Exit after you have opened a new configuration file. You can also force the Configuration program to update the files by choosing the Update command from the File menu.


Save a Configuration Profile
Working With Multiple Configuration Profiles

When you start the Configuration program, it opens the last configuration file that you were working with. The name of the file is displayed in the dialog box title bar.

At this point, you can create a new (additional) configuration profile, or edit the existing profile.

To create a new configuration file:

1.	Use the Configuration program to make any required changes.

2.	Choose the Save As... command from the File menu.

3.	Enter a name for the new profile (the extension .CFG will be appended) and choose OK.

Configuration files are normally stored in the CONFIGS subdirectory of your product installation directory.

4.	To activate the configuration (i.e., update the system startup files to match the configuration), choose Exit.

When prompted about updating the system startup files, choose Yes.

To edit an existing configuration file:

1.	Choose the Open command from the File menu.

2.	Select the configuration file to be edited, and choose OK.

3.	After you have made your changes, choose the Save button (or the Save command from the File menu).

4.	To activate the configuration (i.e., update the system startup files to match the configuration), choose Exit.

When prompted about updating the system startup files, choose Yes.


Use Express Config

Express Config steps you through a minimal configuration procedure, in which you supply:

Network connection type: LAN+DHCP, LAN, or PPP

PC Name

PC IP address

Subnet mask

IP address of a default gateway

DNS search name

DNS domain name

DNS server name

Default user name

IP address of an authentication (PCNFSD) server

Express Config's dialog boxes prompt you to select an option button or type a value. After you supply the requested information, choose the Next button or press the Enter key. Change a previous answer by choosing Back or by double-clicking on the item in the bottom area of the dialog box. Choose Next when you are ready to begin.

Once you have provided all the necessary information, Express Config opens a LAN adapter dialog box. Here, you choose and configure an Ethernet or Token Ring adapter. If you have selected a serial interface, Express Config presents the Serial configuration dialog.


Express Config - Type of Interface

Select LAN for Ethernet or Token Ring connections. Select LAN + DHCP if network configuration through DHCP is available on your LAN. For serial connections, select PPP.


Express Config - Name of PC

The name of your PC is the name associated with your PC's IP address.


Express Config - IP Address of PC

An IP address contains four numbers separated by dots; for example, 127.144.5.17. This address uniquely identifies your PC among all others on the network.


Express Config - Subnet Mask

The subnet mask defines the fields of the IP address that identify the network and identify individual hosts connected to the network. The subnet mask differs according to the class of the network. For example, a class C network typically uses a subnet mask of 255.255.255.0. A class B network uses a subnet mask of 255.255.0.0.

The address segments containing zeros represent portions of the IP address reserved for identifying computers connected to the network.


Express Config - IP Address of Gateway

The default gateway is the computer on your network that routes communication beyond your local network. Do not enter a value here if your LAN is not connected to other networks.


Express Config - DNS Search

A list of Domain Name Servers to search for a server to provide DNS services to the PC.


Express Config - DNS Domain

The DNS (Domain Name Service) domain name is the name assigned to a given network site.


Express Config - IP Addr of DNS Server

The domain name server is the computer that provides DNS services, such as looking up host names. If your network does not use DNS or NIS, you must edit the PCNFSPRO\ETC\HOSTS file to include any host names that you plan to use. Once you've completed Express Config, choose the TCP/IP button to configure NIS or to edit the HOSTS file.


Express Config - Use NFS?

NFS is the industry standard distributed network file system.


Express Config - Default User Name

This name is displayed in the login dialog box at SolarNet startup. You can override this name at login time.


Express Config - IP Addr of PCNFSD Server

The PCNFSD server authenticates you as a valid user of the network. each time you log in. The authentication server must be running version 1 or version 2 of the PCNFSD daemon. Leave this field blank if your network uses DHCP.


Express Config - WfWG?
Express Config - Windows for Workgroups

Windows for Workgroups will always be the primary network with SolarNet as the secondary network.


Express Config - Name of Configuration Profile

This name is used to identify the configuration profile. You can create and use different profiles, as needed.


Express Config - Finishing Up

You have completed Express Config. Review your settings and make any necessary changes. Then, choose Next to generate a SolarNet configuration profile and configure a driver.


Configure TCP/IP

TCP/IP configuration lets you set up a PC for the specific network to which this machine will become a network node. These specifics include:

Type of interface: LAN (Ethernet or Token Ring) or Serial (PPP) interface

Use of the DHCP or BOOTP client

Host name, IP address, and subnet mask for a network interface

Name Service (NIS, DNS, file-based)

Default router

To Configure an Interface to a TCP/IP Network:

1.	From the Configuration main window, press the TCP/IP button.

The TCP/IP configuration dialog box appears.

2.	Choose the Enable check box for a LAN interface, a PPP interface, or both.

If you've enabled a LAN interface and have access to a server that can dynamically assign IP addresses, choose the DHCP check box.

3.	Enter a PC name for any interface that you enabled.

Work with your network administrator to create a unique PC host name and enter that name here.

4.	Enter an IP address for your PC, unless you checked DHCP earlier.

Your network administrator will assign an IP address for your machine.

5.	Enter a subnet mask value.

Your network administrator can provide you with the subnet mask used for your network site.

See Also:

Configure Name Services

Define a Gateway or Router

Configure DNS

Configure NIS


Network Interface Types

SolarNet enables a PC to use a LAN interface, such as Ethernet or Token Ring, or a serial interface such as PPP. SolarNet even permits running both a LAN interface and a serial interface simultaneously.

When either of these interfaces is enabled, SolarNet needs to know the host name, subnet mask, and IP address assigned to that machine. A network administrator will assign a host name and an IP address to a machine when it is first added to a network, except on networks that use DHCP or BOOTP for dynamically assigning IP addresses.


Define a Gateway or Router

Default Gateway

TCP/IP networks use specific server machines to connect one network or subnetwork to another. These machines are known as gateways or routers. The TCP/IP configuration dialog lets you specify a default gateway, and optional network pathways to specific network locations.

To Set a Gateway:

1.	In the TCP/IP configuration dialog box, enter a machine name or machine IP address in the edit box labeled Default Gateway.

SolarNet will use this machine as its default gateway.

2.	Choose the Add button to create a specific route to a subnetwork.

The Add Route dialog box opens.

3.	Enter the appropriate host/network and gateway name into the edit box provided.


Configuring Name Services

TCP/IP networks use a name service to locate other machines on the network. SolarNet PCs can be configured to use up to three name services, and you can specify what name service SolarNet should attempt to use first, second, and third. The name services include: Sun's distributed network information service, known as NIS, Distributed Name Service (DNS), or file-based name services that use the file named hosts. The configuration program lets you edit a hosts file during TCP/IP configuration.

To Configure a Name Service:

1.	In the TCP/IP configuration dialog box, choose the option button in the row labeled NIS, DNS, HOSTS, or None for each of the columns labeled First, Second, and Third.

This selection lets you specify in what order you want SolarNet to look for a specific name service.

2.	Press the Configure NIS or Configure DNS button to summon a name service configuration dialog box.

Enter a domain name, such as xyz.edu, and the IP address of a DNS or NIS server in the edit boxes provided.

3.	Press the Edit HOSTS button to launch Notepad with your local hosts file loaded and ready for editing.

Add any machine name/IP address combinations necessary. Any other machine you want to reach on a network must be listed in the hosts file if you selected HOSTS as your only name service.

See Also:

Configure NIS

Configure DNS


Configure NIS

1	Enter an NIS domain name in the edit box provided.

Domain names usually end with .COM, .EDU, or .ORG.

2	Enter the IP address of an NIS server in the edit box labeled NIS Server.

You cannot enter a name here, only an IP address.

3.	Choose OK.


Configure DNS

1.	Enter your DNS domain name in the edit box provided.

Domain names usually end with .COM, .EDU, or .ORG.

2.	Enter the IP address of a DNS server in the edit box labeled DNS Server #1.

You cannot enter a name here, only an IP address. If you plan to use a LAN interface and a PPP interface simultaneously using DNS, specify two servers by entering a second server IP address in the DNS Server #2 edit box.

3.	(Optional) In the DNS Search edit box, enter up to five DNS domain names, separating each entry with a space.

SolarNet software searches these domains, in the order they are entered, if a name cannot be mapped in the domain specified in the DNS Domain edit box.

4.	Choose OK.


Configure a LAN Connection

Network Adapter (LAN Driver) Configuration

Every Ethernet or Token-Ring network adapter card needs a device driver that lets its hardware communicate with a PC's system software. SolarNet includes a number of device drivers for popular network adapters in packet driver or NDIS driver configurations.

How do you choose a driver? Use the following table to pick a driver type.

If you use...	Choose...

Windows 3.1	NDIS for greatest availability

                                     Packet for best performance

NetWare and SolarNet	Existing ODI

LAN Manager and SolarNet	NDIS

(PC-NFSpro only)

Windows for Workgroups 3.11	Windows for Workgroups (usually NDIS3)

Tip: Windows for Workgroups users do not need to set up a driver, since they will already have performed this setup when they installed Windows for Workgroups. SolarNet can use a Windows for Workgroups driver.

See Also:

Setting Up a Packet Driver

Setting Up an NDIS Driver

Configuring PC-NFSpro to Work With a NetWare Network


To Set Up a Packet Driver

These instructions assume you have installed the SolarNet-supplied packet drivers. If you chose not to have Setup install the packet drivers, rerun Setup and use the Custom Install button to install just the packet drivers.

1.	In the Configuration main window, choose the LAN button.

The LAN Driver dialog box appears.

2.	Within the Type of Driver to Use box, choose the option button labeled Packet Driver.

This choice may already be selected.

3.	Choose the down arrow on the right side of the edit box labeled Installed Drivers.

A list of the packet drivers supplied by SolarNet appears.

4.	Choose the name of the driver for your network adapter.

If you don't know what kind of network adapter is in your PC, you may have to ask for help from a person who knows your machine.

5.	Press the Configure button to inform SolarNet of the I/O Base Address, Interrupt, and other parameters for the driver you've installed.

You must select new parameters if your board uses non-default values. See the adapter documentation for this information.

6.	Choose OK.


Packet Driver Parameters

Most packet drivers require you to specify one or more parameters in order to work correctly with your PC.  Typical parameters you might need to specify include a packet interrupt number or an I/O address. The line of text that appears under the edit box on the Configure Driver dialog box lists all the parameters for the driver chosen for configuration. These parameter names will be abbreviated, and appear in the order in which they must be entered within the edit box. Your network adapter manual will provide suggested values for each parameter. Refer to the following table for a description of common packet driver parameter abbreviations.

Abbreviation	Description

packet_int_no	Packet Interrupt Number

pktint	Packet Interrupt Number

hardware_irq	Hardware Interrupt Number

io_addr	I/O Address

base_addr	Memory Base Address

mem_addr	Memory Base Address

mem_base	Memory Base Address

cable_type	Thick or Thin Ethernet cable

dma_no	Direct Memory Access Channel

Leave a space between parameters, and enter the values exactly as they are shown in the parameter line directly underneath the edit box. Brackets [ ] surround optional parameters.


To Configure an NDIS Driver

1.	On the LAN Driver configuration dialog box, click the option button labeled NDIS Driver.

This choice may already be selected.

2.	Choose the down arrow on the right side of the edit box labeled Installed Drivers.

A list of the NDIS drivers supplied by SolarNet appears.

3.	Choose the name of the driver for your network adapter.

If you don't know what kind of network adapter is in your PC, you may have to ask for help.

4.	Choose the Add New Driver button if you have an NDIS driver for your adapter from its manufacturer.

A dialog appears to let you retrieve this driver from its distribution disk.

5.	Choose the Configure button to inform SolarNet of the I/O Base Address, Interrupt, and other parameters for the driver you've installed.

You must select new parameters if your board uses non-default values. See the adapter documentation for this information.

6.	Choose a parameter (i.e., IOADDRESS, INT, MEM, etc.) in the edit box provided.

This action highlights that value.

7.	Choose or supply a new value.

The default value will be highlighted and you can replace it by entering a new value. See the adapter documentation for the range of possible values for a given parameter.

8.	Choose OK.

6.	Choose OK.


Adding an NDIS Driver

To add an NDIS driver to your SolarNet software:

1.	If it is not already running, start the SolarNet PC-NFSpro Configuration program.

The Configuration main dialog box opens.

2.	Choose LAN.

The SolarNet PC-NFSpro Configuration - LAN Driver dialog box opens.

3.	Choose the NDIS option button in the Type of Driver to Use panel.

The Add New Drivers button is activated.

4.	Choose Add New Drivers.

The Add NDIS Drivers dialog box opens.

5.	Follow the directions in the dialog box regarding entering an NDIS driver path and/or diskette.

6.	Choose OK.

The Add NDIS Drivers dialog box displays a list of NDIS drivers found at the location you specified.

7.	Select a driver from the list and choose Add. (Optionally, install all drivers in the list by choosing Select All and choosing Add.)

The selected driver(s) is added to your SolarNet software.

8.	Choose OK.

The Add NDIS Drivers dialog box closes. An information box opens informing you that the driver was successfully installed.

9.	Choose OK to dismiss the information box.

The SolarNet PC-NFSpro Configuration - LAN Driver dialog box displays a list of preinstalled NDIS drivers, including the driver(s) you added.

10.	To use the driver, select it from the list of preinstalled drivers and choose OK.

Note: You may have to configure the NDIS driver before using it.


Configure a Serial Link

Use this configuration screen to set up serial communications using:

Remote Link Manager (PPP)

See Also:

Setting Up Simultaneous LAN and PPP Interfaces


Setting Up Simultaneous LAN and PPP Interfaces

You use one LAN interface and one PPP interface simultaneously. However, you must configure a default gateway for one interface, and then add a specific route for the other. In addition, you likely will not be able to use the same login name over both interfaces, which will prevent mounting the same drive from both interfaces. Finally, DNS users should configure two DNS servers, with the first configured for the LAN interface and the second for the PPP interface.

Perform these configuration operations on the TCP/IP configuration screen.


Set Up a Default Gateway and Add a Specific Route

A configuration profile can have only one default gateway, even though the TCP/IP configuration dialog box lets you enable both LAN and PPP interfaces. The default gateway will be either the network attached to the LAN interface, or the network attached to the PPP interface.  You should then use the TCP/IP configuration dialog's Specific Routes->Add button to add a specific route to the other network for the other interface.

For example, if your PPP link goes to an Internet Service Provider, you would define a default gateway to the PPP server, and then add a specific route to your LAN network. If you do not know the IP address of the PPP server ahead of time, leave the default gateway edit box blank. Then, bring up the Serial->Advanced PPP Configuration dialog and check the option Add Default Route. This option, in combination with a blank Default Gateway box, will fill in a gateway IP address after PPP client and server negotiation.

Conversely, if your LAN interface is on a network attached to the Internet and your PPP link is to a remote site, you would set the  default gateway to a local LAN server, and then add a specific route to the PPP interface.

You may view currently configured routes using the Network Statistics utility's Routing selection.


User Authorization

The credentials you obtain from an authentication server on the network attached to a local LAN interface will likely not be valid on the machines on the network to which you are attached through the PPP interface, and vice versa.  In practice, this means that you usually will not be able to use NFS-mounted drives on both networks simultaneously with your login name. One interface will need to use another login name, such as nobody.


Use Domain Name Service (DNS)

If you are using DNS on both the LAN and PPP network, you should configure DNS so that server #1 is on the LAN network and server #2 is on the PPP network, in order of use.

To specify DNS servers:

1.	Select the TCP/IP configuration button.

The TCP/IP configuration dialog box opens.

2.	Choose the button labeled Configure DNS.

The Configure DNS dialog box opens.

3.	Enter the IP address of the DNS server for the LAN interface in the edit box labeled DNS Server #1.

4.	Enter the IP address of the DNS server for the PPP interface in the edit box labeled DNS Server #2.

Alternatively, you can put the PPP server's IP address in the local HOSTS file if the remote network does not use DNS.


Establishing a Nomadic PC to Network Configuration

Use a nomadic configuration to connect to a server or network from a remote location. To create a nomadic configuration file:

1.	Start the Configuration program.

2.	Choose Express Config.

The Express Config dialog box opens.

3.	Enter a name for the nomadic Remote Link Manager configuration file and choose Next.

4.	Read the instructions in the screens that follow and enter the appropriate information.

Express Config guides you through required Remote Link Manager configuration items.

5.	When you've entered all required information, choose Save.

You settings are saved in a configuration file with the specified name.

6.	Restart the Configuration program and choose Serial.

The Configuration - Serial Connection dialog box opens.

7.	Select Autoconnect.

8.	Choose Advanced Settings.

9.	Choose Add Default Route.

10.	Choose OK.

11.	Choose Save.

12.	Exit and restart Windows.

The Remote Link Manager starts and dials the remote PPP server. A login dialog box opens.


Changing Existing Remote Link Manager Settings

Once you've used the Configuration program to establish an initial Remote Link Manager configuration, you can change individual settings, such as a phone number, from within the Remote Link Manager.

To change existing settings:

1.	Start the Remote Link Manager.

The Remote Link Manager main dialog box opens.

2.	Choose Configure.

The Configuration program starts and the Serial Configuration dialog box opens.

3.	Change any setting displayed in the Serial dialog box.

Choose Advanced to access and change advanced settings.

4.	Choose OK.

The Serial dialog box closes, revealing the main configuration dialog box.

5.	To update the Remote Link Manager configuration file with your changes, choose Save.

Your configuration changes are saved. In some cases you will need to restart Windows for your changes to take effect.

6.	To use your changes for the current Remote Link Manager session only, choose Save As and enter a name for the alternate configuration file.

The changes you've made apply to the current Remote Link Manager session and your alternate configuration file is updated. Choose No when prompted to update your system files so that the next time you start Windows your normal Remote Link Manager configuration will be used.


Configue User Information
Configure User Information

1.	Enter a valid user name in the edit box labeled Default User Name.

Check with a network administrator to be sure the user name is valid.

2.	Enter the name or IP address of a PCNFSD server in the Authentication Server edit box.

A PCNFSD server provides authentication of users.

3.	If you do not know the name or IP address of an authentication server, enter an asterisk (*) in the Authentication Server edit box.

An asterisk causes PC-NFSpro to broadcast for an authentication server.

4.	Determine whether to cancel the prompt for log in when Windows is started.

If you are using NFS services such as network drives and printers, it is important to log in when Windows is started so the user name can be authenticated. On the other hand, if you are using Windows only locally, or if you are using FTP or Telnet, it is unnecessary to log in to the network before Windows is started. If you do not want to be prompted to log in, select the check box Don't Login at Windows Startup.


Kerberos Security

Kerberos is a user authentication system that provides a high level of security in a network environment. The solvent software includes a Kerberos client program that you can configure to work with a Kerberos server program.

Kerberos security is provided in realms. Think of a realm as a network area in which Kerberos security is required and available. There are two types of realms: your local realm, and an administrative realm. Often they are the same. You must specify an administrative realm.

A Kerberos administrative server oversees Kerberos operations in the administrative realm. It also stores the master Kerberos database of users and their associated privileges.

Note: A Kerberos server program is not included with the SolarNet software. Normally, it is part of the operating system kernel software. Refer to the Kerberos server documentation for information on configuring and using the Kerberos server software.


Configuring Kerberos
Configuring and Enabling Kerberos

To configure and enable Kerberos:

1.	From the Configuration main window press the User button.

The User Information dialog box opens.

2.	Enter the local realm name in the Local Realm edit box.

3.	Choose the Add button in the Kerberos section of the User dialog box.

The Specify Kerberos Server dialog box opens.

4.	Enter the name or IP address of the Kerberos administrative server in the Server edit box.

5.	Enter the name of your network's Kerberos administrative realm in the Realm edit box.

6.	Indicate that this entry is administrative by choosing the Administrative Server check box, and then choose OK.

The Specify Kerberos Server dialog box closes and the User Information dialog box is displayed.

7.	Enable Kerberos by choosing the Perform Kerberos Authentication at Login check box.

An X appears in the check box and Kerberos authentication will occur automatically for subsequent log ins.

Note: Kerberos login is transparent. When it is successful, there is no indication that Kerberos is enabled. If Kerberos login fails, an error message displays indicating that Kerberos login was not successful.

Tip: To learn more about the nature of a Kerberos login failure, enable the Network Event Log and note the Kerberos error messages reported as a result of a failed login.

See Also:

Adding a Kerberos Server

Editing A Kerberos Server Entry

Deleting a Kerberos Server


Adding a Kerberos Server

To add a Kerberos Server:

1.	Enter the server name or IP address in the Server Name edit box.

2.	Enter the name of the realm in the Realm  edit box.

3.	If the server is an administrative server, indicate that by checking the Admin Server check box and choose OK.

4.	Exit the Configuration program and save your changes.


Editing a Kerberos Server Entry

To edit a Kerberos server entry:

1.	Select the server name in the Kerberos portion of the User Information dialog.

The name appears highlighted.

2.	Choose Edit.

The Specify Kerberos Server dialog box opens and displays the highlighted server name or IP address.

3.	Edit the name as required, and choose OK.

The edited entry appears in the Servers portion of the User Information dialog box.

4.	Exit the Configuration program and save your changes.


Deleting a Kerberos Server

To delete a Kerberos server:

1.	Select the server name in the Kerberos portion of the User Information dialog box.

The name appears highlighted.

2.	Choose Delete.

The name is deleted from your configuration profile.

3.	Exit the Configuration program and save your changes.


Configure the NFS Client

Configuring a PC's NFS settings entails specifying a time zone and default options for drive connections, including file-name mapping, data transfer options, and access control.

To Set Up NFS:

1.	From the Configuration main window, press the NFS button.

The NFS configuration dialog box appears.

2.	To use suggested settings for a UNIX server, press the UNIX Server button.

Otherwise, press the other offered buttons, or no button.

3.	Choose the appropriate Default Options for Drive Connections.

Restore at Login of: Current User restores previously connected drives for the user who is currently logged in. This means that a user sees the same drive connections on subsequent logins.

Restore at Login of: Every User restores previously connected drives for any user who logs in. This is particularly useful if a number of users share a PC and work with the same network drives. If a user disconnects a drive, however, the connection will not be restored when the next user logs in.

Restore at Login of: Per Connection Login turns on per-mount logins.

The default options for drive connections are not mutually exclusive.

4.	To set individual  file-name handling values, data transfer, and access control, click in the provided check boxes, or use the drop-down list choices offered.

The values you choose here are defaults that can be overridden at drive connect time.

5.	Choose OK.

See Also:

NFS Cache Settings

NFS Option Settings


Configuring Printing

You can configure two types of SolarNet PC-NFSpro: printing that occurs from within Windows and printing that occurs from within a DOS box.

You can configure Windows-based default printing to use either the Berkeley UNIX LPR print protocol or the PCNFSD protocol. If you opt for the PCNFSD protocol, you can configure several printing options.

You can configure DOS-based printing by enabling the DOS print redirector and specifying a print activity time-out value.

See Also:

Configure Windows-Based Printing

Configure DOS-Based Printing


Configuring Windows-Based Printing

To set up a default Windows-based print protocol:

1.	In the Configuration main window, choose the Printing button.

The Printing configuration dialog box appears.

2.	Select  the option button labeled Use LPR Protocol for Printing, or Use PCNFSD Protocol for Printing.

You may select one or the other.

3.	If you want to restore printer connections at login, select Current User or Every User or both.

Current user restores previously connected printers for the user who is currently logged in. This means that a user sees the same connections at subsequent logins.

Every User restores previously connected printers for any user who logs in. This is particularly useful if a number of users share a PC and work with the same network printers. If a user disconnects a printer, however, the connection will not be restored when the next user logs in.

4.	If you selected the LPR protocol, choose OK.

You have finished configuring a default printing protocol.

5.	If you selected PCNFSD protocol, you may optionally set print options for the protocol by entering values in the provided edit boxes.

The values you choose here are defaults that can be overridden at drive connect time.

6.	Choose OK.


Configure DOS-Based Printing

To setup DOS-based printing:

1.	Start the Configuration program , open the Advanced Settings menu, and choose DOS Print Redirector.

The DOS Print Redirector dialog box opens.

2.	Enable DOS  printing by checking the Install DOS Print Redirector check box.

The DOS Print Redirector is installed each time the Windows program is started.

3.	Enter a DOS print time-out value in seconds in the edit box and choose OK.

The main Configuration dialog box opens.

4.	Choose Save to save the DOS print configuration settings.

The DOS Print Redirector is loaded the next time you start the Windows program .

5.	Exit and restart Windows to enable DOS printing.

Note: To Print from a DOS application, you must first start the DOS Print utility by double-clicking its icon. Once this utility is running, you can execute a Print command from within a DOS application.


Configure NETBIOS

To use certain applications over a network, such as Lotus Notes, SolarNet provides a NetBIOS protocol interface. You can configure this interface by defining NetBIOS parameters. NetBIOS parameters include:

NetBIOS Scope - The group of machines across which a NetBIOS name is known

Domain Scope - The name NetBIOS uses to query DNS to resolve system names

LAN Adapter Number - The logical number of the LAN network adapter

Number of Sessions - The number of sessions that can be run simultaneously

Number of Queued Commands - The maximum number of commands awaiting processing

Number of Registered Names - The maximum number of registered names

To Set Up a NetBIOS Interface:

1.	From the Configuration main window, choose NetBIOS.

The NetBIOS configuration dialog box opens.

2.	Select the check box labeled Enable NetBIOS Services.

The NetBIOS module will be loaded when the SolarNet network is started.

3.	Type a value for the NetBIOS scope into the edit box provided.

4.	Enter a LAN Adapter Number into the edit box provided.

Make sure this number matches the number assigned to PC-NFSpro in the [network.setup] section of the C:\WINDOWS\PROTOCOL.INI file. Look for a line similar to the following:

lana0=tcm$elink3, 1, pcnfspro

The number that follows "lana" is the LAN adapter number. Use this number in the NetBIOS Configuration dialog box's LAN Adapter Number edit box.

NOTE: The LAN Adapter Number default value of 0 will work for configurations where PC-NFSpro is the Primary network, that is, TCP/IP is the primary protocol. Verify this number if you plan to use multiple network protocols. Each protocol that uses NetBIOS as its transport must have a unique LAN adapter number.

5.	Type a value for the Domain scope into the edit box provided.

6.	(Optional) Change the values for the Maximum Number of Sessions, the Maximum Number of Queued Commands, and the Maximum Number of Registered Names.

The default for Sessions is 32, for Queued Commands is 64, and for Registered Names is 32.

7.	(Optional) Choose Edit Broadcast List to edit the file that contains a list of NetBIOS machines not located on the same subnet as the PC.

These machines cannot be reached by broadcasting. The broadcast list contains IP addresses, or if your network uses NIS or DNS, the names of machines outside your PC's local broadcast range.

Each line of the file may contain only one NetBIOS IP address or name. The broadcast file is loaded when the NetBIOS software is started. If you want to change the file name or contents, you should do so before NetBIOS is started.

8.	(Optional) Choose Edit Name Prefix List to edit the list of machine names and IP addresses which assists in NetBIOS name to IP address translation.


Configure Services

PC Server Configuration

SolarNet provides several daemons that can run on a PC to provide services to other machines on a network. These services permit remote access to the PC for file transfers, and remote command access. They include:

FTPd - File Transfer Protocol daemon

Telnetd - Login server daemon

LPD Print Server- LPR protocol daemon

Network Event Log - System message logger daemon

Two of the SolarNet daemons can be started automatically by a fifth daemon that mimics the UNIX inetd daemon. SolarNet calls this daemon Local Services Startup. When running, Local Services Startup starts and stops any combination of the Telnetd and FTPd daemons. It starts any of these daemons when another machine on the networks requests service from them. Once a service-requesting machine exits the caller client application, the Telnetd or FTPd servers unload.

Tip: If you do not configure the Local Services Startup, LPD Print Server, or Network Event Log services to start automatically, you can start them at any time by selecting their respective icons.

To Configure PC Daemons:

1.	In the Configuration main window, choose the Services button.

The Services dialog box opens.

2.	Select the check box labeled Start Local Services Startup to run the nfswinetd.exe program when you use this configuration.

The Local Services Startup program will run whenever you start SolarNet with the current configuration.

3.	Select the check boxes next to any other service you want to enable.

You can choose FTPd, Telnetd, or both.

4.	Enable the LPD Print Server, if needed, and enter LPD Print Server configuration information in the edit boxes provided, and define a print queue for each LPD Print Server printer attached to your machine.

You can specify a spool directory, turn on print logging, and resume the printing of any jobs that were unfinished when you last exited the network and Windows.


Define a Print Queue

SolarNet PC-NFSpro provides an LPD print server daemon that runs on a PC to allow other network machines to print to a printer attached to that PC. A queue is actually a name to identify a printer and the physical port to which it is attached. For example, an HP LaserJet printer attached to a PC's LPT2: port might use the LPD Print Server queue name "hplaser."

To Set Up an LPD Print Server Queue:

1.	On the Services dialog box under LPD Print Server-Queues, choose the Add button.

The Define LPD Queue dialog box opens.

2.	Enter the name of the queue in the edit box labeled Queue.

In the above cited example, hplaser would be entered here.

3.	Select a printer and physical port location from the displayed drop-down list of available printers.

If no printers appear, use Windows Control Panel->Printers to mount one or more printers.

4.	Choose a method for determining the file type of individual print jobs.

Methods are : Auto-Detect File Type, Binary File Always Assumed, or Text File Always Assumed.

Note: LPD Server behavior is determined by file type. LPD spools a text file (detected or assumed) to the Windows print driver associated with the selected printer. LPD spools a binary file (detected or assumed) directly to the printer, subject to the filtering options chosen in step 5.

5.	For binary files, choose whether to map the new-line character to a carriage-return/line feed character pair.

If this box is checked, any line feed character not preceded by a carriage return will have a carriage return inserted immediately before it in the printer output stream.

See Also:

LPD Print Server


Configure an LPD Print Server

1.	Choose the Services button from the Configuration main screen.

2.	Select the check box labeled Start LPD Server.

The print server daemon loads each time the Windows program loads.

3.	Enter a spool directory in the edit box labeled Spool Directory.

The default directory is c:\tmp.

4.	Add any necessary print queues.


Configure SNMP

To facilitate the asset management capabilities of network management software that uses the SNMP protocols, SolarNet provides an SNMP agent that you can configure to start automatically.

To Configure the SNMP Agent:

1.	In the Configuration main window, choose the SNMP button.

The SNMP configuration dialog box opens.

2.	Select the check box labeled Start SNMP Agent Automatically.

This selection will load the SNMP Agent on program startup.

3.	Choose the Add button to enter SNMP community names in the edit box labeled Communities.

A common default community name is "public." Setting up a community with write access turns on Sets. If no community is configured, the SNMP Agent uses a default value of public 0.0.0.0 read. This default community allows any management station to read all the supported variables from this managed PC.

4.	Choose the Add button to enter SNMP Trap Community names in the edit box provided.

The default community name is "public."

5.	Choose the box labeled Issue TRAPs to activate this feature.

By default, this feature is off.

6.	Supply any of the following information to configure variables in the MIB group: System Description, System Location, System Contact.

The System Description variable can contain information about the system's configuration, the System Location can describe the physical location of the machine, and the System Contact can contain the name, phone number, and e-mail address of the contact person for the machine.

7.	Choose OK.

See Also:

Define/Edit SNMP Community

Define/Edit SNMP Trap Community


Configure Packet Driver

To configure a packet driver:

1.	Type any necessary path, packet interrupt, system interrupt, I/O address, and transceiver-type parameters into the packet driver line shown in the edit box.

For example, to specify that the board's I/O address is at 320 hex, add 0x320 to the end of the line in the edit box.

2.	Choose OK.


Change Parameters for an NDIS Driver

To configure an NDIS driver:

1.	Choose a parameter (i.e., IOADDRESS, INT, MEM, etc.) in the edit box provided.

This action highlights that value.

2.	Choose or supply a new value.

The default value will be highlighted and you can replace it by entering a new value. See the adapter documentation for the range of possible values for a given parameter.

3.	Choose OK.


Browse for Connect Scripts

To choose a connect script, select a .SCR file in the file area of the File Open dialog box.


Browse for Disconnect Scripts

To choose a disconnect script, select a .SCR file in the file area of the File Open dialog box.


Define Custom Time Zone

1.	Choose the option box labeled Apply Daylight Savings Time if your time zone uses daylight saving time.

2.	Enter begin and end dates for your time zone's daylight saving time period in the edit boxes provided.

3.	Enter the amount of time, in hours and minutes, that daylight saving time adjusts the standard time in your time zone.

For example, in the U. S. Eastern time zone, daylight saving time adjusts standard time forward by one hour.

4.	Choose OK.


Define/Edit SNMP Community Dialog

This configuration procedure is optional. The default is one community named public, containing all IP addresses, with read-only permission for messages.

1.	Start the Configuration program and select SNMP.

2.	Choose the Add button to provide information about communities.

The SNMP Community dialog box opens.

3.	Provide the requested information, including the community name, the IP address of the system where Network Manager program is running, and the type of access.

A given manager may be in many communities.

Note: The manager address 0.0.0.0 is shorthand for "all IP addresses" and the default access type is read.

Note: Since SNMP uses the "trivial" authentication in which simply using a community name authenticates a message in that community, you should be extremely careful granting write access to anyone. It is relatively easy to "fake" an IP address.

4.	Choose OK to save your entries or Cancel to close the SNMP Community dialog box without saving your changes.


Define/Edit SNMP Trap Community Dialog

This configuration procedure is optional. The default is to send no traps.

1.	Start the Configuration program and select SNMP.

2.	Choose the Add button to provide information about Trap communities.

The SNMP Trap Community dialog box opens.

3.	Provide the requested information, including the Community name, the IP address or host name of the system where the network manager program is running, and the UDP port number.

The port should typically be 162.


NFS Cache Settings

It is not necessary to change the default NFS cache settings, but for better performance, you may choose to do so. Optimum settings vary according to your PC's configuration, so it may be necessary for you to fine-tune the settings to find what works best for your machine.

Access NFS Cache settings from the Advanced Settings menu in the Configuration program.

Click on an item below to view general guidelines for the NFS cache parameter:

How to Determine Your NFS Cache Settings

Size of Data Cache Block

Total Size of Data Cache

Attribute Cache Time-Out

Data Cache Time-Out


How to Determine Your Cache Settings

Adjusting NFS Cache settings may, in certain circumstances, improve overall NFS performance. None of the NFS Cache settings will effect performance of drives mounted with Locking/Sharing enabled, however, since the cache is disabled on such drives.

To improve NFS read and write performance, try the following:

•	Enlarge the size of the Data Cache - If you have enough physical memory (8 Mbytes or more), make the total size of the data cache larger than the default of 256 Kbytes. For example, on a 16-Mbyte machine, try setting the Data Cache to 4096 Kbytes.

•	Lengthen the Attribute Cache Time-out - This reduces the number of NFS GETATTR calls sent over the network. Adjust this parameter with caution, especially if you or others frequently modify your files directly on the server or on other NFS clients.

•	Lengthen the Data Cache Time-out - This setting controls the timing of periodic data cache flushes, (these occur regardless of whether cache attributes appear to have changed). This setting protects against the unlikely occurrence that a file is changed on the server without changing its NFS attributes. A good working value for this time-out is 600 seconds.

See Also:

Total Size of the Data Cache

Attribute Cache Time-out

Data Cache Time-out


Size of Data Cache Block

Enter a value to set the size in bytes of the blocks that are read and written to and from the cache, or accept the default value. Common values are 1024, 2048, 4096 or 8192 bytes. While the size need not be related to the NFS read or write size, it is best to choose a value no larger than the largest of the read or write size.

A large value reduces the number of NFS operations that must be performed, but increases the time each operation takes because each block contains more data.

The default size is 8192 bytes.


Total Size of Data Cache

Enter a value to set the total size in kilobytes of the data cache (the actual size of the cache will be slightly larger than the value you enter). Alternatively, accept the default cache size. This cache uses non-pageable memory, so allocate only as much memory as your PC has physical memory that is not needed for other purposes. Depending on various aspects of your PC's configuration, you may be able to set a much higher value.

A larger value has both a positive and negative impact upon performance. Because more data is likely to be stored in the cache and need not be written to or from the network as frequently, network performance improves. However, because memory is reserved for the data cache and is not available for other purposes, PC performance may decrease.

Set this value to zero to disable the NFS data cache completely.

The default data cache size is 256 kbytes.


Attribute Cache Time-out

Enter a value to set the number of seconds before the network is checked to see whether the file modification time or size (file attributes) have changed, or accept the default.

Specifying a smaller value assures earlier detection that a file has been modified by someone else. Specifying a larger value causes fewer NFS operations, which improves performance. If others only occasionally access the same files as you, you may use a larger value.

The default attribute cache time-out value is 15 seconds.


Data Cache Time-out

Enter a value for the number of seconds that data remains in the cache before it is assumed to be invalid, or accept the default. Occasionally a file can be modified even though its attributes do not change. The time-out ensures that even in this case, the cache eventually will contain the correct data. If a server has a clock with fine granularity, or if the server guarantees that each file modification results in a new file modification time, you may specify a large value.

The default data cache time-out is 600 seconds.


NFS Option Settings

You do not usually need to change default NFS options. However, to maximize performance and functionality, or minimize memory use, you may want to alter some option settings. Since the optimum setting for each option depends on your situation, it may be advantageous for you to try different settings for each option to find what works best for you.

Access NFS Option Settings from the Advanced Settings menu in the Configuration program.

Click on an item below to view general guidelines for an NFS option:

When to Experiment With NFS Option Settings

NFS Files Shown with the Archive Bit: On/Off

Entries in File Name Mapping Table

Entries in Name Lookup Cache

Backoff Multiplier for NFS Retransmissions

See Also:

NFS Cache Settings


When to Experiment With NFS Option Settings

To optimize NFS performance, consider changing the some of the NFS option settings. The NFS option settings to adjust are:

•	Entries in Name Lookup Cache - If you have adequate physical memory (8 Mbytes or more) consider increasing the number of entries stored in the Name Lookup cache. For example, change this setting from the default of 64 entries, to 256 entries.

•	Backoff Multiplier for NFS Retransmission - When using a network monitor you observe excessive NFS retransmissions, use a larger multiplier. If NFS performance seems to suffer because of excessive waiting periods between retransmissions, use a smaller multiplier. The default value of this multiplier is 4. To improve NFS performance, try a setting of 2.

See Also:

Entries in the Name Lookup Cache

Backoff Multiplier for NFS Retransmission


NFS File Archive Bit Setting

DOS files have an attribute called the archive bit. NFS has no equivalent file attribute. SolarNet normally sets the archive bit of files to On. However, some application programs may work better with the archive bit set to Off. For example, some backup programs may refuse to backup a file that has its archive bit set to On.

To set the NFS file archive bit to Off, choose the Off option button in the NFS Options dialog box.

The default NFS archive bit setting is On.

Note: The archive bit for directories is always set to Off.


Entries in File Name Mapping Table
Entries in File-Name Mapping Table

If a file name on a server cannot be directly transformed into a DOS file name, SolarNet creates a new DOS name for the file. This is called file-name mapping and it usually occurs when a server file name is longer than the DOS 8 by.3 character file name limit. By default, SolarNet stores up to 256 such name mappings in a reference table. When there are more than 256 name mappings, some mappings are removed from the table to make room for others. If this occurs, you may not be able to access a file whose name mapping has been removed.

Use the File Name Mapping option to determine how many name-mapping table entries SolarNet can store. A lower number of table entries consumes less system memory but may prevent access to some files whose names have been mapped. Increasing table entries allows access to more files with mapped names but consumes more memory.

The default value for entries in the file name mapping table is 256.

Tip: If you never use File Name Mapping, set the entries in File Name Mapping Table to zero.


Entries in Name Lookup Cache

This option item determines the number of entries that are stored in the Name Lookup Cache. SolarNet uses the Name Lookup Cache to optimize performance by minimizing the number of times a file path name must be looked up over the network.

Setting the number of Name Lookup Cache entries to a higher value improves performance by reducing the number of network-based name lookup operations. Setting the number of entries to a lower value conserves system memory by reducing the number of names stored in the Name Lookup Cache. You can minimize memory usage by setting the number of stored entries to zero. However, system performance will suffer accordingly.

The default value for entries in the name lookup cache is 64 entries.

Tip: Unless your PC has very little system memory, accept the default setting for this option.


Backoff Multiplier for NFS Retransmissions

In most cases, you will not have to change this setting. This option item controls how quickly SolarNet transmits an NFS request when it does not receive a response to a previous NFS request. Setting this option smaller than the default value forces SolarNet to transmit subsequent NFS requests more quickly. Setting this option larger than the default value forces SolarNet to wait longer before transmitting subsequent NFS requests.

If using a network monitor you observe excessive NFS retransmissions, use a larger multiplier. If NFS performance seems to suffer because of excessive waiting periods between retransmissions, use a smaller multiplier.

The default value for the backoff multiplier is 4.

Note: The time-out value you establish for your drive and printer connections determines the initial NFS waiting period.


TCP/IP Options

You do not usually need to change the default TCP/IP options. However, to maximize performance you may want to alter these option settings.

Access TCP/IP Option Settings from the Advanced Settings menu in the Configuration program.

Click on an item below for more information about changing TCP/IP option settings.

When to Experiment With TCP/IP Option Settings

Size of Small Buffer Pool

Size of Large Buffer Pool


When to Experiment With TCP/IP Option Settings

If network performance seems to degrade, use the Network Statistics->Memory function to display statistics about your PC's memory usage.

If you see frequent requests for memory being denied, or requests for memory delayed, gradually increase the size of the Small and Large Buffer Pools .

See Also:

Size of Small Buffer Pool

Size of Large Buffer Pool


Size of Small Buffer Pool

The Size of Small Buffer Pool setting determines the number of kilobytes of extended memory reserved for internal buffers. These buffers are referred to as mbufs and are used to store TCP/IP header information as well as small amounts of data. Each mbuf is 128 bytes in size. The default size for this setting is 160 Kbytes.

Change this setting by opening the Configuration program's Advanced Settings menu, choosing TPC/IP options, entering an alternative value in the Size of Small Buffers edit box, and choosing OK.

Increase the size of this buffer pool in XXX byte increments. Use Network Statistics to re-examine memory usage. When few or no requests for memory are delayed or denied, buffer size is adequate.

Note: You must restart the Windows program for this setting to take effect.


Size of Large Buffer Pool

The Size of Large Buffer Pool setting determines the number of kilobytes of extended memory reserved for internal TCP/IP network data buffers. These buffers, also known as clusters, store network data which does not fit within a 128-byte mbuf. Each large buffer (cluster) is 2 Kbytes in size. The default size for this setting is 160 Kbytes.

Change this setting by opening the Configuration program's Advanced Settings menu, choosing TPC/IP options, entering an alternative value in the Size of Large Buffers edit box, and choosing OK.

Increase the size of this buffer pool in XXX byte increments. Use Network Statistics to re-examine memory usage. When few or no requests for memory are delayed or denied, buffer size is adequate.

Note: You must restart the Windows program for this setting to take effect.


DHCP

The Dynamic Host Configuration Protocol (DHCP) enables a PC to retrieve from a server the parameters it needs to operate in a network, such as its IP address.


Configuration Profile

A configuration profile is a file in which important configuration information about the SolarNet software is stored. This information includes network operating parameters, network services available, and additional information that SolarNet requires to operate effectively in your network environment. This file is created automatically by the Configuration program, stored in the \CONFIGS sub-directory, and has a .CFG file extenstion.

You must make changes to a configuration profile through the Configuration program, rather than by directly editing a .CFG file.


Getting NetWare Coexistence

The Windows for Workgroups Setup program allows you to configure the Windows for Workgroups network and one additional network.  For example, you can configure the WFW network and a NetWare network, or WFW network and the PC SolarNet network.  Using WFW Setup you cannot configure three networks.

SolarNet network software can coexist with another software network by sharing its network adapter driver.  This allows you to run three networks simultaneously on your LAN.  You can configure two networks using Windows for Workgroups Setup.  Configuring SolarNet network software to share one of the existing network adapter drivers gives you access to the resources of all three networks.

You can configure SolarNet software to run simultaneously with Novell NetWare software by using the SolarNet ODI interface driver.  This driver, also known as a shim, translates one network interface into another.  The name for this shim is ODI_PKT.

SolarNet provides a network driver manager that is configured in Windows as the sole network driver.  The network driver manager loads each installed network driver.  When you use File Manager or Print Manager to connect to a network file system, the network driver manager dispatches the request to the appropriate network.  If more than one network is installed, it presents a dialog box, asking you to choose a network.

See Also:

Configure SolarNet and NetWare Over an ODI Driver


Configure for NetWare Over an ODI Driver

You can configure SolarNet network software to work with an existing NetWare network over the same ODI network adapter driver at any time after installing SolarNet software. Sharing the adapter allows you to run three networks at the same time.

Before you begin, make sure that:

Either Windows Version 3.1 or Windows for Workgroups version 3.11 is installed.

Novell NetWare is installed as the primary network under Windows for Workgroups, or as the network driver under Windows 3.1 over an ODI adapter.

To configure SolarNet for a NetWare network over an ODI driver:

1.	Exit any active Windows applications.

2.	Insert the PC-NFSpro Setup diskette into the diskette drive or insert the Setup CD into the CD-ROM drive.

3.	From Windows Program Manager, choose File -->Run, then enter a:\setup, or d:\setup, if installing from CD-ROM.

The PC-NFSpro installation program begins.

4.	Choose Yes to start the configuration now.

A message notifies you that Novell NetWare has been detected.

5.	Choose Yes to use the existing ODI driver.

The PC-NFSpro network will share the existing ODI driver with the currently installed network.

6.	Run Express Config and enter information about your PC and network.

After you complete all the Express Config screens, the LAN Driver Configuration screen opens.

7.	Click OK  to accept the already configured ODI Driver configuration.

A message box may appear with information about the NET.CFG file.

8.	Choose Yes if a message box asks if you want to update the NET.CFG file.

The Configuration program updates the NET.CFG file to enable the existing ODI driver to run over a TCP/IP network. If you choose No, you can configure coexistence with NetWare at a later time.

9.	Choose Save and Exit from the main Configuration dialog box, even if you have made no more changes to the configuration.

10.	Choose Yes to coexist with the existing LAN.

The network driver manager is installed so that you can use the Windows File Manager and Print Manager to mount and unmount network files and printers from all installed networks.

11.	A message warns not to use Windows Setup to change your network configuration.

If you use the Windows Setup program to change your network configuration after configuring NetWare coexistence, Windows reads the OEMNFSW.INF file in the C:\WINDOWS\SYSTEM directory and restores your PC to its original configuration.  Any changes PC-NFSpro makes to the Windows system files for network coexistence are lost.

12.	When you finish configuring your PC, exit Windows and restart your computer.

To undo this configuration, use the unconfigure menu option from the Tools menu.

See Also:

Configure for NetWare Over Windows for Workgroups

Getting NetWare Coexistence

Unconfigure Network Coexistence


Configure for NetWare Over Windows for Workgroups

You can configure SolarNet PC-NFSpro to work with an existing NetWare network over the same ODI network adapter driver at any time after installing PC-NFSpro software. Sharing the network adapter allows you to run three networks at the same time, using Windows for Workgroups version 3.11.

Before you begin, make sure that:

Windows for Workgroups version 3.11 is installed as the primary network.

Novell NetWare is installed as a secondary network over an NDIS3/ODI driver.

In the Network dialog box, Novell NetWare should be the network listed next to the Other button.  In the Drivers panel, check that the card selected is IPXODI support driver ODI/NDIS3.

To configure SolarNet for NetWare over a Windows for Workgroups driver:

1.	Exit any active Windows applications.

2.	Insert the PC-NFSpro Setup diskette into the diskette drive or insert the Setup CD into the CD-ROM drive.

3.	From Windows Program Manager, choose File -->Run, then enter a:\setup, or d:\setup if installing from CD-ROM.

The PC-NFSpro installation program begins.

4.	Choose Yes to start the configuration now.

The Configuration program opens.

5.	Choose OK when a message tells you that the Configuration program has detected NetWare and to run Windows Network Setup to add the PC-NFSpro protocol.

6.	Choose the Exit button to exit the Configuration program.

7.	Run Windows Network Setup.

Windows Network Setup configures the Windows for Workgroups driver to run over a TCP/IP network.

a.	From the Network Setup dialog box, choose Drivers.

b.	Choose the Add Protocol button from the Network Drivers dialog box.

c.	Select Unlisted or Updated Protocol.

d.	When Windows setup asks for the path name to the vendor-supplied files, insert the PC-NFS distribution setup diskette (or CD) (if you have removed it).

e.	Select SunSoft PC-NFSpro from the list of network drivers and choose OK.

f.	Choose OK in the Network Drivers dialog box.

g.	Choose OK in the Network Setup dialog box.

h.	Choose OK in the Windows Network Setup dialog box.

Windows for Workgroups updated the NET.CFG file so that the existing ODI driver can run over a TCP/IP network, and adds the PC-NFSpro protocol to the \WINDOWS\PROTOCOL.INI file.

8.	Answer No when asked about replacing the currently installed PC-NFSpro software.

If you accidentally answer Yes, you will be prompted to insert the PC-NFSpro software distribution diskette to reinstall the network protocol component. Perform this operation if necessary.

9.	Choose Yes to update system files.

10.	Choose Continue.

Do not let Windows restart your computer.

11.	Double-click the Configuration icon to restart the PC-NFSpro Configuration program.

12.	Enter TCP/IP information.

You can use Express Config option or configure each component separately (for example, TCP/IP, LAN, Serial).

13.	Choose Save and Exit from the Configuration dialog box, even if you make no more changes to the configuration.

14.	Choose Yes when prompted for coexistence with NetWare.

The Configuration program updates the SYSTEM.INI file to configure the network driver manager  as the sole network driver in Windows.

15.	When you finish configuring your PC, exit Windows and restart your computer.

To undo this configuration, use the unconfigure menu option from the Tools menu.

See Also:

Configure for NetWare Over an ODI Driver

Getting NetWare Coexistence

Unconfigure Network Coexistence


Unconfigure Network Coexistence
Unconfigure NetWare Coexistence

Removing network coexistence restores the \WINDOWS\SYSTEM.INI file to its previous state.  It does not delete the SolarNet network software.

To remove network coexistence:

1.	Select Unconfigure from the Tools menu on the Configuration main dialog box.

If SolarNet is configured for Windows for Workgroups and NetWare, use the Windows Network Setup program to remove the SolarNet protocol entry from the PROTOCOL.INI file.

2.	From the Network Setup dialog box, choose Drivers.

3.	Select SunSoft PC-NFS(R)pro 2.0 from the list of network drivers.

4.	Choose Remove.

See Also:

Configure for NetWare Over an ODI Driver

Configure for NetWare Over Windows for Workgroups

Getting NetWare Coexistence


NetWare ODI LAN Driver Message Box

You already have an ODI driver configured for your NetWare network.  You can configure your SolarNet network software to share the existing ODI adapter with the NetWare network or you can choose another network driver.

Choose...	To...
Yes	Use the existing ODI driver.   Configuration updates the ODI driver to send and receive TCP/IP packets.
No	Choose another network driver.  You can install NetWare and WFW networks, or you can install SolarNet and WFW networks.  But you cannot install WFW, NetWare, and SolarNet to run together.


Update NET.CFG File Message Box

You can configure your existing NetWare network to run over a TCP/IP network. You need to do this if you plan to run SolarNet with your existing NetWare network.

A NetWare network uses the information in the \NWCLIENT\NET.CFG file to configure the ODI driver to send and receive data using a particular network protocol.  Most NetWare ODI drivers are configured to use the IPX protocol.  SolarNet uses the TCP/IP protocol.

Choose...	To...
Yes	Run SolarNet and NetWare networks together over the same ODI adapter.  The NET.CFG file is updated to enable NetWare to run over a TCP/IP network.
No	Save the changes in the NET.TMP file.  Your NetWare network will continue to run over the IPX protocol.   You will not be able to run SolarNet and NetWare network software together on the same network without updating the NET.CFG file.   You can update the NET.CFG file at a later time and select LAN in the SolarNet Configuration box to enable coexistence.


Coexist With an Existing LAN Message Box

You can configure SolarNet network software to run with the currently installed local area network. Running two networks together allows you to use Windows File Manager to connect to network file systems and network printers on installed networks.

Once configured for multiple networks, you can choose a network when connecting to network file systems and network printers.

Choose...	To...
Yes	Configure SolarNet to run together with your existing network software.  This allows you to use Windows File Manager and Print Manager to mount and unmount network files and printers.   Configuration updates your WINDOWS\SYSTEM.INI file.
No	Use Windows Network Setup to complete network installation.   You can install SolarNet as the only network, or install SolarNet and Windows for Workgroups.  But, these two networks do not coexist.  You can use File Manager to mount and unmount only the SolarNet files.


Windows Network Setup Warning

You have chosen to run SolarNet software with an existing network.  Configuring SolarNet to coexist with an existing network does not update the Microsoft Windows network setup.  Windows allows you to install a maximum of  two networks (Windows for Workgroups and one other).  For example, if you select the Windows Setup icon, the existing LAN (not SolarNet) is displayed as the current network.

If you use the Windows Network Setup to change your network configuration, Windows reads the OEMSETUP.INF file in the \WINDOWS\SYSTEM directory and returns to its originally installed networks.  The configuration for coexistence is not saved.

If you run Windows Network Setup by mistake and lose the configuration for coexistence:

1.	Select Unconfigure from the Tools Menu in the Configuration mail dialog box.

2.	Select LAN configuration... from the Tools Menu.

3.	Choose Existing ODI Driver.


ODI

Open Data Link Interface (ODI) is a driver specification developed by Novell to send and receive multiple communications that use different protocols on the same adapter.  This coexistence allows, for example, drives D through L to be connected as SolarNet network drives (if your SolarNet software provides an NFS network driver), and drives O through X to be mounted as NetWare volumes.


Enable PC-Admin Client

SolarNet PC-Admin software provides additional client management services to PC-NFSpro 2.0 clients. Enabling this capability requires the presence of a PC-Admin 1.5 Server augmented by the PC-Admin 1.5 Upgrade Kit for PC-NFSpro 2.0.

To obtain this Upgrade Kit, contact one of the following:

* Your local PC-NFSpro reseller or SunSoft Authorized Service Provider

* The SunSoft forum on CompuServe [go sunsoft]

* 1-800-USA4SUN in the USA and Canada only (within 90 days of purchase)


Comm Driver Help

Comm Driver Help


DHCP Options Help

DHCP Options Help


Remote Link Manager Help

Remote Link Manager Help