Need some help on Network Policy Server, NAP, CHAP, PAP, NPS and RD Gateway
Need a little guidance with NPS, NAP, PEAP MS-CHAP...
My remote web access is causing heartache... and won't allow clients in from the outside.
If anyone can break the relationship of these with Remote Gateway.. I might get some sleep!
New to Server 2012 R2, came from 2011 where I had all of this whistling... but now, it's incredibly convoluted, and I fear I have made a mess of the components and created more damage than good. I used to be able to give clients 'RDP shortcuts' and they could log in to their office workstation from home without issue... now it's like trying to find a peppercorn in a bucket of spaghetti!
Is this where I should be looking?! Clients can only get access from inside the LAN at the moment.
My remote web access is causing heartache... and won't allow clients in from the outside.
If anyone can break the relationship of these with Remote Gateway.. I might get some sleep!
New to Server 2012 R2, came from 2011 where I had all of this whistling... but now, it's incredibly convoluted, and I fear I have made a mess of the components and created more damage than good. I used to be able to give clients 'RDP shortcuts' and they could log in to their office workstation from home without issue... now it's like trying to find a peppercorn in a bucket of spaghetti!
Is this where I should be looking?! Clients can only get access from inside the LAN at the moment.
Who is Participating?
Hello Manesh,
Thank you for your comments.
Ok, I will disable the other policies.
Regarding the RD Gateway, I have a GoDaddy SSL installed with a FQDN of remote.servername.com, however in mentioning this it is also appropriate to mention that my server has a name of servername.local, so I was having some other issues resolving the SSL, but I think I have resolved that issue by adding a Forward DNS Zone that resolves remote.servername.com to the IP address of servername.local.
Thank you for your comments.
Ok, I will disable the other policies.
Regarding the RD Gateway, I have a GoDaddy SSL installed with a FQDN of remote.servername.com, however in mentioning this it is also appropriate to mention that my server has a name of servername.local, so I was having some other issues resolving the SSL, but I think I have resolved that issue by adding a Forward DNS Zone that resolves remote.servername.com to the IP address of servername.local.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Mahesh (https:#a42460531)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Mahesh (https:#a42460531)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Only RDS_CAP users should remains enabled and make sure required group of users are allowed to connect to all computers or required group of computers
Also do you published RD gateway server on internet with appropriate SSL certificate?