Friday, 19 May 2017

DNS -eq Remoting Pain

Just provisioned a bunch of nice shiny new VMs with Windows Server 2016 Core, joined to the domain, proxy set and Windows Updates applied. All ready for DSC except that I can't connect remotely! The following red text annoys me:

So I try a few things...

1) Try remoting from a VM on the same host - nada
2) Try removing the proxy - nada (just got a different exception)
3) Reboots - nada

So then I decided to talk to a network\infrastructure dude to get help (caus I is a dev).

A huff and puff and some jiggery pokery later and it turns out DNS was holding static records for the previous versions of the machines. You see, the VMs were shiny and new but their names weren't. Once the static DNS records were deleted I could remote! Adds weight to the argument that VMs should be named generically.

Shout out to Si for helping me with this :-)

1 comment:

  1. The problem with this issue is that problems with PS-Remoting are common place but if you look closely at the dreaded red text, the VMs were returning a 403 error? Authentication maybe? So I started looking down the road of permissions; No joy!

    It wasn't until I went back to basic pings and ipconfig until I noticed a discrepancy with DNS – I guess I just took It for granted that as DNS was integrated into AD that it would update? I manually removed the DNS records and allowed the VMs to re-register themselves, however, this still doesn’t explain why the records are not updating automatically? And would this issue reoccur if the VMs were trashed/re-deployed using the same name?

    The saga continues...