Component	Requirement
Processor	Intel or AMD single core x64
Memory	256 MB of free memory
Hard drive	700 MB of free disk space
Screen resolution	800 x 600 pixels or higher

Dualog® Link Activation Codes - Getting Started

INTRODUCTION

The new Activation Code feature will aid you in automating and streamlining Dualog Link client registration on board your ships.
After adding a ship or office to an organization, users can now generate an activation code that can be used as a parameter to automatically register and activate a Dualog link client under the installation tab.

Using these codes, you can now deploy the Dualog Link Client on any ship or office using a single command line.
The client will then be visible on the Dualog Portal, linked to the cloud, and ready to be used in any of our Dualog Link services.

This guide will show you how to activate the Dualog Client on a single vessel/office.
This procedure can be repeated as many times as necessary.

REQUIREMENTS

A valid account on the Dualog Apps portal.
A vessel or office created in your organization that the Dualog Link Client and services will be installed on.

GETTING STARTED

Upon logging into the Dualog Apps portal, click on the hamburger menu located in the top left corner > Installations (Direct link here)
Under Activation codes > click on "Create activation code".
Under Locations, select the vessel that you would like to activate and register the Dualog Link Client through the drop-down options.
Create code
A 10-character alphanumeric string will be created (Not case-sensitive)

Note:

By checking on "Allow multiple activations", the created code can be used for more than one Dualog Link Client activation.
Pre-registered installation is used when activating installations without logging on to each computer. A pre-registered installation will be valid for 7 days after registration.

DELETION OF EXISTING ACTIVATION CODES

Upon logging into the Dualog Apps portal, click on the hamburger menu located in the top left corner > Installations (Direct link here)
Click on the activation that you would like to delete
Click on the trash bin icon > Confirm
The activation code is now deleted.

INSTALLATION AND ACTIVATION OF DUALOG LINK CLIENT

For a manual standard installation, click here for more information.
For a silent installation, click here for more information.

In case you have faced difficulties or have further inquiries on any of the above, get in touch with Dualog Support.

Dualog Antivirus - End of Life notification

INTRODUCTION

Dear Customer,

Dualog Endpoint will replace the Dualog Antivirus service.
Dualog Antivirus Distribution service has reached end-of-life and will be formally retired on November 30, 2023. This aligns with our partner’s, ESET, announcement to stop supporting its legacy antivirus updates distribution.

Dualog Endpoint is a more comprehensive and efficient approach to cybersecurity, providing greater protection against malware, phishing, and ransomware attacks. It also offers enhanced visibility and control over endpoints, enabling administrators to monitor and manage devices more effectively and respond to real-time security incidents.

MIGRATION FROM DUALOG ANTIVIRUS TO DUALOG ENDPOINT

The following article has been written in the interest of better helping our valued existing customers with the required migration:

Dualog® Endpoint - Getting Started

If you need any additional help or have any other questions about the new Dualog Endpoint service or the migration, don't hesitate to contact Dualog support anytime.

Dualog Endpoint license upgrade
Dualog will provide the license upgrade from Dualog Antivirus to Dualog Endpoint without additional license fees. This allows for a smooth transition process without needing company budget adjustments.

We appreciate your understanding of the need for this measure for continued and increased security, and we once again thank you for your support and trust in Dualog.

Dualog® Endpoint - Getting Started

INTRODUCTION

Dualog Endpoint is a comprehensive and efficient approach to cybersecurity, providing greater protection against malware, phishing, and ransomware attacks. It also offers enhanced visibility and control over endpoints, enabling administrators to monitor and manage devices more effectively and respond to real-time security incidents.

Superior protection requires more updates. Dualog Endpoint updates will be distributed daily to provide effective protection against modern threats. On average, Dualog Endpoint will utilize approximately 3 GB of data each month.

PRE-REQUISITES

Ensure that the firewall on the ship is configured to allow the following:

Protocol: TCP
Ports:
- 2222 (For configurations & reporting)
- 2223 (For updates)
- 443 (For Dualog portal)
Direction: From ship to shore
Destination: apps.dualog.com and 93.188.232.76

Dualog Network Control users can add this rule directly on the Dualog Portal. Refer to the article Network Control: Firewall Rules for further details.

GETTING STARTED

Please note that both Dualog Link Client and Dualog Endpoint have to be installed on every single machine that you wish to protect with Dualog Endpoint.

Install and activate the Dualog Link client
- For both new and existing customers:
  - Please download and run the latest client installer > tick on Dualog Endpoint Security service > complete the installation
Install and activate the Dualog Endpoint Service

FOR EXISTING CUSTOMERS ON ANTIVIRUS 6.5

This procedure will also uninstall the obsolete Antivirus ESET 6.5, if present on the machine. This means that there is no need to manually uninstall ESET 6.5 before installing Dualog Endpoint.

Please also ensure that the old Antivirus ESET 6.5 service has been disabled on the Dualog Portal after the successful migration to the new Dualog Endpoint via the following steps:

Click on Antivirus on the default main page (Alternatively, go to Connection Suite > Antivirus)
Click on Configuration > Select the vessel that needs to be disabled for Antivirus 6.5
Under Antivirus Status, select Disabled
Proceed to disable Antivirus

For more information, view the most latest Product Webinar here.

Dualog® Protect - System Requirement

FIREWALL CONFIGURATION

Dualog® Protect has its own set of system requirements that must be met in order for an installation or deployment to be successful.

Client registration and client-server communication require an internet connection. A functioning DNS server configuration is also required to ensure a smooth operation. If DNS traffic is blocked, a custom DNS entry, to resolve "apps.dualog.com" as described below, is required to complete the installation and registration. The following destinations must be reachable in order to register the client to the Dualog Cloud:

Destination: apps.dualog.com
IP address: 93.188.232.76
Port(s): 443
Protocol: TCP/UDP

Dualog® Protect uses different IP addresses according to your chosen tier. Make sure the following is whitelisted:

Secure: 93.188.235.5 | 93.188.236.5
Basic: 93.188.235.6 | 93.188.236.6
Moderate: 93.188.235.7 | 93.188.236.7
Strict: 93.188.235.8 | 93.188.236.8
Blacklist: 93.188.235.9 | 93.188.236.9
(to make it easy you may want to whitelist 93.188.235.0/24 and 93.188.236.0/24)

Port(s): 15353
Protocol: TCP/UDP

Dualog® Protect - Getting Started

INTRODUCTION

Dualog® Protect stops most malware, ransomware, trojan, and phishing attempts, ultimately blocking unsafe or suspicious internet resources before any harm is done by monitoring all activity at the DNS level.

This article will get you started with deploying Dualog® Protect on your fleet.

The service is easy to set up and configure to your requirements for what types of content you wish to block.

PREPARATION STEPS

You will need a couple of things in place before you get started with the installation of Dualog® Protect.

You will need a valid account on the Dualog portal.
Make sure all necessary IP and ports are whitelisted on your firewall(s)
You have created at least one Dualog Protect policy to assign to your ships
Dualog Link Client has been installed and activated on the required machine.
Disable any existing DNS service on the PC where Dualog Protect will be installed. Typical examples
- Any external DNS relay/forwarder
- If you are running Network Control, go to Connection Suite > Network Control > Configure Network Control > choose the ship.
- Make sure to disable DNS Relay and save.

INSTALLATION

Dualog® Protect can be installed on any client PC on board, as long as the system requirements are met. If you are running Active Directory on your ship, Dualog Protect cannot be installed on the Domain Controller as it would create a DNS loop.

Typically, you want to install Dualog Protect on a PC or server that is reachable from all onboard subnets that you wish to protect. If you are running Dualog Network Control, that PC is a good candidate to install Protect. If unsure about where to install it, get in touch with us. We will be happy to help.

The standard installation process is described here. Follow the procedure and, once completed, continue with the steps below to complete the deployment of Dualog Protect.

ASSIGN THE DUALOG PROTECT POLICY

You can now proceed to assign the ship to your Protect policy. Go to the Protect "Configuration" tab. Now click on “Assign” and make sure your ship is ticked for this policy.

DNS ROUTING

Dualog Protect is now active and ready to handle the DNS requests on board.

ON THE DUALOG PROTECT PC

Make sure your WAN network adapter uses 127.0.0.1 as primary DNS.

ON ALL THE CLIENT PCs

Any client PC you wish to protect will need to have the Dualog Protect PC's IP address as their primary DNS server.

You can now go ahead and test Dualog Protect.

Dualog® Drive - System Requirements

FIREWALL CONFIGURATION

Client registration and client-server communication require an internet connection. A functioning DNS server configuration is also required to ensure a smooth operation. If DNS traffic is blocked, a custom DNS entry, to resolve "apps.dualog.com" as described below, is required to complete the installation and registration of Dualog Drive.

The following URLs or IP addresses must be accessible:

Destination: apps.dualog.com
IP address: 93.188.232.76
Port(s): 443 and 4443
Protocol: TCP/UDP

In addition, additional IP ports must be open/blocked for carrier detection.

FILE SHARE AS SOURCE OR DESTINATION FOR DRIVE TASKS

Dualog Drive uses SMB to access file shares/file servers. Supported SMB versions are 2.02, 2.1, and 3.0.

Samba 2.1 is required. Do make sure that it is enabled. For more information, please check Microsoft Documentation.

As a minimum, port 445 (TCP) must be open in the firewall to allow traffic between the Drive computer and the fileserver. Depending on the SMB version and Operating systems, ports 137 & 138 (UDP) and 139 (TCP) might be required to open as well.

Be aware that opening 137 and 138 is a security risk. We highly recommend upgrading to a newer Operating system.

SUPPORTED OPERATING SYSTEMS

The following operating systems are supported:

Windows 7 SP 1 (*)
Windows 8.1 (*)
Windows 10 (version 1607) or later
Windows Server 2008 R2 SP1 (*)
Windows Server 2012 SP1 (*)
Windows Server 2012 R2 (*)
Windows Server 2016 or later

(*) Microsoft Visual C++ 2015 (x86) is required for Windows 8.1/Server 2012 R2 and older. Do make sure it is installed. For more information, please check Microsoft documentation.

HARDWARE REQUIREMENTS

Hardware requirements like CPU, memory, and disk space are very dependent on the type of tasks and number of tasks. As an example, a computer only handling small files to be replicated to shore will not have the same requirements as a computer handling multiple tasks where large amounts of data are received from hundreds of clients.

To reduce bandwidth usage, the protocol for Sync tasks stores data chunks on disk. This data storage will grow, so prepare the disk space to be able to handle approx double the expected data volume to be synchronized.

Required disk space must be calculated based on knowledge of expected data volume.

Recommended disk space: 1TB

SUPPORTED WEB BROWSERS

Registration page (localhost:5000)

Browsers tested OK:

Firefox
Chrome

Browsers not fully supported but functioning:

Internet Explorer
Microsoft Edge

Other browsers (Ex Safari) have not been tested.

Shore Portal (https://apps.dualog.com)

Supported browsers:

Firefox
Chrome
Microsoft Edge

Browsers not supported:

Internet Explorer

Dualog® Drive - Getting Started

INTRODUCTION

This article provides a step-by-step guide on getting started with Dualog® Drive and experiencing the benefits first-hand.

PREREQUISITES

A valid Dualog portal account (Click here to sign up)
An existing organization within the Dualog portal (You can create one upon successful registration of an account)
One or more 'vessels' and 'office' in the portal to use for your testing
One Windows PC per vessel and office to install on (Later versions of Windows 7 or newer)
A modern web browser on the PCs to do the client registration
A user in the Dualog Portal with access to your organization
The following needs to be allowed by the firewall (if applicable)
- - Destination: apps.dualog.com
  - IP address: 93.188.232.76
  - Port(s): 443, 4443
  - Protocol: TCP/UDP

Click here for the complete details of Dualog® Drive's system requirements.

GETTING STARTED

1.1 - SETTING UP
Every Drive task needs two things: One or more vessels and an office.

Expand the top left menu > Organisation
Click on "Add Ship" under Ships > New Setup > Continue
Fill in the necessary fields > Add Ship (Note: Depending on your preferences, this could be a test vessel or a live vessel)
Click on "Add Office" under Offices > Enter office name > Add Office

If you wish for your office to be a SharePoint integration, click here to find out more.

1.2 - INSTALLATION

Dualog® Drive can be easily installed in 5 minutes using Dualog Client Installer.

This must be installed on the endpoint(s)/machine(s) with which you plan to test Dualog® Drive.

The installation is very straightforward and will take you through the following steps:
- - Double click the installer to run the initial installation
  - Pick only Drive when prompted to select products
- The local webpage will open to continue the installation. If it does not open, go to http://127.0.0.1:5000
  - An automated connectivity test will run to ensure it can do all resolving
- Client registration
  - You'll be prompted to log in with your portal user
  - Select the vessel you wish to install the client under
  - Give the client a name that has meaning to you, e.g. "Captain's PC"

More detailed installation instructions can be found here

1.3 - TASK CREATION

You are now ready to create your very first Drive task!
1. Expand the top left menu > Drive
2. To learn more about each type, the differences, and use cases, click on "Read about the sync task" and "Read about the move task."

Recommendation:

Before proceeding with further experimental tests, begin with a simple Move Task between the newly created vessel and office to learn more about the core concept of Dualog® Drive.

1.4 - LET'S TEST!

Now that you have successfully completed the above steps, the folder(s) that you have previously created on the individual task should now populate automatically on the respective installations.
1. Place a file within the folder of the source installation and watch the magic happen!
2. The file should disappear for a brief moment before reappearing in the destination installation's folder.

Feel free to play around with both types of Drive tasks to get a sense of the various options available, as well as a better understanding of the differences between what Move and Sync tasks have to offer.

ADDITIONAL RESOURCES

If you wish to lean back and watch a video, you can watch a good webinar on Dualog Drive here.

You can also read this great e-book on the top 5 use cases of Dualog Drive here.

Dualog Access - Getting Started (For Devs)

GETTING STARTED

The first thing to determine is which grant or flow to use. This depends on the type of application and your evaluation of security risks.

Recommended grants to use on different application types:

Application Type	Preferred Grant Type	Alternative Grant Type
Native	Resource Owner Password	PKCE
Mobile	PKCE	Implicit Flow
Traditional	Authorization Code	-
Single-Page Web	PKCE	Implicit Flow
Machine-To-Machine	Client Credentials	-

Some important questions to ask:

Where and how to enter username/password:
- Provided in the application.
- Redirect to web page supplied by the Identity Server.

Do you have multiple applications and do you plan to implement a single sign-on?
Are you planning to use Multi-factor authentication?
- MFA is currently not supported by Dualog Access but will be supported in a later version.
What does it take to change your applications?
How is authentication implemented today, where are users stored, and do you foresee a major redesign?
Other considerations to take?

RESOURCE OWNER PASSWORD

Version 1.x of Dualog Access only supports this grant type. In a later version, other grant types will be supported as well.

The Resource Owner Password flow allows exchanging the username and password of a user for an access token.

BASIC STEPS

Ask the user for their credentials.
- The first the application should do is to ask the user for their credentials.
Exchange the credentials for an access token
- The application must make a POST request to the Dualog Access service for an access token providing the credentials and client information.

Required POST parameters:

grant_Type - value must be “password” for this flow.
scope - One or more registered scopes. If not specified, a token for all explicitly allowed scopes will be issued. Available scopes: “OpenID”, “profile” and “email”
client_id - The client identifier. This will be provided by the organization owner. This value corresponds to the value configured for this application on Dualog Portal.
client_secret - This is a secret provided by the organization owner. This value corresponds to the value configured for this application on Dualog Portal.
username - The username provided by the user.
password - The password provided by the user.

EXAMPLE (WITH CURL)

curl -d "grant_type=password" \
-d "client_id=nameoftheclient" \
-d "client_secret=thesecret" \
-d "username=test%40test.com" \
-d "password=_password_" \
https://url

If the user-provided credentials are successfully authenticated, an access token will be returned from the Dualog Access service containing an access token:

{
"issued_at":"0101990561212",
"signature":"SF132DFG3434DFGS345SFL=",
"access_token":"the_access_token"
}

Dualog Access - Technical Requirements

BASIC REQUIREMENTS

Version 1.x of Dualog Access uses the account database in Dualog Connection Suite. Hence, both Dualog Access- including the Dualog Link Platform - and Dualog Connection Suite must be installed. Dualog Access must have privileges to read the Connection Suite database.

All applications/computers/devices from where users will log in must be able to contact the computer running Dualog Access.

Version 1 of Dualog Access only supports one Grant type, the Resource Owner Password Flow. This is the flow normally used for native applications.

SUPPORTED OPERATING SYSTEMS

The following operating systems are supported:

Windows 7 SP 1
Windows 8.1
Windows 10 Anniversary Update (version 1607) or later
Windows Server 2008 R2 SP1
Windows Server 2012 SP1
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019 (For more information, please check Microsoft documentation:)
- https://docs.microsoft.com/en-us/dotnet/core/windows-prerequisites?tabs=netcore21

Dualog® Fetch - Introduction

INTRODUCTION

Dualog Fetch is a service for collecting syslog data from devices onboard ships. Data gathered will be transferred to the Dualog Fetch cloud and made available in message queues for authorized shore receivers.

OVERVIEW

The figure shows an overview of the components composing Dualog Fetch:

The Fetch Client is installed on ships to receive syslog data from devices broadcasting this data on port 514. Based on configuration the client either adds received messages to the outbound queue – or discards them. The Dualog Fetch client also counts data received (number of lines and bytes) and transfers these numbers to the cloud. Data volume reports are available in the portal.
The Link Platform Client handles the outbound message queue - using the Link Transfer messaging protocol to transfer data to the Cloud. The Link Platform also handles configuration, software updates, Carrier Detection and connection status.
The Cloud Services make sure data is forwarded to the configured outbound queues. It also adds data volume numbers to the Aggregated data database, for viewing in Dualog Portal.
In Dualog Portal, configuration can be added, deleted and modified. Data volume reports is also available in the portal.

SUPPORTED SYSLOG FORMATS

Several SysLog formats exist, all having some nuances in content format. The following syslog message formats are currently supported:

RFC 3164. The message will be converted to RFC 5424 format when this format is recognized.
RFC 5424

The Fetch client parses all received messages to identify devices and filter on severity and facility.

If the message is not recognized with a supported SysLog format, an RFC 5424 message is created, with the content added to the message section. It will be up to the receiver to extract the details.

Dualog® Fetch - Getting Started

INTRODUCTION

Dualog Fetch is available in the standard Dualog Link Platform installer, available from Dualog Portal. A user account with access to the company is required for login.

For new installations of the Link Platform, the client must be registered on Dualog Cloud. To complete registration, internet access is required.
For existing installations of the Link Platform, the latest Dualog Link Platform installer has to be downloaded and executed, followed by selecting Dualog Fetch during the installation wizard.

Please refer to the system requirements to ensure that the machine fulfills all of them.

Both installations and registrations can be performed in either of the following ways:

CONFIGURATION

Configuration is performed on Dualog Portal. Two separate and independent configurations are required to receive syslog data:

Client configuration. (Basic filtering options to define data to accept.)
Data receiver configuration. (Configuration of outbound queues)

In its basic form, the client configuration is simple. You can either allow all or block all syslog data received.

From there on exceptions can be added, and here it can easily be complicated.

Latest Antivirus download links

INTRODUCTION

On this page, you will find the latest download links for Antivirus and relevant files. Before installing, make sure all system requirements are met.

Click on the link related to the file you wish to download and select where you want to save the file on your PC.

Antivirus 2.38 and above

File/Link	Size	Purpose
AV Server Installer	310Mb	Antivirus Server Installer
AV Base	94Mb	Antivirus signature file

Please follow the links for guides on how to install and uninstall Dualog Antivirus:

Latest Connection Suite Download Links

INTRODUCTION

On this page, you will find the latest download links for Dualog Connection Suite. Click on the link related to the product you wish to download and select where you want to save the file on your PC.

The release notes are available here.

CONNECTION SUITE 3.13 FILES

File/Link	Size	Purpose
setup_x64_3.13.004.exe	495MB	Full installer 64bit (x64), includes Oracle 11G
setup_x86_3.13.004.exe	477MB	Full installer 32bit (x86), includes Oracle 11G
core_setup_3.13.003.exe	173MB	Core setup, installs only Connection Suite
Upgrade_3.00-3.13.004.exe	81.3MB	Upgrade from 3.00 - 3.13
Instant Vessel Kit_3.13.exe	1MB	Clean-up database to a fresh start (This wipes out the mail store as well)
Welcome Guide (Captain).pdf	291Kb	A quick guide on familiarizing with the new user interface
Welcome Guide (Crew).pdf	233Kb	A quick guide on familiarizing with the new user interface

Click here to download the unattended versions of the same installers.

OLDER VERSIONS

If you need an even older version of Dualog Connection Suite, please inquire Dualog Support at support@dualog.com.

Dualog Connection Suite - System Requirements

INTRODUCTION

Dualog Connection Suite consists of a standard package plus optional extensions. This document describes the requirements of different configurations of Dualog Connection Suite, as well as software requirements/support. This document is valid from Dualog Connection Suite version 3.0 and onwards.

CORE INSTALLATION HARDWARE REQUIREMENTS

Please note that these requirements are a minimum.
IMPORTANT: If other applications are running on the same computer as Dualog Connection Suite, higher CPU, memory, and disk capacity apply.

The following requirements apply when running the Dualog Connection Suite Core service only:

CPU	Intel® Core™ i3 or equivalent
RAM	Minimum 2 GB (recommended 4 GB)
DISK SPACE	The installation itself takes approx. 50 GB. In addition data storage (e-mail, log files, File Transfer, database, etc) must be added. HQ graded server disks are highly recommended.
I/O	Serial Ports, Network Adapters according to communication equipment requirements.

E-MAIL

When using the email services (Business Mail and Crew Mail), no further requirements apply to CPU and RAM, while disk requirements will increase. On average, the email services generates approx. 20 GB per year, while backup will add up this space multiplied by 4.

NETWORK CONTROL

To avoid reduced throughput on internal traffic, a CPU with at least four cores is required. The following minimum HW recommendations apply:

CPU	Intel® Core™ i5-2300+ or equivalent
RAM	4 GB
DISK SPACE	Network Control stores data in the Oracle database, with no specific HDD requirements
I/O	A minimum of two network interfaces: one connecting the ship’s LAN and the other to the communications equipment.

SUPPORTED OPERATING SYSTEMS

Dualog Connection Suite Services and Extensions can run on the following Microsoft Operating Systems:

Operating System	Connection Suite Supported
Windows 11 (64-bit)	YES
Windows 10 (64-bit)	YES
Windows 2008 Server SP2 (32 bit + 64 bit)	YES (*)
Windows 2012 Server (64-bit)	YES (*)
Windows 2012 Server R2 (64-bit)	YES (*) KB2919355 and KB2919442 required
Windows 2016 Server (64-bit)	YES (*)
Windows 2019 Server (64-bit)	YES (*)
Windows 2022 Server (64-bit)	YES
Additional Required Software (included in the latest Dualog installer)
Visual C++ Redistributable for Visual Studio 2015 Update 3
.NET Framework 2.0, 3.0, 3.5, or 4

(*)We do not recommend Connection Suite installations on a Windows Server that is also a domain controller.

In all server versions, we recommend that tests and pilots are done before a production rollout, as we are not able to guarantee that all architecture designs will provide the same results.

SUPPORTED BROWSERS

The user interface in Connection Suite is mainly a Non-Flash based webpage and can be accessed via any computer connected to the ship's LAN. The following browsers are tested and highly recommended.

Microsoft Edge (Chromium)	Latest version available
Mozilla Firefox	Latest version available
Google Chrome	Latest version available

Important note: For user log-in and usage of the Internet, Quota Management, and CrewMail (Webmail), HTML5 is supported. Therefore, tablets and smartphones may be used by ship staff to access Connection Suite Services.

Connection Suite Ship - Release Notes

Connection Suite release notes provide information on the features and improvements in each release. This page includes release notes for platform releases and ship releases.

Version 3.13

Connection Suite 3.13 Release Notes

Version 3.12

Connection Suite 3.12 Release Notes

Version 3.11

Connection Suite 3.11 Release Notes

Version 3.10

Connection Suite 3.10 Release Notes

Version 3.0

Connection Suite 3.0 Release Notes

Version 2.39

Connection Suite 2.39.005 Release Notes

Version 2.38

Connection Suite 2.38.000 Release Notes

How to install Connection Suite

INTRODUCTION

This guide describes the necessary steps to install the latest version of Dualog Connection Suite. The PC where Dualog Connection Suite is going to be installed will be referred to as "Dualog PC".

REQUIREMENTS

The Dualog PC must match the current System Requirements.
Any preexisting installation of Dualog Connection Suite and its related modules need to be uninstalled from the Dualog PC. (Including Oracle)
A Dualog Connection Suite full installer file
A Dualog Startpack that matches the Connection Suite version that is going to be installed.
A vessel that has been created on the Dualog Apps portal.

INSTALLATION PROCEDURE

Double click on the setup x86/x64 installer > Click "Yes"
Click “Next” to proceed with the setup wizard > Agree to the terms of the agreement
Browse and select the destination folder that the Dualog Connection Suite should be installed.
Click "Next" > A popup window will appear and prompt that Port 80 is available for Dualog Web Server > Click "Yes" (In the unlikely event that port 80 is occupied by something else, choose port 81 and click on OK, then in the following window click on “Next”.)
Browse and select the local directory that the MailStore folder should be installed > Click "Next"
You will be now prompted to choose if you want to install Oracle XE as a part of the installation. (Make sure that the Archive Log checkbox is ticked and click on the Install button.)
After the installation, click “Yes” or "No" (Required if Network Control is configured)
Upon completion, click on “Next” and "OK" to initiate the Oracle XE installation.

ORACLE 11g EXPRESS EDITION INSTALLATION PROCEDURE

On the InstallShield Wizard for Oracle Database 11g Express Edition welcome window, click Next.
Click on “I accept the terms in the license agreement” and click on “Next”.
Browse and select the destination folder where Oracle 11g will be installed > Click "Next".
When prompted to enter and confirm a password for the database, please enter any desired password.
Confirm the password, click “Next” and "Install" to proceed with the installation.
After installation, the installer will configure and initialize the database. When you see the “Database Initialization OK” window, click on “Next”.
You are now requested to insert the StartPack file. Click on the “…” button, navigate to where the StartPack file is located on your computer and click on Next.
The installer will proceed to insert Start Pack and finalize the setup, which may take a few minutes.
You may be prompted to allow the Apache service through the Windows Firewall. Select all options (Private networks and Public networks) and click on the “Allow access” button. Complete the installation.
You will be asked if you want to reboot the PC now. Click on "Reboot Now".

After the PC has rebooted, test all Dualog functionalities (send and receive emails, test internet surfing, register crew onboard where applicable) and if you notice something out of ordinary, please contact your IT department or Dualog support @+47 7762 1911

ADDITIONAL INFORMATION

If this is not a new installation of Connection Suite (Eg: Re-installation or server migration) and you possess an IMAP backup that needs to be restored for historic emails, please proceed with IMAP restoration.

If you are preparing a reinstallation, remember to perform an IMAP backup before uninstalling Connection Suite.

If you are planning to install the Dualog ESET Antivirus solution on the Dualog PC, you can proceed here, after the installation of the Dualog Connection Suite.

Basic Troubleshooting of Ship Connection Suite

INTRODUCTION

Connection Suite is a conglomerate of modules held together by a database running in the background. This database, known as Oracle, may stop working for a variety of reasons, such as unexpected server shutdowns, bad sectors on the hard drive, or program bugs. Most of the time, though, issues are caused by the database not running properly.

SYMPTOMS

The following steps will cover how to troubleshoot Oracle and bring it back to full working conditions when it becomes unresponsive. This is how to determine if Oracle is down:

Check the status of the Dualog Connection Suite webpage. It might either NOT be visible at all, or the auto-filling of the username will not work.
Check if the Oracle XE and Oracle TNS Listener services are started. Note: In many cases, the Oracle XE service might be running even though the database is down.
Check if both Web4Sea services are started. Only one of them will run if Oracle is not running properly

If you are experiencing one or more of the above symptoms, the Oracle database is likely the cause of the disruption of the Connection Suite.

TROUBLESHOOTING

The first thing to do when troubleshooting Oracle is to restart the database. This can be achieved automatically by rebooting the Dualog PC, or manually by performing the following steps:

Stop all Dualog Connection Suite services
Stop the Oracle XE service
Restart the Oracle TNS Listener service
Start the Oracle XE service
Start all Dualog Connection Suite services

If this does not resolve the issue, the database is likely to be corrupted in some way.

The next step will be to connect to the database to determine what is wrong. This will be carried out through the Windows Command Prompt.

In CMD, type: sqlplus
When prompted for a user, type: sys as sysdba
When prompted for a password, type the password that has been chosen during the installation process, usually: oracle
Note: the password will not show while typing. Just type the password and hit Enter. If you do not know the password, contact Dualog Support for further assistance.

!!!IMPORTANT!!!

You are now connected to the Oracle database as the database administrator user. Only authorized personnel are advised to proceed with any change described below at their own risk. If in doubt, contact Dualog Support. It is vital that you do not enter any command without knowing exactly what you are doing, as there is no “safety net” in case you corrupt the database.

In such a scenario, a full reinstallation of the Dualog Connection Suite will be required.

The first task will be to restart the database. This is the easiest way to find out if there are errors related to the database. Enter the following commands:

shutdown immediate;

// Wait for the operation to complete

startup;

This sequence of commands will first shut down the database, and then start it up again. Oracle will give you one of these responses:

"Database opened" - means there are no issues with the database, and the database has been successfully opened and is ready to be used.
"Database mounted" - means that Oracle managed to mount the database but was not able to open it. There are therefore some issues preventing the database from opening.
If Oracle only managed to mount the database, you will also likely be presented with an Oracle error message with the format “ORA-1111 <error text>”. Should this happen, please call Dualog Support.

MISCELLANEOUS DATABASE CORRUPTION ERRORS

The database can get corrupted in many ways, each returning a proprietary error code. If you experience a database corruption error string, access the oracle database through Sqlplus as shown before, then type as follows:

recover database;

Once this has finished, type:

alter database open;

If everything goes well, the database will open, and you should see a message stating “database opened”.

If the aforementioned commands did not resolve your Oracle issue, return to the command prompt window, and navigate to start -> all programs -> Dualog -> Connection Suite -> Support -> and run a program called “Restore XE DB”.

Alternatively, execute "XeRestore.bat" as an administrator via C:\dualog\connectionsuite

This will run an automated database sanity check that will identify and solve some of the most common Oracle issues. Once this process is completed, you will be prompted to press any key to continue. Press any key and then run Dualog Connection Suite and test if everything is in full working order.

"ORA-00257 ARCHIVER ERROR"

"ORA-03113 END-OF-FILE ON COMMUNICATION CHANNEL"

These error messages indicate that space allotted to the Oracle archive logs has reached its maximum size and the database is therefore not able to open anymore.

The solution is to increase the maximum allowed size for the archive logs.

Access the Oracle console as previously described and insert the following set of commands. You may immediately get an error reporting that you are unable to connect to the database. In this case, shut the command prompt down and log into sqlplus again, then follow the steps below.

Shutdown immediate;
Startup mount;
Show parameter db_recovery;

//Check what the limit is set to be (e.g. 30G)

Alter system set db_recovery_file_dest_size=60G scope=both;

//Ensure that the size (60G) specified in step 4 is greater than the size you found (30G) in step 3.a.

Alter database open;

Alternatively, if prompted to use resetlogs, type in: alter database open resetlogs;

Once done, the archive log size has been increased, and the database should open. At your earliest convenience, do contact Dualog Support and inform them that your Dualog Connection Suite has been affected by this particular issue. They will need to gain access to the Dualog server and take a closer look to ascertain the causes of this issue.

"ORA-12505 - TNS: LISTENER DOES NOT CURRENTLY KNOW OF SID GIVEN IN CONNECT DESCRIPTOR"

This error indicates that the TNS listener service is unable to locate the Oracle database, and as such, the database is not functioning.

First of all, make sure that the Oracle TNS Listener service is started.

If it is running, navigate to C:\dualog\connectionsuite\, run the program called ‘OraEnvSetter’ and choose the option to set the ORACLE_SID and ORACLE_HOME environment variables.

Once this has been done, stop and start the database as described at the beginning of this document, or reboot the server, then check if Connection Suite is working as intended.

Promoted articles

SUPPORTED OPERATING SYSTEMS

SUPPORTED WEB BROWSERS

For Client registration and activation on localhost:5000

INTRODUCTION

REQUIREMENTS

GETTING STARTED

DELETION OF EXISTING ACTIVATION CODES

INSTALLATION AND ACTIVATION OF DUALOG LINK CLIENT

INTRODUCTION

PREPARATION STEPS

INSTALLATION

DNS ROUTING

HARDWARE REQUIREMENTS

SUPPORTED WEB BROWSERS

INTRODUCTION

PREREQUISITES

GETTING STARTED

1.1 - SETTING UP

1.2 - INSTALLATION

1.3 - TASK CREATION

1.4 - LET'S TEST!

ADDITIONAL RESOURCES

Version 3.13

Version 3.12

Version 3.11

Version 3.10

Version 3.0

Version 2.39

Version 2.38

INTRODUCTION

SYMPTOMS

TROUBLESHOOTING

PORTAL

LINK SERVICES

CONNECTION SUITE SERVICES

TUTORIALS

CYBERSECURITY

FIRMWARE

SEAFARER

Promoted articles

SUPPORTED OPERATING SYSTEMS

SUPPORTED WEB BROWSERS

For Client registration and activation on localhost:5000

INTRODUCTION

REQUIREMENTS

GETTING STARTED

DELETION OF EXISTING ACTIVATION CODES

INSTALLATION AND ACTIVATION OF DUALOG LINK CLIENT

INTRODUCTION

PREPARATION STEPS

INSTALLATION

DNS ROUTING

HARDWARE REQUIREMENTS

SUPPORTED WEB BROWSERS

INTRODUCTION

PREREQUISITES

GETTING STARTED

1.1 - SETTING UP

1.2 - INSTALLATION

1.3 - TASK CREATION

1.4 - LET'S TEST!

ADDITIONAL RESOURCES

Version 3.13

Version 3.12

Version 3.11

Version 3.10

Version 3.0

Version 2.39

Version 2.38

INTRODUCTION

SYMPTOMS

TROUBLESHOOTING