(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Setting a Modem to Pulse Dial with MHS
DOCUMENT ID#: FYI.S.MHS65
DATE: 03SEP92
PRODUCT: NetWare MHS
PRODUCT VERSION: All
SUPERSEDES: N/A
SYMPTOM: NA
ISSUE/PROBLEM
How can NetWare MHS be initialized to phone another host in pulse mode?
SOLUTION
NetWare MHS will automatically dial in touch-tone mode. However, it can be set to dial in pulse mode by entering a "P" in front of the remote host phone number in "Routes to Workgroup, Hosts, and Gateways." For example, the phone number string for NHUB would be "P408-428-9600".
FYI: Print Options Supported when Printing from an IBM AIX RS6000 System to NetWare NFS or FLeX/IP
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Print Options Supported when Printing from an IBM AIX RS6000 System to NetWare NFS or FLeX/IP
DOCUMENT ID#: FYI.S.NFS21
DATE: 18AUG92
PRODUCT: NetWare NFS and FLeX/IP
PRODUCT VERSION: NFS v1.2 or above
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
When trying to suppress the banner page from AIX using the lpr "-h" option or lpr "-Nnumber" option from AIX to a NetWare file server running NetWare NFS or FLeX/IP, the banner page cannot be suppressed and multiple copies of the print job are printed.
SOLUTION
AIX RS6000 supports multiple form filter configurations on a per print queue basics. Make sure the spooler setup from AIX to NetWare NFS/FLeX/IP is not using AIXSHORT or AIXLONG filter.
For Novell related printing, it should be configured to use BSDSHORT and BSDLONG filter inside AIX "smit" for print queues reside on a Novell file server.
Check in AIX "smit" the following:
smit->
spooler->
manage local printer subsystem->
local print queue->
change/show characteristics->
select queue from AIX to Netware->
Pathname of Short form filter is "/usr/lpd/bsdshort"
Pathname of Long form filter is "/usr/lpd/bsdlong"
This should take care of interoperability problems between AIX and NetWare printing specifying no banner or multiple print job options.
FYI: Cannot Remove NetWare NFS files after Using HPView Utilities
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cannot Remove NetWare NFS files after Using HPView Utilities
DOCUMENT ID#: FYI.S.NFS22
DATE: 11AUG92
PRODUCT: NetWare NFS
PRODUCT VERSION: NFS v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
After using HPView to drag a directory icon from desktop to the wastebasket bin, the directory cannot be remove by using the UNIX command line "rm" command and it is not accessible from the NetWare workstation.
SOLUTION
HPView creates hard links when deleting directories from within HPView. This can be confirmed using the UNIX "ls -il" command to see if two files have the same inode number.
Because there is a hard link across two directories, try to use UNIX command "unlink" to remove the file from the UNIX client. (For additional information, also see the UNIX manual page for unlink(2))
FYI: MHS Administrator Cannot Enter Directory Manager
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Administrator Cannot Enter Directory Manager
DOCUMENT ID#: FYI.S.MHS60
DATE: 07JUL92
PRODUCT: MHS
PRODUCT VERSION: v1.5N, v1.5CN
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
While logged into the file server as Supervisor or equivalent and invoking MHS, the Directory Manager says "Starting Directory Manager" then returns the user back to the opening MHS window.
SOLUTION
This is a symptom of MHS when too many drives are mapped. Do some MAP DELs until the total number of drives mapped is less than fifteen, this should resolve the problem.
You may also want to create a special user on the fileserver via SYSCON named ADMIN (the same as the default MHS administrator's name), make ADMIN a Supervisor-equivalent, and make sure that ADMIN's login script has the minimum of drives mapped. Then log in as ADMIN for any MHS administrative work and you don't have to worry any more about drive mappings, and the Supervisor login script can retain all the drive mappings necessary for network responsibilities.
FYI: Cardinal 2400 Modem and COM Ports 3 and 4
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cardinal 2400 Modem and COM Ports 3 and 4
DOCUMENT ID#: FYI.S.MHS64
DATE: 05JUL92
PRODUCT: MHS
PRODUCT VERSION: v1.5 Rev B
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
Cardinal 2400 modem is not releasing the line when using Com Ports 3 and 4.
SOLUTION
Switch to Com Ports 1 and 2, and the problem will clear.
FYI: "Can not find NETDIR.TAB" Error Received after Installation
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Can not find NETDIR.TAB" Error Received after Installation
DOCUMENT ID#: FYI.S.MHS63
DATE: 05JUL92
PRODUCT: MHS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: "Can not find NETDIR.TAB"
ISSUE/PROBLEM
When installing MHS, the error message "Can not find NETDIR.TAB" was returned when trying to enter the Directory Manager.
SOLUTION
Correctly setting the environmental variable (MV) solves this problem. It is also a good idea to make sure the total mapped drives on the workstation are less then 15 and that the user has the proper trustee rights.
FYI: Upgrading from MHS 1.1 to MHS 1.5
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Upgrading from MHS 1.1 to MHS 1.5
DOCUMENT ID#: FYI.S.MHS62
DATE: 04JUL92
PRODUCT: MHS
PRODUCT VERSION: v1.1
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the procedure of upgrading from MHS 1.1 to MHS 1.5?
SOLUTION
Customer needs to call 1-800-UPDATE1 to purchase Netware MHS version 1.5.
FYI: NETMGR.QUE Renamed after Upgrade from MHS 1.5 Rev A to MHS 1.5 Rev B
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NETMGR.QUE Renamed after Upgrade from MHS 1.5 Rev A to MHS 1.5 Rev B
DOCUMENT ID#: FYI.S.MHS61
DATE: 04JUL92
PRODUCT: MHS
PRODUCT VERSION: v1.5 Rev B
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
After upgrading from MHS 1.5 Rev A to MHS 1.5 Rev B, all hosts in the Directory Manager's "Routes to Workgroups, Hosts and Gateways" which were added by the customer were no longer in the database. The NETMGR.QUE was renamed to "NETMGR.???" and a new .QUE file was created at about half the size.
SOLUTION
Restore a backup copy of the NETMGR.QUE file. If you don't have one, rename the current .QUE file to .BAC and the .??? to NETMGR.QUE.
FYI: Attachment Types
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Attachment Types
DOCUMENT ID#: FYI.S.MHS59
DATE: 03JUL92
PRODUCT: HSAPI
PRODUCT VERSION: v1.5 (SMF 71)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Companies are requesting vendor specific attachment types to be added to the list in the SMF Programmer's Reference.
SOLUTION
If a company wants specific vendor attachment types, all they need to do is use their attachments; if they want them officially added to the public list in the programmer's reference, then they need to formally advise Novell.
FYI: Running the Directory Manager and a Secondary Transport Server Simultaneously
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Running the Directory Manager and a Secondary Transport Server Simultaneously
DOCUMENT ID#: FYI.S.MHS72
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: "Error reading NETMGR.QUE@147"
"Error reading NETMGR.QUE@148"
ISSUE/PROBLEM
The message"Error reading NETMGR.QUE@147" or "...@148" appears when making changes in the Directory Manager while a secondary transport server is still up and running.
SOLUTION
The Directory Manager will not be run while secondary transport servers are running. The proper procedure is to stop all transport servers then run the Directory Manager.
FYI: MHS and -L Switch
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and -L Switch
DOCUMENT ID#: FYI.S.MHS71
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (Network Edition, all revisions)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Is there a way that the workstation running the Connectivity Manager could be made more secure?
SOLUTION
If MHS is invoked with the "-L" switch (MHS -L), the MHS workstation will be logged off the file server if the Connectivity Manager is exited.
FYI: MHSUSER -X02 Not Deleting Users
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHSUSER -X02 Not Deleting Users
DOCUMENT ID#: FYI.S.MHS70
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (all types)
SUPERSEDES: NA
SYMPTOM: "Status 1: Definition, modification, deletion or verification failed."
ISSUE/PROBLEM
MHSUSER -X02 is not deleting MHS users from the MHS database.
SOLUTION
The documentation for MHSUSER -X02 is not quite correct. The -X02 switch does not delete users. It does remove an application from the list of applications used by a particular user, as long as that application is not the preferred application for that user.
FYI: MHSUSER -X01 and -Y Switch
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHSUSER -X01 and -Y Switch
DOCUMENT ID#: FYI.S.MHS69
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (all types)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How is MHSUSER -X01 used to create new users?
SOLUTION
MHSUSER -X01 should not be used to create new users. Its function is to add to the list of applications used by a pre-existing user.
Note: The documentation for MHSUSER -X01 does not say that the default value for the -Y switch is "also uses." To make the specified application the preferred application for a user, the MHS administrator must specifically add "-Y0" to the MHSUSER command line.
FYI: Running the Directory Manager and a Secondary Transport Server Simultaneously
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Running the Directory Manager and a Secondary Transport Server Simultaneously
DOCUMENT ID#: FYI.S.MHS58
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: "Error reading NETMGR.QUE@147"
"Error reading NETMGR.QUE@148"
ISSUE/PROBLEM
"Error reading NETMGR.QUE@147" or "...@148" when making changes in the Directory Manager while a secondary transport server is still up and running.
SOLUTION
The Directory Manager should not be running while secondary transport servers are running. The proper way is to stop all transport servers then run the Directory Manager.
FYI: MHS and -L Switch
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and -L Switch
DOCUMENT ID#: FYI.S.MHS57
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (Network Edition, all revisions)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
MHS logs itself off the file server rather than go to the DOS prompt when someone manually exits from the Connectivity Manager.
SOLUTION
MHS and the Connectivity Manager should be invoked with the "-L" switch (the complete command is "MHS -L<return>").
FYI: MHSUSER -X02 Not Deleting Users
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHSUSER -X02 Not Deleting Users
DOCUMENT ID#: FYI.S.MHS56
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (all flavors)
SUPERSEDES: NA
SYMPTOM: "Status 1: Definition, modification, deletion or verification failed."
ISSUE/PROBLEM
MHSUSER -X02 is not deleting MHS users from the MHS database.
SOLUTION
The documentation for MHSUSER -X02 is not quite correct. The -X02 switch does not delete users. It does remove an application from the list of applications used by a particular user, as long as that application is not the preferred application for that user.
FYI: MHSUSER -X01 and -Y Switch
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHSUSER -X01 and -Y Switch
DOCUMENT ID#: FYI.S.MHS55
DATE: 29JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5 (all flavors)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How is MHSUSER -X01 used to create new users?
SOLUTION
MHSUSER -X01 should not be used to create new users. Its function is to add to the list of applications used by a pre-existing user.
Note that the documentation for MHSUSER -X01 does not say that the default value for the -Y switch is "also uses". To make the specified application the preferred application for a user, the MHS administrator must specifically add "-Y0" to the MHSUSER command line.
FYI: NFS RPC/UDP Packets Dropped
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NFS RPC/UDP Packets Dropped
DOCUMENT ID#: FYI.S.NFS20
DATE: 24JUN92
PRODUCT: Netware NFS
PRODUCT VERSION: NFS v1.2
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
The RPC/UDP problem has reappeared in several instances with NFS 1.2.
SOLUTION
The first thing to check is the LAN STATISTICS for the LAN CARD being used. If it is a 8- or 16-bit card it is possible that the card has reached its maximum saturation level for packet receives and transmits.
When checking the LAN STATISTICS, check the ENQUEUEDSENDCOUNT to see if a high percentage of the total number of packets sent or received. The driver has to buffer the packets if it is too busy to send the packet. (This stat is similar to the TX QUEUE D because adapter TXing for a NE3200. It is recommended that you upgrade the card to the next level card for better performance. For instance NE2000 to NE3200.)
FYI: PLPD Mapping Mode Configuration
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PLPD Mapping Mode Configuration
DOCUMENT ID#: FYI.S.NFS16
DATE: 24JUN92
PRODUCT: NFS FLeX/IP
PRODUCT VERSION: NFS v1.2 FLeX/IP v1.0
SUPERSEDES: NA
SYMPTOM: When trying to use one of the mapping modes in PLPD users get error to update mapping mode.
ISSUE/PROBLEM
When using PLPD to print from UNIX to NetWare it requires that the admin sets up a mapping of UNIX user to NetWare user table. At initial setup the table defaults to ALL CLIENTS use same NETWARE Account.
This mapping mode has no NetWare account defined initially. If an ADMIN decides to use one of the other two mapping modes first like SETUP TABLE or USE CLIENT Username as NetWare Username, then a problem can arise in two scenario's:
1. Mapping mode is setup to the third option of USE CLIENT Username as NetWare Username. This actually states that if the UNIX client has a NetWare account with same name then use that account otherwise default to what was set in the first mapping mode. If nothing was set for the first mapping mode then it will error with:
DIAG: an invalid username, check your username mapping mode.
2. Mapping mode is setup to second option of SETUP TABLE. If a UNIX client prints and there is a one to one mapping, then it will use that NetWare account otherwise default to the first option. Again if nothing is setup for first option then the above error will happen.
The best scenario is at initial setup, pick the first option of mapping mode and assign a NetWare account to that mode. Update the mapping mode to use first option and then pick the other option that you want like All clients use same NetWare account. Load PLPD and everything should work.
FYI: Count Number in Connectivity Manager
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Count Number in Connectivity Manager
DOCUMENT ID#: FYI.S.MHS68
DATE: 24JUN92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM::
ISSUE/PROBLEM
In the Connectivity Manager option for "Connect to Another Host", a count number and time is displayed in the reachable hosts list. What do these numbers refer to?
SOLUTION
The Reachable Host table displays the following information:
Host => host that you wish to connect to
Type => the host type
Count => total number of 128 byte blocks of data to be transferred
Time => estimated time to transfer queued messages
Similar information is displayed in the MHS Connection Activities screen of the Connectivity Manager as it connects to an asynchronous host. In this screen the following information about the outgoing messages and attachments are displayed:
Coms => number of messages to be transferred
Atts => number of attachments to be transferred
Bytes => total number of bytes to be transferred
Count => number of 128 bytes blocks to be transferred
Time => estimated time to transfer message and attachments
Note that this information is incorrectly stated in the MHS manual on pages 5 to 7.
FYI: Count Number in Connectivity Manager
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Count Number in Connectivity Manager
DOCUMENT ID#: FYI.S.MHS54
DATE: 24JUN92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
In the Connectivity Manager option for "Connect to Another Host", a count number and time is displayed in the reachable hosts list. What do these numbers refer to?
SOLUTION
The Reachable Host table displays the following information:
Host => host that you wish to connect to
Type => the host type
Count => total number of 128 byte blocks of data to be transferred
Time => estimated time to transfer queued messages
Similar information is displayed in the MHS Connection Activities screen of the Connectivity Manager as it connects to an asynchronous host. In this screen the following information about the outgoing messages and attachments are displayed:
Coms => number of messages to be transferred
Atts => number of attachments to be transferred
Bytes => total number of bytes to be transferred
Count => number of 128 bytes blocks to be transferred
Time => estimated time to transfer message and attachments
Note that this information is incorrectly stated in the MHS manual page 5-7.
FYI: Burst Mode Shell in WINDOWS.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Burst Mode Shell in WINDOWS.
DOCUMENT ID#: FYI.S.MPR3
DATE: 19JUN92
PRODUCT: MPR
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM:
ISSUE/PROBLEM
Interoperability of BURST MODE shell in WINDOWS
SOLUTION
The new release of Burst Mode shell (BNETX.COM for the workstation) may not work reliably with WINDOWS. This problem has been noted and is being looked into.
FYI: MHS 1.5 Rev A and PATCH.COM
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS 1.5 Rev A and PATCH.COM
DOCUMENT ID#: FYI.S.MHS67
DATE: 19JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5N Rev A, v1.5P Rev A
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Hosts running MHS 1.5N Rev A and using the latest modem drivers obtained from the file MHSMDM.ZIP (NetWire) are unable to connect asynchronously to other hosts. The modem driver installed in both the MHS Host Setup and Transport Server menus are correct for the type of modem being used. Default speed and speed sensing variables are set correctly.
SOLUTION
Before using the new drivers for the first time on MHS hosts running 1.5N Rev A or 1.5P Rev A, PATCH.COM must be run. Copy the *.LOG and *.DEF files from MHSMDM.ZIP into the MHS\SYS subdirectory, then set MV and run PATCH.COM. Next run MHS and redeclare the modem driver in the Host Setup and Transport Server menus. PATCH.COM only needs to be run once.
FYI: MHS 1.5 Rev A and Patch.Com
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS 1.5 Rev A and Patch.Com
DOCUMENT ID#: FYI.S.MHS53
DATE: 19JUN92
PRODUCT: MHS
PRODUCT VERSION: v1.5N Rev A, v1.5P Rev A
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Hosts running MHS 1.5N Rev A and using the latest modem drivers obtained from the self-extracting file MHSMDM.EXE, are unable to connect asynchronously to other hosts. The modem driver installed in both the MHS Host Setup and Transport Server menus is correct for the type of modem being used. Default speed and speed sensing variables are set correctly.
SOLUTION
Before using the new drivers for the first time on MHS hosts running 1.5N Rev A or 1.5P Rev A, PATCH.COM must be run. After running MHSMDM.EXE, copy the *.log and *.def files into the MHS\SYS subdirectory, then set MV and run PATCH.COM. Next run MHS and redeclare the modem driver in the Host Setup and Transport Server menus. PATCH.COM, a file created when MHSMDM.EXE is run, needs only be run once after the *.log and *.def files have been copied into the MHS\SYS subdirectory.
FYI: Error Code 2 Returned from SMFSEND
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Code 2 Returned from SMFSEND
DOCUMENT ID#: FYI.S.MHS66
DATE: 18JUN92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: "Errorlevel return code 2"
ISSUE/PROBLEM
After submitting a message to the MHS utility SMFSEND.EXE, an errorlevel code 2 was returned to the gateway.
SOLUTION
Errorlevel code 2 refers to not enough file space for opening of a file. MHS has a minimum requirement of 20 open files. This must be set in CONFIG.SYS as "files=20". If this is already set properly, then increasing the number of open files may resolve the problem. MHS application programmers should reduce the number of simultaneously opened files in their applications and gateways to a minimum.
FYI: Error Code 2 Returned from SMFSEND
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error Code 2 Returned from SMFSEND
DOCUMENT ID#: FYI.S.MHS52
DATE: 18JUN92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: "Errorlevel return code 2"
ISSUE/PROBLEM
After submitting a message to the MHS utility SMFSEND.EXE, an errorlevel code 2 was returned to the gateway.
SOLUTION
Errorlevel code 2 refers to not enough file space for opening of a file. MHS has a minimum requirement of 20 open files. This must be set in CONFIG.SYS as "files=20". If this is already set properly, then increasing the number of open files may resolve the problem. MHS application programmers should reduce the number of simultaneously opened files in their applications and gateways to a minimal number.
FYI: Dialing an MHS Host That Requires the Use of an Extension
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.
TITLE: Dialing an MHS Host That Requires the Use of an Extension
DOCUMENT ID#: FYI.S.MHS39
DATE: 12JUN92
PRODUCT: MHS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How can a host connect to another host asynchronously if the destination host is reached via an automated answering system that prompts the caller for an extension?
SOLUTION
After entering the phone number of the destination host in "Routes to Workgroups, Hosts and Gateways", type two or more commas and then the extension. The number of commas will vary depending on the length of the answering system's announcement.
Some experimentation will be needed to determine the amount of time MHS should pause between when the call is answered and when the extension is dialed.
One example of an entry might be: 1-415-555-1212,,,,,,,,123.
FYI: OS Dependency NLMs for NetWare NFS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: OS Dependency NLMs for NetWare NFS
DOCUMENT ID#: FYI.S.NFS19
DATE: 07JUN92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What are the OS dependency NLMs for NetWare NFS?
SOLUTION
OS (server.exe), clib.nlm, nut.nlm, rpcstub.nlm, tcpip.nlm, stream.nlm, tli.nlm. For product installation, NFS depends on pinstall.nlm & btrieve.nlm.
FYI: Misconfigured Export Path for NetWare NFS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Misconfigured Export Path for NetWare NFS
DOCUMENT ID#: FYI.S.NFS18
DATE: 07JUN92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1 or above
SUPERSEDES: NA
SYMPTOM: NFS clients can mount file system from NetWare NFS, but the UNIX session/window hangs on any NFS operation. Cannot issue a UNIX "ls" or "vi" command.
ISSUE/PROBLEM
Mis-configured NetWare NFS server may cause the NFS server to function partially. You may be able to mount but other NFS operations may fail.
SOLUTION
Make sure exported volume names are speficied correctly. Sample exported volume names "/volumename" and exported directories are "/sys/directoryname" not "/volname/" and "/sys/directoryname/".
FYI: Printing from SCO to NWNFS Using NFS PATCH NFS117.ZIP
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Printing from SCO to NWNFS Using NFS PATCH NFS117.ZIP
DOCUMENT ID#: FYI.S.NFS17
DATE: 07JUN92
PRODUCT: NWNFS & FLEX/IP
PRODUCT VERSION: 1.2 Rev A
SUPERSEDES: NA
SYMPTOM: After applying the NFS117 patch as a print enhancement, still cannot print from an SCO UNIX client to NetWare NFS PLPD.NLM.
ISSUE/PROBLEM
The patch NFS117.ZIP is only a temporary solution that will allow printing from SCO and Interactive clients, to the NetWare PLPD.NLM. The printing *DOES* work but when applying the patch, you need to fully understand what are all the parameters used in "lprcfg" command.
One common mistake being made is using the wrong parameter when they run "lprcfg" on the SCO host.
An example is listed below when setting up printing from a SCO UNIX spooler named "netware" to Novell server "fs" , going thru Novell print queue "nwqueue".
A common mistake is that the last parameter is omitted and the default "/dev/tcp" transport parameter for lprcfg does not apply to SCO host.
SOLUTION
Example:
In SCO UNIX prompt use > lprcfg netware fs nwqueue /dev/inet/tcp
In ISC UNIX prompt use > lprcfg netware fs nwqueue /dev/tcp
FYI: MHS and CCITT X.400
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and CCITT X.400
DOCUMENT ID#: FYI.S.MHS34
DATE: 03JUN92
PRODUCT: MHS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Is NetWare MHS based on a CCITT X.400 standard?
SOLUTION
MHS (Message Handling Service) from Novell, not to be mistaken with the CCITT X.400 MHS (Message Handling Systems), is the defacto standard in the LAN-based messaging world. X.400 is the messaging standard for OSI. Though they both use the same acronym and are messaging standards, they are not the same.
Both are store-and-forward messaging systems. While they use analogous services, the names for those services differ in the two systems.
OSI transport protocols NetWare transport protocols
FYI: Adjusting Modem Speaker Volume
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Adjusting Modem Speaker Volume
DOCUMENT ID#: FYI.S.MHS38
DATE: 02JUN92
PRODUCT: NetWare MHS
PRODUCT VERSION: all versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can the speaker volume of a modem be adjusted or turned off using MHS?
SOLUTION
The speaker volume on a modem can be adjusted using the either the L or M command from the Hayes AT command set. However, not all Hayes compatible modems will implement these two commands.
The L command refers to the loudness to the speaker and can be set to values between 0 and 3. L0 and L1 are low speaker volume, L2 is medium (default), and L3 sets high speaker volume.
The M command sets the speaker to monitor calls. M0 will turn the speaker off completely and no dialing will be audible. M1 turns the speaker on until the carrier is detected and is usually the default modem setting. M2 turns the speaker on at all times. M3 setting turns the speaker on except when dialing and when the remote carrier is detected.
To enter one of the above settings in MHS, the command can be added to the end of the phone number of the remote host in "Routes to Workgroup, Hosts, and Gateways". An example setting to turn the modem speaker off while calling NHUB would be "9W408-426-9 600 M0". Here, "9" will access the telephone line outside the local PBX and "W" waits for a second dial tone. This is followed by the phone number to NHUB, a space, and the "M0" command to turn the modem speaker off at all times.
In addition, some modems have an external switch which controls modem speaker volume.
FYI: MHS and Other Network OS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and Other Network OS
DOCUMENT ID#: FYI.S.MHS17
DATE: 02JUN92
PRODUCT: MHS
PRODUCT VERSION: NETWORK
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Does MHS work on other Network Operating Systems besides NetWare?
SOLUTION
NetWare MHS (Network Edition), owned and sold by Novell although originally created by Action Technologies Inc, has an IPX/NetWare requirement.
Anyone who desires the Network Edition of MHS on a different platform should contact Action Technologies at 510-521-6190 and inquire what other platforms are supported. Action provides MHS on non-NetWare platforms.
Addendum: For those situations where the functionality of the Network Edition of MHS is not required, NetWare MHS (Personal Edition) might be the solution.
FYI: MHS Multiport Support Version Availability
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Multiport Support Version Availability
DOCUMENT ID#: FYI.S.MHS37
DATE: 01JUN92
PRODUCT: HS
PRODUCT VERSION: 1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Is there any MHS v1.5 multiport support version available to work with the same MHS host? Can it handle four Com ports (with four modems) for communication service?
SOLUTION
MHS v1.5 doesn't support this; NetWare Global Messaging will achieve this by supporting serial I/O adapters.
FYI: Automating MHS login with AUTOEXEC.BAT
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Automating MHS login with AUTOEXEC.BAT
DOCUMENT ID#: FYI.S.MHS16
DATE: 29MAY92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When automating the startup of MHS in AUTOEXEC.BAT, MHS does not automatically start the Connectivity Manager. Instead, it asks for the administrative user's ID and password.
SOLUTION
There are several things to check. First, verify that there are no more than 16 drive mappings, including local, network, and search drives. Secondly, the NetWare user and MHS administrator both should have the same user name. For example, if the MHS administrator is ADMIN, you should log into the file server as ADMIN as well. If they are different, the environmental variables USR and PWD need to be set to the user ID and password for the MHS administrative user.
Finally, if the above suggestions fail to resolve the login problems, you may need to clear the keyboard buffer before starting MHS. This can be done using DEBUG to create a program. The following outlines the creation of such a file, CLRBUFF.COM:
DEBUG CLRBUFF.COM <-- you type
File not found <-- response from debug
-a100 <-- debug prompts '-', you type 'a100'
xxxx:0100 MOV AH,1 <-- type instruction beginning with MOV
xxxx:0102 INT 16 <-- this checks if a key is in the buffer
xxxx:0104 JZ 10C <-- no key, jump to end of program
xxxx:0106 MOV AH,0 <-- key found, clear it out
xxxx:0108 INT 16
xxxx:010A JMP 100 <-- continue checking buffer
xxxx:010C INT 20 <-- terminate
xxxx:010E <-- press ENTER to blank line
-rcx
CX 0000
:E <-- E is the size of this program in hex
-w <-- write the file to disk
-q <-- quit DEBUG
Once the file is created, add the command CLRBUFF in the AUTOEXEC.BAT file prior to the MHS call.
FYI: Stats file problem
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Stats file problem
DOCUMENT ID#: FYI.S.MHS14
DATE: 28MAY92
PRODUCT: MHS
PRODUCT VERSION: v.15
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Incorrect entries are appearing in the stats file <HOSTNAME.R00> when one message is sent to a number of users at a remote host in SMF v70 format, ie a message is addressed to user1@host1, user2@host1, user3@host1, user4@host1, user5@host1. The Transmission Activities screen shows the message being routed to the five users. The <HOSTNAME.R00> file contains five entries, however the first four entries list user5 as the recipient and the fifth entry lists user1 as the recipient. Users 2, 3 and 4 are not named in any entry even though they received the message.
SOLUTION
This is an MHS bug; PMR (Product Modification Request) 5467 has been created and submitted to engineering to be addressed.
FYI: Operator assisted calls using MHS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Operator assisted calls using MHS
DOCUMENT ID#: FYI.S.MHS13
DATE: 21MAY92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How to run MHS when operator assistance is needed to make the call to a remote host.
SOLUTION
Use the HAYESMAN driver. Invoke the Connectivity Manager. When MHS reaches the point of dialing out, it will halt and prompt the user to dial the number. Using a phone connected to the modem, dial the operator and have them connect through. Once the receiving host answers and you hear the synch tones, press <ENTER> to continue the MHS connection sequence, then hang up the phone. MHS will establish the connection and exchange messages.
FYI: NULMODEM and "phone number"
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NULMODEM and "phone number"
DOCUMENT ID#: FYI.S.MHS12
DATE: 21MAY92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
In the Directory Manager, under "Routes to Workgroups, Hosts and Gateways", if the host type defined is a HUB (a host that this host phones), a phone number needs to be supplied. If there is no phone number needed (ie: using a T1 line or operator assisted call), this field still must be filled.
SOLUTION
It is recommended that a "," be used.
FYI: "Missing Signature" Error Message from MHS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Missing Signature" Error Message from MHS
DOCUMENT ID#: FYI.S.MHS11
DATE: 18MAY92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: "Missing Signature"
ISSUE/PROBLEM
MHS keeps generating error messages reporting a "Missing Signature", yet the application is submitting a legal message to MHS. In some cases, the message may even be delivered.
SOLUTION
Check that there is sufficient space available on the disk/volume/drive where MHS and MHS gateways are installed. Also, verify that there is sufficient account balance for the user running both the Connectivity Manager and any gateways that might be installed.
FYI: Recalculates checksum after editing ping packets.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Recalculates checksum after editing ping packets.
DOCUMENT ID#: FYI.S.LANZ1
DATE: 11MAY92
PRODUCT: LANalyzer
PRODUCT VERSION: 3.11
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
After capturing a ping packet and editing the TCP address, will the LANZ recalculate the checksum so you can retransmit the packet?
SOLUTION
Yes, if you edit the packet correctly the LANZ will recalculate the checksum.
FYI: Unresolved references to toolkit functions
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unresolved references to toolkit functions
DOCUMENT ID#: FYI.S.LWP6
DATE: 07MAY92
PRODUCT: LWPD Toolkit
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The linker can not find our toolkit functions when making a Windows application:
Verify: #defined WINDOWS. This line: '-D WINDOWS' should be added to your compile line.
FYI: Slow performance during large file transfer operations
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Slow performance during large file transfer operations
DOCUMENT ID#: FYI.S.TCP15
DATE: 01MAY92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When file sizes are smaller, file transfers or copy operations appear to work fine. But when large file sizes are involved, the server appears to hang up.
SOLUTION
The problem could be with the LAN driver. One way of verifying this is to check the following field in TCPCON. LOAD TCPCON ->, Select Statistics ->, Select IP Statistics ->, View ipReasmFails ->.
If this value increases as the operation is being performed, then the problem is with the LAN driver. (Note: This does not imply that EVERY time there is a driver problem, ipReasmFails will increase)
FYI: Unable to connect from old HP 3000's/9000's to NetWare TCP/IP
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to connect from old HP 3000's/9000's to NetWare TCP/IP
DOCUMENT ID#: FYI.S.TCP14
DATE: 01MAY92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Addresses and configuration all appear ok, but NetWare TCP/IP can not connect to the HP machines, but is able to connect to other TCP/IP nodes.
SOLUTION
Old versions of HP never age out their ARP cache. Hence, if an IP address was assigned once to any machine, then the IP address is associated with the MAC address of that machine. If the network is reconfigured and IP addresses are reassigned, the HP still maintains the old ARP cache. The only solution is to reboot the HP.
FYI: Subnet zero IP addressing is not supported
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Subnet zero IP addressing is not supported
DOCUMENT ID#: FYI.S.TCP13
DATE: 01MAY92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Subnet zero cannot be used while assigning subnet addresses.
SOLUTION
Subnet zero cannot be assigned as the address to any segment. For example, when a network address of 89.0.0.0 is subnetworked with a subnet mask of ff.ff.0.0, the address of 89.0 should not be assigned as network address to any segment of the network.
FYI: TCP/IP connectivity from HP to the NetWare 3.11 server
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TCP/IP connectivity from HP to the NetWare 3.11 server
DOCUMENT ID#: FYI.S.TCP12
DATE: 01MAY92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
TCP/IP configuration appears to be fine on both the NetWare server as well as the HP, but the HP is unable to ping the NetWare server.
SOLUTION
Verify that HP has been configured for ARP as well. It may be configured to only do Probe Network Services ( proprietary to HP). NOTE: NetWare 3.11 TCP/IP only supports ARP and not PROBE or PROXY ARP.
FYI: TCPIP IPTUNNELLING
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TCPIP IPTUNNELLING
DOCUMENT ID#: FYI.S.TCP11
DATE: 01MAY92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How does IPTunnel communicate SAP information between multiple NetWare servers? The concern about IPTunnel is the amount of broadcast packets on the Internet.
SOLUTION
IPTunnel uses the concept of "peer". The only traffic between IP tunnel peers is point to point "unicast" traffic. SAP updates are sent directly to "peers" and not as broadcast on the Internet.
FYI: PCNFS Authentication
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PCNFS Authentication
DOCUMENT ID#: FYI.S.NFS15
DATE: 01MAY92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1, v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can the authentication daemon provided by the PCNFS vendor be compiled and run on a NetWare NFS server?
SOLUTION
The authentication daemon (PCNFSD) source code provided by other vendors can be compiled and run on UNIX machines only, and cannot be compiled on a NetWare platform.
FYI: Presence of negative inode numbers
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Presence of negative inode numbers
DOCUMENT ID#: FYI.S.NFS14
DATE: 01MAY92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Some NFS operations such as "tar" or "df" fail when performed by an NFS client on a directory that is mounted from NetWare NFS.
SOLUTION
Use NetWare NFS 1.2. In NFS 1.1, the inode number is an 8-bit generation number. When the number of files increase in a directory and this generation number becomes greater than 127, negative inode numbers can be seen.
FYI: Recursion with NetWare NFS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Recursion with NetWare NFS
DOCUMENT ID#: FYI.S.NFS13
DATE: 01MAY92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1, v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When recursion is set to yes in the "Change File Information" within NFSADMIN, the next time access is made it still appears as no.
SOLUTION
The default for recursion is always no. Hence, even when it is set to yes, it will revert to the default value of no the next time access is made. However, the operation that was performed at the time the option was set to yes will allow recursion.
FYI: NetWare FTP Date and Time Discrepancies
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: NetWare FTP Date and Time Discrepancies
DOCUMENT ID#: FYI.S.NFS12
DATE: 01MAY92
PRODUCT: NetWare NFS (FTPSERV)
PRODUCT VERSION: v1.1, v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
During ftp from a client, if the command "DIR" is issued, the files and directories reflect the time and date different from "DIR" executed from a NetWare workstation on the same directory.
Connecting to NetWare 3.11 fileserver via FTP and doing a DIR (directory listing) will show a different date and time for files and directories, than that reflected by a NetWare workstation listing the same files or directories via IPX.
SOLUTION:
FTPSERV reflects the creation time, as opposed to the Information last accessed time reflected in the other case.
FYI: PLPD error message when using POSTSCRIPT print filter
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PLPD error message when using POSTSCRIPT print filter
Print jobs sent from a UNIX lp client to NetWare never showed up in PCONSOLE, when trying to print a large postscript file from applications that generate postscript output. The error message that is returned to the NetWare NFS error message screen is:
in procedure StartQueueJob :hostname : username : filename :E1
SOLUTION
In PLPDCFG verify that user mapping mode is set to a particular NetWare user (eg. user guest). Make sure the disk quota/volume restriction in SYSCON for this user has not reached its allocated diskspace. If disk quota/disk restriction has reached, print job will not be queued up by NetWare NFS PLPD.
FYI: Running MHS on Netware Lite
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Running MHS on Netware Lite
DOCUMENT ID#: FYI.S.MHS33
DATE: 30APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5, all releases
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can MHS run on NetWare Lite?
SOLUTION
NetWare MHS v1.5N is not designed to work on NetWare Lite. However, MHS v1.5P, which does support multiple users, can be installed on one of the workstations and used to connect asynchronously to other hosts. Users will need to access this workstation to send and receive messages as well as run the Connectivity Manager.
NOTE: Using MHS 1.5P on NetWare Lite is unsupported. Users can implement the above solution at their own risk.
FYI: RESOLV.CFG entries must be in lower case
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: RESOLV.CFG entries must be in lower case
DOCUMENT ID#: FYI.S.LWP4
DATE: 30APR92
PRODUCT: LWP for DOS and OS/2
PRODUCT VERSION: 4.01 DOS, 3.0 OS/2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
If the RESOLV.CFG domain or nameserver entries are in caps, the DNS does not work.
SOLUTION
Use lower case characters. Note that the example on page 3-5 of the Administrator's Guide shows caps, is incorrect.
FYI: PLPD error when using "Use Client Username ..." mapping mode
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PLPD error when using "Use Client Username ..." mapping mode
DOCUMENT ID#: FYI.S.NFS10
DATE: 29APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.2
SUPERSEDES: NA
SYMPTOM: PLPD-Error: plpd: An error occurred in procedure ...
ISSUE/PROBLEM
PLPD error when using one of the three user mapping mode (use client name). The following error message is displayed in NFS Error message screen when selecting "Use Client Username as NetWare Username" in PLPDCFG when printing from UNIX-to-NetWare:
PLPD-Error: plpd: An error occurred in procedure CreateQueueJobAndFile : username: DIAG: probably user has no access to the print queue
SOLUTION
Make sure that the NetWare user belongs to group EVERYONE.
FYI: MHS Displays "Q" for Host Route/Queue
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Displays "Q" for Host Route/Queue
DOCUMENT ID#: FYI.S.MHS32
DATE: 29APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
In the "MHS Utilities", "List all Host Routes and Queues" display, a host may have the value "Q" under the "Act" column heading. What does the "Q" mean? It is not documented in the MHS Installation manual.
SOLUTION
"Q" is a valid value for this field. It signifies that there is queued mail waiting for a host that telephones this host.
FYI: French and German installation bug
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: French and German installation bug
DOCUMENT ID#: FYI.S.LTRN1
DATE: 29APR92
PRODUCT: LANtern Services Manager French and German
PRODUCT VERSION: 1.3B
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When installing the LSM French or German versions, C:\LSM was placed between the SET PATH words instead of after the equal sign.
SOLUTION
The install script works correctly if you have PATH=, but has a problem if you have SET PATH=. Moving the C:\XLN after the equal sign will resolve the problem.
FYI: MHS Connectivity Manager Hangs
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Connectivity Manager Hangs
DOCUMENT ID#: FYI.S.MHS35
DATE: 27APR92
PRODUCT: MHS
PRODUCT VERSION: 1.5N, Rev A and Rev B
SUPERSEDES: NA
SYMPTOM: "Waiting for incoming calls"
ISSUE/PROBLEM
A user goes into the Directory Manager and Transport Server Setup screens and configures MHS. However, when he starts the MHS Connectivity Manager, the message "Waiting for incoming calls" is displayed and then the MHS host hangs.
SOLUTION
The interrupt on the Network Interface Card in the MHS host was conflicting with the interrupt for the COM port declared in MHS. If another COM port using a different interrupt is chosen, or if the Network Interface Card is reconfigured to use a different interrupt, the problem should be corrected.
FYI: IP Loopback Address
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IP Loopback Address
DOCUMENT ID#: FYI.S.LWP24
DATE: 27APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Unable to telnet to an RS6000, but can successfully ping it.
SOLUTION
The IP address of the RS6000 began with 127 (127.XXX.XXX.XXX). This IP address is reserved for loopback, changing it resolved the problem.
FYI: Socket functions use of DOS interrupt 21
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Socket functions use of DOS interrupt 21
DOCUMENT ID#: FYI.S.LWP20
DATE: 25APR92
PRODUCT: LWP Toolkit for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Do any of the socket API functions use DOS interrupt 21?
SOLUTION
Only the host database functions (i.e., gethostbyname(), getnetbyname(), etc.), use DOS interrupt 21.
FYI: SEAL.EXE Missing from MHS 1.5
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: SEAL.EXE Missing from MHS 1.5
DOCUMENT ID#: FYI.S.MHS31
DATE: 24APR92
PRODUCT: NetWare
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When developing to SMF64 but not SMF70, SEAL.EXE is missing from MHS 1.5 and without SEAL.EXE, applications don't work with MHS1.5.
SOLUTION
There are multiple issues involved.
First, the SEALing function is not required by MHS 1.5. The developer may be able to make minor revisions to his application so that it will work more directly with MHS 1.5. The developer should open an MHS API support call (800-NETWARE or 801-429-5588) to discuss this more fully.
Second, the developer should purchase the MHS 1.5 Developer's Kit. This SDK includes four copies of MHS software (2 Network, 2 Personal), the SMF API Programmer's Reference manual, and some MCB software utilities. These MCB utilities include NSEAL.EXE for use with Network MHS and PSEAL.EXE for use with Personal MHS. The MHS SDK can be ordered through MHS Developer Relations (408-473-8989).
FYI: R-Utilities hanging when executed in batch file
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: R-Utilities hanging when executed in batch file
DOCUMENT ID#: FYI.S.LWP19
DATE: 24APR92
PRODUCT: LWPD
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Difficulty executing R-Utilities from within a batch file; system hangs when trying to connect to the remote host.
SOLUTION
Insert a few "WAIT" statements in order that the remote host is not caught in a tight loop, executing the utilities.
FYI: PLPD.NLM delays releasing TCP/IP connection for 15 seconds
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: PLPD.NLM delays releasing TCP/IP connection for 15 seconds
DOCUMENT ID#: FYI.S.NFS9
DATE: 23APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When printing a job from UNIX to NWNFS PLPD, FILTER.NLM takes extra time in processing the print job and holds the TCP/IP connection for an extra 15 seconds before resetting the port and closing the connection.
SOLUTION
Verify that there is at least one entry imported into the PRINTDEF database from the NetWare workstation, by making sure the file NET$PRN.DAT exists in the SYS:PUBLIC directory. If this is not done, FILTER.NLM will retry to open this file resulting in an extra delay in printing.
FYI: IBM AIX National Language Support
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: IBM AIX National Language Support
DOCUMENT ID#: FYI.S.LWP18
DATE: 23APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
LWP National Language Support (NLS) in Host Presenter and TNVT220 will not work with the IBM AIX operating system.
SOLUTION
AIX does not use the DEC VT220 code sets for NLS that Novell supports, but rather, something called "ISO-Latin-1", as well as code sets based on the IBM PC 850 code set. Support for ISO-Latin-1 will be available in LWP v4.1.
FYI: No documentation at this time for PC-Names assigned to nodes detected by LSM
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: No documentation at this time for PC-Names assigned to nodes detected by LSM
DOCUMENT ID#: FYI.S.LTRN3
DATE: 23APR92
PRODUCT: LSM
PRODUCT VERSION: 1.3b
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When LSM was installed and went to detect new stations on the segment, the PC-Names of certain machines equated to the names in the HOSTS file. This information cannot be found in the manuals.
SOLUTION
This is an undocumented feature. The LSM will assign the PC-Name to the station if the station is running TCPIP and the PC-Name is in the local XLN\TCP\HOSTS file on the workstation running the LSM.
FYI: System V - ROUTE ADD command
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: System V - ROUTE ADD command
DOCUMENT ID#: FYI.S.TCP10
DATE: 22APR92
PRODUCT: NetWare TCP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The "ROUTE ADD destination command" on the Data General System V UNIX system will appear in the routing table (netstat -r), but no routing will take place.
SOLUTION
A metric value has to be added to the end of the ROUTE ADD command, or the default of zero is assumed. With a value of zero, no routing will take place. The value needs to be a value of one or greater.
FYI: Number of users limited
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Number of users limited
DOCUMENT ID#: FYI.S.MHS30
DATE: 22APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When pgraded DaVinci from 1.7 to 2.0 and MHS1.11 to 1.5 where is the limited user amount was coming from.
SOLUTION
DaVinci has a user limitation; it will allow for the user mailboxes but will only recognize the first 10, 20, 50, or 100 users in the "Users at This Host" list.
FYI: Re-register DaVinci eMail
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Re-register DaVinci eMail
DOCUMENT ID#: FYI.S.MHS29
DATE: 22APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Using MHSUSER -x10 client was not able to re-register an earlier version of DaVinci. The error -8 "unable to modify application" was displayed.
SOLUTION
Go to the EMAIL\ADMIN directory and run DVS_MHS. When it asks for the MHS path, this MUST BE with a drive letter and not fileserver/volume:. This might be M:\ or M:\MHS; if it doesn't work one way, the message, "can't find NETDIR.TAB" will appear; then try the other format.
FYI: Email message "cannot open header missing"
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Email message "cannot open header missing"
DOCUMENT ID#: FYI.S.MHS28
DATE: 22APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: Cannot open; Header missing
ISSUE/PROBLEM
When trying to run DaVinci eMail, the message "cannot open; header missing" appears.
SOLUTION
This is a common problem in DaVinci 2.0d and is fixed in rev H. Call the DaVinci bulletin board at 919-881-4342 and download two files; EMAILDOS.BBB (pswd=alex), a 200K file and REPORTFM.TXT (no password). If there is a problem with the patch, use the .TXT file form and fax it to DaVinci. This patch corrects 65% of the major bugs. Client MUST be on DaVinci 2.0 Rev D for the patch to work.
FYI: TNVT220 "hot key"
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TNVT220 "hot key"
DOCUMENT ID#: FYI.S.LWP22
DATE: 22APR92
PRODUCT: LWP
PRODUCT VERSION: 4.x
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can you "hot key" from a TNVT220 session to a WordPerfect application and return?
SOLUTION
Use Alt-D to reach the command line prompt (C:\>) and launch the application, when finished go back to the C:\> prompt and type "exit" to return to the terminal session.
FYI: FTP and "Lost Connection - Open: I/O Error"
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: FTP and "Lost Connection - Open: I/O Error"
DOCUMENT ID#: FYI.S.LWP16
DATE: 22APR92
PRODUCT: LWPD
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: "Lost Connection - Open: I/O Error"
ISSUE/PROBLEM
Received the following error when trying to FTP to a SCO Unix host:
Lost Connection - Open: I/O Error
Telnet to the host works fine.
SOLUTION
The FTP Daemon file was corrupted on the Unix host. Replace the file and it will work.
FYI: DOS loading order
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: DOS loading order
DOCUMENT ID#: FYI.S.LTRN2
DATE: 22APR92
PRODUCT: LWPD and LSM
PRODUCT VERSION: NA
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When trying to load LWP on a PC with LSM, the LWP install fails.
SOLUTION
LWP should be installed before installing the LSM when both applications are going to reside on the same PC. This happens because the LWP sees the \XLN subdirectory created by the LSM software.
FYI: Toolkit Header problems
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Toolkit Header problems
DOCUMENT ID#: FYI.S.OS23
DATE: 21APR92
PRODUCT: LWP Toolkit for OS/2
PRODUCT VERSION: 3.0 Beta II
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Several minor Toolkit header and documentation problems.
1. Definition of res_mkquery in BSD43.H contains a variable named "class". This is a reserved word in C++.
2. The symbol RES_DEFAULT in RESOLV.H is also defined in the MS-C 6.0 PMGPI.H file.
3. The symbols u_char, u_short, and u_long are referenced in the header file NETINET\IP.h, but are not defined anywhere.
4. On page 5-25 of the Socket API manual, the "argp" argument to the ioctl function is defined as int*. It should be char*.
SOLUTION
NA
FYI: MHS modem drivers that aren't supported
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS modem drivers that aren't supported
DOCUMENT ID#: FYI.S.MHS27
DATE: 21APR92
PRODUCT: NetWare MHS
PRODUCT VERSION:
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Customer wants Novell to provide the information necessary so he may modify/create modem drivers.
SOLUTION
Novell does not support editing of the modem driver files (*.LOG and *.DEF files). This is not included in the MHS API.
FYI: Registering host with NHUB
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Registering host with NHUB
DOCUMENT ID#: FYI.S.MHS26
DATE: 21APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: (all versions, all releases)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
How to register my host with NHUB, Novell's MHS hub service?
SOLUTION
To register an MHS host with NHUB via email or fax:
Send email to: "hubadmin@nhub",
Fax info to: "hubadmin @ 408-433-0775".
Include the following information:
MHS host name,
workgroup name,
MHS administrator's name,
contact person's name,
contact's email username,
company name & address,
voice phone number, and
fax phone number.
FYI: Memory allocation error
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
Memory allocation errors have been fixed in Rev B. The Rev B upgrade (V15B-N.EXE) is available on Netwire.
FYI: Using LWP Toolkit with Watcom C
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Using LWP Toolkit with Watcom C
DOCUMENT ID#: FYI.S.LWP13
DATE: 20APR92
PRODUCT: LWP Toolkit for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can LWP Toolkit be used with Watcom C?
SOLUTION
In Windows, yes. The Watcom C program can call our socket functions just as it would any other Windows DLL.
In DOS, no. Our libraries are not compatible with the Watcom compiler.
FYI: LAN WorkPlace for OS/2 v3.0 and OS/2 Requestor v1.3
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: LAN WorkPlace for OS/2 v3.0 and OS/2 Requestor v1.3
DOCUMENT ID#: FYI.S.OS22
DATE: 17APR92
PRODUCT: LWP for OS/2
PRODUCT VERSION: 3.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
A problem exists with the new release of OS/2 v2.0 and the Netware OS/2 Requestor v1.3. Numerous TRAP 000D and TRAP 0003 errors are encountered.
SOLUTION
Install the latest Requester v2.0.
FYI: Bypassing Host Connections when Starting Connectivity Manager
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Bypassing Host Connections when Starting Connectivity Manager
DOCUMENT ID#: FYI.S.MHS24
DATE: 17APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Under certain circumstances, it may be desired that the Connectivity Manager connect to just one host rather than to all possible hosts.
SOLUTION
After choosing the Connectivity Manager option from the main menu, hitting the return/enter key four (4) times before the Connectivity Manager has begun to process any messages will bring up the Connectivity Manager's menu and the desired host may be selected.
FYI: Sending 0xff through a telnet connection
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Sending 0xff through a telnet connection
DOCUMENT ID#: FYI.S.LWP10
DATE: 17APR92
PRODUCT: LWP Toolkit for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
A custom program was written to transmit binary files through a telnet connection. All data transferred properly except for 0xff; for every 0xff sent, two showed up in the LANZ trace.
SOLUTION
That is the way telnet works. 0xff is a control value in telnet. Therefore, to send 0xff as data, telnet doubles it up.
FYI: Purpose of the VTCPIP.386 driver
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Purpose of the VTCPIP.386 driver
DOCUMENT ID#: FYI.S.LWP9
DATE: 17APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the purpose of the VTCPIP.386 driver?
SOLUTION
This driver enables Windows programs to communicate with the TCP/IP protocol stack. It has two primary functions:
1. It acts as traffic cop for network data going to and from multiple, concurrent Windows programs.
2. It converts network data buffer addresses from DOS format to Windows format, and vice versa.
FYI: Minimum LWP files required for 3rd-party applications
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Minimum LWP files required for 3rd-party applications
DOCUMENT ID#: FYI.S.LWP8
DATE: 17APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What are the minimum LWP files required to run 3rd-party applications over our protocol stack?
SOLUTION
It depends upon the application API (sockets or telnet API) and the program type (DOS or Windows).
All applications require the basic protocol stack (i.e. LSL, the MLID, and TCPIP). Additional required files are:
DOS sockets: none
DOS telnet: telapi
Windows sockets: vtcpip.386, wlibsock.dll
Windows telnet: vtcpip.386, telapi
FYI: Printing from UNIX to Appletalk printers, through NetWare 3.11
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Printing from UNIX to Appletalk printers, through NetWare 3.11
DOCUMENT ID#: FYI.S.NFS8
DATE: 16APR92
PRODUCT: NetWare for NFS and NetWare for MAC
PRODUCT VERSION: NFS-all, MAC-3.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
With NetWare NFS 1.2 and NetWare MAC 3.01, printing from a UNIX workstation to the Appletalk printer can easily be done if the Appletalk printers are on the same NetWare 3.11 server that has NetWare NFS.
If the Appletalk printers are on different NetWare servers then the NetWare 3.11 server with NetWare NFS and NetWare MAC, then queries for all other Appletalk printers must be performed by doing the following configuration.
SOLUTION
Edit the file ATPS.CFG on the server with NetWare NFS, and make entries for all the Appletalk printer that you wish to access.
Example:
"Bldg 2 (Purchasing) NTX:SJF-Building 2" -o PS3
"Bldg 1 (Engineering) NTX:SJF-Building 1" -o PS2
This will create the queues with the -o option and will let NetWare NFS access to these queues.
FYI: MHS and OS/2 v. 1.3
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and OS/2 v. 1.3
DOCUMENT ID#: FYI.S.MHS23
DATE: 16APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Not able to open DOS box for running MHS in OS/2.
SOLUTION
The NetWare Requestor for OS/2 v.1.3 does not have strong support for its DOS box and this is why MHS has a problem running in it; it is not able to support MHS. The NetWare Requestor for OS/2 v2.0 supports virtual IPX and thereby supports the DOS box in running MHS.
FYI: Format of IP address in the telnet xtelopen_API() function
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Format of IP address in the telnet xtelopen_API() function
DOCUMENT ID#: FYI.S.LWP5
DATE: 16APR92
PRODUCT: LWP Toolkit for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the format of the remote host IP address used in the xtelopen_API() function, and how is it loaded into the CX:DX registers?
SOLUTION
The remote host IP address is an unsigned long integer. It can be loaded into the CX:DX registers in a C program as follows:
unsigned long remoteHost = 0x04030201; /* IP addr = 1.2.3.4 */
_asm {
mov dx, word ptr[remoteHost]
mov cx, word ptr[remoteHost+2]
}
FYI: TCPIP and SynOptics Concentrators
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TCPIP and SynOptics Concentrators
DOCUMENT ID#: FYI.S.LWP3
DATE: 16APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
PC machines with 3COM 3C507 cards can ping all nodes except for the nodes on the other side of a SynOptics Concentrator, running SynOptics Network Management. PC machines with 3C503 cards can ping all nodes successfully.
SOLUTION
SynOptics Concentrators running SynOptics Network Management have the capability to filter packets at the Macintosh address level. In this case, it was incorrectly set up to filter all packets originating from 3C507 cards. Changing this parameter resolved the problem.
FYI: Number of minutes between forced connections
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Number of minutes between forced connections
DOCUMENT ID#: FYI.S.MHS10
DATE: 15APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When changing the number of minutes at "Force connection every:" in HOST THAT THIS HOST PHONES, the value automatically changes to 10 minutes.
SOLUTION
The number of minutes between forced connections must be either 0 or 10 or greater minutes. If a value between 0 and 10 minutes is entered, MHS will automatically change it to 10 minutes.
The force connection value represents the number of minutes between connection attempts. Regardless of the number of messages queued, MHS will make a connection to the remote host to check for inbound mail and deliver any queued messages.
The number of force connect minutes must also be greater than the number of seconds specified at "Schedule every:" in the TRANSPORT SERVER SETUP menu.
FYI: File Express problems with Windows 3.1
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: File Express problems with Windows 3.1
DOCUMENT ID#: FYI.S.LWP25
DATE: 15APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Two problems with File Express in Windows 3.1:
1. If you resize the File Express window to a minimum width, the application hangs, and you have to press Ctrl-Alt-Del to terminate it.
2. When you first enter File Express, selecting certain menu options or file buttons can cause a General Protection (GP) fault.
SOLUTION
1. Scheduled to be fixed in v4.1.
2. Scheduled to be fixed in v4.1. The workaround is to set an initial directory focus by clicking on the local or remote directory window.
FYI: Host Presenter French keyboard problems
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Host Presenter French keyboard problems
DOCUMENT ID#: FYI.S.LWP1
DATE: 15APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When Host Presenter is configured for a French keyboard and display, certain keys do not work. They are the Alt-gr keys, and the plus (+) and asterisk (*) keys on the numpad.
SOLUTION
To be corrected in v4.1.
FYI: Extended addressing
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Extended addressing
DOCUMENT ID#: FYI.S.MHS22
DATE: 14APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: (All releases, all versions)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Not sure of extended addressing syntax for DaVinci.
SOLUTION
The MHS syntax is USERNAME@WORKGROUP. This translates into DaVinci's syntax WORKGROUP:USERNAME. Similarly, the extended addressing syntax for MHS is USERNAME@WORKGROUP {extended address}; the DaVinci syntax is WORKGROUP "extended address":USERNAME.
FYI: Error 14964 in Connectivity Manager
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Error 14964 in Connectivity Manager
DOCUMENT ID#: FYI.S.MHS9
DATE: 14APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: .s\PARCEL\ ERROR 14969
contact your MHS dealer
ISSUE/PROBLEM
In the Connectivity Manager, when routing a message, the error message " .s\IPARCEL\ ERROR 14969 contact your MHS dealer" is displayed. There are no messages in the QUEUE or PARCEL directory.
SOLUTION
By removing the LOG and STAT files, space will be relieved for proper routing.
FYI: MHS Limiting Number of Declared Hosts
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Limiting Number of Declared Hosts
DOCUMENT ID#: FYI.S.MHS8
DATE: 14APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: "Sorry too many (nn) host; exit and restart utilities".
ISSUE/PROBLEM
Customer complained that MHS was limiting the number of hosts he could declare to 55. The error message is, "Sorry too many (nn) hosts; exit and restart utilities".
SOLUTION
MHS limits the number of hosts that can be added in a single session; the limit is 49. This particular customer had six hosts previously declared. If one needs to declare more than 49 hosts, one needs to back out to the MHS Main Menu, then go into the Directory Manager again. More hosts can now be added.
This is documented on page B-15 of the MHS Installation manual, but it incorrectly gives the number of hosts as 50 rather than 49. A documentation PMR has been entered.
FYI: LWP for DOS and Carbon Copy
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: LWP for DOS and Carbon Copy
DOCUMENT ID#: FYI.S.LWP23
DATE: 14APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.xx
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can Carbon Copy be used to remotely connect to a PC and run LWP for DOS?
SOLUTION
Yes, Carbon Copy can be used to remotely connect to a PC and run LWP for DOS.
FYI: LWP v4.x and Windows 3.1 compatibility
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: LWP v4.x and Windows 3.1 compatibility
DOCUMENT ID#: FYI.S.LWP21
DATE: 14APR92
PRODUCT: MS WINDOWS
PRODUCT VERSION: 3.1
SUPERSEDES: NA
SYMPTOM: "general protection error WLIBSOC.DLL mod address 0008:0357"
ISSUE/PROBLEM
Using File Express and opening an FTP connection returns "general protection error WLIBSOC.DLL mod address 0008:0357".
SOLUTION
In the Windows SYSTEM.INI file, under the [386 enh] section, make sure that "device=vtcpip.386" line is included.
FYI: UAE with LWP for DOS and Open Connect 3270 Emulator
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: UAE with LWP for DOS and Open Connect 3270 Emulator
DOCUMENT ID#: FYI.S.LWP17
DATE: 13APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: "UAE" (Unrecoverable Application Error)
ISSUE/PROBLEM
"UAE" appears when attempting to connect to a remote host using Open Connect Systems 3270 emulator, over LWPD (running Windows via the server).
SOLUTION
Verify that the statement "device=vtcpip.386" is included under the [386enh] section of the SYSTEM.INI file.
FYI: LWP 4.x telnet to SCO
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: LWP 4.x telnet to SCO
DOCUMENT ID#: FYI.S.LWP15
DATE: 13APR92
PRODUCT: SCO UNIX, Xenix TCP/IP Stack
PRODUCT VERSION: 1.0.1h
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
LWP cannot establish a telnet session to a SCO box running TCP/IP v1.0.1h.
SOLUTION
Request a TCP/IP patch from SCO v1.0.2 and make sure TELNETD.EXE is dated April 9, 1992.
FYI: LSM caused General Protection Fault error in WLIBSOCK.DL.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: LSM caused General Protection Fault error in WLIBSOCK.DL.
DOCUMENT ID#: FYI.S.LTRN4
DATE: 13APR92
PRODUCT: LANtern Services Manager
PRODUCT VERSION: 1.3
SUPERSEDES: NA
SYMPTOM: "General Protection Fault Error in WLIBSOCK.DLL"
ISSUE/PROBLEM
LSM returns "General Protection Fault Error in WLIBSOCK.DLL" message when trying to run LSM under Windows 3.1.
SOLUTION
Insert "Device=c:\xln\bin40\vtcpip.386" into the Windows SYSTEM.INI file under the [386Enh] section. This is a different error message for the same problem that was encountered under Windows 3.0.
FYI: Modem difference discussion
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Modem difference discussion
DOCUMENT ID#: FYI.S.MHS7
DATE: 12APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the difference between hi-speed modem standards V.32, V.32bis, V.42, V.42bis and MNP (Microcomm Networking Protocol)?
SOLUTION
CCITT V.32 and V.32b are relatively new standards that define the electronic communication scheme so that two different modem manufacturers can design modems that "understand" each other. V.32 defines a 9600 baud, full duplex modulation scheme and the V.32bis is a much newer 14,400 baud scheme.
CCITT V.42 and V.42bis are "add-on" features to modems that use either V.32 or V.32bis modulation schemes. V.42 defines an "error-control" scheme so that the two modems can detect errors and correct them without the help of the host computers. V.42bis defines a "data compression" scheme for modems that "must already" support the V.42 "error-control" standard. Again the data compression is performed by the modems without the help of the host computers.
MNP is a collection of licensed "proprietary" protocol standards for modems designed prior to the V.32 / V.42 era. The MNP collection of protocols are "numbered classes", Class 1 through Class 9. Class 1 defines a low performance, byte oriented, half -duplex scheme of interaction. Classes 2 through 4 define "alternative" schemes that achieve better and better performance. Class 5 (MNP5) defines a "data compression" scheme which is not as good as the V.42bis data compression standard.
Some modern modems provide more than one type of data compression and/or error-control schemes. The modems can actually "negotiate" which standard is common to both without the help of the host computer. The host computer has the option of allowing or preventing this modem-to-modem negotiation procedure to happen immediately after a connection is established.
With NGM, the administrator has the option to ENABLE or DISABLE the MODEM NEGOTIATION process. You might want to disable it if the serial ports are too slow to handle the Data Compression rates OR if the modem negotiation process confuses one of the modems and thereby prevents a connection between the two. This may happen with "older" modems.
FYI: "Automate" Login to MHS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "Automate" Login to MHS
DOCUMENT ID#: FYI.S.MHS21
DATE: 10APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5(all versions)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The customer does not want to be bothered by having to enter the MHS administrator's login name and password when he wants to modify the MHS configuration.
SOLUTION
The MHS administrator's MHS login name and password can be declared through DOS environmental variables. Place the following commands in the administrator's user login script or AUTOEXEC.BAT file: "SET USR=admin_name", and "SET PWD=admin_password". Note, the MHS administrator still needs Supervisor-equivalency.
FYI: MHSUSER adds extra blank line when output is redirected to a file
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHSUSER adds extra blank line when output is redirected to a file
DOCUMENT ID#: FYI.S.MHS20
DATE: 10APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5 (all revisions)
SUPERSEDES: NA
SYMPTOM: MHS 1.1 File: MHS 1.5 File:
User1 User1
User2
User3 User2
User3
ISSUE/PROBLEM
MHSUSER adds extra blank line when output is redirected to a file, "MHSUSER -X03 -Aapplication > filename". In MHS v1.5 there is a blank line added between the listing of user names that was not there in MHS v1.1. For example, see "SYMPTOM" above.
SOLUTION
Developers who are affected by this change need to program around it.
FYI: Received error: "Detected Non-Standard Product"
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Received error: "Detected Non-Standard Product"
DOCUMENT ID#: FYI.S.LANZ2
DATE: 10APR92
PRODUCT: LANalyzer
PRODUCT VERSION: 3.X
SUPERSEDES: NA
SYMPTOM: "Detected Non-Standard Product"
ISSUE/PROBLEM
Following installation of the Ethernet LANalyzer software, this error message appeared: "Detected Non-Standard Product".
SOLUTION
The problem resulted from the old Excelan 225 LANalyzer card being used. The LANalyzer software requires the new 325 card.
FYI: Using Sybase with LWP OS/2
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Using Sybase with LWP OS/2
DOCUMENT ID#: FYI.S.OS21
DATE: 09APR92
PRODUCT: LWP for OS/2
PRODUCT VERSION: 3.0
SUPERSEDES: NA
SYMPTOM: "can't demand load application segment"
ISSUE/PROBLEM
Cannot load program written with the Sybase OS/2 toolkit.
Returns error:
can't demand load application segment
SOLUTION
Call Sybase and request the v1.0.1 update to their toolkit. This is required to write Sybase applications with our v3.0 protocol stack.
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
PLPD error message "PLPD: Internal protocol error" in the NetWare NFS error message screen.
SOLUTION
When the UNIX client lpd process hangs, stop the lpd process in UNIX print client and restart it. The warning message mentioned above should go away.
FYI: "FATAL: LSLERR_OUT_OF_RESOURCES" error.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: "FATAL: LSLERR_OUT_OF_RESOURCES" error.
DOCUMENT ID#: FYI.S.LWP14
DATE: 09APR92
PRODUCT: LAN WorkPlace for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: "FATAL: LSLERR_OUT_OF_RESOURCES"
ISSUE/PROBLEM
FATAL: LSLERR_OUT_OF_RESOURCES error is generated when attempting to load TCPIP.EXE.
SOLUTION
Insert the following line in the NET.CFG file:
MAX STACKS = 5
The number 5 has been specified in the above example, but a greater number can be used if 5 does not work. Normally, only four "Stacks" are used when loading IPX and IP. One for IPX, one for IP, one for ARP, and one for RARP functions.
LSL v1.2 defaults to 4 stacks. If another protocol has been specified, you may not have enough stacks available.
FYI: Loading multiple protocol stacks with LWP v4.x
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Loading multiple protocol stacks with LWP v4.x
DOCUMENT ID#: FYI.S.LWP12
DATE: 09APR92
PRODUCT: LAN Workplace for DOS
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: "File server not found"
ISSUE/PROBLEM
"File server not found" error returned when loading LSL, MLID, TCPIP, TELAPI, IPXODI and NETX. Login to TCP/IP host is successful.
SOLUTION
IPXODI was being loaded with the wrong frame type. Change IPX frame type in the LINK DRIVER section of the NET.CFG to the frame type specified in the AUTOEXEC.NCF file on the NetWare file server.
FYI: TCP/IP and IPX under DesqView
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: TCP/IP and IPX under DesqView
DOCUMENT ID#: FYI.S.LWP11
DATE: 09APR92
PRODUCT: LWP for DOS
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Concurrently running an IPX application and TNVT220 under DesqView, the IPX application starts properly in one window, and the telnet connection starts properly in another window. However, when you return to the IPX application, it has lost its connection.
SOLUTION
Load TBMI and TASKID in the IPX window before starting the application.
FYI: FTP to NetWare v2.x server(s)
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: FTP to NetWare v2.x server(s)
DOCUMENT ID#: FYI.S.LWP7
DATE: 09APR92
PRODUCT: NetWare
PRODUCT VERSION: 2.x
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Problems encountered when trying to FTP to a Netware v2.x server
SOLUTION
Use LWP v4.x and load both TCP/IP and IPX protocols. Login to the server as a user, to establish network drive mappings. FTP to the TCP/IP system and open a connection to the remote host. Use the LCD command in FTP to change your local directory to your "network" drive (e.g. Z:) and use the FTP "put" or "get" commands to transfer files.
FYI: FTP access to a NetWare 2.x servers
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: FTP access to a NetWare 2.x servers
DOCUMENT ID#: FYI.S.NFS2
DATE: 08APR92
PRODUCT: NetWare NFS and FLeX/IP
PRODUCT VERSION: NFS v1.2 and FLeX/IP v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Requests for TCP/IP access to NetWare 2.x servers. NetWare 3.11, is the only NetWare server that supports TCP/IP.
SOLUTION
With NetWare NFS 1.2 FTPserve and FLeX/IP software, a NetWare 3.11 server can act as an FTP gateway to NetWare 2.x file servers. This doesn't give full TCP/IP access to the 2.x servers. It is only a FTP server gateway to 2.x servers even though TCP/IP is not loaded on the remote NetWare 2.x server.
FYI: MHS Bundled with NetWare
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Bundled with NetWare
DOCUMENT ID#: FYI.S.MHS36
DATE: 08APR92
PRODUCT: MHS
PRODUCT VERSION: 1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Is MHS bundled with NetWare?
SOLUTION
No, not anymore. MHS is now a separate item with a separate cost.
FYI: SNMP Network management traps generated by other non-Novell SNMP agents
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: SNMP Network management traps generated by other non-Novell SNMP agents
DOCUMENT ID#: FYI.S.TCP9
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Can NetWare 3.11 SNMP.NLM capture and display other SNMP Network management traps generated by other non-Novell SNMP agents?
SOLUTION
Yes, to do this specify the Internet address of the NetWare fileserver where the destination of all SNMP-trap messages should be sent.
Also make sure TCPIP.NLM , SNMP.NLM and SNMPLOG.NLM are currently running on that server. All local and remote SNMP trap messages will be written to the log file SYS:ETC/SNMP$LOG.BIN.
FYI: Problem booting Network Management Agents across NetWare 3.11 IP router
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Problem booting Network Management Agents across NetWare 3.11 IP router
DOCUMENT ID#: FYI.S.TCP8
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
There are problems in booting up Network Management Agents across the NetWare 3.11 IP router where the NetWare management consoles are using the BOOTP protocol to boot up the remote agent from the console.
SOLUTION
NetWare 3.11 TCPIP 1.0 does not come with any bootp packet forward feature. A common workaround is to use TFTP to copy the bootable image manually to the remote agent accross the NetWare 3.11 IP router.
FYI: Does NetWare 3.11 IP routing support variable subnet mask?
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Does NetWare 3.11 IP routing support variable subnet mask?
DOCUMENT ID#: FYI.S.TCP7
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Trying to use variable subnet mask in the network and force IP routing across NetWare 3.11 IP router.
SOLUTION
Variable subnets on the same logical network is not supported. Split the network physically and logically into proper subnets with the appropriate subnet mask; using identical subnet mask throughout the same logical network.
FYI: The "arp=no" option in NetWare TCP/IP returns a warning message about ARP disabled
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: The "arp=no" option in NetWare TCP/IP returns a warning message about ARP disabled
DOCUMENT ID#: FYI.S.TCP6
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: IP : ARP disabled. Warning : Because you have disabled ARP, 140.140.140.140 is incorrect. I am using the correct local address for this interface 140.140.34.24
IP : Bound to board 1. ....
IP LAN protcol bound to ....
ISSUE/PROBLEM
When specifying bind ip to lan driver, the specified IP address gets changed to a different IP address when specifying "arp=no". Example: "bind ip to landriver addr=140.140.140.140 arp=no". (The warning message that is returned is displayed in the "SYMPTOM" section, above)
SOLUTION
Since the configuration has specified not to use ARP, part of the MAC address of the LAN interface has been used as the host portion of the Internet Address.
Note, do not specify "arp=no" unless it is necessary.
FYI: Enterprise specific traps data structure recognized by NetWare3.11
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Enterprise specific traps data structure recognized by NetWare3.11
DOCUMENT ID#: FYI.S.TCP5
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the enterprise specific traps data structure being recognized by NetWare 3.11, as valid trap messages coming in from SNMP-trap known port ? Developers would like to know what data structure for enterprise specific traps are supported by NetWare TCP/IP 1.0.
SOLUTION
The enterprise specific trap is one of the 6 different kinds of snmp-trap messages. Detail data structure in enterprise specific trap can be found in RFC 1157.
FYI: Function of the SYS:/ETC/HOSTS file on NetWare
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Function of the SYS:/ETC/HOSTS file on NetWare
DOCUMENT ID#: FYI.S.TCP4
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
What is the minimum configuration in the SYS:/ETC/HOSTS file for IP routing on a NetWare 3.11 fileserver?
SOLUTION
There is no minimum entry in SYS:/ETC/HOSTS file.
For IP routing, the file SYS:/ETC/HOSTS is not a required configuration file because all required parameters for IP routing are setup in the AUTOEXEC.NCF file.
TCPCON does use the SYS:/ETC/HOSTS file for hostname to Internet address mapping to display network management information.
Some other add-on TCP/IP related NLMs such as NetWare NFS, require the client and server's Internet addresses be specified in the SYS:/ETC/HOSTS file in order to provide network service.
FYI: SNMP and SNMP trap well known ports
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: SNMP and SNMP trap well known ports
DOCUMENT ID#: FYI.S.TCP3
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: v1.0
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Customers would like to find out what well known ports are defined with SNMP related services in NetWare TCP/IP.
SOLUTION
The two well known ports in use are snmp (port 161) and snmp-trap (port 162) for snmp related trap messages. This can be found in sys:/etc/samples/services file: "snmp 161/udp", "snmp-trap 162/udp".
FYI: Setup NetWare 3.11 to do IP Routing through routers without RIP
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Setup NetWare 3.11 to do IP Routing through routers without RIP
DOCUMENT ID#: FYI.S.TCP2
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
If a network is not configured to use IP RIP as the routing protocol between IP routers, a NetWare 3.11 IP router can be configured to communicate with other non-RIP routers.
SOLUTION
There are ways to configure NetWare 3.11 to route IP packets to non-RIP routers:
1) Enable RIP on the non-RIP router,
2) Add static route entries in both the NetWare server and the non-RIP router, and
3) Specify the gateway parameter so that the NetWare 3.11 IP router will send packets to the gateway address for routing purposes, when binding IP to the IP LAN driver: "Bind ip to IPLAN addr=XX.XX.XX.XX gate=YY.YY.YY.YY ".
FYI: Confusion between Ethernet IEEE 802.3 and Ethernet_SNAP frame types
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Confusion between Ethernet IEEE 802.3 and Ethernet_SNAP frame types
DOCUMENT ID#: FYI.S.TCP1
DATE: 07APR92
PRODUCT: NetWare TCP/IP
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
A few customers may require that only the frame type IEEE 802.3 be used on their networks, instead of "ETHERNET_II" which is the standard frame type on most IP networks, then the frame type to load to IP on the NetWare 3.11 server is "ETHERNET_SNAP" and NOT "ETHERNET_802.3" or "ETHERNET_II".
SOLUTION
They should use the frame type "ETHERNET_SNAP" when loading a LAN DRIVER.
(NOTE: The primary purpose of SNAP is to allow other protocols to run over an IEEE 802 network.)
FYI: Authentication denied when using PCNFS to access files in NetWare NFS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Authentication denied when using PCNFS to access files in NetWare NFS
DOCUMENT ID#: FYI.S.NFS7
DATE: 07APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1, v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Using PCNFS to access files in NetWare NFS returns a message stating that authentication was denied.
SOLUTION
Most PCNFS products (e.g. SUN PCNFS, Beame and Whiteside PCNFS , FTP SOFTWARE PCNFS) or MACNFS client software has a PCNFSD authentication daemon dependency. Most PCNFS vendors ship their product with the source code for pcnfsd daemon which has to be compiled and run on a UNIX server host.
The design of most PCNFS products forces the DOS client to check with the authentication server before any NFS operations are allowed. It is the pcnfs daemon's task is to validate the NFS client's UID and GID before any PCNFS operations are allowed.
If any authentication denied messages are generated while using PCNFS, check to make sure the authentication daemon pcnfsd is running and that it validates the proper UID and GID on the UNIX host. Otherwise, *ANY* pcnfs NFS operations will get authenication denied.
FYI: Suppress banner page from NetWare to UNIX printer
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Suppress banner page from NetWare to UNIX printer
DOCUMENT ID#: FYI.S.NFS5
DATE: 07APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Customer would like to find out how to suppress banner page when printing from NetWare Workstation to UNIX printer if the print job is going through the NetWare NFS LPR Gateway.
SOLUTION
1. If using "capture", specify the "nb" and "nff" options.
2. If using "nprint", specify the "nobanner" option.
3. If using printcon, specify in the default job configuration to set the banner page option to "no".
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
The NFS error message screen has the following undocumented error message: PLPD-Error: plpd : AddQueue :GetBinderyObjectID : E252
SOLUTION
The NetWare queue that has been configurated in PLPDCFG for NetWare NFS PLPD.NLM has been deleted. This is a warning message indicating that the NetWare queue no longer exists although the PLPDCFG was set up to use that queue.
FYI: Using the NetWare NFS LPR_GWY to print to remote LPD hosts.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Using the NetWare NFS LPR_GWY to print to remote LPD hosts.
DOCUMENT ID#: FYI.S.NFS1
DATE: 07APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: 1.2
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When sending a print job from NetWare to a remote LPD host, through the NetWare NFS LPR_GWY, a message comes up on the LPR_printserver screen stating:MOUNT FORM 1! and no further action takes place. This message is stating that the FORM from NetWare does not correctly match the FORM that the remote LPD host is supporting. (A FORM designates print parameters such as the number of lines per page and the number of columns per page)
SOLUTION
To resolve the problem, either delete the FORM through PRINTDEF and use the default print FORM that comes with NetWare. Or, configure the FORM on the NetWare fileserver such that the number of lines and columns coincide with the FORM that is configured on the remote LPD host.
FYI: Running MHS with NACS/NASI
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Running MHS with NACS/NASI
DOCUMENT ID#: FYI.S.MHS19
DATE: 07APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: all versions, all releases
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
MHS is not recognizing the network modem pool. The Netware Asynchronous Communications Server (NACS) has been installed and is running with modems that are supported by MHS.
SOLUTION
MHS does not support NACS. Modems must be installed on the workstation from which MHS will be run. MHS will only recognize modems that are installed on its workstation's COM ports.
FYI: Could not find routing directory
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Could not find routing directory
DOCUMENT ID#: FYI.S.MHS18
DATE: 07APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: v1.5, all releases
SUPERSEDES: NA
SYMPTOM: Could not find routing directory
ISSUE/PROBLEM
On starting MHS for the first time after installation, an error message was displayed, "Could not find routing directory." MHS did not start and returned back to DOS.
SOLUTION
Customer had a TSR running in the background. MHS will not start with any TSRs, such as Norton Anti-Virus (NAV), running. This can be tested by rebooting the workstation with minimal configuration in AUTOEXEC.BAT and CONFIG.SYS files.
FYI: Attachments in PARCEL are not being deleted
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Attachments in PARCEL are not being deleted
DOCUMENT ID#: FYI.S.MHS6
DATE: 07APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Attachments are not being deleted after they are sent from the PARCEL directory. Client's disk is filling up with old attachments.
SOLUTION
User is lacking the E(rase) right in MHS\MAIL\PARCEL. MHS is writing a temporary attachment file, then copying/renaming it after it is successfully written, then deleting the temporary file.
FYI: Dedicated Host Requirement for MHS
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Dedicated Host Requirement for MHS
DOCUMENT ID#: FYI.S.MHS5
DATE: 07APR92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Many customers ask if MHS requires a dedicated PC to operate as the MHS host.
SOLUTION
No, this is not a requirement for MHS. However, mail will accumulate and not be routed until someone invokes MHS on a PC that is set up to run MHS (ie, MV is set properly, etc).
The customer needs to decide for himself the relative importance of not having to dedicate a PC to run the MHS Connectivity Manager versus delaying the routing of mail until MHS is invoked on a non-dedicated PC.
FYI: Installation of LWPD 4.01
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Installation of LWPD 4.01
DOCUMENT ID#: FYI.S.LWP2
DATE: 06APR92
PRODUCT: LWPD
PRODUCT VERSION: 4.01
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Unsuccessful installation of LWPD.
SOLUTION
Unload SHARE and all TSRs from the CONFIG.SYS and the AUTOEXEC.BAT. This will free up enough RAM to allow the installation to complete successfully.
FYI: Products that Work with MHS.
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Products that Work with MHS.
DOCUMENT ID#: FYI.S.MHS4
DATE: 05APR92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Customer wants to know what products are available, ie applications, gateways, utilities, etc., that work with MHS?
SOLUTION
Novell produces a document called the NetWare MHS Solutions Guide which contains this information. The MHS Solutions Guide, part number 462-000230-002, may be ordered by calling Novell at 800-526-5463 (801-429-7000).
It is also available electronically in three files from Novell. To get an electronic copy, send three messages via NHUB or CompuServe to LIBRARY @ NOVELLPM. The "Subject:" line in each message should be one of the following keywords: A-SGAPPS, A-SGGATE, and A-SGUTIL.
FYI: Connection with 9600 Baud and the US Robotics HST Modem
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Connection with 9600 Baud and the US Robotics HST Modem
DOCUMENT ID#: FYI.S.MHS3
DATE: 05APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
The US Robotics HST modem does not seem to be connecting at 9600 when other 9600 baud modems call it.
SOLUTION
As for a "high speed" connection, this can only be made with another HST modem. The HST does not Support v.32 thus it will always connect at 2400 with v.32 modems. It is important that the 2400 baud modems use the proper drivers.
FYI: MHS and the US Robotics HST modem
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS and the US Robotics HST modem
DOCUMENT ID#: FYI.S.MHS2
DATE: 05APR92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When calling from a 9600 baud US Robotics modem to a 2400 baud modem, connections fail.
SOLUTION
By adding the string "&K0&M0" to the phone number this problem has been fixed. The phone number would then look like "1,4085551212 &K0&M0.
FYI: The order to unload the NFS related NLMs
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: The order to unload the NFS related NLMs
DOCUMENT ID#: FYI.S.NFS3
DATE: 04APR92
PRODUCT: NetWare NFS
PRODUCT VERSION: v1.1
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Unloading the NFS related files in random order may cause unreliable results on the NetWare fileserver.
SOLUTION
In NFS 1.2 there is a file called NFSSTOP.NCF that unloads the NFS related files in a specific order, therefore making the unload graceful. (In NFS 1.1, this file was not provided but can easily be created with a simple text editor). Edit a file called NFSSTOP.NCF (If you wish to call the file that) and enter the following commands:
Unload ftpserv
Unload plpd
Unload filter
Unload fltrlib
Unload plpdcfg
Unload nfsadmin
Unload lockd
Unload statd
Unload nfsserv
NOTE: These commands can also be executed at the console prompt.
FYI: Messages from NHUB Not Being Picked Up
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Messages from NHUB Not Being Picked Up
DOCUMENT ID#: FYI.S.MHS51
DATE: 02APR92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
A user is having problems picking up messages from NHUB, and it does not appear to be modem- or modem-driver-related. The particular symptom is that a small percentage (For example: less than 5 percent) of the messages is received during each call to NHUB.
SOLUTION
Check when the last (working) connection to NHUB occurred. If a host does not contact NHUB for six months, the account is "put on hold." The customer should contact the NHUB administrator to have the account reactivated. In addition, constant calling to NHUB with a small percentage of the messages transferred each time, eventually clears the problem.
FYI: Serial Number Not Found in MHS Upgrade
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Serial Number Not Found in MHS Upgrade
DOCUMENT ID#: FYI.S.MHS50
DATE: 02APR92
PRODUCT: NetWare MHS
PRODUCT VERSION: 1.5 rev. B upgrade
SUPERSEDES: NA
SYMPTOM: "serial number not found"
ISSUE/PROBLEM
The MHS 1.5 rev B upgrade program, V15B-P.EXE, was exploded in the MV\MHS subdirectory. The UPGRADE.EXE program was run and terminated with the error "serial number not found."
SOLUTION
The wrong upgrade program is being run to upgrade MHS 1.5N(Network edition). V15B-P.EXE is written for MHS 1.5P rev A (Personal edition). Instead, upgrade program V15B-N.EXE should be used to upgrade the Network edition of MHS.
Both upgrade programs are available on NetWire in Library 6.
FYI: Cannot Find NETDIR.TAB
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Cannot Find NETDIR.TAB
DOCUMENT ID#: FYI.S.MHS49
DATE: 01APR92
PRODUCT: MHS
PRODUCT VERSION: LL
SUPERSEDES: NA
SYMPTOM: "NETDIR.TAB cannot be found"
ISSUE/PROBLEM
A routing host in a multihost workgroup receives the message that the NETDIR.TAB file cannot be found. This does not have to do with the routing host's file but another host on the same internetwork (INET).
SOLUTION
The adminstrative user on the INET host did not have the proper rights to the directory where the file was found and therefore could not read the file. Adjusting the rights will allow reading of this file.
FYI: Unable to Decompress Files
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Unable to Decompress Files
DOCUMENT ID#: FYI.S.MHS48
DATE: 31MAR92
PRODUCT: MHS
PRODUCT VERSION: 1.5
SUPERSEDES: NA
SYMPTOM: "Unable to decompress files, check the file path"
ISSUE/PROBLEM
The MHS 1.5 installation is started, the server and volume where MHS will be installed is specified, and "First-time installation..." is chosen. After inserting the second diskette, the error "Unable to decompress files, check the file path" occurs.
SOLUTION
Verify that only one fileserver has been logged into. If the user is logged into more than one server, MHS will be confused by the additional servers.
Log out of all servers except for the specified server where MHS is being installed; check that the master volume variable MV, is set properly by typing SET at the DOS prompt. MV should point to the parent directory of the \MHS subdirectory.
FYI: MHS Admin Rights to Add/Delete Users
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Admin Rights to Add/Delete Users
DOCUMENT ID#: FYI.S.MHS47
DATE: 27MAR92
PRODUCT: MHS
PRODUCT VERSION: Network (all flavors)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Administrative user is not able to add/delete users.
SOLUTION
The user who is logged into NetWare does not have supervisory right to the MHS directory area. Either grant this user a supervisor equivalence or assign supervisory rights to the MHS directory.
FYI: Abnormal Display when Transferring Large Attachments
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Abnormal Display when Transferring Large Attachments
DOCUMENT ID#: FYI.S.MHS43
DATE: 19MAR92
PRODUCT: MHS
PRODUCT VERSION: 1.5 (all flavors)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
When a large attachment (approximately .5Mb or larger) is transferred, the Connectivity Manager will have an abnormal display. This abnormal display usually includes a negative percentage of the amount of the attachment remaining to be transferred.
SOLUTION
This is a cosmetic bug in MHS. The attachment has been transferred properly.
FYI: MHS 1.5 Support for Encrypted Passwords
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS 1.5 Support for Encrypted Passwords
DOCUMENT ID#: FYI.S.MHS42
DATE: 12MAR92
PRODUCT: MHS
PRODUCT VERSION: 1.5C (Rev A/B), 1.5 Rev B (all flavors)
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
MHS 1.5C, and all MHS 1.5 Rev B, are advertised as supporting encrypted passwords. However, if one looks at NETDIR.TAB, the passwords are unencrypted.
SOLUTION
MHS is functioning as designed. The support for encrypted passwords refers only to MHS's ability to create a new user in the NetWare bindery.
Before the CompuServe and Rev B versions, this MHS-created account in the bindery was unusable if the NetWare fileserver had encrypted passwords set to "ON". Passwords in MHS are unencrypted at this time.
FYI: Upgrading MHS 1.5 to CompuServe version
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Upgrading MHS 1.5 to CompuServe version
DOCUMENT ID#: FYI.S.MHS40
DATE: 11MAR92
PRODUCT: MHS
PRODUCT VERSION: 1.5
SUPERSEDES: NA
SYMPTOM: "pksfx: Warning can't open filename" "Can't serialize mhsn.ovr"
ISSUE/PROBLEM
When upgrading MHS 1.5 to the CompuServe version, various errors occur when UPGRADE.EXE is run. Errors such as "pksfx: Warning can't open filename" and "Can't serialize mhsn.ovr" are displayed.
SOLUTION
Before running the upgrade program, the user must be logged into the server that contains the MHS files with an account that is supervisor equivalent. The environmental variable MV, must be set according to MHS standards.
FYI: New MHS Modem Drivers
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: New MHS Modem Drivers
DOCUMENT ID#: FYI.S.MHS46
DATE: 06MAR92
PRODUCT: MHS
PRODUCT VERSION: .5
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
MHS has revised the list of modem drivers it will now support.
SOLUTION
The newest release of available drivers are on NetWire in a self-extracting file called MHSMDM.EXE. (This file can be found in Library 6) These drivers replace and supersede all previous drivers. Any previous drivers are not guaranteed to work and are no longer supported.
The MODEM.DOC file dated February 18, 1992 and included in MHSMDM.EXE goes into detail about what drivers are currently available, the modems they support, and the configuration parameters required.
FYI: MHS Communication with Non-MHS-Compatible Applications
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: MHS Communication with Non-MHS-Compatible Applications
DOCUMENT ID#: FYI.S.MHS45
DATE: 06MAR92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Sites using non-MHS-compatible EMAIL applications want to communicate with MHS.
SOLUTION
Noncompatible applications need an additional piece of software called a gateway. After MHS is installed, go to the Directory Manager and define the specific gateway. From there, you can define a group or a postman as being reached through (HVIA) the particular gateway.
FYI: Communication via MHS using Different EMAIL Applications
FYI
(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Communication via MHS using Different email Applications
DOCUMENT ID#: FYI.S.MHS44
DATE: 06MAR92
PRODUCT: MHS
PRODUCT VERSION: ALL
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Two sites using different email applications want to communicate with each other.
SOLUTION
By installing MHS at both sites, the applications can send a message to their local MHS host, which then will connect to the other host and send the message. The receiving host can then deliver the message to the particular recipient's email package for delivery.
