Single Label Domain Migration Problem


hi all,

im in process of migration sld (single label domain) fqdn domain , experiencing strange problem. have created virtual lab , replicated issue. setup environment:

old forest:

domain name: dom2 (single label)
domain controller : dc1.dom2 (windows 2008 sp2), running wins server feature
file server: fs1.dom2 (this file server has share named "share1") (windows 2008 r2 sp1)
workstation: client1.dom2 (windows7)

nes forest:

domain name: newdom.com
domain controller: dc2.newdom.com (windows 2008 r2 sp1)

there 2 way external trust between these 2 domains. sid history filtering disabled. dns conditional forwarding between both domains.

i set admt server , pre-requirements migration dom2 newdom.com domain. im able migrate groups, users , computers. have migrated user called john1 , workstation client1 newdom.com. performed security translation well. john1 has "modify" permissions "share1" able access when in dom2 domain, when trying reach \\fs1.dom2\share1 migrated pc (logged migrated user account) getting "access denied". strange thing is able access short name \\fs1\share1 , \\10.0.0.15\share1. nslookup fs1.dom2 returns 10.0.0.15. no matter if set dns server (on client1 tcp/ip settings) dc1.dom2 or dc2.newdomain.com - result still same. more strange when logoff , logon can access \\fs1.dom2\share1 !!! after reboot of workstation situation same again - unable access share long server name (fs1.dom2).

i know ms doesn't recommend use single label domain names. legacy setup , migration project should solve bad design. ideas?

p.s. has been implemented in both domains:  

https://support.microsoft.com/en-us/kb/300684




just provide final update - forest trust has been changed one-way workaround kerberos issues duration of migration project.


Windows Server  >  Migration



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file