8.1 PCShare and firewall software
When using PCShare 3 server/clients in VPN networks or behind firewalls you have to make sure that the server IP address is reachable as well as the following server ports:
- 137/TCP & UDP NetBIOS Name Service (usually only UDP is used)
- 138/TCP & UDP NETBIOS Datagram Service (usually only UDP is used)
- 139/TCP & UDP NETBIOS Session Service (usually only TCP is used)
- 2001 when using PCShare 2.x native protocol
- 2003 when connecting to PCShare 3 NBS from remote
In case you do not need browsing from behind the Firewall, port 139 would be sufficient.
Also make sure that these ports are only made available for the IP addresses of the servers which have to be reached from outside.
Additionally, you have to add the Windows clients which are allowed a remote login to the PCShare server's IP access list.
For product specific information see your firewall software product documentation.
HELIOS offers a variety of support options to help you get the most from HELIOS products. This section summarizes those options.
If you have any questions about your HELIOS product, first read the printed documentation. Also consult the README files, which may have been provided with the product to describe late news which is not covered by the main manual. Last but not least, you may check our web site regularly:
If you still cannot find the answer to your question, your first line of support is your HELIOS product supplier or dealer. Please have the following information at hand:
- Did you try to get help from one of our dealers or distributors? Please let us know how helpful your dealer was in resolving the problem.
- The serial number of your HELIOS product (this is printed on your "Activation Key Request" form. Alternatively, the machine ID of your computer (see What you have to do in "Welcome to PCShare 3").
- Your full address, telephone/fax number, and e-mail address, if available.
- HELIOS partner contact: Name, e-mail address, fax, phone.
- For every EtherShare/PCShare server at your site:
- EtherShare/PCShare: Contents of the respective "Versions" file in "$PCDIR" and "$ESDIR"
- UNIX: information about the hardware and operating system.
- The version of all relevant HELIOS software modules and the name and version of any Windows application software (such as DTP programs)
- For printer related queries, we need details of your
"/etc/printcap" file, too.
- The exact wording of any messages that appeared on your screen, and details of relevant messages in the following files:
- Printer log file
- System message file (contents since last start)
- What - you think - happened and what were you trying to do at the time the problem occurred?
- How did you try to solve the problem? Contents of
"/etc/passwd", "/var/yp/passwd" (we are only interested in the location of users' home directories).
- Let us have the output of "ps -efl", or "ps aux", respectively.
- Let us have the output of "$ESDIR/swho -c" and "$PCDIR/swho -c".
- Is the result reproducible or does it emerge only occasionally? Any clue on the suspected pattern will be helpful!
- In case you have additional information available, e.g. core files, trace output, please store it safely and make a note in your report - do only send it on request.
Depending on the severity of the problem it may be necessary to stop and restart PCShare services completely. If you use shared volumes together with EtherShare, stop PCShare first, and restart it only after restarting EtherShare.
If the dealer cannot solve the problem, he or she can contact the official HELIOS distributor in your country. HELIOS has appointed distributors in about 20 countries - you can find their addresses on HELIOS product brochures or on the HELIOS web site
www.helios.de. Each distributor and HELIOS OEM customer is obliged by contract to have technical support staff who are experienced with HELIOS products.
Note: The current HELIOS CD-ROM provides a support questionnaire called "ps_quest.pdf" which helps you have all important information at hand when contacting the HELIOS product supplier or dealer.
All HELIOS products require an Activation Key (kind of password) to be entered during (or after) the installation. Without the Activation Key, the software cannot be started. End-user Activation Keys are dependent on the machine ID of the host and the PCShare serial number. The installation program will let you know your machine ID automatically.
Note: If we generate a key twice for the same combination of machine ID and PCShare serial number, the second key may be different from the first one. This is normal.
At their discretion, HELIOS distributors can provide their dealers - for a reduced fee - with so-called dealer demonstration versions of our products, which are fully working copies of our software but carry a special Activation Key which expires after a given period of time. You will be informed about the time remaining on your demonstration copy by a "pcshare" message which pops up each time you log on to the file server, and then each 3 - 4 hours while being logged-on to the file server (see Figure
79):
Fig. 79: Demonstration key warning
|
|
Note: If you do not enter any Activation Key the HELIOS product you have installed will run in a 3 hour demo mode only.
If you are transferring your PCShare software from one host to another, then we call this an "Activation Key Transfer". When you apply for a new key, you will need to state that you will no longer use PCShare on the original host - fax our key registration department (+49-5131-70 93 25) and ask for details of the exact wording to use and the conditions that apply. The "Activation Key Transfer" form can be found as file "Key-Transfer.pdf" in the "manuals" directory on the HELIOS CD-ROM.
HELIOS releases new versions of its software products from time to time, for example to make improvements or to correct known faults. HELIOS distributors and OEM customers automatically receive the latest version in new shipments.
An automatic software update service ("Software Update Service Agreement") is available for end-users who wish to receive new major product versions and intermediate product releases automatically. This is implemented by shipping a single CD-ROM containing the latest versions of all of our products. The CD-ROM will be produced whenever a significant new product version is released.
In addition, Update Service customers may immediately download updates from the HELIOS web site when they are posted.
Customers not taking part in the update service will only receive replacement software modules if their installation does not function according to the claims made by HELIOS at the time of purchase. For example, if Microsoft upgrades its Windows OS and this causes a problem with one of our products, the solution to the problem will only be made available to customers with a service contract. Other customers can still upgrade their software when new major releases become available, by paying the appropriate upgrade fee. HELIOS will inform all customers who do not have an update service contract about fees for upgrading existing installations as soon as new releases become available.
Another way to obtain the latest HELIOS software updates is called "Internet Update Access", which provides the customer with the latest updates via the HELIOS web site.
For both update service products contact your supplier for price information and for a copy of the relevant application form, or visit the HELIOS web site:
http://www.helios.de.
The following section lists and describes the most important error messages for all UNIX program modules.
All error messages are constructed the same way. They start with the name of the issuing program followed by the UNIX process ID [in brackets]. This is then followed by a verbose error message which may include variable strings and numbers, for example:
pcshare[12345]: %s: sendmsg to %s failed, %m
In the following, strings are abbreviated by "%s", numbers by "%d", UNIX system error messages by "%m", and long hexadecimals by "%lx". Refer to your UNIX documentation for more information on UNIX system error messages.
8.4.1 "license" error messages
All PCShare servers verify the integrity of the executable image by performing a checksum and verify the license by reading the license file "$PCDIR/conf/pcshare.lic".
Program file corrupted, please reinstall
The program checksum did not match. A common reason is that you have transferred your PCShare installation via FTP and you have forgotten to set FTP to image (binary) mode.
$PCDIR/conf/pcshare.lic: %m
The license file could not be opened, probably because it is missing.
No valid PCShare license found
The license file "$PCDIR/conf/pcshare.lic" contains no valid license for PCShare.
The demo license has expired
PCShare demo versions run for a limited time, and the license has now expired. Each user is warned at every login to the file server that he is using a demo version, and also for how many days the license will still be valid. Thus, the expiry should not take effect surprisingly. See
Demonstration keys in
8.3 "Keys and updates".
The license checksum is invalid
The "Checksum" field in the license does not match the data in the other fields. This should not happen as the installation procedure verifies that a license is valid before entering it into the license file. However, this error message may appear e.g. if you have upgraded from PCShare 2.5 to PCShare 3 but still use the old key, or when you installed another version of the product to another directory and the data mix up.
The license is not valid on this machine
The "MachID" field of the license does not match the host's machine ID. This might happen if you transfer a complete installation to a new host or if you get a new machine due to a hardware replacement. Contact our license department for a license transfer (see
Activation Key Transfers in
8.3 "Keys and updates").
Missing required base license %08lx
The user expansion license did not find the proper base serial number. Verify that you have specified the proper base serial number when requesting the user expansion license from our license department.
8.4.2 "generic" error messages
Most programs issue a generic error message when anything goes wrong for a simple system call.
Various error messages from system calls are logged-in this form. "syscall" is one of the common system calls (fork, malloc, -) and "%m" gives the reason why the call failed. Common reasons like "No more processes" or "Not enough core" point to resource shortages, such as "not enough swap space", or "process table too small". Refer to your UNIX documentation for more details.
8.4.3 Printer interface errors and status messages
Since, under PCShare, printer interface programs are referenced by the logical (UNIX) printer name rather than their real name (such as "smbif" or "pcif") it is necessary to look up the real program name (e.g."epson" or "deskjet") in the "$PCDIR/if/" directory. The following section describes errors using the real program names.
8.4.4 Messages shared by all printer interfaces
The following messages can be issued by any of the printer interfaces, no matter if issued by PCShare or EtherShare:
Usage: %s [-n user] [-h host] [acctfile]
The interface program "%s" was called with missing or wrong parameters.
Cannot create an unique log filename: %m
A temporary file name for saving error output until the real error message file has been established could not be determined. System call failure.
Cannot open log file `%s': %m
The temporary file "%s" for saving error output until the real error message file has been established could not be created. System call failure.
Cannot initialize library libsched.
The "libsched" shared library could not be initialized. Mostly a system call failure.
Cannot initialize library libhelios: Error %d
The "libhelios" shared library could not be initialized. Error is given in "%d".
Cannot find product locations: %s
None of the locations (directories) of the HELIOS products were found. "%s" is an explanatory error message.
Cannot find HELIOS PCShare product location.
The HELIOS PCShare product location (directory) could not be found. Mostly an installation error.
Cannot find executable '%s'.
The executable program could not be found. Mostly an installation error.
Cannot open resource '%s': %s
The named resource "%s" could not be opened. "%s" is an explanatory error message.
Cannot initialize library libprint: %s
The print support library could not be initialized. "%s" is an explanatory error message.
Cannot initialize resource messages '%s': %s
The message string handling for the message block "%s" could not be initialized. "%s" is an explanatory error message.
License initialization failed
License code init failed. Mostly a lack of system resources.
License file is seriously corrupted.
No valid license could be found in the license file.
The license found is not valid.
The printer does not have an entry the "/etc/printcap" file.
Missing spooldir entry in printcap
The printer has an entry in the "/etc/printcap" file but lacks the information about its spool directory.
Error while restarting lpd
A fatal error occurred while restarting the line printer daemon. Mostly a UNIX system failure caused by a lack of system resources or an already running "lpd".
The current print job does not have a control file. This may occur in case a printer interface program is started manually and not by the "lpd".
No history information found
The current print job should have a history entry in its control file but none is found. This occurs with damaged control files either created while the system was out of resources or manipulated manually.
The printer requested has no entry in "/etc/printcap".
The capability requested is not listed in the printer's capabilities.
The line printer daemon process issued the output "%s" while starting or handling requests. This output normally is an error message and indicates a serious problem of the "lpd" system.
Allocation of %d bytes failed: %m
A memory block of "%d" bytes could not be allocated. This indicates a lack of virtual memory.
Cannot parse filename '%s'
The file name "%s" could not be parsed into its key and path parts. This indicates a configuration error of a preference value.
The file "%s" could not be opened. This indicates an access problem either because the file does not exist or there are not enough privileges to open the file.
Cannot find spool directory for printer '%s': %s
The spool directory for printer "%s" does not exist. "%s" is an explanatory error message.
Cannot open printer queue '%s': %s
No information could be gathered for printer queue "%s". This indicates a configuration error. "%s" is an explanatory error message.
Cannot query status for queue '%s': %s
The status of the printer queue "%s" could not be determined. This indicates a configuration error. "%s" is an explanatory error message.
Cannot read control file for current job: %s
The control file of the current print job cannot be read. This indicates a damaged or missing control file. "%s" is an explanatory error message.
Cannot rewrite control file '%s': %s
The modified print job's control file could not be written. This indicates a UNIX system call failure. "%s" is an explanatory error message.
Cannot open job history file '%s': %m
The print job's history file could not be opened due to a UNIX system call failure.
Cannot seek in job history file '%s': %m
The print job's history file could not be sought due to a UNIX system call failure.
Cannot seek in job log file: %m
The print job's message log file could not be sought due to a UNIX system call failure.
Cannot write to job history file '%s': %m
Writing to a print job's history file failed due to a UNIX system call failure.
Cannot write to job log file: %m
Writing to a print job's message log file failed due to a UNIX system call failure.
Cannot add job history to control file: %s
The job history file entry could not be appended to a job's control file. "%s" is an explanatory error message.
Cannot find resource '%s': %s
The HELIOS resource "%s" could not be found. This indicates a corrupted program file. "%s" is an explanatory error message.
Information on an open file could not be retrieved due to a UNIX system call failure.
Cannot disable queue after fatal error: %s
The status of the printer queue for the current job could not be changed. "%s" is an explanatory error message.
Cannot copy job to error queue: %s
The current print job could not be copied to the error queue after job completion. "%s" is an explanatory error message.
Cannot restart error queue: %s
The error queue could not be restarted after a job had been copied. "%s" is an explanatory error message.
Cannot mail to print job initiator: missing user name
A printer interface program could not send mail to a print job's originator because the originator is unknown.
A printer interface program could not find the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
Cannot read from job log file: %m
A UNIX system call error occurred while reading from the job's message log file.
Error while opening mailer: %m
A printer interface program could not start the required program for delivering mail to a print job's originator. This is mostly caused by an inappropriate system installation.
Error while writing to mailer
A UNIX system call failed while piping data to the mailer program. This is mostly caused by an unexpected abortion of the mailer program due to e.g. a lack of resources.
Cannot copy data to '%s': %m
A UNIX system call failure occurred while copying data to a file or location "%s".
Error while writing to '%s': %m
A UNIX system call failure occurred while writing data to the file "%s".
Cannot reopen file '%s': %m
A UNIX system call failed while trying to reopen the just created file "%s".
Cannot open file '%s': %m
A UNIX system call failed while trying to open the file "%s".
Cannot open pipe to '%s': %m
A UNIX system call failed while trying to open a pipe to the program "%s".
A UNIX system call failed while reading data from a file.
A UNIX system call failed while writing data to a file.
Cannot parse PostScript: %s
An error occurred while parsing PostScript data. "%s" is an explanatory error message.
Cannot create temporary string stream: %m
A UNIX system call failed while creating a temporary stream.
Unknown or illegal option '%s'
The unknown or illegal option "%s" was supplied to a printer interface program.
Cannot read directory '%s': %m
The UNIX directory "%s" could not be enumerated due to a UNIX system call failure.
Missing version in procset file '%s'
The procset file "%s" does not contain a version string and therefore is ignored.
Cannot move font to fontlist: %s
An error occurred while moving font information between internal lists. "%s" is an explanatory error message.
Your print job has been interrupted.
A print job has been canceled by user request.
Printing disabled due to a fatal error. Please inspect system and printer logs.
A fatal error occurred while initializing a printer interface program. This error will be a persistent system failure and would cause the following print jobs also to fail. Therefore the printer queue has been stopped until the cause of the failure has been eliminated. The queue has to be restarted manually.
Error on printing device:
A serious error occurred on a printing device. More error output follows this message.
Warning: Cannot set RSS limit to %d kB: %m
The "Resident Set Size" UNIX parameter could not be changed to "%d Kilo bytes".
An internal execution operation failed. This mostly occurs in case the system is low on virtual memory. More error output follows after this text.
