Windows server 2012 essentials no longer visible

Dear Forum,

After installing Direct Access and VPN on a Windows server 2012 essentials the server is no longer visible on the internal network.
- SQL is invisible
- server does not show up on the network
- But Anywhere Access is however still visible

I have no idea where to start looking for problems?

Using:
- 1 router
- 1 server Proliant ML350

Roles and Features:
*Essentials has installed these using a wizard
AD CS
AD DS
DNS
File and Storage Services
IIS
NAP

I myself installed:
Fax Server
Print Services

+ Anywhere Access

Extra information:
- The server has a fixed IP
- I haven't done any special configurations, I just used the wizards to install these services
- I have purchased an SSL that Anywhere Access uses

*Picture show error of access client not able to find the server using ODBC

Are you able to RDP to the server? Is it joined to a domain? My initial guess is that the Windows firewall is blocking it.

I log on using teamviewer because it is not at the location where I am.
It is joined in a domein.
Firewall didn't block SQL before, Rules are still in place and activated.

Now that you've installed all of those roles it's possible that the network has been identified as public. All of your firewall rules will look correct but if it's using the wrong network profile nothing will work. Windows uses DNS to identify the network so after installing the DNS role on the server it may see the network as a new one and default back to public.

AdmnPower said:

Now that you've installed all of those roles it's possible that the network has been identified as public. All of your firewall rules will look correct but if it's using the wrong network profile nothing will work. Windows uses DNS to identify the network so after installing the DNS role on the server it may see the network as a new one and default back to public.

Click to expand...

I didn't even think of that myself.

OP, try going into the Services and restart the Network Location Awareness service.

Windows firewall along with the network profile settings have bitten us pretty bad around my office a number of times. At least in terms of time wasted troubleshooting only for it to be that the network profile is set to public.

AdmnPower said:

Windows firewall along with the network profile settings have bitten us pretty bad around my office a number of times. At least in terms of time wasted troubleshooting only for it to be that the network profile is set to public.

Click to expand...

Yup, happens to me too. Need to remember to check that first before wasting time.