asked on Windows Server DNS failed
Hi All, I have a 2019 Server that had joined an older (2000) domain and was working fine, but now when I try to go to DNS I get an errror.
The server "server name" could not be contacted the error was
Access was denied
Would you like to add it anyway?
When I say yes it brings me to an empty dns manager. And the action menu is all greyed out except launch nslookup.
Thanks all.
The server "server name" could not be contacted the error was
Access was denied
Would you like to add it anyway?
When I say yes it brings me to an empty dns manager. And the action menu is all greyed out except launch nslookup.
Thanks all.
Windows OSDNSWindows Server 2019Windows 2000
Last Comment
Dan
I would be very surprised if 2019 RSAT DNS can connect to a 21 year old Windows Server.
Why not just log into the 2000 server and open DNS from there?
Why not just log into the 2000 server and open DNS from there?
ASKER
Thanks guys...
Arnold so the DNS records are for the domain, for authentication nothing to do with Internet stuff
yes the IP address of the server is pingable.
No on the public IP, really there is nothing in the DNS management tool
I usually have the IP of the server primary, and a google one 2nd.
Does it have any public, external IP address listed? If so, remove it.
Going into dns I mean is DNS Manager from Server Manager.
I don't know how to retard it.
EC
Good Eye, OK, I upgraded the functionality of the 2000 server, then created a virtual 2008 Server, and had that be a domain controller, then a 2012 server, same thing, then added the 2019 Server.
The 2000 server died, I have a virtual image of it, but it won't boot :(
Arnold so the DNS records are for the domain, for authentication nothing to do with Internet stuff
yes the IP address of the server is pingable.
No on the public IP, really there is nothing in the DNS management tool
I usually have the IP of the server primary, and a google one 2nd.
Does it have any public, external IP address listed? If so, remove it.
Going into dns I mean is DNS Manager from Server Manager.
I don't know how to retard it.
EC
Good Eye, OK, I upgraded the functionality of the 2000 server, then created a virtual 2008 Server, and had that be a domain controller, then a 2012 server, same thing, then added the 2019 Server.
The 2000 server died, I have a virtual image of it, but it won't boot :(
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
you get warned when you try to raise the domain level to 2003 from 2000 that all 2000 server DCs will stop working.
Could you access shares on the 2000 server from the 2019? deals with whether you enabled SMbv1 on the 2019 to access the shares on 2000,
Could you access shares on the 2000 server from the 2019? deals with whether you enabled SMbv1 on the 2019 to access the shares on 2000,
ASKER
Dr Dave, Ill try that, thanks a ton.
Arnold, Yes we could access the shares and I don't remember adding smb1 support from the newer servers, and I never did on the Windows 10 stations. I'm honestly starting to doubt that it was a 2000 server, maybe it was a 2008r1 server, I'm super sorry guys.
I'll report back after I go through Dave's link.
Arnold, Yes we could access the shares and I don't remember adding smb1 support from the newer servers, and I never did on the Windows 10 stations. I'm honestly starting to doubt that it was a 2000 server, maybe it was a 2008r1 server, I'm super sorry guys.
I'll report back after I go through Dave's link.
ASKER
Dr Dave, the first step was to stop the KDC Proxy service, it was off, I tried to start it and got an "error 5: access denied"
It's not the KDC Proxy service that you need to stop; it's the Kerberos Key Distribution Center (KDC) service.
ASKER
Oh, thanks, going back in. :)
ASKER
Holey crap that worked!!!! The only thing they didn't say in the walk through was to restart the KDS service. You guys rock.
What DNS records does the server have?
Is the IP pingable?
Does it have any public, external IP address listed? If so, remove it.
Your AD joined systems should only have the IPS of your DC/s listed as valid name servers.
Please clarify what do you mean by going to DNS?
if this is the DNS management tool, you could/should be able to retarget it in the event you have an external DNs on the record.