Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, April 28, 2020 4:54 PM
We acquired a company last year and their workstations and users are part of our domain (DOM1) but their internal application is still on their domain (DOM2). The application connects from the client side (DOM1) to a SQL server in DOM2. The code is written using just the host name and not FQDN. Very randomly, the Windows 10 1809 workstations will not be able to resolve the HOSTNAME for the SQL box.<o:p></o:p>
When I look in the DNS Client logs on the workstation, at the time this occurs, I will see Event ID 3008 with a status of 87, which is ERROR_INVALID_PARAMETER.<o:p></o:p>
The Description for the event looks like this: DNS query is completed for the name SQLBOX, type 1, query options <RandomNumbers> with status 87 Results<o:p></o:p>
If you go into the DNS screen in the properties for the Network Adapter and then click OK without changing anything, it starts working again.<o:p></o:p>
We have the dns suffix search list populated with DOM1 and DOM2 via GPO<o:p></o:p>
We use DHCP so there's no manual settings for DNS.<o:p></o:p>
I have no idea what the parameter that is invalid is. I'm wondering if anyone has anything thoughts as to what the parameter might be or where else I could look for more information.
<o:p>Thanks in advance!</o:p>
<o:p>WB</o:p>
All replies (7)
Wednesday, April 29, 2020 7:04 AM
Hi ,
Please turn on exhaustive debugging mode of NSlookup, this will display detailed information of name resolving process.
Open Command Prompt on client ,type nslookup and type set d2 .Then type SQLBOX,we might find some clues through the process .
>NSlookup
>set d2
>[name which you want to resolve]
Compare the nslookup results of successful and unsuccessful.
Note: since this is a public forum, everyone could view your information, please remove private information that might leak your privacy.
Best regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Friday, May 1, 2020 9:02 AM
Hi ,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Friday, May 1, 2020 12:56 PM
Thank you for the suggestion about nslookup. Right now I'm still waiting to hear of an instance where it happens again. The platform architect told me that it seems to happen during Group Policy processing so I've enabled verbose logging for that as well. I will let you know what I find out.
Thank you!
WB
Monday, May 4, 2020 1:51 AM
I will wait for your updates.
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Wednesday, May 13, 2020 6:29 PM
I'm still waiting to hear of another occurrence. Unfortunately being that the issue is intermittent, it may take a little while but I will post periodic updates.
Thursday, May 28, 2020 3:25 PM
I am still waiting to hear that these users have had another issue so I can examine the DNS client logs, capture the nslookup information as per your post and review the Group Policy logging information as well.
Wednesday, June 3, 2020 4:13 PM
Just another update that I'm still waiting to hear of the issue happening again so I can investigate.