Docker hv-sock proxy (vsudd) is not reachable, Windows 10

Yes, I am playing (or trying to) with Docker.  My first step is to install Docker and get it up and running. So far I am confident that I have all the prerequisites, however Docker fails to properly start with the following error:

Docker hv-sock proxy (vsudd) is not reachable
at Docker.Backend.ContainerEngine.Linux.ConnectToVsud(TaskCompletionSource`1 vmId) in C:\gopath\src\\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 267
at Docker.Backend.ContainerEngine.Linux.DoStart(Settings settings) in C:\gopath\src\\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 251
at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) in C:\gopath\src\\docker\pinata\win\src\Docker.Backend\ContainerEngine\Linux.cs:line 123
at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.<Register>b__0(Object[] parameters) in C:\gopath\src\\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47
at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

Currently I am researching possible solutions to fix, however non of the suggestions has worked for me. If you have suggestions please feel free to comment and let me know.

Here is a systeminfo of the system I am testing with:

OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.15063 N/A Build 15063
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation

System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz
[02]: Intel64 Family 6 Model 30 Stepping 5 GenuineIntel ~2926 Mhz

Total Physical Memory: 4,096 MB
Available Physical Memory: 2,755 MB
Virtual Memory: Max Size: 4,800 MB
Virtual Memory: Available: 3,167 MB
Virtual Memory: In Use: 1,633 MB

How to demote a Windows Server 2012 Domain Controller

In this short write up I will go over steps to demote a Server 2012 domain controller.

If you have worked in Active Directory and Windows Domain Administration over the years you may recall that in previous version of Windows Server that you would use the command line tool of ‘DCPROMO’ to promote or demote a server. Since Server 2012, the use of DCPROMO has been deprecated. In fact, if you attempt to use it you will be inform of this via the Active Directory Domain Service Installed.

In Server 2012 and later versions the use of Server Manager or PowerShell is required to promote / demote a server to/from a Domain Controller (DC). Below I provide steps on how to demote a server with some illustration along the way. Also, here is a quick YouTube video on the process:

Log into the domain controller you intend on demoting and Launch the Server Manager, select the Manage drop down menu, select Remove roles and features.

On the server selection page, select the desired server from the pool.

On the Remove Roles and Features Wizard, un-tick the Active Directory Domain Services box

The Remove Roles and Features dialog box will open. Click Remove features

On the Remove Roles and Features Wizard dialog box Validation Results box will appear. The domain controller must be demoted before continuing. Click on Demote this domain controller.

On the Active Directory Domain Services Configuration Wizard enter the required credentials to demote this server, click Next.

You will have several removal options. From the forced remove of failed domain member, to removing of the last domain in your forest. Make the selections which is appropriate for your remove task and click Next

Finally you will arrive on the New Administrator Password, enter and confirm the new local administrator account password, click Next.

On the Review Options verify the information is correct and click Demote.

After the server has restarted it will no longer be a domain controller

And that is it.

Tech Short: Capturing packets on Checkpoint

I’ve recently found myself capturing network traffic to troubleshoot reported issues. To successfully capture packets the use of tcpdump is required.  And while you may be familiar with using this tool, the use is slightly different on Checkpoint devices.

The devices in this reference is Checkpoint R77.30 and R80 devices.

To capture the correct network packets you must first disable Checkpoints SecureXL feature which is an acceleration solution that maximizes network performance of the Firewall.

To disable SecureXL, run the command:

fwaccel off

To check the overall SecureXL status:

fwaccel stat

Now that SecureXL has been disabled, continue to the capture steps below:

To capture packets, issue the following command:

tcpdump -s 0 -nni <interface_name> -w capture_file_name.pcap

Press Control-C (Ctrl C) to break the capture

Re-enable SecureXL, by running the following command:

fwaccel on

Retrieve the capture file and review using a tool such a Wireshark

Tech Short: Debug VPN in Checkpoint R77.30

The following tech short will provide a list of commands used to enable debugging in Checkpoint’s R77.30 Firewall. To start you must  SSH into firewall host (or active member).

To turn on VPN debug from the expert mode:

# vpn debug trunc

At this point you want to test your VPN connection and verify that IKE Phases. This can be done with the following commands:

# vpn tu (option 1 and 2), you may need to reset tunnel to test. This is done by using (option 7)

To tune off the VPN debug the following commands should be issued:

# vpn debug off

# vpn debug ike off


When completed retrieve the logs vpnd.elg and ike.elg – located under $FWDIR/log

Checkpoint has an IKEView tool which is located on their site, and used to review the logs, else using a tool such as Notepad++ for analysis is helpful.

X1 Set-Top Box Issues RDK-03004 & RDK-03033

Excellent Comment from one of my previous post:

Sharing the information below.  Thanks dude for sharing.


Equipment List:

1. Cable Modem -> Xfinity TG1682G internet cable modem (
2. Main DVR Unit -> Xfinity PX0113ANM main cable box (
3. Remote Units -> 2 Xfinity PXD01ANI receivers (
4. Amplifier -> Commscope CSAPDU5VP 5 port Subscriber Amplifier (
5. MoCa Filter -> PPC MoCA Ground Block PoE Filter, Combo Wave (


Xfinity internet was disconnecting frequently, and the main Xfinity cable box (PX013ANM) was rebooting. Basically, service was going in and out.  Neighbors were not having any issues.  Called Comcast a number of times.  Sometimes they customer service representative could ping (i.e. see) the devices, other times they could not.

Complicating Factors

Internet was consistently dropping.  Great performance, then nothing. Reboot the modem, work for a period, then same issue would repeat.

All of a sudden main cable DVR unit would reboot multiple times per day.

Cable would begin randomly freezing on remote units.  I would reboot the remote units, and they would time out, not connect, and display the error: rdk-03036.

I’ll jump to the solution so I don’t bore you to sleep….


After hours (possibly days) of internet research, hair pulling, and deep, deep soul searching, I figured out the issue and now (knock on wood) have a speed demon, high-performance Xfinity network.

1.  Make sure your cable line is GROUNDED.  This is important.  My cable line is grounded using the MoCa filter which is explained in #2 below.  Grounding the line really important.  Proper grounding reduces noise/static in the cable line which allows the data to perform better.  Here is a link explaining the situation:  Safety note: You also want to ground the line in the rare situation that the cable line outside gets hit by lightning, sending that dangerous current into your house destroying everything in its path (all electronics and possible your home)

2. Make sure you have a MoCa filter (see equipment list above) installed on your cable line BEFORE any amplifier or splitter.  This is very important – also, make sure the directional arrow on the filter points into the house as if data were flowing into your home.  NOTE: My MoCa filter is also the ground point.  I’ll explain this MoCa pain in the a$$ down below.

3. If you are using the Commscope amplifier, it is really important on where you connect your devices.  On my Commscope 5 port, there are four active ports (Out 1 -> Out 4), and one passive port (-4dB VoIP Out).   There is also the line IN port (this is where you connect the cable line coming into the house {assuming the MoCa filter is on the other end connect to the main line from the outside cable}), and the Power In port.

– The cable modem MUST be connect to the VoIP Out passive port.  This is defined as “passive”  since the amplifier does not send any power to it (i.e. amplification).  The main purpose is that if your power goes out, and your cable modem has a backup-battery, the phones will still work (i.e. land lines).
– The rest of your cable devices (main DVR, and remote boxes) should be connected to 1, 2, 3, and 4.  I’m only using 1, 2, 3.  My Main DVR is connected to Port number 1.  Also, if you have an open port, you should cap it with an F-Type terminator -> (aka dummy load)

4. Make sure the MoCa communications settings on the Cable Modem/Router is DISABLED!.  Using a browser on your home network, go to and login as the Admin.  (Note: the default password is “password”).  Select Communications, find MoCa and disable it.

5. Unplug all your devices, wait a few minutes and plug them back in.  Once they are all up and running, use the Xfinity My Account app on your mobile device, and send a REFRESH single to your system.

If all goes to plan, everything should come back to life.  If you still have issues, check the following:

1. Make sure you limit splitters on your cable network.  If you have any, and require splitting, please make sure they are high-quality.  Also, if you have a one to four, or one to two splitter, and you are not using all the connectors, the ports need to be capped with an f-type male terminator.  Otherwise, you lose signal.

2. If you are having internet issues and are using a downstream router, make sure all your Ethernet cables are high quality.  I had some old cables where the ends did not fit well, and that was causing internet problems.

3.  If you are still having cable issues on the remote boxes, go to the main DVR, grab the remote and perform the following procedure:

– Press and hold the EXIT button for five seconds
– Click the down arrow twice
– Hit the number 2 button

You should be presented with the diagnostics menu. Arrow to the MoCa Diagnostics section and confirm that the MoCa Link Status is set to LinkOn (not NoLink).  If this is set to NoLink, then your cable will not work on the remote boxes. Check to make sure the MoCa filter is installed correctly. Also, make sure MoCa is disabled on the cable modem router page.

*** MoCa PITA (Pain in the A$$) ***

So, I learned a lot about MoCa during this exercise.  Multimedia Over Coax Alliance (“MoCa”) is the data communications method used by the Xfinity devices to communicate.  The remote devices do nothing more than connect to the main DVR for processing. When you are watching cable on a TV connect to a remote PXD unit, all the interaction (guides, internet apps, DVR viewing) is being served by the main DVR unit in the home. All the data is being controlled by MoCa.  If you don’t have the MoCa filter connected to your cable line coming into the house, you can get MoCa traffic into your home network which causes congestion and conflict.  Hence, there is so much traffic that the devices can’t connect to the right host – your main DVR.  By installing the filter, outside MoCa traffic is left outside.

In theory, the MoCa configuration on your Comcast router should not impact the performance of your cable devices.  However, when I had it on, I had internet and cable problems.  By making sure the filter was installed correctly, and MoCa was OFF on the router, the system worked perfectly.

I hope this helps and saves at least one person some time and headaches.

submitted by frustrated xfinity (comcast) customer