Network Location Difficulties...
good day,
i running windows 2008 r2 enterprise edition on stand-alone server with hyper-v role installed. server joined domain. have 1 domain controller. vm running same system stand-alone host. setup has been working me several months of sudden (around 2 weeks ago.) network location keeps changing "work" "public" , again whenever reboot either machine, which causing sorts of problems clients accessing services on the intranet. know network location should "domain" (obviously). there way "force" network location "normal" settings? have not found helpful in log files. all services seem work fine "inside" network i.e.: nps, powershell remoting, dhcp, dns, , file sharing. when windows-7 sp1 clients connect (via wifi/nps radius server), network shares not available in windows explorer (client-side). (but are available via unc paths.) clients able "browse" shares have access like before. know wrong can not seem resolve issue.
any pointers in right direction great help. :)
thank-you , salutations,
bluesurf
the network location detection depends on dns configuration , dc availability. if can 'ping' domain controller, location domain. "work" , "public" location defined subnet , gateway.
also clients not mapping drives loginscript/ad settings indication clients not being able to connect to the dc when logging on (they log on using cached credentials)
i think best take alook @ network availability of dc. check it's event logs laten directory services issues. check clients using dc dns server (or @ least dns server holds ad service records)
because issue seem change beteen network loacation, might there rogue dhcp server on network. check clients taht faulty current ip configuration (dhcp server, dns server)
also check: http://support.microsoft.com/kb/888794 => still recommended ahve ate least 1 physical dc!
mcp/mcsa/mcts/mcitp
Windows Server > Directory Services
Comments
Post a Comment