Unable to het trial version

LightBurn Software Questions
21
  1. Wifi from fiber optic
  2. Im used to swicth on sometimes
22

Is this a dedicated separate WiFi router or is this integrated with the fiber modem?

23

using WIFI extender…is it a modem?

24

If you’re using an extender I assume the core WiFi is provided by the modem.

Here’s what I suggest you try.

Modify your network settings in Windows to manually add a different DNS entry to see if that resolves the issue.

Follow this guide:
How to change DNS settings on your PC running Windows 10 | Windows Central

Then recheck whether or not you can connect to the server in powershell:

Test-NetConnection api.cryptlex.com -p 443

Make sure all firewall and AV is off.

25

already modify the network as per guide
already off AV and firewall

image
image1920×1080 209 KB

26

image
image1920×1080 261 KB

27

Can you rerun the test? You’re missing part of the command. Make sure you copy the whole command.

28

image
image1920×1080 181 KB

29

The DNS entry didn’t work.

Can you take a screenshot of the changes you made?

30

image
image1920×1080 298 KB

31

Can you run this in a terminal and return output:

ipconfig /all
32

image
image1920×1080 209 KB

image
image1920×1080 236 KB

image
image1920×1080 279 KB

33

Not sure what’s up.

Can you run this in Terminal and return output?

nslookup api.cryptlex.com
34

PS C:\Users\User> nslookup api.cryptlex.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: api.cryptlex.com
Addresses: 35.71.188.31
52.223.22.71

PS C:\Users\User>

35

That’s confusing. That seems to be working as I’d expect.

Can you try rerunning this:

Test-NetConnection api.cryptlex.com -p 443
36

PS C:\Users\User> Test-NetConnection api.cryptlex.com -p 443 WARNING: TCP connect to (127.0.0.1 : 443) failed
ComputerName : api.cryptlex.com
RemoteAddress : 127.0.0.1
RemotePort : 443
InterfaceAlias : Loopback Pseudo-Interface 1
SourceAddress : 127.0.0.1
PingSucceeded : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded : False

PS C:\Users\User>

37

That’s really interesting. For some reason the nslookup is using the correct DNS and indicating the correct remote IP. But for some reason this test doesn’t use that.

Try one thing. What happens if you run this?

Test-NetConnection 52.223.22.71 -p 443
38

image
image1920×1080 185 KB

I already disable the firewall and AV

39

That’s interesting. So that’s working fine. So seems issue may just be DNS resolution.

Can you run this in powershell and return results?

Resolve-DnsName -name api.cryptlex.com

[EDIT]
Also this:

Get-DnsClientServerAddress
40

image
image1920×1080 187 KB