#Home network file sharing from server full#
#Home network file sharing from server windows 10#
#Home network file sharing from server windows#

We'll take advantage of some of these interface changes, since they offer shortcuts to sharing folders, but we're going to avoid Homegroup. Over the years Microsoft has attempted to simplify the job of managing networked file shares, which in our opinion only helped to confuse the situation.

This underlying architecture for Windows NT has remained the same then, with security handled through the Security Reference Monitor system, using Access Control Lists and unique Security Identifi ers called SIDs to orchestrate this symphony. Technically, Windows 8, RT and Server 2012 will all be based on Windows NT v6.2. The whole Windows range was effectively merged with Windows Vista as NT v6 and onwards. As you should know, Windows NT became the core of Windows 2000 aka NT v5 and then Windows XP as NT 5.1. The truth is that the networking that exists inside all of Microsoft's current products is the same underlying system that was built into Windows NT back in 1993. So you can pick and choose depending on how tiered you want to make your file sharing access. Besides, once you've nailed the more complex systems, they work with and are the Homegroup system anyway. So why when Microsoft goes to all that time and trouble to provide an easy route, should you care to learn the hard way? Frankly because it offers far more flexibility for a little more investment of your time.

For complete control you want to unleash the full Windows network file sharing. Like we said, Homegroup is fine if you're seeking the basic control.

Let's not also forget the ability to limit, monitor and revoke access too. It's a reassuringly complex system, which once you understand the basic elements, is easy to deploy with total control, allowing you to decide who, how and exactly what is shared and accessible over your network. ** You can test this in windows by opening a new Explorer window and entering in: \10.0.0.That's the key here - not only does it arm you with the knowledge to twiddle with network shares on Windows 7, but without too many complications, everything from Windows NT, XP Server right through to Vista and Windows 8. ** You can test this in windows by opening a new Explorer window and entering in: \192.168.0.xxx <- IP of HOST Server The server can be access from any client on the PPTP VPN, 10.0.0.xxx The server can be access from any client on the internal LAN, 192.168.0.xxxДў. So, at this point, your Server / HOST machine hosting the SMB shares can be access via 2 IPs:ДЎ. Enter in the IP Address from the 'Connections > Assigned IP' field. On the 'General' tab, click on the 'use the following ip address:Д¦. Click on the 'Internet Protocol Version 4' then Properties button.ДҐ. Right Click on the connection and click on the 'Networking' tab.Д¤. Find the new VPN connection, named after step 3's 'Connection Name'.ДЈ. While still on the VPN connection page, scroll down and click on 'Change Adapter Options'Дў. Verify that the server is connected in the list of 'PPTP VPN Connections'.Дў. In the TP-Link Router Advanced > VPN Server > Connections page:ДЎ. Setting this to private should allow File share transfer over port 445. Set the 'Network Profile' from Public to Private. Once connected, click on the VPN Connection > Advanced OptionsД§. Click on the VPN connection and click on the Connect button.Д¦.

** NOTE: My Host machine is an old Windows 10 box **ДҐ. On the Server or Host machine hosting the SMB shares: Take note of the Starting and Ending client IP Range as there are only 10 clients allowed at the time of this writing. Here's what I did to get things working on Windows.Д¤. I'm not sure if you got this working, but I wanted to let you know that after A LOT of Googling online and stumbling on this message board.

#Home network file sharing from server windows#

#Home network file sharing from server full#

#Home network file sharing from server windows 10#