HP 3000 Manuals HP 3000 Manuals
Resource Sharing A.02.00 for MPE/iX Industry Standard TCP/IP Enhancement
by Dan Clavin
Software Services and Technology Division
Overview of Enhancement
The primary enhancement to Resource Sharing A.02.00 is a modification to
the server's network communication method.
The Resource Sharing server previously used a communication method
developed by Hewlett-Packard. It now uses the industry standard network
communication method for name registration. The NetBIOS name
registration service uses the TCP/IP protocol (stream mode) to provide a
mechanism for a server to register its existence on the network for a
client to find potential servers.
HP 3000 Server Information
The Resource Sharing server has been enhanced to process requests from
the Microsoft(R) LAN Manager and Microsoft(R) Windows for Workgroups(TM)
(WfW) client PCs communicating with industry standard TCP/IP protocol
(stream mode).
NetBIOS Name Service Resolution.
The Resource Sharing/iX server uses an added NetBIOS monitor process that
resolves the name service requests that the Microsoft LAN Manager client
PCs generates during connection.
SHOWNBSTATUS Command.
The SHOWNBSTATUS command was added to the existing PPCDIAGC.PPC.SYS
utility to allow for a system administrator to determine whether the name
service resolution is active or not. If the name service resolution is
active, a message is given indicating that the process has been started.
Otherwise, the network must be restarted to enable the industry standard
TCP/IP (stream mode) connections to complete.
Installation and Configuration Changes
The Resource Sharing/iX product is installed as described in the Software
Update Notice for Resource Sharing A.02.00 (B1718-90004) and the HP 3000
MPE/iX Installation, Update, and Add-On Manual (36123-90001). Additional
configuration changes may be required for the network interface settings
for the Network Services product. Please refer to the HP 3000/iX Network
Planning and Configuration Guide (36922-61023) for network configuration
information.
Network Configuration.
This enhancement may require network configuration changes to operate
correctly. If the clients are currently communicating with the HP 3000
(i.e., FTP, VT, etc.), then changes are not likely to be needed. Below
are some configuration areas to check.
Ethernet/802.3 Flag.
The protocol(s) that the PC Client uses (or gateway for remote clients)
must be enabled on the HP 3000. Check:
NMMGR Path = @NETXPORT.NI.<niname>
Subnet Mask.
Verify that the configured subnet mask is correct for the network to
which the HP 3000 and PC Clients are connected. The subnet mask must be
the same for all nodes on the same network. Check:
NMMGR Path = @NETXPORT.NI.<niname>.PROTOCOL.IP
Neighbor Gateways.
In the event that the PC Clients and the HP 3000 are on different
networks (or subnets), then a gateway must be configured on both
platforms. Check:
NMMGR Path = @NETXPORT.NI.<niname>.INTERNET
Reserved Server Requirement.
The network configuration files that allow Network Services to manage the
Resource Sharing/iX have also changed, and are updated during the
installation of the product. The JCONFJOB.NET.SYS job updates the
appropriate configuration files and adds a reserved server that is
required for this enhancement. This should be noted in the event that a
custom job or UDC explicitly sets the reserved server pool with a value
of zero.
NOTE Please update any job, UDC, or command file that might prevent at
least one reserved server from being allocated.
LOOP Network Interface Name.
Make sure the "LOOP" network interface is started along with the other
network interfaces used by the Network Transport on your 3000 system.
The "LOOP" network interface provides loopback functionality needed by
the new NetBIOS name resolution, so it will work with TCP/IP in stream
mode.
For example, a common sequence for starting the network is the following:
:NETCONTROL START;NET=LOOP
:NETCONTROL START;NET=LAN1
:NSCONTROL START
Client Networking Information
The Resource Sharing server now supports the connection of clients with
supported versions of Microsoft LAN Manager and Microsoft Windows for
Workgroups software using the industry standard TCP/IP connection and
communication method (stream mode). Please note that Microsoft Windows
for Workgroups requires a TCP/IP protocol driver to be installed, which
is not included with the WfW software.
The HP PC NS/ARPA Services (J2246A) product is no longer required for a
Microsoft LAN Manager client to connect to a Resource Sharing/iX A.02.00
host server, but can still be used if desired.
NOTE Note that other PC client software (such as PC Backup) may still
require functionality provided by the HP PC NS/ARPA Services. For
more information, refer to that product's user guide and to the HP
PC Network Services User Guide (J2246-90003).
Microsoft LAN Manager Client Software.
The Resource Sharing/iX host server supports connections by the Microsoft
LAN Manager network client software product. It is strongly recommended
that version 2.2b of this networking software be installed on the client
PCs. Please note that Microsoft directly supports the client software.
How To Obtain Microsoft LAN Manager Client Software.
NOTE The general Microsoft support phone number in the USA is (800)
426-9400. Please note that this information can be changed at the
discretion of Microsoft's support organization.
This will only be the LAN Manager version 2.2a client. The LAN
Manager 2.2b patch should be obtained through either Internet or
Compuserve or by contacting Microsoft at their sales and support
phone number.
There are at least three methods to obtain the recommended version of
Microsoft LAN Manager version 2.2b Client software:
Download files from Internet.
To Get LM 2.2 client software:
1. Anonymous ftp to ftp.microsoft.com (IP address=131.107.1.11).
2. Go to bussys/MSclient/dos and go to either 35 or 525 depending on
whether you want to copy to 3.5-inch media or 5.25-inch media.
3. Copy files to your local machine.
4. Follow instructions for installation.
To Get LM 2.2b patch software for client:
1. Go to bussys/lanman/public/fixes.
2. Copy any readme files and follow instructions.
3. Copy file to your local machine.
4. Follow instructions for installation.
Download files from Compuserve.
To Get LM 2.2 client software:
1. GO MSCLIENT.
2. Download appropriate files per instructions in forum.
To Get LM 2.2b patch software for client:
1. GO MSNETWORKS.
2. Choose library named MS Info and Index.
3. Choose item called LAN Manager 2.2b patch and download.
Order "Network Client Pack" from Microsoft or retailer.
1. Contact retailer and order product # 2723850V100.
How To Obtain the 16-bit TCP/IP Protocol for Microsoft Windows for.
Workgroups 3.11
If using Windows for Workgroups 3.11, Microsoft has developed a software
protocol that provides TCP/IP (WfW does not include this protocol).
This protocol (WFWTCP.EXE) is available on ftp.microsoft.com in the
bussys/MSclient/WFW directory. Follow the README.TXT instructions that
are included with the protocol software.
When installing the protocol, you must run NETWORK SETUP, choose DRIVERS,
and then choose ADD PROTOCOL (add unlisted). WfW NETWORK SETUP then
tries to load the TCP/IP protocol files from the floppy disk or the
chosen source area. Additional addressing information may be required to
use the TCP/IP protocol.
To make the new protocol active, under NETWORK DRIVERS, the Microsoft
TCP/IP protocol must be set as DEFAULT PROTOCOL.
How To Obtain the 32-Bit TCP/IP Protocol Version for Microsoft Windows.
for Workgroups 3.11
This protocol (WFWT32.EXE) can be obtained from the same ftp server in
the bussys/MSclient/WFW directory. Follow the README.TXT instructions
that are included with the protocol software.
The protocol is installed in the same manner as the 16-bit TCP/IP
protocol; however, this 32-bit implementation is quite different. The
protocol is loaded via virtual drivers where the networking software is
not actually loaded unless the Windows environment is running. The
ADDNAME.EXE utility (and others) are not included, instead the
configuration is done through WfW NETWORK SETUP.
Please note that when accessing hosts that are not on the same subnet
(just as the ADDNAME.EXE utility would have updated LMHOSTS), the ENABLE
LMHOSTS LOOKUP flag in the ADVANCED MICROSOFT TCP/IP CONFIGURATION screen
must be set.
Please contact Microsoft for further information regarding obtaining this
protocol software and obtaining technical support.
Other References
These references are provided for additional information in understanding
this enhancement to Resource Sharing/iX.
* Software Update Notice for Resource Sharing A.02.00 (B1718-90004)
* HP 3000 MPE/iX Installation, Update, and Add-On Manual
(36123-90001)
* Resource Sharing for MPE/iX (B1718-90002)
* HP 3000/iX Network Planning and Configuration Guide (36922-90003)
* HP PC Network Services User Guide (J2246-90003)
* Microsoft LAN Manager User's Guide for MS DOS