Link to home
Start Free TrialLog in
Avatar of Mike M
Mike M

asked on

Half the machines on the new domain are not resolving local DNS names or mapping drives. Also, remnants of the previous domain are showing up as part of the issue.

We have moved machines from domain Alpha to domain Omega (mock names).  Anyway, we removed the windows 10 computers from the domain to a workgroup, restarted the PCs Win 10), joined them to the new domain, 'Omega'.  They join fine.  Users logon and it seems good.  However, they cannot map drives to the file server 'Data' on the domain.

Also, on the machines, that have the issue, when they ping the DC or file server, it is appending the old domain to the response.  There is only one DNS server currently in the new domain being set up.  Roughly half of the users have no issues and can map drives and surf the web.  The other half has a problem mapping drives, locating local devices and can surf the external internet sites.

I'm not seeing anything on the DNS side.  One machine effected, I have looked at the registry and found several keys referring to the old domain lingering.  I removed them and fixed the ping issue.

Ideas on a course of action?
Avatar of Mahesh
Mahesh
Flag of India image

However, they cannot map drives to the file server 'Data' on the domain.

Where is file server located ? In which domain?

Did you grant migrated users right on file server if its in target domain?

also what about users, did you created new users or migrated with some tool?

Need more clarity
ASKER CERTIFIED SOLUTION
Avatar of Bradley Fox
Bradley Fox
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Look at your DHCP settings, if you are using it. Make sure you don't have the old (Alpha) domain listed under option 15
Avatar of Mike M
Mike M

ASKER

Seems that the MS Surface Pro systems didn't fully purge old domain information. Manually removing entries from the registry seems to resolve the problem. Not sure why those remained and conflicted the process.  Other systems, Dell, didn't have the problem of leftover domain info in the reg.