Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Network Location Difficulties...

$
0
0

Good day,

I am running Windows 2008 R2 Enterprise Edition on a stand-alone server with Hyper-V Role installed. The server is joined to a domain. I only have one Domain Controller. It is a VM Running the same system as the stand-alone host. This setup has been working well for me for several months but all of a sudden (around 2 weeks ago.) My Network Location keeps changing from "Work" to "Public" and back again whenever I reboot either machine, which is causing all sorts of problems for clients accessing services on the Intranet. I know the Network Location should be "Domain" (Obviously). Is there a way to "Force" the Network Location back to its "Normal" settings? I have not found anything helpful in the log files. All services seem to work fine from "Inside" the network i.e.: NPS, Powershell Remoting, DHCP, DNS, and File Sharing. When certain Windows-7 SP1 clients connect (Via WiFI/NPS as RADIUS Server), sometimes some Network Shares are not available in Windows Explorer (Client-Side). (But ARE available via UNC Paths.) I would like my clients to be able to "browse" the shares they have access to like before. I know something is wrong but can not seem to resolve the issue.

Any pointers in the right direction would be a great help. :)

Thank-You and Salutations,

Bluesurf



Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>