Thursday, December 20, 2018

Azure Point to Site VPN failure with error code 809

I ran into some trouble today troubleshooting a developer's workstation. The issue was when using a Point to Site IKEV2 VPN some clients could not connect - they received an error:


The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem. (Error 809)
The strange thing was that some other workstations seemed fine.


After bashing our collective heads against the wall, checking checking the P2SChild, doing all sorts of network troubleshooting to the endpoint DNS name - azuregateway-8fc2c9e3-26cd-432a-ae47-92b7f6422a5d-e1a7e8cec41d.vpn.azure.com, editing registry, checking firewalls, etc, we finally determined the cause of the issue.

The issue was only apparent on Windows 10 desktops with OS version 1703. After manually updating these Workstations to Windows 10 1803 we no longer received the 809 error.

Moral of the story - Remember to update your Windows 10 versions!

Tuesday, December 18, 2018

Tip 0004: Handy Cheatsheats

Here are some handy cheat-sheets to reference for Powershell, Git, ETC.

https://github.com/PrateekKumarSingh/CheatSheets

Here is a great list of network cheat-sheets.

http://packetlife.net/library/cheat-sheets/

Wednesday, December 5, 2018

Tip 0003: ASP page to emulate server response codes

This is a handy page to emulate a response code on the server. This is useful for testing your custom error pages, either from IIS or Cloudflare.

https://gist.github.com/blarsonrp/fa373cd9a562d91d9a42419a34a24a7a


<html>
<%@ Page Language="C#" AutoEventWireup="true"%>
<script runat="server">
protected override void OnLoad(EventArgs e)
{
base.OnLoad(e);
this.Response.StatusCode = 418;
Response.TrySkipIisCustomErrors = true;
}
</script>
</html>

Friday, October 26, 2018

Tip 0002: httpstat.us for HTTP response codes

Need to trigger a specific response code for some testing? Possibly need to test how your monitoring tool handles a 301 response code?

There is a wonderful free service called httpstat.us which can be used to trigger HTTP response codes and payload. This is helpful in testing apps, or web monitoring tools. Simply append the response code that you want to receive with the tool you're testing, for instance, httpstat.us/500

Site:
https://httpstat.us/
GitHub project:
https://github.com/Readify/httpstatus

Friday, October 19, 2018

MSSQL - Fixing Transaction Log backups failing with error "@@SERVERNAME does not match SERVERPROPERTY('ServerName')"

To Fix Transaction Log backups failing with error "@@SERVERNAME does not match SERVERPROPERTY('ServerName')" you can simply run the following to verify that the machine name and server name property are the same:


SELECT SERVERPROPERTY('MachineName')
SELECT @@SERVERNAME


If not, you must fix it manually and RESTART SQL - replace oldname and newname with the new name of the SQL server.

sp_dropserver 'OLDNAME;
GO
sp_addserver 'NEWNAME', local;
GO

Monday, October 15, 2018

What is a DPOR (Designated Partner of Record) - Azure Knowledge

The DPOR stands for designated partner of record. This is a delegation you can add to your Azure subscription that I partner may request. This request allows the VAR, MSP, or consulting group to get benefits for assisting their partner in Azure.

By entering in the partner information when requested your really help your partner out :)



More information here:

Monday, October 8, 2018

Tip 0001: Invoke-Webrequest for a specific hostname without a host entry

My imposter "Ah-ha" moment of the day is finally realizing that you can invoke-webrequest for a specific hostname without setting a host entry by using the invoke-webrequest cmdlet with the host header.

Ie: invoke-webrequest 172.16.43.5 -Headers @{Host = "mydomain.com"}

Azure Point to Site VPN failure with error code 809

I ran into some trouble today troubleshooting a developer's workstation. The issue was when using a Point to Site IKEV2 VPN some clients...