How I can implement a single installation over multiple network's?

We have 2 completely different network's that I would like to manage with one installation of SharePoint 2013. Is that doable?

Our internal network uses active directory domain accounts and our external does not.

Is there a way they can live together seamlessly? With one installation of SharePoint?

I want...

For example, if I create a Publishing Site for the external site, I want to be able to manage it from our internal installation. That's my goal.

Thank You for any help you can provide.

well have one farm internally and create for the web applications zone for extranet and using web application proxy (if needed)

Thanks John. It sounds like you know what I need done.

However, can you please be more specific? =/

So,

1) I do a Complete Install of SharePoint 2013 on our internal DOMAIN network box.

2) ???

How do I expose the internal DOMAIN network box to the public for browsing? Is this done with routing? Which Web Application Proxy? Are you talking about Microsoft Proxy Server?

What does creating for the Web Application Zone do for me?

Thank you for your help!

When you say different network, im assuming youre talking about services and not physical?

Yes you would install SharePoint on the network with AD (your internal). Hes talking about extending your Web App into a different zone that would be a url space that the seperate network can reach. For example your internal could be http://sharepoint and then you can extend that to http://sharepoint.yourcompany.com.

Is your 2nd domain in a DMZ? When you say public I assume you mean internet facing? If so then you would probably want some some of reverse proxy (I think he was talking about Microsoft's Web Application Proxy which is a feature/role in Server 2012. Its very easy to configure and can do SSL termination but I beleive it requires ADFS) on your perimeter.

We are required to install our public facing web server on a physically separate network. 

I understand about extending the web application into a different zone. The same thing can be done by adding a new site. What is the benefit of extending?

Yes, the 2nd domain is in something like a DMZ. I'm checking to see if this box has access to both networks.

Yes, by public I mean internet facing.

I've never heard of the Web Application Proxy feature but sounds worth investigating.

You said the following that caught my attention "...that would be a url space that the separate network can reach..." What would I use to point an outside url to an inside one?

Thanks for your help

Hi,

yes for the first one,

then for the second questions, use this link to publish it through window server web application proxy

http://blogs.msdn.com/b/sambetts/archive/2014/12/10/publishing-sharepoint-with-windows-server-2012-r2-web-application-proxy.aspx

or if you have old technology like ISA

Extending makes a seperate IIS site that hosts the same content with different urls and potentially authentication mechanisms and other web app level settings. If you just create a different web app then it will have its own content.

The url mapping is done by extending the web app. More specifically it is done by AAM (alternate access mapping) which is what tells SharePoint to serve up the same content to different urls. You could just use AAM but then you would have to use the same authentication provider....which usually people want people accessing the content from outside to use forms or something.