Forum Discussion
DNS not auto Detected on client machines
- Aug 10, 2020
Please run;
- Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
- repadmin /showrepl >C:\repl.txt
- ipconfig /all > C:\dc1.txt
- ipconfig /all > C:\dc2.txt
- (etc. as other DC's exist)
- ipconfig /all > C:\problemworkstation.txt
then put unzipped text files up on OneDrive and share a link.
Pretty vague but assuming a domain environment then I'd check the domain controller and problem member both have the static ip address of DC listed for DNS and no others such as router or public DNS
Thanks Dave.. Apols for the vague, this ones a carry on from someone elses job!! And to be honest, not at all sure as to how to deal with, hence why i'm on here
Your correct, Domain Controller with the DNS. I've now got the Server itself seeing the correct DNS (which it wasn't before), just not the clients now. If i enter the IP manually, their fine. Leave it on Obtain auto and the NSLOOKUP comes back with DNS timed out and picks up google
Its bound to be a server config somewhere i assume
Any pointers, fire away. Going round in circles at the mo!!
- Dave PatrickAug 10, 2020MVP
Please run;
- Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
- repadmin /showrepl >C:\repl.txt
- ipconfig /all > C:\dc1.txt
- ipconfig /all > C:\dc2.txt
- (etc. as other DC's exist)
- ipconfig /all > C:\problemworkstation.txt
then put unzipped text files up on OneDrive and share a link.
- RoddersAug 10, 2020Copper Contributor
THanks again, i've just messaged you, as our onedrive requires email address with the person to share.
I could add the zip below, however concerned with possible data issue like this
Could you message me a different way
Thanks
- Dave PatrickAug 10, 2020MVP
Yes, please do not zip the files. If sharing the files is an issue I'd suggest start a case here with product support.
https://support.microsoft.com/en-us/hub/4343728/support-for-business