DFS-N - Problems resolving names after adding new DC
hi there,
use dfs-namepace our 2 local domain controllers acting namespace-server. added dc that's installed on our azure-account (connected site2site vpn).
dc has replicated , dns server. got problem, machines, logon against new dc can't resolve dfs-namespace called \\ourdomain.de\dfs (for example our other member servers in azure fail open dfs-fileshare) ... necessary install dfs-role on new azure dc , add server namespace-host? seems logical, because when ping ourdomain.de server logged on against new dc resolves new azure-dc , trying access dfs attempt open share on \\new-azure-dc\dfs not there ... wrong?
or did misconfigure something?
thanks,
marcel
use dfs-namepace our 2 local domain controllers acting namespace-server. added dc that's installed on our azure-account (connected site2site vpn).
dc has replicated , dns server. got problem, machines, logon against new dc can't resolve dfs-namespace called \\ourdomain.de\dfs (for example our other member servers in azure fail open dfs-fileshare) ... necessary install dfs-role on new azure dc , add server namespace-host? seems logical, because when ping ourdomain.de server logged on against new dc resolves new azure-dc , trying access dfs attempt open share on \\new-azure-dc\dfs not there ... wrong?
or did misconfigure something?
thanks,
marcel
i found ... somehow in dfs propertys option "exclude targets outside clients site" activated ... set lowest cost - dfs works :)
Windows Server > Directory Services
Comments
Post a Comment