Server 2012 DNS without Active Directory
Hi,
I have a client who currently has an SBS server. This is obviously a domain controller, but since the installation of that server, the client has replaced all user PCs with non domain joined workstations. Shares on the existing server are accessed by username and password when clicking a share, and credentials are saved.
I am installing a new 2012 R2 server, and the client wishes to retain non domain joined clients. (Don't ask me why, but he is insistent on that.)
I supplied the new server, and created local users and groups and shared the documents on the new server and all was going well.
At this point the old server was still providing DHCP and DNS services to the clients.
Finally I wanted the new server to take over the DHCP and DNS roles.
I installed both of these roles, and disabled the two services on the old server.
I configured a zone called "abc.local" on the new server to match the previous AD domain name. I created an A record (abcserver) in this zone for the new server. I configured DHCP to allocate addresses, giving the new server as DNS, and "abc.local" as the DNS suffix.
I went to one existing PC, did ipconfig /release and ipconfig /renew and also rebooted the PC.
After this I could ping abcserver without any problems, the correct address was resolved and the pings succeeded. However, if I entered \\abcserver into the run box, I could not see the shares on the server.
How do I fix this? Do I need to setup AD, even if no other devices will join the domain, or is there a way to get DNS / filesharing working correctly without AD?
If I do need to upgrade to AD, can I migrate the existing local users or do I need to create them all again?
Thanks for your help.
Richard
I have a client who currently has an SBS server. This is obviously a domain controller, but since the installation of that server, the client has replaced all user PCs with non domain joined workstations. Shares on the existing server are accessed by username and password when clicking a share, and credentials are saved.
I am installing a new 2012 R2 server, and the client wishes to retain non domain joined clients. (Don't ask me why, but he is insistent on that.)
I supplied the new server, and created local users and groups and shared the documents on the new server and all was going well.
At this point the old server was still providing DHCP and DNS services to the clients.
Finally I wanted the new server to take over the DHCP and DNS roles.
I installed both of these roles, and disabled the two services on the old server.
I configured a zone called "abc.local" on the new server to match the previous AD domain name. I created an A record (abcserver) in this zone for the new server. I configured DHCP to allocate addresses, giving the new server as DNS, and "abc.local" as the DNS suffix.
I went to one existing PC, did ipconfig /release and ipconfig /renew and also rebooted the PC.
After this I could ping abcserver without any problems, the correct address was resolved and the pings succeeded. However, if I entered \\abcserver into the run box, I could not see the shares on the server.
How do I fix this? Do I need to setup AD, even if no other devices will join the domain, or is there a way to get DNS / filesharing working correctly without AD?
If I do need to upgrade to AD, can I migrate the existing local users or do I need to create them all again?
Thanks for your help.
Richard
ASKER
I am certain there is no IP conflict.
I didn't try \\ip I'm afraid, I will try that when onsite tomorrow.
I didn't try \\ip I'm afraid, I will try that when onsite tomorrow.
if \\ip is not working, then you may have a firewall issue on the server.
ASKER
It works fine as long as DNS and DHCP are handled by the old server.
If you run \\abcserver does the explorer window open for the server and just not display the shares or does it error out?
ASKER
It gives an error. I can't remember the exact error, but it is along the lines of the server name not being resolved, despite pings to the server name working.
Other usual culprit are cached credential, if there are any, remove them.
ASKER
But the cached credentials are correct! Aren't they?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I know in windows 7, 8 and 2012 you have network discovery which allows u to view other devices on the network. This may have nothing to do with your issue but is the enabled on the server.
how does \\ip react ?
Also, the \\abcserver is likely to use IPV6 if it's available on both...