asked on

Initial setup of DirectAccess on Windows Server 2012

My DirectAccess server is NAT'd. Following various documents, I have created firewall rules to forward ports 41, 443, 3544 but I'm thinking the problem isn't there.

At the moment I believe the problem may be on the DirectAccess server itself. I'm expecting to be able to see some type of page at the DirectAccess URL the clients use (NAT'd of course) at the local URL of https://192.168.1.50/IPHTTPS

Should I see some type of page using that URL as a test?

Thanks.

ASKER CERTIFIED SOLUTION

David Johnson, CD

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan-Aspitel

ASKER

Clients are all Windows 8.

I'm learning as I go. Since it is installed behind a single NIC it looks like the port is set as 62000 and not 443. So I forward 443 to 62000 in the firewall.

I can bring up the IIS start web page. However I still can't get the client to connect.

I went through Microsoft's DirectAccess lab and I see nothing wrong with my own DA server.
http://technet.microsoft.com/en-us/windowsserver/hh968267.aspx

I'm thinking it is something in my firewall configuration. If I could somehow test locally without going through the firewall then I could be sure it is the firewall.

Thanks.

SOLUTION

David Johnson, CD

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan-Aspitel

ASKER

Yes. Win8 Enterprise.

Dan-Aspitel

ASKER

I have DirectAccess working now and it was easy to setup. The problem was really unrelated to DA but instead an Active Directory problem. An AD server was not sync'ing and so only one AD server had the DA settings.