Search This Blog

Loading...

Wednesday, September 28, 2016

Unblocking URL blocked by Trend Micro Worry Free Business Security

When a URL has been blocked by Trend Micro Worry Free Business Security, it is because the URL has been classified by Trend Micro's security team as being a source of a security issue.  The block is then transmitted globally to all Trend Micro products that utilize the Trend Micro Block List.  However in some instances, you may find that you need to locally unblock a URL blocked by Trend Micro Worry Free Business Security.

Following are the steps to locally unblock a URL blocked by Trend Micro Worry Free Business Security:
  1. From your Windows Server, open Internet Explorer.

  2. Browse to the Trend Micro Worry Free Business Security Manager on your Local Area Network: https://[server-name].[domain-namne]:4343/officescan/default_SMB.htm

  3. Click Continue to this website.

  4. Enter the password and log on.

  5. Click Security Settings.

  6. Click Desktops and confirm the relevant Desktops are Connected and Online.  If not, you may need to reinstall the Client on the Desktops.

  7. Right-mouse click Servers (default) - Configure Settings.

  8. Click Approved/Blocked URLs.

  9. Under URLs to approve, type the website address.  Add both http://domain.com and http://www.domain.com and any other relevant sub-domains.

  10. Click Add.

  11. Click Save.

  12. Click Security Settings.

  13. Right-mouse click Desktops (default) - Configure Settings.

  14. Click Approved/Blocked URLs.

  15. Under URLs to approve, type the website address.  Add both http://domain.com and http://www.domain.com and any other relevant sub-domains.

  16. Click Add.

  17. Click Save.

  18. Click Security Settings.

  19. Right-mouse click [server-name] - Configure Settings.

  20. Click Approved/Blocked URLs.

  21. Under URLs to approve, type the website address.  Add both http://domain.com and http://www.domain.com and any other relevant sub-domains.

  22. Click Add.

  23. Click Save.

  24. Close Internet Explorer.

  25. From the Server and any Client using Trend Micro Worry Free Business Security, right-mouse click the Trend Micro Worry Free Business Security icon in the System Tray and select Update Now.

  26. After updating, the website that was previously blocked by Trend Micro Worry Free Business Security is now accessible.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Tuesday, August 23, 2016

Intuit Quickbooks 2016 Database Server Manager Stopped + Windows Server 2012 + SQLAny Event ID 1

Today, I was contacted by a customer regarding the Intuit QuickBooks 2016 Database Server Manager running on their Windows Server 2012.  Since May of 2016, they have been able to start or restart their QuickBooks Database Server Manager without issue.  As of a day ago, QuickBooks Database Server Manager would not start.  The error logged in the Event Viewer was SQLANY Event ID 1, SQLANY 16.0 cannot be found.  This would lead one to believe the QuickBooks Database Server Manager needed to be reinstalled on the Server.  This was not the resolution to the issue.  A page on the QuickBooks Community website indicated the latest update for QuickBooks needed to be manually installed on the Server.  This was also not the resolution to the issue.  I was able to isolate the cause of the issue when I read on a third-party website that if you stop the Windows DNS Server Service and then try starting the QuickBooks Database Server Manager, you may find the QuickBooks Database Server Manager starts without issue.  I did as instructed and it did start without issue.  This would lead one to believe the problem is a port conflict between the port being assigned to the QuickBooks Database Server Manager Service (QuickBooksDB26) and the Windows DNS Server Service.  This was not the cause of the issue.

The issue was resolved by Intuit QuickBooks Technical Support instructing me to change the QuickBooks Database Server Manager Service (QuickBooksDB26) from logging on as QuickBooksDB26 to Local Account and Allow Service to Interact with Desktop.

So in effect, I was told by Intuit to change the LogOn settings of the Windows Service designed by Intuit from the default Intuit setting to a custom setting.  First, I am perplexed as to why this issue arose out of nowhere when there have been no changes to the Server.  Second, I find it odd that if this is a known issue by Intuit wouldn't the installer have set the LogOn to Local Account upon installation.  Third, what is the purpose of the installer creating QuickBooksDB26 if it is now not utilized by the Service?

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Tuesday, May 24, 2016

This app can't open. App can't be opened using the Built-in Administrator account.

The error message, "This app can't open.  App can't be opened using the Built-in Administrator account." is not a normal error message one would encounter in the use of their Windows 8/Windows 10 computer.  This issue is likely being manufactured by someone who modified Windows 8/Windows 10 by Disabling EnableLUA without a complete understanding of User Account Control and Admin Approval Mode.  To quote the popular website Windows IT Pro, "This is not a supported state of the OS and will block the modern applications-- so don't do this."

EnableLUA controls not only User Account Control but also Admin Approval Mode.  By default in Windows 8/Windows 10, EnableLUA is Enabled.  On the internet, there is the mistaken belief that setting EnableLUA to Disabled is an inocuous registry setting one can use to Disable User Account Control.  This is incorrect.  If EnableLUA is set to Disabled then Admin Approval Mode is Disabled which results in the error message: "This app can't open.  App can't be opened using the Built-in Administrator account."  Therefore, it can be understood that setting EnableLUA to Disabled results in functionality within Windows 8/Windows 10 to no longer function.  This includes built-in apps like Microsoft Edge, Clock, Calculator but also Control Panels like the Windows 10 Settings Control Panel.  Ultimately, it is a terrible idea to Disable EnableLUA because it impacts not just User Account Control but also Admin Approval Mode.

The proper method to disable User Account Control is to drag the User Account Control slider to Never Notify.  Dragging the User Account Control slider to Never Notify does not change EnableLUA from 1 to 0 therefore allowing Windows 8/Windows 10 to continue to function as it was designed by Microsoft.

To return Windows 8/Windows 10 to normal functionality:
  1.   Click Start - Run.

  2.   Type: regedit

  3.   Click OK.

  4.   Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Policies\System

  5.   If it does not exist, create a new DWORD (32-bit value) entitled EnableLUA and set the value to: 1

  6.   If it does not exist, create a new DWORD (32-bit value) entitled FilterAdministratorToken and set the value to: 0

  7.   If it does not exist, create a new DWORD (32-bit value) entitled ConsentPromptBehaviorAdmin and set the value to: 5

  8.   If it does not exist, create a new DWORD (32-bit value) entitled ConsentPromptBehaviorUser and set the value to: 1

  9.   Reboot.
This issue has been resolved.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Friday, April 22, 2016

The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.

You may encounter the following error message when using the L2TP/IPSec VPN Client that is native to the Windows Operating System: "The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer."  This error message typically occurs when you are using the wrong Pre-Shared Key for your L2TP VPN.  This error message can occur when other components of your configuration are incorrect but the first thing to confirm is that you are using the correct Pre-Shared Key.

If you are using the wrong Pre-Shared Key, the L2TP VPN connection will say Connecting for a long period of time and then display the error message: "The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer."

If you are using the wrong username or password, the L2TP VPN will immediately respond with: "The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server."

If you are using the correct username, password and pre-shared key, the VPN connects immediately.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Wednesday, September 16, 2015

How do you Remote Desktop to a computer using an L2TP VPN?

To Remote Desktop to a computer using an L2TP VPN:

These steps may be slighly different on your computer depending upon which version of Windows you are using.
  1. Click Start - All Programs.

  2. Click Accessories.

  3. Click Remote Desktop Connection.

  4. In the Computer field, enter the IP Address of the computer or the Fully Qualified Domain Name (FQDN) of the computer you wish to control.

  5. Click Connect.

  6. Enter the username and password you use to login to the computer.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you disconnect from an L2TP VPN using Microsoft Windows?

To disconnect from an L2TP VPN using Microsoft Windows:

These steps may be slightly different on your computer depending upon which version of Windows you are using.
  1. Click Start - Control Panel.

  2. Click Network and Sharing Center.

  3. Click Change Adapter Settings.

  4. Double-click the VPN Connection.

  5. Click Disconnect.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you connect to an L2TP VPN using Microsoft Windows?

To connect to an L2TP VPN using Microsoft Windows:

These steps may be slighly different on your computer depending upon which version of Windows you are using.
  1. Click Start - Control Panel.

  2. Click Network and Sharing Center.

  3. Click Change Adapter Settings.

  4. Double-click the VPN Connection.

  5. Click Connect.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you setup L2TP VPN Windows Domain DNS using the Watchguard XTM-25 Web UI?

To setup L2TP VPN Windows Domain DNS using the Watchguard XTM-25 Web UI:
  1. Browse to the Watchguard XTM Web UI.

  2. Click Network.

  3. Click Interfaces.

  4. Below DNS Servers in the DNS Server field, enter the IP Address of the Windows Domain Controller.  Insure this IP Address is the first in the list.

  5. Below this, enter the Primary and Secondary DNS Servers from your ISP.

  6. Click Save. 
When connected to the L2TP VPN, you will have to use the Fully Qualified Domain Name (FQDN) ala host.domain.suffix to access the Computer inside the Windows Domain.  Example: computer01.mydomain.com.  

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Legal Notice

Alan Curtis provides programming examples and technical information for illustration only without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose.

Alan Curtis does not assume any legal liability or responsibility for the accuracy and/or completeness of the information provided. Alan Curtis will not be held liable for any direct or indirect loss or damage arising under this legal notice or in connection with the use of this website. Alan Curtis is not affiliated with Microsoft, Yahoo and Google. All trademarks and copyrighted material are the property of their respective owners.

The opinions expressed by Alan Curtis on this blog is based upon information he considers reliable but is not warranted for its completeness or accuracy and should not be relied upon as such. Alan Curtis' statements and opinions are subject to change without notice.

The entire contents of this blog has been copyrighted by Alan Curtis unless otherwise indicated. All rights are reserved by Alan Curtis and content may not be reproduced, downloaded, disseminated, published, or transferred in any form or by any means, except with the prior written permission of Alan Curtis.