HP moved a program that is referenced in some HP PPDs. If you are using the ExtremeZ-IP PPD download capability this is an issue if you need to support both Leopard and pre-Leopard clients with the same PPD.
Why do some Intel Macintoshes fail to reconnect to the server after a temporary loss of network connectivity?
A bug in the Macintosh OS X Finder prevents clients logging in with the Kerberos authentication mechanism from an Intel Macintosh from reconnecting to the server. Users that have temporary network connectivity issues will not automatically reconnect to the server, and instead will need to manually re-login to the server. All changed documents they had open at the time of the incident will be lost and the files may be corrupted.
Why is one client computer much slower than all the others?
The primary cause of network issues that we receive support calls about is a mismatch between the Ethernet speed and duplex negotiated by the switch and that of the Macintosh client. In some cases we find that it is actually the server that has the duplex mismatch. Either of these issues can be fixed by hard-coding the speed and duplex of the switch and Ethernet card.
Particular port configurations may allow invalid printers to be built on Mac OS X via Bonjour.
By default ExtremeZ-IP will accept inbound print jobs on port 515. This can be changed in the ExtremeZ-IP Administrator via the Print Server Settings tab in the Settings dialog box. Changing this setting can break some Bonjour printers.
When receiving forwarded files, the replacement permissions for the sender apply, not the replacement permissions for the originating user.
When a forwarded file is received that duplicates a file already in the Received mailbox, the replacement privileges of the sender of the file, not the originating user, are used to determine whether to reject the incoming file or overwrite the existing file.
If ExtremeZ-IP encounters a crash, sometimes the best source of information is retrieved from a Dr. Watson Log. Dr. Watson gathers stack information and obtains symbols from ExtremeZ-IP to aid in figuring out where the crash occured.
For Dr. Watson to work, it must be "installed" as the default application debugger. Upon reboot this information can be lost and when a crash does occur Dr. Watson may not catch the crash. This document will explain how to configure Windows so Dr. Watson is allways installed on startup.
MassTransit may report error messages when sending certain files to WAM!NET Address Book contacts. These files may contain illegal characters that are valid on Macintosh or Windows platforms.
WAM!NET has its own rules for valid filenames. When sending or receiving files via WAM!NET that have not followed WAM!Net rules, the files will not be transferred. Please check the WAM!NET user manual for complete information. To make certain that all files are successfully transferred, please follow these rules regarding file naming:
mobilEcho is the industry’s first and only Mobile File Management (MFM) software for enterprise iPad users. mobilEcho enables enterprise IT to provide secure access to enterprise file servers for iPad users, eliminating the need for work-arounds like emailing files to yourself or storing critical enterprise files in unsecure third-party cloud providers.
Illegal file/folder names and conventions for the following operating systems: Windows Mac OS 9 Mac OS X
======================== EXPLANATION & OVERVIEW
In the realm of cross-platform file sharing, sometimes the end users are not aware of the limitations posed by the operating system. This article will explain which characters can cause problems with files that use these characters.
mobilEcho clients connect to mobilEcho servers on port 443 by default.
If the mobilEcho server that contains your home directory shared volume(s) is configured to use a port other than 443, you will need to create a Network reshare path mapping that points to the correct mobilEcho server and share on the correct port. This will allow the mobilEcho client to know to connect to the server on the non-default port.
Versions 3.5, 3.5.1, and 3.5.2 of the mobilEcho iOS app use an encrypted database to manage the files stored within the mobilEcho app's on-device storage. The information required to access this database is stored in the iOS keychain. For security reasons, mobilEcho's keychain items are not restored to the new device during the backup and restore process.
How can I move the activEcho FileStore to a non-default location?
In our example we will use a FileStore running on the default port of 5787 located at “C:\Program Files (x86)\Group Logic\activEcho Server\FileStore” and we will be changing it to be located at “E:\activEcho Data\FileStore” but keep the port the same.