03-19-2023, 10:13 AM
Jim,
Can you run some commands from a terminal window ?
Press the three keys 'Ctrl' 'Alt' and 'T' simultaneously to open a terminal window.
To check your Linux Lite version enter this command followed by enter
Versions 4.x, 5.x and 6.x are currently supported, although version 4.x is end of support in April 2023.
Version 3.x and earlier are out of support and should not be used to connect to the Internet.
To test basic internet connection and DNS function, run some commands in the terminal window.
Copy the commands carefully.
followed by enter
Allow this to run for about 5 seconds, then terminate command by pressing 'Ctrl' and 'C' together
You should see something like
If the number of packets transmitted = packets received, then you have a basic connection and can test DNS with this.
followed by enter.
If you get results similar to the text below, DNS is working, so allow it to run for about 5 seconds, then use Ctrl and C as before.
But if you get something like
It indicates DNS is not working.
If you report the results of the above the next steps can be determined.
Can you run some commands from a terminal window ?
Press the three keys 'Ctrl' 'Alt' and 'T' simultaneously to open a terminal window.
To check your Linux Lite version enter this command followed by enter
Code:
cat /etc/llverVersions 4.x, 5.x and 6.x are currently supported, although version 4.x is end of support in April 2023.
Version 3.x and earlier are out of support and should not be used to connect to the Internet.
To test basic internet connection and DNS function, run some commands in the terminal window.
Copy the commands carefully.
Code:
ping 8.8.8.8Allow this to run for about 5 seconds, then terminate command by pressing 'Ctrl' and 'C' together
You should see something like
Quote:PING 8.8.8.8 (8.8.8.8 ) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=18.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=18.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=18.0 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=118 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=118 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=118 time=18.0 ms
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 17.963/18.210/18.499/0.208 ms
If the number of packets transmitted = packets received, then you have a basic connection and can test DNS with this.
Code:
ping google.comIf you get results similar to the text below, DNS is working, so allow it to run for about 5 seconds, then use Ctrl and C as before.
Quote:PING google.com (142.250.180.14) 56(84) bytes of data.
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=1 ttl=118 time=16.5 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=2 ttl=118 time=17.3 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=3 ttl=118 time=16.6 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=4 ttl=118 time=17.2 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=5 ttl=118 time=16.7 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=6 ttl=118 time=17.0 ms
^C
--- google.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 16.496/16.869/17.299/0.307 ms
But if you get something like
Code:
ping: google.com: Temporary failure in name resolutionIf you report the results of the above the next steps can be determined.
stevef
clueless
clueless