No IPv4 access to RDG. Only IPv6

%3CLINGO-SUB%20id%3D%22lingo-sub-2646485%22%20slang%3D%22en-US%22%3ENo%20IPv4%20access%20to%20RDG.%20Only%20IPv6%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2646485%22%20slang%3D%22en-US%22%3E%3CP%3EOkay%2C%20got%20a%20really%20weird%20one%20here.%20I%20reluctantly%20admit%20it%E2%80%99s%20100%25%20my%20fault%20too.%20On%20a%20Server%202019%20domain%20controller%20with%20RDGateway%20installed%20it%E2%80%99s%20set%20up%20so%20the%20business%20owner%20can%20remote%20in%20from%20home%20to%20a%20VM%20set%20up%20on%20the%20DC.%20I%20also%20can%20remote%20in%20via%20the%20RDG%20directly%20to%20the%20server%20itself%2C%20so%20I%20can%20perform%20my%20monthly%20maintenance%20remotely.%3C%2FP%3E%3CP%3EA%20few%20weeks%20ago%2C%20in%20the%20process%20of%20figuring%20out%20and%20setting%20up%20IPv6%20it%20seems%20I%20somehow%20disabled%20IPv4%20access%20to%20the%20RDG%20as%20a%20way%20to%20confirm%20it%20was%20correctly%20configured%20for%20IPv6.%20Got%20RDG%20and%20all%20working%20with%20IPv6%20now.%20But%20for%20the%20life%20of%20me%20I%20can%E2%80%99t%20remember%20exactly%20what%20I%20did%20to%20disable%20IPv4%20to%20the%20gateway.%20I%E2%80%99ve%20googled%20quite%20a%20bit%2C%20and%20nothing%20I%20find%20seems%20to%20re-enable%20IPv4%20on%20the%20RDG.%20Heck%2C%20I%E2%80%99m%20not%20even%20sure%20it%E2%80%99s%20RDG%20where%20the%20issue%20is.%26nbsp%3B%20I%20need%20to%20re-enable%20IPv4%20so%20the%20business%20owner%20(and%20a%20few%20other%20managers)%20can%20regain%20remote%20access%20now.%20Here%E2%80%99s%20what%20I%E2%80%99ve%20checked.%3C%2FP%3E%3CP%3E-IPv4%20is%20enabled%20on%20the%20network%20adaptor.%3CBR%20%2F%3E-IPv4%20is%20enabled%20on%20the%20VM%3CBR%20%2F%3E-Port%20443%20is%20not%20blocked%20for%20IPv6%20on%20the%20firewall%3CBR%20%2F%3E-Checked%20the%20policies%20in%20Gateway%20Manager%20and%20nothing%20there%20indicates%20IPv4%20is%20blocked.%3CBR%20%2F%3E-Checked%20the%20RD-CAP%20network%20policy%20in%20NPS%20and%20nothing%20there%20indicates%20IPv4%20is%20blocked.%3C%2FP%3E%3CP%3EI%E2%80%99m%20at%20a%20loss%20and%20could%20use%20some%20help%20in%20recovering%20from%20my%20own%20stupidity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2646485%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServer%202019%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Okay, got a really weird one here. I reluctantly admit it’s 100% my fault too. On a Server 2019 domain controller with RDGateway installed it’s set up so the business owner can remote in from home to a VM set up on the DC. I also can remote in via the RDG directly to the server itself, so I can perform my monthly maintenance remotely.

A few weeks ago, in the process of figuring out and setting up IPv6 it seems I somehow disabled IPv4 access to the RDG as a way to confirm it was correctly configured for IPv6. Got RDG and all working with IPv6 now. But for the life of me I can’t remember exactly what I did to disable IPv4 to the gateway. I’ve googled quite a bit, and nothing I find seems to re-enable IPv4 on the RDG. Heck, I’m not even sure it’s RDG where the issue is.  I need to re-enable IPv4 so the business owner (and a few other managers) can regain remote access now. Here’s what I’ve checked.

-IPv4 is enabled on the network adaptor.
-IPv4 is enabled on the VM
-Port 443 is not blocked for IPv6 on the firewall
-Checked the policies in Gateway Manager and nothing there indicates IPv4 is blocked.
-Checked the RD-CAP network policy in NPS and nothing there indicates IPv4 is blocked.

I’m at a loss and could use some help in recovering from my own stupidity.

 

0 Replies