home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
network
/
fyixla.zip
/
FYI_SA.NET
< prev
next >
Wrap
Text File
|
1993-02-17
|
14KB
|
445 lines
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 Support when Printing from an
IBM AIX
DOCUMENT ID#: FYI.S.NFS21
DATE: 18AUG92
PRODUCT: NetWare NFS and FLeX/IP
PRODUCT VERSION: v1.2 or above
SUPERSEDES: NA
SYMPTOM
When trying to suppress the banner page from AIX using the lpr
"-h" option or the lpr "-Nnumber" option to the NetWare file
server (running NetWare NFS or FLeX/IP), it will not perform
banner page suppression or suppression of multiple copies of
the print job to be done.
ISSUE/PROBLEM
AIX RS6000 supports multiple form filters configuration 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.
Novell related printing should be configured to use BSDSHORT
and BSDLONG filter inside the AIX "smit" for print queues on
a Novell file server.
SOLUTION
Check within AIX "smit" for 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
(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 Intel HUB.LAN v1.12 Does Not Support
AppleTalk Phase 2 Routing
DOCUMENT ID#: FYI.S.MPR6
DATE: 10DEC92
PRODUCT: MPR and NetWare 386
PRODUCT VERSION: MPR v2.0 and NetWare 386 v3.11
SUPERSEDES: NA
SYMPTOM
When using more than one Intel HUB card and wanting to bind
AppleTalk to one or all of the HUB cards, the AppleTalk stack
will not work properly.
ISSUE/PROBLEM
The version 1.12 of HUB.LAN that Intel supplies is not able to
support AppleTalk Phase 2 when more than one of the Intel HUB
cards has been loaded. If other protocol stacks like IP and
IPX are loaded when AppleTalk is configured, it will stop the
functions of the other protocol stacks.
SOLUTION
Intel has a newer driver version 1.13 available on their BBS
that fixes this 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: Using an Existing NetWare Print Server Name in
LPR$PSRV.NAM
DOCUMENT ID#: FYI.S.NFS36
DATE: 03DEC92
PRODUCT: NetWare NFS or NetWare FLeX/IP
PRODUCT VERSION: All
SUPERSEDES: NA
SYMPTOM
When going into NFSadmin to configure the Print Gateway, the
local PSERVER configuration is corrupted.
ISSUE/PROBLEM
When installing the NetWare FLeX/IP or NFS products, a name
for the NetWare-to-UNIX print server gateway is requested. If
the name that is given is the name of an existing NetWare
PSERVER, the name will not be recognized. The name needs to
be unique.
SOLUTION
There is a file in the SYS:ETC/PLPD directory called
LPR$PSRV.NAM. This is a text file that contains the name of
the NetWare-to-UNIX gateway. This should be a unique name and
not an existing NetWare PSERVER name. Edit the file and
change the name to something unique. Reconfigure the NetWare
PSERVER because this information has been corrupted and then
reload the PSERVER.
Now when entering NFSadmin and configure the NetWare-to-Unix
print gateway, the information will be stored under the
correct Print Server name.
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: LPR_GWY Unloads Itself from Memory
DOCUMENT ID#: FYI.S.NFS37
DATE: 04DEC92
PRODUCT: NetWare NFS / FLeX/IP
PRODUCT VERSION: v2.0
SUPERSEDES: NA
SYMPTOM
LPR_GWY.NLM was loaded but does not show up in the modules
listing or the following error message is returned, "Module
LPR_GWY.NLM is NOT loaded."
ISSUE/PROBLEM
LPR_GWY.NLM appears to load correctly; however, in subsequent
searches for it in the modules listing it is not listed as a
loaded NLM. When attempting to unload this module, NetWare
responds with the following error message:
"Module LPR_GWY.NLM is NOT loaded"
SOLUTION
This problem occurs when LPR_GWY is not fully configured with
NFSADMIN.NLM or FLEXCON.NLM. Follow the steps outlined in the
NetWare NFS Supervisors Guide/NetWare FLeX/IP Supervisors
Guide for configuring NetWare-to-UNIX printing.
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 Entry for Administrative User
<username>
DOCUMENT ID#: FYI.S.MHS119
DATE: 26JAN93
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM
Corrupted NETDIR.TAB. Missing entry for administrative user
<username>.
ISSUE/PROBLEM
The Connectivity Manager is running fine; however, the client
is not able to administer the database. It receives the
following message whenever the user tries to enter the
Directory Manager:
"Corrupted NETDIR.TAB. Missing entry for administrative
user <username>."
MHSUSER -X00 shows the correct administrative user's name.
SOLUTION
The user created a new routing directory and reset up the host
and users; this created a new NETDIR.TAB. Then after the user
reestablished the original NETMGR.QUE, everything worked fine.
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: "PROC add_rec line 202 disk full" Error
Message Received
DOCUMENT ID#: FYI.S.MHS120
DATE: 30DEC92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM
"PROC add_rec line 202 disk full" error message in
Connectivity Manager.
ISSUE/PROBLEM
Connectivity Manager gives error when it begins to process
messages downloaded from the hub.
SOLUTION
Two files were "owned" by N/A (no such user). By coping the
files to another area and back again, the user was able to
change ownership which cleared this 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: Hayes 2400 Smart Modem Quad
DOCUMENT ID#: FYI.S.MHS121
DATE: 30DEC92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM
United Kingdom (U.K.) cannot get Hayes 2400 Smart Modem Quad
to work on Com 2.
ISSUE/PROBLEM
This modem, which is specific to the U.K., will consistently
not work on Com 2. We tried setting different interrupts with
no success.
SOLUTION
Do not use this COM port. This modem is specifically
different from other Hayes 2400 modems in that it needs a
special driver. Advise user to try another COM port.
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: Detaching an Attachment
DOCUMENT ID#: FYI.S.MHS122
DATE: 30DEC92
PRODUCT: MHS
PRODUCT VERSION: v1.5
SUPERSEDES: NA
SYMPTOM
Detach an attachment before final destination.
ISSUE/PROBLEM
The user needs to detach an attachment at the workgroup-wide
router; the message is going on to a host within the
workgroup.
SOLUTION
There is no utility to separate an attached file as it is all
in the queue as one file. Advised to get it from the
following directory in the user's host's MHS directory:
MHS\MAIL\USERS\<username>\IPARCEL
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: Installing NGM; Error Code 64
DOCUMENT ID#: FYI.S.NGM7
DATE: 30DEC92
PRODUCT: NGM
PRODUCT VERSION: v1.0 Revision A
SUPERSEDES: NA
SYMPTOM
"Error code 64; the MMS directory database already exists;
library routine unknown, program routine
netInitMMSNameServiceDatabase severity fatal program execution
cannot continue normally."
ISSUE/PROBLEM
While installing NGM, the user was able to get to the third
disk where he fills in the CONFIG names. When the user tries
go on after supplying the data the system displays the
following error:
"Error code 64; the MMS directory database already
exists; library routine unknown, program routine
netInitMMSNameServiceDatabase severity fatal program
execution cannot continue normally."
SOLUTION
The previous installation was not removed before future
attempts. The user needs to completely remove NGM before
attempting a reinstall. The user may use DINSTALL, NGMDEINS,
or FILER to remove the 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: Deinstalling NGM Not Successful
DOCUMENT ID#: FYI.S.NGM8
DATE: 30DEC92
PRODUCT: NGM
PRODUCT VERSION: v1.0 Revision A
SUPERSEDES: NA
SYMPTOM
NGMDEINS does not seem to completely deinstall NGM.
ISSUE/PROBLEM
After unsuccessful attempts to install NGM, attempts to use
deinstall also fail.
SOLUTION
Because NGM did not completely install, NGM.CFG was not
created. This is required by NGMDEINS to remove NGM.
Creating this file will allow NGM to deinstall.
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 Run DIRADM.EXE
DOCUMENT ID#: FYI.S.NGM9
DATE: 30DEC92
PRODUCT: NGM
PRODUCT VERSION: v1.1
SUPERSEDES: NA
SYMPTOM
The following error message is displayed when attempting to
run the DIRADM utility:
F7006: Fatal error: Unable to open Name Service database
ISSUE/PROBLEM
Attempts to run DIRADM in the input or output mode failed with
the error message described above. BTRIEVE.NLM and NGM.NLM
have been loaded on the server, and BREQUEST.EXE has been
loaded on the workstation.
SOLUTION
This error can be caused by the MV variable being set
incorrectly or BSPXCOM.NLM not being loaded on the server.
Make sure the MV variable is set to the volume and directory
that contains the MHS directory. To check if BSPXCOM.NLM has
been loaded, at the server's console prompt, type "MODULES."
If BSPXCOM.NLM is not listed, at the server's console prompt,
type "load BSPXCOM."