Posts Tagged ‘Windows’

Using ArchiveConnect with ExtremeZ-IP Network Reshare

Wednesday, June 6th, 2012

Introduction

ArchiveConnect is fully compatible with ExtremeZ-IP 8.0’s new Network Reshare capability. This feature expands the options for giving Macs access to archive volumes on SMB accessible storage and also provides an excellent workaround for known issues with Mac clients running OS X 10.6.7 and later accessing SMB/CIFS archive volumes.

Network Reshare and ArchiveConnect provide a solution for accessing file archives on NAS storage

Due to an issue in Mac OS X 10.6.7 and later, Macs connecting to SMB accessible archive volumes on file servers or NAS storage are not able to properly recall files. This issue is fully detailed in this related knowledge base article.

By utilizing ExtremeZ-IP Network Reshare to make file archives, previously only available through SMB/CIFS connections, available to Macs using the standard AFP file sharing protocol, this issue can be avoided and Mac file recall behavior is properly managed by ArchiveConnect over the AFP connection.

Additional ArchiveConnct features included in ExtremeZ-IP also provide advantages to using AFP Network Reshare vs. using direct SMB access from Mac clients. An example is a configurable color label that indicates which files shown in the Finder are currently offline.

NetApp specific benefits to using ArchiveConnect with Network Reshare volumes

Before ExtremeZ-IP 8.0 with Network Reshare, Mac SMB access to NetApp archive volumes required the “Assume all SMB files are offline” setting to be configured in ArchiveConnect. This is not necessary when they are reshared through ExtremeZ-IP, so Mac users retain the ability to see thumbnail icons and quick look previews for files that are already online.

Accessing DFS files using ExtremeZ-IP Network Reshare

Wednesday, June 6th, 2012

Introduction

Prior to the release of version 8.0, ExtremeZ-IP supported Mac AFP access to Microsoft Distributed File System (DFS) file shares in several ways. Traditional ExtremeZ-IP DFS support requires one or more DFS namespaces to be added to the DFS tab in the ExtremeZ-IP Administrator’s Settings window. Then, Mac clients must be set up with one of the following options:

  • – The “Zidget” Dashboard widget – Used to browse DFS namespaces and mount specific resources within them.
  • – The ExtremeZ-IP “DFS Client” application – Used to allow mounting of DFS volumes in the Finder and browsing of the related DFS namespace, similar to the experience Windows presents to users.
  • – Manual modification of the Mac’s “auto_master” file – Provides the same experience as the DFS Client option, but requires editing a standard Mac config file rather than installing client software.

All of these options require client side software or changes on each Mac that requires access to DFS.

ExtremeZ-IP 8.0’s Network Reshare feature introduces an additional option for providing Macs with access to DFS resources. Network Reshare allows ExtremeZ-IP AFP file volumes to give access to folders located on other servers and NAS devices on your network. Macintosh clients continue to connect to ExtremeZ-IP using the standard AFP file sharing protocol, while ExtremeZ-IP utilizes the SMB/CIFS file sharing protocol to access files that are requested by Mac users from remote servers and NAS systems. By doing so, Mac users retain all the benefits of AFP file sharing while gaining access to resources that have traditionally only been available through SMB/Windows file sharing.

DFS shares can be configured as ExtremeZ-IP Network Reshare volumes. DFS target resolution simply occurs in the SMB reshare communication layer and Macs are able to seamlessly browse and access the reshared DFS resources presented in a standard AFP volume. No Mac client-side software or changes are required. Macs simply connect to ExtremeZ-IP AFP Network Reshare volumes in the Finder and can immediately browse the DFS namespace.

For more details on Network Reshare, see our Configuring Network Reshare support in ExtremeZ-IP knowledge base article.

Limitations

ExtremeZ-IP Server acts as DFS client
When hosting a Network Reshare DFS volume, the ExtremeZ-IP Windows server makes requests for resources located in DFS namespaces on behalf of the the Mac client. From the perspective of DFS, the Windows server itself is the client, not the actual Mac user making the request. For this reason, all DFS target selection and site costing will be negotiated for the Windows server, rather than the Mac client.

All Network Reshare communication is routed through the ExtremeZ-IP Windows server
Network Reshare routes all communication between your Mac clients and your DFS namespaces through the Windows server where ExtremeZ-IP is installed. This requires an extra network hop compared to the Mac client accessing DFS targets directly. For the best possible performance, it is recommended that ExtremeZ-IP is installed on a server with the fastest available NICs, and ideally this server has one or more NICs dedicated to communicating with the servers, NAS, or DFS namespaces being reshared.

ExtremeZ-IP Network Reshare feature and Network Reshare DFS volume configuration

For full details on configuring your ExtremeZ-IP server for Network Reshare and instructions on setting up a Network Reshare DFS volume, please see our Configuring Network Reshare support in ExtremeZ-IP knowledge base article.

Is MassTransit Web Client plug-in compatible with 64-bit versions of Windows and Mac OS?

Monday, June 14th, 2010

Summary:

Group Logic supports MassTransit Server on Windows 64-bit platforms. Currently, version 7.0.1 of the MassTransit Web Client plug-in (available for the latest MassTransit HP 7.0.1 Servers) is supported for Safari in 64-bit mode but it is not supported for Internet Explorer running in 64-bit mode. MassTransit Web Client plug-ins prior to version 7.0.1 are not supported for Internet Explorer and Safari browsers running in 64-bit mode. However, you can use the MassTransit Web Client plug-in on a 64-bit operating system by running the browser in 32-bit mode.

If you do not want to switch your browser to 32-bit mode and the HTTP transfer method is available on the server, you can use it to transfer files with the MassTransit Web Client. To use HTTP click, the “Switch to use HTTP” link on the Send Files or Download Files page. For information about how to configure the HTTP transfer method, see the “Windows Web Configuration Instructions” document on the MassTransit Latest Releases page.

If you are using Mozilla Firefox, you shouldn’t have any problems with MassTransit Web Client on 64-bit Windows and Mac, since all current versions of Firefox released by Mozilla are 32-bit.

Description:

To use MassTransit Web Client 7.0.1 via Internet Explorer on 64-bit operating systems, you must run Internet Explorer in 32-bit mode. If you use MassTransit Web Client prior to version 7.0.1, you must run Internet Explorer or Safari in 32-bit mode. The 64-bit platforms of Window and Mac have both the 32-bit and 64-bit versions of Internet Explorer and Safari available.

Set Internet Explorer 8 to run in 32-bit mode on 64-bit Windows

The 32-bit version of Internet Explorer is available in the Start menu. Commonly, the 32-bit Internet Explorer is the default browser. However, some programs will automatically launch the 64-bit version of the browser. To check which version of Internet Explorer is currently running open the Help menu in IE and select About Internet Explorer. If you are running the 64-bit browser, it will say “64-bit Edition“ after the version number. In this case, close Internet Explorer and:

  1. Go to the Start menu->All Programs
  2. Run the 32-bit version of the browser by clicking on the Internet Explorer application.

Set Safari 5 to run in 32-bit mode on 64-bit Mac OS

To run Safari 5 in 32-bit mode:

  1. Quit Safari if it is running.
  2. Open Applications.
  3. In Applications, highlight the Safari application and press Command (Apple) key+I, or open File->Get Info.
  4. In the Safari Info window, mark the Open in 32-bit mode check box and close the window.
  5. Restart Safari.

Now, you can download the MassTransit plug-in for the Web Client and use it to transfer files.

For more information about the MassTransit Web Client plug-in of MassTransit 7, please refer to the Web Client User Guide.

MassTransit 6.1.x Web Client plug-in with Firefox 3.6 displays the drag and drop area all black (Windows only)

Tuesday, April 6th, 2010

Symptom:

If Firefox 3.6 for Windows is used with the MassTransit Web Client plug-in to log into a MassTransit server, the “drag and drop” area of the “Send files” tab appears black.

Steps to reproduce:

Launch Firefox 3.6 and log in to the server with a web client account.

When you log in, select the plug-in transfer mode, if not selected.

Select the “Send files” tab and observe the “drag and drop” area. It is displayed black.

Fix:

An update for the MassTransit server resolves this visual glitch with Firefox 3.6. A MassTransit administrator can download the webclient.zip file, extract it, and place it in the ~Group Logic\MassTransit Server 6\MTWeb\webroot\css folder.

Restart the web browser.

Next time you log in to the server via Firefox 3.6, the drag and drop box will appear correctly, displaying the “Drag files here” text.

Error: Incorrect Key File For Table [Windows]

Wednesday, January 23rd, 2008

Summary:

The MassTransit Engine may inadvertently shut down, and will not properly restart. Within the Application Log of the Windows Event Viewer, the following error message may be displayed:

SA_Exception[xxxx]: DB_Files_Edit: Incorrect key file for table ‘tablename‘; try to repair it.

Commonly, tablename may be referenced as ‘dfiles’

Description:

This error indicates that the table listed within the error message has become corrupt, and must be repaired. In most cases, the table can easily be fixed with through the MySQL command line. Follow this procedure to repair failed tables:

  1. Open a Windows command prompt
  2. Navigate to the MySQL monitor command-line utility, which may be found at this location:
    C:\Program Files\MySQL\MySQL Server X.X\bin
  3. Invoke the MySQL monitor utility with the following command:
    mysql -uroot -p
  4. Enter your root password as specified during the initial installation of MySQL server.
  5. After successfully logging in, you should see a ‘mysql>’ prompt.
  6. At the ‘mysql>’ prompt, type the command: repair table tablename quick;
    NOTE: tablename should be the name of the table listed in the Event Viewer error message, such as dfiles. Note also that the semi-colon character (;) at the end of the statement is required.
  7. When the repair process is completed, the results of the process will be displayed within the terminal.
  8. You may now close your terminal window.

The status message should indicate that the repair status was successful by indicating “OK.” If any further errors result, it is important to contact Group Logic technical support for additional troubleshooting and repair instructions.

After a successful repair has been completed, you may now be able to restart your MySQL Service, followed by the MassTransit Engine Service.

Upgrading MySQL from 4.x to 5.0 – Microsoft Windows

Monday, September 10th, 2007

Summary:

MassTransit 5.1 and later introduce support for MySQL versions 5.0 and greater, which allows for faster performance, better management, enhanced data integrity, improved security and additional replication services. MySQL 5 is the default database for MassTransit 5.1 and later. Group Logic recommends that customers using previous versions upgrade to take full advantage of these added capabilities.

Description:

Please see the attached document for information on updating MySQL to version 5.0 for use with your MassTransit installation on Microsoft Windows.

Related Document: