Welcome to Dualog Knowledge Base. What are you looking for?
Promoted articles
-
[CYBERSECURITY ADVISORY] Dualog's response to the Russia-Ukraine Crisis
In response to the escalating military conflict between Russia and Ukraine, Dualog is on heightened alert and is monitoring the situation regarding expected cyber-attacks towards the maritime industry. We acknowledge the severity of the situation and are taking the necessary precautions to mitigate any incoming threats and to enhance cyber preparedness during this time.
We highly recommend all customers elevate their cyber posture and raise awareness among shore and sea personnel.
We know that based on the ongoing cyber-attacks on Ukraine, the use of the so-called supply chain has been a common attack vector. Hence, as a supplier, we have removed all software products related to Russia so that they cannot be used as an entry point.
As a result, one of our virus scanners deployed in our MailDefence product has been decommissioned. We are in the process of replacing this scanner and have ensured that we are providing optimal protection for our customers.
It is worth mentioning that the malware used in supply-chain attacks is designed to inflict serious damage to its target. They have been known to delete files without any way of paying a ransom to get them back. This is not a typical ransomware threat. An off-line backup is the best insurance for this attack.
So far, we have not experienced an attack on any of our customers. However, as the situation escalates, we do anticipate seeing some form of attacks targeting the maritime industry specifically. We will continue monitoring all activity to stop any potential threats as early as possible.
Dualog is prepared to swiftly respond and assist any organizations that fall victim to cyberattacks associated with these geopolitical events.
In case of any significant changes to the situation, we will keep you informed.
Geir Inge Jensen
Chief Information Security Officer
Dualog Portal - Getting Started
This article will provide step-by-step instructions on how to get started on Dualog Portal before accessing the available features.
- Register an account on Dualog Portal (For both existing and new customers)
- Request for an invitation to an organization.
- If there is/are existing members within the organization, they may send an invitation (Under Procedure for Owner)
- If there is/are no existing members within the organization, reach out to Dualog support at support@dualog.com with the registered email address or username.
- Accept the invitation (Under Procedure for invitee)
- You are all set to access the available features now!
Articles on the available features on Dualog Portal are available here, along with video tutorials here.
For official feedback submission, please log in to Dualog Portal and submit a form located at the bottom right.
Spam Score Quarantine
INTRODUCTION
Aside from the general quarantine feature, where a message that exceeds the enforced size restriction is quarantined or rejected if the feature is not enabled.
Spam score quarantine is now available for your vessels as an additional layer of email filtering and security. By default, this feature is disabled.
When enabled, all incoming emails with a spam score higher than a certain threshold are quarantined here before being delivered to the intended vessels.
Dualog Maildefence evaluates and determines the spam score.
This article will walk you through the process of enabling the spam score quarantine feature, editing the spam score option, and releasing quarantined emails due to the spam score threshold.
ENABLING OF SPAM SCORE QUARANTINE
- Upon logging into the Dualog portal with your account, proceed to Connection Suite > Email
- Go to Settings > Under the Quarantine section, click on Edit settings
- Click on Edit Threshold
- By default, 7- 10 option is selected (Other options that best meet your requirements can be chosen)
- Save Changes
Note: The threshold option can be changed at any time, and it will apply to newer incoming emails.
RELEASING OF SPAM SCORE QUARANTINED EMAILS
- Upon logging into the Dualog portal with your account, proceed to Connection Suite > Email
- Click on Quarantine Messages
- Locate email(s) that is/are quarantined due to the reason "spam score"
- Click on the kebab menu to approve, reject or check on the email headers for further assessment of the legitimacy of an email
How to check for quarantined, sent and pending messages
INTRODUCTION
This article will provide step-by-step instructions to check Quarantine Messages, Pending Messages, and Sent messages in Dualog Portal.
- Quarantine Messages - Messages that exceed the allowed message size on a company's filter and require manual release. (Click here to access the Quarantine feature and its settings)
Note: If the Quarantine feature is not enabled, emails will be rejected if they do exceed the allowed message size on a company's filter
- Pending Messages - Messages received have passed through the various filtering mechanisms and checks within a company's configurations and awaiting download to the intended vessel(s).
- Search for Messages - Useful for email investigations to identify messages that could potentially be blocked due to specific filtering mechanisms in a company or have been successfully sent or received to and from a vessel.
QUARANTINED MESSAGES
When an email has been quarantined, the sender, recipient, and ship postmaster will receive a Quarantine Notification. (Click here for the settings)
This needs to be approved manually by an administrator, through the Dualog Portal or Admin App, where a quarantined email can be released or rejected accordingly.
- Log in to Dualog Portal with the appropriate credentials > Select Quarantine Messages
- Check and select the Quarantine Message(s) required to be released or rejected.
- Show Headers can be selected to verify the headers within an email for more information.
PENDING MESSAGES
- Log in to Dualog Portal with the appropriate credentials > Select Pending Messages
- Check on the latest pending message(s) for a vessel and reject if necessary.
- Show Headers can be selected to verify the headers within an email for more information.
MESSAGE SEARCH
- Log in to Dualog Portal with the appropriate credentials > Select Search for Message
- Set all necessary settings (Date range, time, vessel, to ship or from ship) > Search
- Click on Message Details to specify the search even further.
Note The current search period is limited to 7 days and below.
MX and SPF records for Dualog Mail Defence
On this page, you will find the technical information required for email deliveries to our Dualog Mail Defence and to your vessels
- ROUTE YOUR DOMAIN TO DUALOG MAILDEFENCE
Important: when routing new domains to MailDefence, notify support@dualog.com in advance.
For domain(s) under your management (e.g. fleet.yourdomain.com), apply the following changes.
Shore to ship traffic routing - MX records
To route the traffic directed to your domain to Dualog MailDefence, change the MX record of your domain(s) to:
- mx1.dualog.com (preference 10)
Ship to shore traffic routing - SPF records
In order to allow our servers to send out email with your domain, add the following to the domain's SPF record:
For domain(s) hosted under dualog.net
No action will be required
IMAP Backup & Shore Configuration
The following document serves as a guide to initiating IMAP backup onboard and configuring IMAP backup on the Dualog Portal.
IMAP Backup automatically backs up all email, both crew mail, and business mail, on the Dualog Mail Server. Once configured, the IMAP Backup will run on a daily or weekly basis and will back up all mail same time, the same day of the week.
- Login to Dualog Connection Suite on the ship Dualog connection suite with an appropriate account and access.
- Click on the menu > Technical Setup > IMAP Backup > Backup Mail Store
3. Navigate to the specified IMAP backup folder and verify that a dualog backup folder called dualog_backup_tmp has been created. Ultimately, the IMAP backup process will create a minimum of two files, named:
- imapmailstore.dualogbackup.archive
- imapmailstore.dualogbackup0
If the IMAP repository on board already contains several GB of mail, other files will appear, such as:
imapmailstore.dualogbackup1
imapmailstore.dualogbackup2
imapmailstore.dualogbackup3
and so forth. This is normal and indicates that the automatic IMAP backup procedure is working as intended.
Depending on the amount of mail already stored on the IMAP server on board, the entire procedure can last from a few minutes to several hours. Remember that the IMAP backup will include all mail history of the vessel from the beginning of time until the moment the IMAP backup was initiated. Any subsequent mail will only be included in the upcoming backup.
The previous IMAP backup will be stored within the OLD folder of the configured directory.
!!!IMPORTANT!!!
If the IMAP backup directory points to a network drive, the user running the Windows Service called 'Dualog Connection Suite IMAP Service' needs to have read/write access to the directory to be able to place it there.
- IMAP BACKUP CONFIGURATION (SHORE)
To specify or amend the location where the backup(s) will be saved, this has to be done on Dualog Portal.
- Login to Dualog Portal, go to Connection Suite > CS Ship Setup > Select the vessel.
2. Under Periodic Backup, you may choose to amend the existing backup location directly or clicking on "Add Backup Location" for a new one.
3. Select the backup interval accordingly (Either Daily or Weekly, followed by the time in UTC)
- Under Dualog Portal > Select a vessel > Scroll down to Periodic Backup > Click on the "Backup History" to display both the latest and overall backup details
Enable Sign-In Approval Feature
The crew sign-in feature has been activated to improve security and prevent unauthorized use of accounts onboard. If enabled, Internet and email will only be available to crew members after approval from the captains. Authorized persons will receive an email asking for approval, whenever a new sign-in is performed onboard.
This article will show how an administrator can enable the sign-in approval feature within the organization and for a specific user group.
Login to Dualog Portal using an administrator account: (Click here if you have yet to register)
- Click on the Hamburger menu at the top left corner > Connection Suite > CS Groups
- Search or select the user group(s) that require(s) the sign-in approval feature
- Under Group Settings > enable "Require sign-in approval"
- Click on Save to apply the change
Alerts - Configuration and settings
INTRODUCTION
The Dualog Alerts feature allows administrators to configure alerts for several Dualog services should specific errors or thresholds be encountered or reached. The alert notifications will be sent to all configured recipients.
Alerts configuration can be found at the bottom of the "Organisation" page.
The following will be demonstrated in this article:
- Overview of all configurable alerts
- Configuring an alert
- Adding of the recipient(s)
OVERVIEW OF ALERTS
- Antivirus
- Alert when a ship has an outdated Antivirus server.
- Configurable threshold: 1 - 30 days.
- Alert when a ship has outdated Antivirus clients.
- Configurable threshold: 1 - 30 days.
- ConnectionSuite
- Alert when Connection Suite has not connected to the Dualog Cloud for an extended period of time.
- Configurable threshold: 60 - 2880 minutes.
- Alert when there’s more than a predefined amount of crew signed on a ship.
- Configurable threshold: 1 - 200 minutes.
- DualogDrive
- Alert when Drive detects an issue.
- Configurable threshold: 15 - 2880 minutes.
-
- Alert when a transfer has taken too long to complete.
- Configurable threshold: 15 - 10080 minutes.
- DualogProtect
- Alert when a device is trying to contact a malware (Command&Control/C2) server - Enable/Disable.
- Email
- Alert when a ship does not have a recent IMAP server backup.
- Configurable threshold: 2 - 30 days.
- Link
- Alert when a Link Platform installation has been offline for an extended period of time.
- Configurable threshold: 15 - 2880 minutes.
CONFIGURATION OF ALERTS
- To enable an alert, first select its category from the list and a pop-up window will then appear where the applicable alerts and their parameters may be adjusted.
- Save Changes
When the configured threshold has exceeded for an active alert, an email will be sent to all alert recipients.
ADDING OF THE RECIPIENT(S)
- You may select "Add Alert Recipient" to add email recipients of your configured alerts as shown below:
- When the recipient(s) is/are added, they will receive an email to verify that they want to receive future Dualog Alerts.
- Proceed with the verification to receive the configured alerts.
Dualog® Protect - Changelog
INTRODUCTION
This page lists every addition/modification to Dualog® Protect since its first release.
3.4 (21 February 2022)
IMPROVEMENTS:
- OTA Upgrade
Upgraded to use Digital Platform version 8.4
3.3 (29 January 2021)
IMPROVEMENTS:
- Unbound Upgrade
Upgraded to version 1.13
- Stability and Performance
Prevents potential situations where exceptions are not handled properly
BUG FIXES:
- Last Known Configurations
Fixed an issue where the latest configurations would now be remembered in situations where a computer installed with Protect has been restarted, along with the internet being unavailable, configurations will be lost upon restarted.
Cloud Services (26 January 2021)
IMPROVEMENTS:
- Unbound and NIM Upgrade
Upgraded to version 1.13
- .NET Core Upgrade
Upgraded to version 5.0
- Security Modifications
Version and Identity to be made invisible from public
- Improved Logging
Improved logging for the simplification of error detections and etc
Added carriers and timestamp to the logs whenever cloud servers receive a message
- Re-structuring of caching method (Client Keys)
3.2 (26 August 2020)
IMPROVEMENTS:
- Encryption key fetched from Dualog cloud
The encryption key is now obtained from the Digital Platform shore system
- Improved logging
Protect is now writing all activities from the DNS server (Unbound) into the Protect log. It also logs when port 53 is occupied.
BUG FIXES:
- Protect client stuck in starting
If unbound is not able to start, the Protect client is stuck in Starting, which again causes it to be hard to stop, for instance during an upgrade
3.1 (14 April 2020)
NEW FEATURES:
- Support Win32 Operating systems
Added support for 32-bit operating systems. Version 3 installed OK on 32-bit OS but did not start.
- Retrieve logs from client
Log retrieval was added to version 7 of the Digital Platform (released 19. Mar 2020). The Protect client now supports this feature, which is only available for Dualog Superusers.
IMPROVEMENTS:
- Modified Blacklist functionality
The blacklist feature is modified to also blacklist sub-domains, example: Blacklisting bbc.com will also blacklist live.bbc.com and bbc.com/programs
By using whitelisting, specific subdomains can be made available.
- Blacklist and whitelist architecture redesigned
To achieve the modified Blacklist functionality, separate black- and whitelist servers are installed and configured in the cloud. This also means that requests for white- and blacklisted domains are logged and can be displayed in dashboards.
Dualog® Protect - How to get 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 apps.dualog.com
- 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
- Download the latest installation file from https://apps.dualog.com/installations
- 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.
Make sure your WAN network adapter uses 127.0.0.1 as primary DNS.
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 - How to get 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
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.
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.
[Configurations] Sharepoint Integration
TABLE OF CONTENT
Configuring Drive to use SharePoint requires multiple steps:
- Setting up Azure Active Directory for SharePoint Integration
- 1.1 - Find your Tenant ID
- 1.2 - Create a new Application
- 1.3 - Setting up permissions
- 1.4 - Setting up Secrets
- Setting up SharePoint Integration
- 2.1 - Set up SharePoint Connection
- 2.2 - Select SharePoint drive
- Configure Drive to use SharePoint
1. SETTING UP AZURE ACTIVE DIRECTORY
To be able to integrate Dualog Drive with your organization, below are the initial steps that need to be available in your Azure Active Directory:
1.1 FIND YOUR TENANT ID
For the Dualog Drive SharePoint Integration to work, you need the have the Tenant ID available. The Tenant ID can be found under Properties in the Microsoft Azure Portal:
Note: Do safeguard this ID for future use.
For more information about the Tenant ID, click on the official Microsoft link below:
https://docs.microsoft.com/en-us/onedrive/find-your-office-365-tenant-id
1.2 CREATE A NEW APPLICATION
Under App registrations, you must create a new registration. The following values must be added:
- Display name - Add a descriptive Display name
- Supported account types - Select desired account type
When entering the application properties, please take note of the Application Id (Client Id).
Other values are optional (client credentials/secrets are added in 1.4 Setting up secrets)
1.3 SETTING UP PERMISSIONS
For Dualog Drive SharePoint integration to work properly, you must give the application the needed permissions:
1.4 SETTING UP SECRETS
Finally, you need to create a secret to be used for the Dualog Drive SharePoint Integration: Press New Client Secret, give the secret a description and an expiration time, then press Add.
Take a copy of the value and keep it for later.
IMPORTANT: Copy the Value and not the Secret ID
The Client secret must be added to the configuration of the SharePoint Integration in Dualog Portal (2.1 Set up Sharepoint Connection).
For more information (Contact your site admin for assistance):
https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azureacs.
2. SETTING UP SHAREPOINT INTEGRATION
Multiple SharePoint integrations can be configured for your organization. These configurations can then be used to set up Drive to use SharePoint as a source for Sync tasks. Setting up SharePoint Integration is only available from the Drive configuration within the Dualog Portal.
Important: This configuration is only available for Sync tasks with an office installation as the source.
2.1 SET UP SHAREPOINT CONNECTION
The first step is to configure the connection to SharePoint. The following values must be added. How to find/create these parameters are described in Setting up Azure Active Directory for Sharepoint Integration.
- Tenant ID
A global UID for your organization inside Microsoft Azure AD.
- Client ID
Global UID credential required for Drive cloud to authenticate with your SharePoint (together with the Client Secret). This is the value created in section 1.2 (Create New Application)
- Client Secret
Password to use together with the Client ID for Drive to get a token to use accessing SharePoint. (As described in section 1.4 (Setting up secrets).
- Integration Name
Give the integration a descriptive name.
STEPS
- Upon logging into the Dualog Portal > Click on Create Drive Task
- Specify One-Way Sync > Office to ship > Single or multiple ships > Individual or same folder > Create task > Edit Source
- Select Integration > Click Add new Integration to start setting up a SharePoint integration.
- The config window will appear > Add the values and click on Verify Integration:
- Verify Integration will try to set up a connection to SharePoint, using the configured values.
Note: If some of the parameters added are wrong, an error message will appear, and the “Add Integration” button will remain disabled. Verify values and try again.
6. When a configuration is correctly added, the window will expand, and SharePoint drives can be added.
2.2 SELECT SHAREPOINT DRIVE
The last step in configuring SharePoint Integration is to select what folders in SharePoint this integration is allowed to use. We recommend setting up dedicated folders for Dualog Drive use.
With a SharePoint connection successfully defined, the Site and drive can be selected from the dropdowns.
At this point, you may add a new SharePoint drive or update an existing one.
3. CONFIGURE DRIVE TO USE SHAREPOINT
When SharePoint integration is set up, Drive can be configured to use this as a source or destination for Sync task
- Select the appropriate SharePoint configuration(s) from the list.
- After selecting the correct SharePoint integration, you will be asked to enter SharePoint Drive and a path to synchronize data to or from.
- In the example below, SharePoint is the source, but the same process will be valid for SharePoint as the destination:
- SharePoint Drive: Drives related to the integration selected. If the SharePoint config is configured correctly, you can select it from the dropdown.
- Path: Specify the path from where files are to be synchronized. ( / has to be indicated for Sharepoint Integration )
IMPORTANT: Do not include the full path. Root path and SharePoint Drive shall NOT be included in the path. If folders/subfolders are missing, Dualog Drive will create the path.
[Introduction] Sharepoint Integration
INTRODUCTION
The Dualog Drive SharePoint integration enables the synchronization of data from SharePoint to Drive clients and from Drive clients to SharePoint. Later it will also support moving files between SharePoint and Drive Clients.
The SharePoint Integration will not offer two-way synchronization, and no direct connection would be established between Drive clients and Sharepoint.
Both the integration and interaction would only be made through the Dualog cloud.
The SharePoint integration will, when fully implemented, simplify the Drive architecture, as no physical Drive Client needs to be installed onshore.
HOW IT WORKS - OVERVIEW
By using SharePoint integration, Drive clients only need to be installed on ships. The Dualog Drive Cloud connects to SharePoint to either collect data for distribution to ships or deliver data received from ships.
Currently, SharePoint integration supports Sync-tasks. Move-tasks will be supported in Q3-2022.
It is important to notice that this integration is only for having such systems as source or destination - and will not include their full file sharing features.
Drive Cloud will replace the office client by scanning configured locations (Drives/folders) on SharePoint for updates, as well as distributing updates from ships to the configured destination on SharePoint.
CONFIGURATIONS
Configuring Drive to use SharePoint requires multiple steps:
- Azure Active Directory configuration
In Azure AD, you need to both find the required information and make config changes
- Set up SharePoint Integration
Multiple SharePoint integrations can be configured for your organization. These configurations can then be used to set up Drive to use SharePoint as a source for Sync tasks.
- Set up SharePoint Connection
Configure Dualog Drive to connect to your SharePoint. Required information is obtained/created in the previous section
- Select SharePoint Drive
Select which SharePoint Drive to use
- Configure Dualog Drive to use SharePoint
Configure Drive to use the configured Sharepoint integration as a source or destination for Sync tasks.
UPCOMING FEATURES
Supporting of Move tasks will be introduced in Q3-2022.
Dualog® Drive - Changelog
INTRODUCTION
This page lists every changelog to Dualog® Drive since its first release.
8.11 - 06 June 2022
IMPROVEMENTS:
- Sync: Set max number of changes in one revision
We've had timeout issues when a sync revision contains a large number of changes (seen on revisions with more than 10 000 deleted files).
The client initially attempts to send metadata for changes.
The connection times out due to so many changes, and the client retries sending the data.
We have set a hard limit of 500 updates per revision to avoid this situation.
If there are 15000 changes, they will be distributed in 30 revisions.
BUG FIXES:
8.9 - 25 May 2022
IMPROVEMENTS:
- Adjustments to utilize the new sync protocol
Several improvements have been made in the sync protocol (part of the Link Platform). To utilize these changes, changes have been made to the Sync client
BUG FIXES:
- Sync: Cleanup when a sync task is deleted
When a task is deleted, some cleanup is required. A housekeeping routine is now implemented to clean up database tables holding information on ongoing transmissions for the deleted task(s). Without this cleanup, the sync task will try to complete the download forever and keep logging error messages. This only applies to situations where a task is deleted while it still has data to up/download.
8.4 - 21 March 2022
BUG FIXES:
- Sync: BlobTransfer protocol
Fixed issues with the BlobTransfer protocol on Link Platform.
8.3 - 14 March 2022
IMPROVEMENTS:
- HTTP Header now includes a Correlation ID
BUG FIXES:
- Sync: Sync protocol
Fixed an issue with the Sync protocol.
8.2 - 21 February 2022
IMPROVEMENTS:
- Improved logging
Added logging when failing to filter files, build number, and detailed logging on the version number
BUG FIXES:
- Migration Issue from Drive 7.x to 8
The destination might end in an infinite loop if the next operation is "delete".
- Move: High memory usage
Fixed issue where the memory usage on the Move client is high.
- Sync: High memory usage
Reduced memory usage by upgrading SDK's and other minor patches
- Sync: BlobTransfer protocol
Fixed an issue with the BlobTransfer protocol.
8.1 - 02 December 2021
After upgrading, Drive will automatically migrate certain parts of the databases for better performance. Depending on the size of this database, this might take some time.
NEW FEATURES:
- Sync: New Transfer Protocol
The sync transfer protocol has been totally redesigned and is now added as a Link Platform service. Drive now uses this protocol for Sync transmissions. The new protocol uses multiple IP channels for transmissions, improving throughput. In addition, protocol overhead has been reduced.
- Sync: Error messages appear in apps.dualog.com
Added functionality to transfer errors from client to cloud. Errors will be displayed as Detected errors on the Drive status page
IMPROVEMENTS:
- Sync & Move: hidden files and folders not being transferred.
Hidden files will now not be sent. Normally such files are system files or temp files. We have experienced files like thumbs.db being transferred, causing problems at the destination.
- Move: improved SQLite database performance
Improved by removing the encryption layer.
- Move: Error messages transferred to the Drive cloud
Some critical error messages are now being transferred to the cloud. Apps.dualog.com will soon show these error messages on the Drive status page.
- Move: Improved behavior when downloading package having permanent failure
If a package is not possible to download, the Move client moves on to the next package instead of failing out and then retrying the failed package. This avoids a long queue of pending downloads when such errors occur.
- Move: Improved performance
Improve performance with multiple destination tasks by doing parallel unpack and download.
- Move: Changed folder tree access rights requirements
Previous versions of Move required full access to the whole folder tree structure, instead of only the task root folder. This has caused some head-scratching when troubleshooting access rights issues.
BUG FIXES:
- Sync: Stop syncing blobs when the configuration is disabled
Fixed an error where Sync tasks being disabled were still syncing blobs.
- Move: Fixed bug causing the transfer to hang after service restart
Fixed issue where transfer status may be wrong when the service is restarted during transfer.
- Move: Double gzip encoding
In some rare instances, the files sent can be compressed twice.
7.11 - 21 June 2021
BUG FIXES:
- Sync: Destination client fails to download an update
Fixed a protocol bug that prevented the destination client from downloading an update for the sync task. (This fix would only prevent the error message from being logged, but will not help with the corrupted transmission itself)
[ERR] Failed to download blob; aborting this run; Error Message: Hash Control Error on incoming chunk(0)
WORKAROUND:
- Determine which file(s) are stuck in the logs.
- At the source, copy this file to another synced folder (or create a subfolder to copy the file to)
- Drive will then sync this file to the cloud, and the chunk will be added to the database.
- The chunk will then be delivered to the destination folder, allowing you to proceed.
-
As there could be more than one file stuck, you may need to repeat the operation on more files.
-
When the task has finished successfully syncing, remember to clean up by deleting the copy of the file (s)
7.10 - 27 May 2021
BUG FIXES:
- Move: Failure to resume on download
If a package download is aborted, the client will throw an exception the next time it tries to download the package before sending an acknowledgment to the server.
- Sync: Multiple instances of the client can be started
Prevented instances where multiple instances of the Sync client launch.
7.9 - 12 May 2021
BUG FIXES:
IMPROVEMENTS:
- Improved logging on exceptions
Added task information on certain exceptions to improve traceability.
7.8 - 09 March 2021
BUG FIXES:
IMPROVEMENTS:
- Support for Samba 3.0
Samba 3.0 is now officially supported for File Share.
7.7 - 4 December 2020
BUG FIXES:
-
Move: Set Max Transmission per file/package size to 3GB
The Move protocol has problems when transmitting multiple GB of data, where the 3GB limitation has now been set in place. If the package is more than 3GB, it will be divided into multiple transmissions
- Windows Share: Fixed a Samba issue when many files are to be stored concurrently
7.6 - 7 September 2020
BUG FIXES:
-
Sync and Move: Storing data to file share fails
The Samba server has a maximum size for data to send or receive. This maximum size was not checked and respected by the Drive client, causing potential rejection from the file share. The client has now been redesigned to check the maximum size before sending data.
7.5 - 28 August 2020
IMPORTANT:
Click on the following for the detailed instructions on how to detect and enable SMB 2.1 protocol:
BUG FIXES:
-
Sync: High CPU usage
Fixed problem where the Sync client gradually increases its CPU usage
-
Sync: the transfer is not resuming until after one hour
If a transmission fails, it will take one hour until transmission resumes.
-
Sync: Downloads not completing
Some sync downloads are hanging forever. The reason is a bug in the sync client, not being able to create the files from the received blobs. Reading of metadata failed.
IMPROVEMENTS:
- Move & Sync: Improved writing data to file shares
Redesigned writing to file shares to avoid the potential problems when many tasks access the same file share
-
Sync: Location of temp files
Currently, Sync is using the Windows temp folder. This may have unwanted consequences if other applications are using the same temp, and not cleaning up temp files.
We will now create and use a temp folder on the location of the installation.
-
Move: Changed download order to avoid heavy delay for some downloads
When the heavy load on downloads, we have experienced downloads for some tasks to be pending for a long time. Changed communication between cloud and destination to contain all pending downloads instead of one task at a time.
7.4 - 29 June 2020
BUG FIXES:
7.3 - 10 June 2020
BUG FIXES:
- Sync: Error situation at destination when a file is deleted at the source
When a file is deleted, it may occur that file info is not sent from the server. This was not properly handled by the client, causing the update to not complete
-
Sync: Handling of error situation when temp file is not possible to be created
This is related to situations where the windows temp folder is not cleaned by other applications. Temp files will have 8.3 namings, and when the namespace is “full”, the application will crash when not able to find an available file name. This is now handled, but for a future release, we will redesign the service to use a separate temp folder.
-
Sync: Client hanging on source task operation
Fixed a problem where the client is not able to send folder updates.
Log error: The state is out of sync with the file system. Suspending operation for 30 seconds.
-
Sync: Error situation when config changes
When the sync client receives a configuration change and there are many sync tasks configured, it is possible to end in a situation where there are several instances of a task running.
-
Sync: Failure on the destination when an update has no metadata
When an update only contains file deletion, meaning that no metadata is included, the sync client might end up reporting the following error:
The required feature DestinationStateChangeFeature was not set on the context.
-
Sync: Client stops transferring data
All transfers stop until the client is restarted. The reason is an error in exception handling, causing the client not to return from a function.
7.1 - 04 May 2020
- The protocol handling authentication now supports the use of WebSockets. We have eliminated the limitations in some operating systems like Windows® 7 and Windows® Server 2012.
- We have improved efficiency on file download by simplifying database operations.
- Drive now has a new and streamlined metadata format. We have also improved the compression of metadata to reduce transfer size.
- The service now performs disk space checks to verify sufficient disk space before initiating up-and-download.
- Bug fix: We have made several stability improvements in the sync protocol. In the move protocol, an error where resumes on large files failed is now fixed.
7.0 - 19 March 2020
- The Smart Folder™ feature now includes the option of using custom ship codes to automate folder creation on either source or destination. This dramatically improves the flexibility to manage file locations to correspond with company-specific requirements.
- For move tasks, there is now the option of having the service copy files automatically to a local backup folder without interfering with the transfer. This can be a useful feature in case a transmission fails, or if having a rollback option available is a requirement
- There is now an option to enable or disable tasks. This feature makes it easy to stop all activities on a task temporarily or to delay startup until the installation on all your clients is complete.
- Super-admins can now receive logs from clients automatically for complete traceability into data transfer tasks.
6.3 - 04 February 2020
- BUG FIX: The destination folder scanning does not work for UNC paths. This bug was introduced in Drive 6.0.
6.2 - 14 January 2020 (patch release)
- Fixed a bug where temporary zero-byte files were not deleted from the disk when not needed anymore
- Resolved an error situation when bandwidth control is enabled but not configured
6.1 - 08 January 2020 (patch release)
- Sync: Fixed a potential crash situation
- Sync: Improved handling of token renewal upon expiry
- Move: Last modified time of files are no longer taken into consideration unless the task is configured to have a delay. This allows for files with a last modified in the future to still be sent.
- Move: Improved handling of token renewal upon expiry
6.0 - 06 January 2020
- Scan sync files on the destination
- If files or folders are added, modified, or deleted, Drive will alter the changes making sure destinations are an exact mirror of the source. Previously, destination folders would be scanned for changes on an hourly basis
- Proactive data import
- In cases where a large amount of data is to be synchronized to the ships, data might be delivered on a USB stick or similar to destinations. For this purpose, a feature called Proactive Data Import is created.
By copying files into this folder
<install folder>DualogDrive\DualogDrive.Sync.Client\DataImport
they will be imported to the storage for the deduplication transfer protocol. After adding data to the storage, files will be deleted from the DataImport folder.
When this data is to be downloaded, the protocol will recognize this data as already available and create the files without having to download them.
Any data can be stored in this folder and help the system to reduce bandwidth usage.
Be aware that subfolders will not be imported, so make sure all files are copied to the DataImport root folder.
5.0 - 05 January 2019
- Platform: Carrier detection
- Allows you to configure carrier detection for ships to identify which internet carrier is currently in use for the platform
- Drive: Bandwidth control
- Set rules in Drive tasks to tell which carriers they are allowed to send data over
- Platform: now reports carrier changes to the cloud
- Sync: added support for Windows 7
- Sync: improved logging
- Sync: fixed an issue causing sync to sometimes time out while downloading
- Move: added re-trying of storing a file in the destination folder. Previously this would only happen on a restart of the service
- Platform: Improved handling of knowing whether an installation is offline in cases where the LiveLink on the installation crashes
- Changed logging folder to DualogDigitalPlatform\DigitalPlatform.Client\logs
- Move: Overwrite will merge with the existing file in the destination folder instead of replacing it
- Move: improved handling of situations where config is changed while a file is being uploaded.
- Improved service startup on Windows reboot due to race conditions
3.1 - 20 November 2019 (patch release)
- Improved deduplication protocol handling of files from the cloud to installation, lowering the amount of failed transfers
- Improved software requirement checks during installations
- Sync: Improved exception handling
3.0 - 18 October 2019
- Added global deduplication protocol using algorithms to minimize the amount of data transferred between installation and cloud
- Added LiveLink handling of ship installations
- Added over the air (OTA) updating
- Re-implemented Sync
- Improved registration of installations by adding more error checks
2.4 - 23 September 2019 (patch release)
- Added resume option for when files fail to download to an installation
2.3 - 22 August (patch release)
- Improved handling of files larger than 1GB
- Improved handling of Windows shares needing user authentication
- Fixed a bug causing very large files to fail to send
- Improved error reporting and logging
- Changed all logging to be in UTC
- Drive components now report version numbers
- Improved error messages on the installation registration page
2.2 - 30 June 2019
- Major redesign of the backend to utilize the platform services
Dualog Access - Developers' Guide
INTRODUCTION
Dualog Access is a single sign-on/identity management service created for use on locations not always online. The service is designed for maritime use but is suitable for any remote location where internet access is unstable or absent.
To use Dualog Access for logon/authentication to applications, each application must implement integration with Dualog Access. Dualog Access uses the OAuth 2.0 standard for authentication. Before integrating applications to use Dualog Access, it is advised to learn more about OAuth 2.0.
This article describes how to use Dualog Access from a developer’s perspective. Installing and configuring Dualog Access and Dualog Connection Suite is not covered in this document.
TABLE OF CONTENTS
-
- Supported Operating Systems
-
-
- Authorization Code Flow
- PKCE
- Implicit Flow with Form Post
- Hybrid Flow
- Client Credentials Flow
- Device Authorization Flow
- Resource Owner Password Flow
-
- Resource Owner Password
- Basic Steps
-
- Discovery
- Authorize
- Token
- User Info
- Device Authorisation
- Introspection (Coming Soon)
- Revocation
- End Session
Latest Antivirus download links
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.
Please follow the links for guides on how to install and uninstall Dualog Antivirus:
- Installation on Dualog Server
- Installation on Clients
- Uninstallation of Dualog Antivirus
- Uninstallation of Dualog Antivirus (With ESET removal tool)
How to install the Dualog Antivirus (Client side)
Since the release of Connection Suite version 2.38 onwards, the Dualog ESET Antivirus solution has been completely overhauled.
This article provides the step by step instructions on downloading the antivirus client installer directly from the ship Dualog connection suite and the installation procedure.
- Connection Suite version 2.38 or later installed on the Dualog PC.
- Antivirus Client installer file (downloadable from the Connection Suite interface onboard).
- ANTIVIRUS CLIENT INSTALLER DOWNLOAD
- Login to the ship Dualog Connection Suite with an appropriate account > Click on the menu located on the top-left corner > Under External Links > Antivirus installer.
- If there is no download link, it could be due to the account used does not have the relevant access or the Antivirus software is not correctly installed on the Dualog PC. Please make sure that the
Dualog Antivirus software is installed on the Dualog PC or check with Dualog support.
- The installer will be downloaded automatically and saved to the designated download local directory of the web browser used.
- ANTIVIRUS CLIENT INSTALLATION PROCEDURE
- Double-click on the Dualog_Antivirus_Client_Installer.exe to initiate the installation wizard. (Click on Yes if you are prompted with the User Access Control)
2. Click on "Next", browse and select the destination folder for the installation > Click "Next"
3. The next step is choosing the folder where the weekly antivirus update files will be stored. The default location will normally be used. Press "Next" to continue.
4. The next step of the installation is choosing whether to perform a silent installation or to see the full interactive user interface for the installer. Press "Next" to continue.
TAKE NOTE! This option will be enabled on "Windows Server" Operating Systems automatically for the installation. (Please refer to the next section specifically for "Window Server" Operating systems as well)
5. Next, an option will appear where it will be possible to block access to USB/FireWire storage on the computer. It is not important to choose now, this option can be manually enabled or disabled at a later stage.
6. Verify all installation parameters and settings before pressing "Install" to start the installation.
7. The installation of the Antivirus is now finished. Press "Finish" to close the Setup Wizard.
8. Launch ESET from the taskbar.
Your PC is now protected by the Dualog ESET Antivirus installation. Two new services have been added at the Operative System-level (Dualog Agent and Dualog Client Upgrade) and they will be responsible to communicate with the shore servers and make sure that the Antivirus is correctly updated to the latest signature.
In the case of multiple signature updates from the Cloud, it might take some time until the client is fully updated and the current version is correctly displayed.
- ESET ENDPOINT SETUP (FOR WINDOW SERVER OS ONLY)
- If you are installing Antivirus on Window Server OS, the following steps would be shown and have to be performed
- Click "Next", the setup will indicate ESET Endpoint Antivirus will be installed on a Window Server OS
- Proceed to accept the terms and click "Next".
- Uncheck "ESET LiveGrid"> click "Next > Enable/Disable detection and proceed with the installation.
- Click "Finish" to complete the setup wizard and launch ESET from the taskbar.
How to install the Dualog Antivirus (Server side)
Since the release of Connection Suite version 2.38 onwards, the Dualog ESET Antivirus solution has been completely overhauled.
If your ship is already equipped with an older version of the Dualog ESET Antivirus, you will need to uninstall every instance of the Dualog ESET Antivirus from every PC on board, including the Dualog PC, in order to install the new, improved version.
- Connection Suite version 2.38 or later installed on the Dualog PC.
-
Antivirus Server installer file
- A valid and latest ESET base update package
-
DUALOG ANTIVIRUS SERVER INSTALLATION
The Dualog ESET Server installer has two features. It will copy the Antivirus Client installer and extract and copy the ESET base update package into the Connection Suite installation folder. This installer is compatible with both 32 and 64-bit versions of Windows and has no uninstaller, as it only copies files into an existing Connection Suite installation.
- Double-click on the Dualog Antivirus Server Installer placed on the Dualog PC to initiate the installation wizard. (Click on Yes if you are prompted with the User Access Control)
- Click on "Next" until you are prompted to select the base update.
3. When prompted to select where the antivirus base file is located, click on the "Browse" button > Navigate to the location where the file is stored, select the file > press "Next".
4. Review the chosen parameters > click on the "Install" button to confirm.
5. Once the installation is completed successfully, ensure that "Install Dualog Antivirus Client" is checked to proceed further with the ESET installation.
- DUALOG ANTIVIRUS CLIENT INSTALLATION
- After finishing the above installation wizard, you will now proceed with the Antivirus installation. (Click on Yes if you are prompted with the User Access Control)
2. Click on "Next", browse and select the destination folder for the installation > Click "Next"
3. The next step is choosing the folder where the weekly antivirus update files will be stored. The default location will normally be used. Press "Next" to continue.
4. The next step of the installation is choosing whether to perform a silent installation or to see the full interactive user interface for the installer. Press "Next" to continue.
TAKE NOTE! This option will be enabled on "Windows Server" Operating Systems automatically for the installation. (Please refer to the next section specifically for "Window Server" Operating systems as well)
5. Next, an option will appear where it will be possible to block access to USB/FireWire storage on the computer. It is not important to choose now, this option can be manually enabled or disabled at a later stage.
6. Verify all installation parameters and settings before pressing "Install" to start the installation.
7. The installation of the Antivirus is now finished. Press "Finish" to close the Setup Wizard.
8. Launch ESET from the taskbar.
Your PC is now protected by the Dualog ESET Antivirus installation. Two new services have been added at the Operative System-level (Dualog Agent and Dualog Client Upgrade) and they will be responsible to communicate with the shore servers and make sure that the Antivirus is correctly updated to the latest signature.
In the case of multiple signature updates from the Cloud, it might take some time until the client is fully updated and the current version is correctly displayed.
- ESET ENDPOINT SETUP (FOR WINDOW SERVER OS ONLY)
- If you are installing Antivirus on Window Server OS, the following steps would be shown and have to be performed
- Click "Next", the setup will indicate ESET Endpoint Antivirus will be installed on a Window Server OS
- Proceed to accept the terms and click "Next".
- Uncheck "ESET LiveGrid"> click "Next > Enable/Disable detection and proceed with the installation.
- Click "Finish" to complete the setup wizard and launch ESET from the taskbar.
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.11 FILES
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.
System Requirements for Connection Suite
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. |
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.
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, no specific HDD requirements |
| I/O |
A minimum of two network interfaces: one connecting the ship’s LAN and the other 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 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 (*)
Compatible only with Dualog Connection Suite 2.39 and above.
|
| 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 Window 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.
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.
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
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.
Admin App Introduction
INTRODUCTION
| The Dualog Admin app is the enterprise mobility app that allows Dualog® Connection Suite™ administrative functions to be performed in a convenient, modern and safe manner. |
 |
FUNCTIONALITY
Functions currently available in the administration Dualog portal will be alternatively available from the Dualog Admin app, and new functions might only be available in the app. This is to follow the trend that more and more users (and administrators) are using mobile devices (smartphones and tablets) instead of personal computers.
Because the Admin app is focused on administrative tasks, it requires administrator authentication to function. The users will be the same as the ones that currently have access to administer their vessels in dualog.net. The initial functionality is the Email Quarantine Administration.
DOWNLOAD LINKS
The Admin App can be downloaded from the following locations:
Google Play:
https://play.google.com/store/apps/details?id=com.dualog.admin
App Store:
https://itunes.apple.com/kr/app/dualog-admin/id1322916600
Scan the QR code to download from the App Store or Google Play:
Crew Connection App introduction
INTRODUCTION
|
Dualog Crew Connection App is for connecting to Dualog® Connection Suite™ Ship software when used onboard a ship with the service enabled. It provides authentication and internet usage control.
|
 |
KEY ELEMENTS
- Fair allocation of data capacity onboard, by management assigning each crew member a data volume (Mbyte) quota per month or week or day. There might also be a time limit per day, as well as the possibility of buying additional data.
This app allows the individual crew member to monitor data usage, providing full visibility and control over his quota.
- Quota allocation and email access require each crew member to use his/her credentials (email and password) provided by management.
This app makes it simple to use these credentials to log on and log off mobile devices from Dualog® Connection Suite™ Ship.
- Dualog® Connection Suite™ Crew Email can be accessed directly from within the app when onboard.
DOWNLOAD LINKS
The Crew Connection App can be downloaded from the following locations:
Google Play:
https://play.google.com/store/apps/details?id=com.dualogapp.dualogapp
App Store:
https://itunes.apple.com/kr/app/crew-connection/id1139734652?l=en&mt=8
Scan the QR code to download from the App Store or Google Play:
