Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem on initial setup (Windows) #3375

Closed
PtDragon opened this issue Jul 25, 2021 · 6 comments
Closed

Problem on initial setup (Windows) #3375

PtDragon opened this issue Jul 25, 2021 · 6 comments
Labels

Comments

@PtDragon
Copy link

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • [ X] I am running the latest version
  • [ X] I checked the documentation and found no answer
  • [ X] I checked to make sure that this issue has not already been filed

Issue Details

  • Version of AdGuard Home server:
    • AdGuard Home v0.106.3 Latest
  • How did you install AdGuard Home:
    • GitHub releases
  • How did you setup DNS configuration:
    • System
  • If it's a router or IoT, please write device model:
    • Not a router, Windows 10 x64
  • CPU architecture:
    • AMD64
  • Operating system and version:
    • Windows 10 x64 with all latest updates

Expected Behavior

Actual Behavior

Error: control/install/configure | dnsServer.Prepare: setting up resolvers: systemResolvers: can't get addresses: start command executing: open NUL: The system cannot find the file specified. | 500

Screenshots

Finish configuration fully ignoring DNS setting of system as they can be defined later.

Screenshot: ![изображение](https://user-images.githubusercontent.com/5212271/126903417-e5d5923f-f110-4935-9cdc-6d65a9cdafeb.png)

Additional Information

@PtDragon PtDragon changed the title Problem on initial setup Problem on initial setup (Windows) Jul 25, 2021
@ainar-g
Copy link
Contributor

ainar-g commented Jul 26, 2021

Hello and thank you for your report! If you open a console—either cmd.exe or a Powershell one—and type something like nslookup adguard.com, does it show a valid DNS request result or an error along the lines of executable not found?

@ainar-g ainar-g added compatibility waiting for data Waiting for users to provide more data. labels Jul 26, 2021
@PtDragon
Copy link
Author

Hello and thank you for your report! If you open a console—either cmd.exe or a Powershell one—and type something like nslookup adguard.com, does it show a valid DNS request result or an error along the lines of executable not found?

Server: UnKnown
Address: 192.168.4.134

Non-authoritative answer:
Name: adguard.com
Addresses: 104.20.91.49
172.67.3.157
104.20.90.49

@ainar-g
Copy link
Contributor

ainar-g commented Aug 30, 2021

Sorry for the late reply. Is there any kind of antivirus software that could prevent AGH from executing correctly?

@PtDragon
Copy link
Author

No antivirus no firewall at all (Microsoft ones are disabled and no others installed).

adguard pushed a commit that referenced this issue Aug 31, 2021
Updates #3375.

Squashed commit of the following:

commit a98f376
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Tue Aug 31 15:06:03 2021 +0300

    aghnet: imp windows nslookup
@ainar-g
Copy link
Contributor

ainar-g commented Aug 31, 2021

I see, thanks. The most recent edge channel release, v0.107.0-a.152+2365ddd2, should contain some logging improvements. Could you please test it when you have the time and report the results?

@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants