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.
Network Control/Gateway Audit Events: Always send gateway connection status on start-up
Webmail: Give better error page if users don't have access to webmail
Version 5.13.002
New Features and Improvements:
Network Control: Record gateway online/offline status in cloud
Identity/AD integration: Add security group handling based on user rank and mappings configuration
Bugfixes:
DHCP: Now correctly handles leases created on apps.dualog.com
DHCP: Now correctly updates lease expire time and hostname on change
Version 5.13.001
New Features and Improvements:
Mail: Makes IMAP auto-subscribe to a folder after creating it.
Quota: Transaction list values are now rounded to 2 decimals.
Bugfixes:
Mail: Clean up orphaned MIME messages in the SMTP server.
Mail: Use an 'envelope from' as the email sender instead of aliases or message header values. Previously, sending from an alias could cause the message to be sent to "Needs Approval".
Mail: Enforce UTF-8 byte limits when truncating values for Oracle byte-sized columns.
Version 5.13.000
New Features and Improvements:
Quota: Added "speed cap" as option to Quota configuration. This is a per-device maximum speed limit that is automatically enforced.
Quota/Terms and Conditions: Added audit log for when users have accepted terms and conditions
Captain's Overview: Added search-filter to look up active users
Webmail: Updated to Roundcube 1.6.15
Bugfixes:
Mail/SMPT: Fix empty subject causing SMTP server to fail
Login/OAuth: Fix access tokens not being properly cached (token caching was turned off)
Webmail: Stop collecting addresses in Roundcube
Quota: Fix rare edge-case where users with expired timer or exceeded quota were not logged out
Quota/Captive Portal: Only show 2 decimals in currency
Quota/Captive Portal: No longer marks some sessions that are manually logged out as "remotely logged out"
Installer: Check that hostname does not exceed 15 characters in the full-installer
Webmail: Deny access for users that don't have access to webmail
IMAP: Change error message when file is to large for IMAP
Captain's Overview: Now hides user groups with no users
Version 5.12.002
New Features and Improvements:
Quota:
Added new "captain's overview" for logged in devices with option to log-out users (Requires QuotaReports-permission).
Users must now scroll down to bottom of terms and conditions before they can accept.
Terms and conditions headers 3-9 now have correct sizes.
Version 5.12.001
New features:
The legacy captive portal (/ipcontrol) has been removed. Users are now redirected to the Ship GUI "My Page".
The PHP API used by the legacy captive portal and the “Crew Connection App” is disabled.
The "Crew Connection App" no longer works with this version. Users must upgrade to the Quota App.
New features:
Quota/Terms and Conditions:
Custom terms and conditions can be configured that must be accepted by users before using internet on board.
App users require Quota App version 4.3.0 or newer. Otherwise, terms and conditions must be approved in the Captive Portal.
Quota/Captive Portal:
Allows user to change gateway or throttle-settings without logging out.
Device List: Added hostname from DHCP to logged-in devices overview.
Device List: Added "This device"-indication.
User and Login:
Supports "User cannot change password" property. If this is set, users are not allowed to change their password on board.
User is now required to enter an end-date when signing on to a new ship. This defaults to next month.
Bugfixes:
Quota:
Normal logout from Internet is no longer listed as "Remote logout".
Wallet balance now shows decimal numbers.
The "Connected devices"-page is now refreshed on an interval.
Speed-limit for gateway-config is no longer shared between different accounts on the same device.
"Network has changed"-events from Windows are now correctly processed. This reduces the risk of failing after network disconnection events.
Mail:
Cloud email accounts are now correctly sent to shore.
SMTP Relay: Fixed problem where incoming messages were not relayed.
"Manual Connect" button is hidden if user doesn't have access to it.
Identity Server:
Now always update scopes on restart.
Version 5.11.008
Bugfixes and Improvements:
Apache: Fixed a problem where the Apache Web Server did not start after a fresh installation due to a missing logs folder.
Version 5.11.007
New Features
Quota/Captive Portal
Allows users to throttle their Internet speed to reduce streaming quality and save bandwidth.
Requires "Gateway Selection At Login" User Group toggle, under the Groups > General tab.
Webmail
Added AI-Proof Reader
Note: This feature requires a feature flag to be set.
DHCP
Expired leases are now deleted on the client so the shore report only contains active leases.
Ship GUI/Captain's Overview
Added user group filtering for on-board users.
Note: This features hides users with no user groups by default
Ship GUI/Approve Hire
Allows approver to edit the pre-hire before approving it
Bugfixes and Improvements:
DHCP
Fixes problem where some leases are never considered "expired" and thus cannot be reused.
Quota/Captive Portal
Now refreshes the "Used Data" without requiring page reload.
Ship GUI/Hire
Hires created from devices with the local time set to the past or in the future are now correctly created.
IMAP
Adjust error text when large mail is appended to IMAP.
Security/Other:
Webmail
Upgraded RoundCube to 1.6.12
Ship GUI
Upgraded to Angular 20
Network Control
Network Control is no longer susceptible to DNS poisoning attacks. Source ports chosen by the NAT-engine are now picked randomly instead of from a sequential list.
Version 5.11.004
Bugfixes and Improvements:
Network Control/Quota
The NAT-engine in Network Control now uses ports from the IANA private range 49152-59152.
DNS requests now get their one entry per request in the NAT-table in Network Control. This is done to avoid UTMs from classifying the Dualog DNS relayed traffic as spam or hostile
Version 5.11.003
Bugfixes and Improvements:
Network Control
Now correctly marks gateways with no valid IP address as offline
DHCP
Fixed a potential crash when releasing a lease on the ship
Version 5.11.002
New Features
Sell Quota
The Sell Quota page now contains more details about users (incoming balance, usage, top-up per) per month - now also including last month
The Captain can now stop top-up for the remainder of the month for all users in one go
My Page
The automatic disconnect-timer can now be renewed
Users can now see their other logged in devices
The "Quota Reset" count-down now shows days or hours depending on how much time is left
Bugfixes and Improvements:
Sell Quota
It is no longer possible to create 0-dollars transactions
Quota can now be sold in cents
My Page
Now only refreshes if the user was successfully logged on
Local time zone no longer affects the "Quota Reset" count-down
Mail Management
Fix mail subpage stuck in infinite loading when mail has empty receiver fields
Mail
Set correct timestamp on mails sent internally
Fix mail statistics job populating stationary users from other ships
Version 5.11.001
Bugfixes and Improvements:
Platform:
Fixed a bug where the check for an existing Link installation would fail if it was in the 32 bit registry path.
Quota:
Fixed a bug where the IsSomeoneLoggedIn API response unpopulated CarrierVesselId field
Fixed a bug where a race condition would occur if a user logged out and back in very quickly.
Identity:
Added support for exposing a crew's rank to the id token and userinfo endpoints. This allows third-party applications to give access based on a user's rank.
Version 5.11.000
Bugfixes and Improvements:
Users are now logged out from Internet once their hire is expired. With the new "Custom IP Login Timer" feature, users are potentially allowed to be logged in for years. With this feature, it was suddenly possible to have an Internet login that lasts longer than the user's hire. In this case, the user is now logged out as soon as the hire expires.
Bugfix: Captive portal is now always redirecting to "my page" - also for users with permission to view the overview page.
Bugfix: Clicking the admin-panel no longer opens a new tab. This prevents the user to be logged out after one hour if both attempt to refresh the authentication token at the same time.
Minor: Legacy and no-longer-used antivirus services and GUI-links are removed.
Version 5.10.005
New Features
Quota
My Page
Users with the required permission are now allowed to specify their own "IP Login timer"
Slop Chest
Captains are now able to stop users from topping up their account for the rest of the month
Captive Portal
Added automatic mode for captive-portal to remove the need for common DNS across multiple networks. This will greatly improve Dualog Protect interoperability
Bug Fixes and Improvements
IMAP: Prevent files that are too large from being added to IMAP folders.
Version 5.10.003
Bug Fixes and Improvements
Extended token lifetime in the identity server from 1 to 24 hours. We experience time drift on many ships, and this is an attempt in being more lenient.
Introduce new rename behaviour for IMAP to reduce incidences of Outlook sync issues on the IMAP server
Fixed a bug where Link id updates were not correctly replicated to the linkintegration table
Version 5.10.002
Bug Fixes and Improvements
Network Control/Gateway Selection
Route caches could incorrectly point to incorrect gateway after login with gateway selection enabled. Route caches are now correctly cleared on login.
Version 5.10.001
Bug Fixes and Improvements
Network Control/DNS Relay:
DNS servers were not correctly updated on failover between gateways
Version 5.10.000
New Features
Quota Gateway Selection
It is now possible to allow user groups to choose between the quotas they have configured. This allows users, for example, to use their VSAT quota for reading the newspaper, while saving the Starlink quota for watching a movie later.
Note: this requires a new user group configuration to be enabled
Bug Fixes and Improvements
"Login loop" is fixed. Users are now logged in on their first attempt
Captive Portal redirection now works for rules with gateway specified
Version 5.09.000
Bug Fixes and Improvements
Ship UI
General: upgrade Angular from v16 to v19
General: fixed a memory leak
General: Add username field to active hire table
Identity: Fix blank page in login flow if user must change password and set hire
Identity: Add session to tokens so that when you log out from one browser you're not logged out of all browsers
Identity: Fix when logging out of Dualog Webmail, you're redirected to Ship UI login page instead of the webmail login page
Identity: Better token handling in the Ship UI. Makes sure tokens are not tried to refresh in parallel.
Identity: Fixed a bug where if hire has expired for user they are not able to log in again until cookies are cleared
Quota: Add SignalR for live updates of gateway fail-over state
Quota: add MTU validation to external routes
Quota: Added a filter to the purchase history so only Top-ups are shown.
Mail:
Fixed SMTP client parsing commands wrongly e.g. if a mail address contains the string "quit", the SMTP server will terminate the session
Version 5.08.009
New Features
Added the newest version of the Link Platform, which contains the new Remote Terminal feature. Dualog admins and customers with the feature flag for this enabled can now remotely run PowerShell on the installation from the Dualog Portal.
Changes
Identity Management:
Added Active Directory provisioning. Added new service DualogAccess.Client.Worker.Service that is responsible for provisioning users to AD
Bug fixes
Mail:
Fixed an issue where the access rights were not being set properly on IMAP inbox folder in some cases
Platform:
Fixed an issue with ICM trying to upload empty replication files
Fixed an issue where login fails in the new UI when a user is already logged into the old UI and "remember me" was pressed
Fixed an issue where Ship UI won't switch to using OAuth when persistently logged in and OAuth has been enabled
Ship API:
Fixed an unhandled exception in backgroundservice causing service to stop when Oracle is down
Network Control:
Fixed an issue where if Network Control had a gateway at the top of the priority list with a gateway address that doesn't exist, it would use that as the active carrier forever.
Version 5.08.008
Changes
Network Control/Captive Portal - Now redirects users to the ship portal instead of the PHP-based portal
Network Control/Live Traffic: Now support Live Traffic reporting
Bug fixes
Network Control/Captive Portal - Now correctly redirects users to captive portal.
Ship UI - Login bypasses change-password dialogue if username has a case-insensitive match
Ship UI - No longer log out users when they should still be logged in
Ship UI - Make access client cookie not session only
Ship UI - Fix loading spinner color in access client
Version 5.08.007
Bug fixes
Fixed an issue with ship-to-ship emails
Version 5.08.006
Bug fixes/Other
Add NOOP and RSET commands to SMTP
Update roundcube to 1.6.11
Fix accounts that have no delivery option will be detected as external mails and sent to shore
Version 5.08.005
Bug fixes
Add more logging to mail flow
Make sure worker continues processing mails even though one mail fails
Fix casing issue when sending internal mails
Fix master getting extra copies of mail
Fix duplicate body parts being generated
Fix sign-on being wrong in some time zones
Add option to not use "mime from" when checking the from address
Version 5.08.004
Bug fixes
Fixed a case where internal emails were stored into the wrong IMAP folder
Release Notes
Version 5.08.003
Bug fixes
Ship API/Worker - Fix case sensitive email comparison on queries
Ship API - Use 127.0.0.1 when connecting to Network Control
Service Manager - Hotfix: Ensure connect to 127.0.0.1 when doing lock on tunnel
Version 5.08.002
Bug fixes
Installer - Add firewall allow in smtp server (on new install/upgrade to 5.08).
Network Control - Simplified DNS by changing its behavior to broadcast incoming requests to all configured DNS servers simultaneously and forwarding only the first response received.
SMTP server - Don't use Mimekit library to add Dualog headers so it will preserve the header formatting.
Ship API - Add lowercase when checking if mail sender needs approval
Ship Worker - Fix rescheduling of background tasks
Transmission Client - emails approved from quarantine are now downloaded properly when ICM is enabled
Version 5.08.001 (version 5.07 has been merged with this version)
New Features
New login page
Role-Based Access Control
Outlook/App Passwords
Synchronizing user ranks to ship side
Implemented password policy on ship side identity server
SSO between Ship UI and webmail
Turned Connection Suite service ports off by default
Added OAuth support to
IMAP server
LDAP server
Ship UI
Webmail
Ship API
New Services
Reimplemented SMTP server
Identity server
Bug fixes/Other
Fixed a bug where desktop view in webmail would sometimes malfunction
Various minor bug fixes in the Ship UI
Network Control Failover: Fixed a bug where reset gateway to init state from worker fails if allow override is false
Updated third-party dependencies
Version 5.06.004 (note that version 5.06.003 has been merged with this version)
Bug Fixes
Quota: Users are now correctly logged out if their quota is exceeded.
Live Traffic Reporting (Experimental): A disconnected Link-client no longer shuts down the Worker Windows-service.
Version 5.06.002
Bug Fixes
Network Control/Firewall: Rules with the same source IP, gateway and overlapping port numbers are now correctly processed.
Network Control/Failover: The lowest ranked gateway in Network Control is no longer deactivated if ping-test fails. This prevents Network Control from having no available gateways and reporting an error to users.
Network Control/Live Traffic Reporting (Experimental): Now correctly uploads traffic data to cloud.
Version 5.06.001
General Changes
This version and future versions of Connection Suite now only support 64-bit operating systems
Updated .NET to version 8
User Interface - Connections
Override now lets the user specify allow/block. When an override is applied, the user is able to choose if they want to enable or disable the gateway. This allows users to add override commands to enable a gateway even if it is already online
Ship API
Network Control
WAN-failover settings no longer require restart. If the initial-state or other WAN-failover settings are changes, they are now applied automatically.
Clearing the override now resets the gateway to its initial state. When an override is reset, the gateway is reset to its "initial state". This prevents gateways from ending up in an unintended state.
Network Control/Quota
Added support for gateways with the same MAC-address. Gateways with the same MAC-address can now be used as long as they are in separate LAN-segments. This is common when the communication equipment is located behind a firewall/router and separated using VLANs.
IMAP Server
If a mail is over 50 MB, a MIME message gets returned to the end user that saying the message is too big. We’ve seen at least one case where the mail parsing caused an extremely large message. This caused Outlook to get out of sync.
Added logic to stop an infinite loop when parsing content-language. If a MIME has multiple languages in the content-languages, it could cause an infinite loop when parsing the message.
Version 5.06.000
Desktop view is now available in Dualog Webmail, displaying the messaging preview underneath the message listing, rather than on the side
Visual improvements to Instant Communication Mode: End users can now see the status of Instant Communication Mode i.e. whether the vessel is currently Downloading, Uploading, In Sync, or Offline
Fixed a bug in Instant Communication Mode where there could be a mismatch in generated hardware id
Version 5.05.003
Fixes
Fixed a bug where Quota traffic incorrectly was marked as business traffic and not counted towards a user's allowance
Version 5.05.002
Fixes
Rewritten part of the Instant Communication Mode where some ships have observed uploads stopping.
Version 5.05.001
Fixes
Increased a timeout value in Instant Communication Mode to resolve an edge cases where some ships have reported uploads stopping.
If there are existing members in the organization, they can send you an invitation (see Procedure for Owner).
If there are no existing members, please contact Dualog Support at support@dualog.com using your registered email address or username to request access.
Accept the invitation (Under Procedure for invitee)
You are all set to access the Dualog portal and all its features!
ADDITIONAL INFORMATION
Articles on the available features on Dualog Portal are available here.
For official feedback submission, please log in to Dualog Portal and submit a form by clicking on the round icon located at the bottom right of the page.
The Dualog Client allows you to install the new Digital Platform services. The client can be installed on any client PC on board, as long as the system requirements are met.
Depending on the service you are planning to install, you may need to install the same client on different PCs on board i.e. you can have Dualog Protect on one PC and Dualog Drive on another PC. If unsure about where to install it, get in touch with us. We will be happy to help.
PREPARATION STEPS
You will need a couple of things in place before you get started with the installation of the Dualog services.
Ensure that you have configured your firewall to allow:
Protocol: TCP Ports: 443 Direction: to and from Destination: apps.dualog.com and 93.188.232.76
If you use the Dualog Network Control service, the rule can be added directly on the Dualog Portal. Refer to the article Network Control: Firewall Rules if you should need extra assistance.
Follow the process, choosing the installation path and the service(s) you wish to install:
Dualog Drive
Dualog Protect
Dualog Access
Dualog Fetch
Dualog Endpoint Security
A Complete window will appear after it has successfully completed the installation > Click “Finish”.
The next step will be to activate the client.
ACTIVATION OF DUALOG LINK CLIENT (VIA ACTIVATION CODE)
Once the installation is completed successfully, you will be re-directed automatically to the following page:
Click on "Check connectivity" to perform the mandatory internet connectivity test.
Once the internet connectivity test is successful, click on "Activation Code" (Go here to troubleshoot a failure in one or more checks)
Input the activation code that must first be created on the Dualog Apps portal.
Click on "Activate"
Upon successful activation, the installation is now active and reflected on the Dualog Apps portal under Installations.
ACTIVATION OF DUALOG LINK CLIENT (VIA MANUAL LOGIN)
Once the installation is completed successfully, you will be re-directed automatically to the following page:
Click on "Check connectivity" to perform the mandatory internet connectivity test.
Once the internet connectivity test is successful, click on "Activation Code" (Go here to troubleshoot a failure in one or more checks)
You will be redirected to apps.dualog.com, where sign-in is required with a valid account.
Select the organization, and ship you are installing on, followed by an installation name before clicking on "Activate Client"
Click on "Activate" on the confirmation window.
Upon successful activation, you will see the confirmation message.
SHORESIDE CHECKS
Before moving forward, we need to check that the Dualog Cloud is “seeing” the new ship online.
VERIFICATION ON DUALOG APPS PORTAL
Go to Installation, and confirm that the ship you have installed is “online”.
Verify that the required service(s) has/have been installed and shown.
If your ship is not listed or offline, please make sure all services are running. In case you are not able to get the ship online on apps.dualog.com, get in touch with Dualog Support.
3. Click on the individual installed service(s) and confirm that the needful has/have been enabled as well. (Configurations or tasks would have to be pre-configured prior to this)
Dualog Drive
Dualog Protect
Dualog Endpoint Security
Dualog Access
If you have difficulties or have further inquiries on any of the above, get in touch with Dualog Support.
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".
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, proceed with IMAP restoration.
You are now ready to create your very first Drive task!
Expand the top left menu > Drive
To learn more about each type, the differences, and use cases, click on "Read about the sync task" and "Read about the move task."
Useful tip:
Before diving into more advanced testing, start with a simple Move Task between the newly created vessel and office. This will help you understand the core concept of Dualog Drive.
1.4 Let’s Test
Now that you’ve completed the steps above, the folder(s) you created for each task should automatically appear on the respective installations.
To test:
Place a file in the folder on the source installation
Observe the transfer process in action
You’ll notice that the file briefly disappears before reappearing in the destination folder.
Feel free to experiment with both types of Drive tasks to explore the available options and better understand the differences between Move and Sync tasks.
Dualog Endpoint provides a comprehensive and effective approach to cybersecurity, delivering strong protection against malware, phishing, and ransomware. It also enhances visibility and control across endpoints, allowing administrators to monitor devices more efficiently and respond to security incidents in real time.
Maintaining a high level of protection requires frequent updates. Dualog Endpoint distributes updates daily to stay ahead of evolving threats. On average, it consumes approximately 3 GB of data per 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: to and fro
Destination: apps.dualog.com, downloads.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 machine that you wish to protect with Dualog Endpoint.
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.
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 click 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 a machine that is an active 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 within the Dualog Apps Portal. Now click on “Assign” and make sure your ship is selected 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.
CUSTOM DNS ZONE RESOLUTION
If you have a local domain controller onboard your vessels that you wish to use to resolve a local domain name, you can configure protect to route requests for that domain to a specific IP address to resolve these requests.
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:
As part of Dualog Link's platform, a Remote Terminal feature (PowerShell) has been introduced since Connection Suite v5.08.009. This feature is enabled for all Dualog users and will require 2FA enabled on their accounts.
Activation
Activation will first require a feature flag to be enabled. In order to do so, please send in a request to support@dualog.com.
Enabling Remote Access
Once the feature flag is enabled, please proceed to log onto https://apps.dualog.com/. Upon logging in, go to Organisation on the left panel and scroll down to 2FA and Remote Terminal in order to enable.
You can also choose to enable and authorize the team at Dualog Support to access the Dualog PC remotely for trouble shooting purposes.
Accessing Remote Shell
Once enabled, on Dualog Apps portal, proceed to Installation> Installation Overview> Choose Ship> Click on Machine> Remote Terminal Tab
Click on + New Session and you will be presented with a Windows PowerShell screen as per below to perform any PowerShell commands and scripts.
Upon completion, click on Close Session. For security and audit purposes, you will be able to view the Session History which indicates who had logged in to the machine and the amount of time spent during that session.
Do kindly reach out to us at support@dualog.com if you should require any additional assistance or information with regards to this feature above.
The Connection Suite is composed of various modules interconnected by a background database known as Oracle. This database may encounter interruptions in its functionality due to a range of factors, including unexpected server shutdowns, hard drive bad sectors, or program bugs.
However, the majority of issues typically stem from the database not operating correctly.
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:
You will not be able to login to the Dualog Connection Suite page due to the error "could not connect to the database.
No emails can be sent or received, especially on Outlook where it reflects send/receive error
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.
BASIC 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. (Please contact Dualog Support if you are uncertain of the initial password)
Hit Enter (Note: the password will not show while typing. Just type the password and hit Enter. )
!!!IMPORTANT!!!
You are currently logged in as the database administrator user and connected to the Oracle database. Only authorized personnel are advised to proceed with any described changes at their own risk.
If uncertain, it is recommended to contact Dualog Support for assistance. It is crucial to exercise caution and refrain from executing any commands without a clear understanding of their implications, as there is no safety mechanism in place to mitigate potential database corruption.
In the event of database corruption or errors, a complete reinstallation of the Dualog Connection Suite will be necessary to restore functionality.
The initial step is to restart the database, as it serves as the simplest method to identify any potential errors associated with it. Please input 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.
ADVANCED TROUBLESHOOTING (DATABASE)
If the issue persists despite completing the basic troubleshooting steps outlined above, you may choose to proceed with either of the following options:
Navigate to the directory: C:\dualog\oraclexe\app\oracle\diag\rdbms\xe\xe\trace, retrieve the alert_xe.log file, and forward it to Dualog Support for further analysis.
Alternatively, if you possess advanced technical expertise:
Proceed with the following troubleshooting steps:
If you encounter a database corruption error message, which may manifest in various proprietary error codes, you should access the Oracle database through SQL*Plus, as demonstrated previously. Once connected, input the following commands:
recover database;
Once this has finished, type:
alter database open;
If the database successfully opens and you receive a message confirming "database opened," then everything has proceeded as expected.
In the event that the aforementioned commands do not resolve the Oracle issue, you can return to the command prompt window and navigate to the following path:
Start -> All Programs -> Dualog -> Connection Suite -> Support -> and run a program named "XERestore."
Alternatively, you can execute "XeRestore.bat" as an administrator via the directory:
C:\dualog\connectionsuite
This action will initiate an automated database sanity check, which will identify and resolve some of the most common Oracle issues.
Upon completion of this process, you will be prompted to press any key to continue. Once you have done so, proceed to run Dualog Connection Suite and verify if everything is functioning correctly.
"ORA-00257 ARCHIVE ERROR"
"ORA-03113 END-OF-FILE ON COMMUNICATION CHANNEL"
The error messages suggest that the space allocated for Oracle archive logs has reached its maximum capacity, resulting in the inability to open the database.
To resolve this issue, it is necessary to increase the maximum size permitted for the archive logs. Access the Oracle console as outlined previously and input the following sequence of commands.
If you encounter an error indicating inability to connect to the database, close the command prompt and log into SQL*Plus again. Then, proceed with the following steps:
1. Open CMD
2. Type “rman target sys/”
3. Type in the oracle password
4. startup mount
5. delete noprompt archivelog all;
6. alter database open;
Once the database has been opened and mounted, proceed to verify by logging into Dualog connection suite page again.
"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.
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 the recipient(s)
OVERVIEW OF ALERTS
ConnectionSuite Alert Parameters
Alert
Description
Threshold
Connection Suite Connectivity
Alert when Connection Suite has not connected to the Dualog Cloud for an extended period of time.
60 - 2880 min
Crew sign-on limit
Alert when there’s more than a predefined amount of crew signed on a ship.
1 - 200 min
Dualog Drive Alert Parameters
Alert
Description
Threshold
Drive Detected issues
Alert when Drive detects an issue
60 - 2880 min
Transfer not completed
Alert when transfer has taken too long to complete
5 - 10080 min
Drive Move Package with missing destination
Alert when there is no installation destination available
Threat detected in file
Alert when Drive has detected a threat in one of the files to be transferred.
Dualog Protect Alert Parameters
Alert
Description
Threshold
Devices with detected C2 Traffic
Alert when a device is trying to contact a malware (Command&Control/C2) server .
Dualog Protect Alert Parameters
Alert
Description
Threshold
Failing IMAP backup
Alert when a ship does not have a recent IMAP server backup.
2 - 30 days
Dualog Link Alert Parameters
Alert
Description
Threshold
Link Platform Connectivity
Alert when a Link Platform installation has been offline for an extended period of time.
15 - 2880 min
SharePoint Integration Alert Parameters
Alert
Description
Threshold
SharePoint Secret Expired
Alert when a sharepoint secret expires
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.
