eset error code 20003

[moulaydjh 0]

eset error code 20003

[Marcos 4,704]

If you don't use a firewall that might be blocking communication with ESET's servers, check C:\Windows\System32\drivers\etc\hosts  and remove lines containing "eset", save the file, reboot the computer and try again.

[moulaydjh 0]

On 4/30/2023 at 9:44 AM, Marcos said:

If you don't use a firewall that might be blocking communication with ESET's servers, check C:\Windows\System32\drivers\etc\hosts  and remove lines containing "eset", save the file, reboot the computer and try again.

All solutions have been tried but did not work

This is an ESET LOG COLLECTOR report

essp_logs.zip

[Marcos 4,704]

1 hour ago, moulaydjh said:

All solutions have been tried but did not work

This is an ESET LOG COLLECTOR report

Unfortunately you have removed the most essential parts of logs. Please run ELC again and provide the generated archive.

[moulaydjh 0]

THANK FOR REPLAY

THE ZIP FILE IS TO LARGE

 

ELC_logs.zip

[Marcos 4,704]

Have you removed ESET entries from the hosts file recently? If so, did you reboot the machine afterwards? Asking since there are still Avast records and the machine had been running for almost 3 hours without a reboot.

[moulaydjh 0]

All solutions have been tried but did not work

[Marcos 4,704]

Please provide a Wireshark pcap log from an activation attempt.

[moulaydjh 0]

This is an new ESET LOG COLLECTOR report

 

eis_logs.zip

[Marcos 4,704]

Please provide a pcap log generated by Wireshark during an activation attempt that I asked for.

[moulaydjh 0]

Name resolution for the name edf.eset.com timed out after none of the configured DNS servers responded.

- <Event xmlns="hxxp://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />

  <EventID>1014</EventID>

  <Version>0</Version>

  <Level>3</Level>

  <Task>1014</Task>

  <Opcode>0</Opcode>

  <Keywords>0x4000000010000000</Keywords>

  <TimeCreated SystemTime="2023-05-05T13:23:31.022225600Z" />

  <EventRecordID>1159042</EventRecordID>

  <Correlation />

  <Execution ProcessID="1476" ThreadID="1712" />

  <Channel>System</Channel>

  <Computer>sniper</Computer>

  <Security UserID="S-1-5-20" />

  </System>

- <EventData>

  <Data Name="QueryName">edf.eset.com</Data>

  <Data Name="AddressLength">128</Data>

  <Data Name="Address">0200000001010101000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>

  </EventData>

  </Event>

[itman 1,538]

2 hours ago, moulaydjh said:

Name resolution for the name edf.eset.com timed out after none of the configured DNS servers responded

Open a command prompt window. Then enter the following;

tracert edf.eset.com

The first thing displayed is one of the two IP addresses, 13.64.23.53 or 13.91.140.245, as shown below;

Tracing route to bal-kube-westus-02.westus.cloudapp.azure.com [13.91.140.245]
over a maximum of 30 hops .............

Finally, the tracert should complete connection to one of the two IP addresses prior to timing out.

Edited May 5 by itman

[moulaydjh 0]

THANK FOR REPLAY

23 hops is complete

7 time out

and eset is not work

[itman 1,538]

7 hours ago, moulaydjh said:

23 hops is complete

7 time out

It appears you cannot reach Eset activation web server.

Refer to the below screen shot. Note what I highlighted. The last tracert connection shown prior the trace completing should be the edf.eset.com DNS resolved IP address shown at the beginning of the trace.

Are you using a VPN?

 

Edited May 6 by itman

[moulaydjh 0]

Are you using a VPN?

NO

 

[itman 1,538]

When you ran the tracert command, were you able to connect to Eset's activation server or not? We are not "mind readers" here in the forum.

[moulaydjh 0]

THIS IS THE TRACERT  result

 

[itman 1,538]

7 minutes ago, moulaydjh said:

THIS IS THE TRACERT  result

The output indicates you didn't connect to Eset activation servers.

Possible reasons are your router/gateway firewall is blocking the connection; you are using a network perimeter firewall that is blocking the connection; your ISP is blocking and not forwarding the connection, etc..

[itman 1,538]

I suggest you contact the Eset authorized retailer where you purchased your license from. They might be able to activate your license for you.

[Marcos 4,704]

8 minutes ago, itman said:

I suggest you contact the Eset authorized retailer where you purchased your license from. They might be able to activate your license for you.

They would have to connect to user's machine and activate it from there so this is not an option. However, they might know better if OP's ISP has been having connectivity issues if also other users of the same ISP reported the issue.

[itman 1,538]

I will also add that since network communication to Eset activation servers is being blocked, there is a high likelihood that other Eset network communication such as updates, LiveGrid, etc. will be blocked. This leads to the conclusion that something on the existing local network is blocking Eset network communication.

Edited May 7 by itman

[moulaydjh 0]

If I install Windows 10, can I activate ESET?

[itman 1,538]

40 minutes ago, moulaydjh said:

If I install Windows 10, can I activate ESET?

If you are running Win 7 as long as it has been updated to SP1, Eset should run on it. However, the latest Eset ver. 16.1 is not fully supported anymore on Win 7.

In any case, Eset would have not installed if there was an OS issue. Your problem is Eset can't activate its license due to network blockage to its servers from your device.

Finally, you can no longer upgrade to or download Win 10. Microsoft officially stopped selling it a month or so back.

Edited May 7 by itman