Score:0

network issue with wsl2, nslookup works, but ping fails

pk flag

I am facing bad network issue with networking on windows10 machines.

tried most of the solutions available over internet. yet there is no solution.

Solutions tried -

  1. Solutions related to enabling HyperViser and its virtual switch.
  2. Solutions related to resolve.conf

The strange part is, nslookup works for same domain, but ping and telnet fails.

Here is the tcpdump I retrieved.

    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:07:52.232609 IP (tos 0x0, ttl 128, id 35195, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:07:52.664089 IP (tos 0x0, ttl 4, id 44165, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:07:52.843167 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.24.208.1 tell 172.24.219.122, length 28
12:07:52.843455 ARP, Ethernet (len 6), IPv4 (len 4), Reply 172.24.208.1 is-at 00:15:5d:39:59:34 (oui Unknown), length 28
12:07:52.977687 IP (tos 0x0, ttl 128, id 58887, offset 0, flags [none], proto UDP (17), length 167)
    172.24.208.1.domain > 172.24.219.122.34134: 55784 NXDomain* 0/1/0 (139)
12:07:52.985984 IP (tos 0x0, ttl 128, id 58888, offset 0, flags [none], proto UDP (17), length 118)
    172.24.208.1.domain > 172.24.219.122.34134: 55784*- 0/0/0 (90)
12:07:52.986009 IP (tos 0xc0, ttl 64, id 40921, offset 0, flags [none], proto ICMP (1), length 146)
    172.24.219.122 > 172.24.208.1: ICMP 172.24.219.122 udp port 34134 unreachable, length 126
        IP (tos 0x0, ttl 128, id 58888, offset 0, flags [none], proto UDP (17), length 118)
    172.24.208.1.domain > 172.24.219.122.34134: 55784*- 0/0/0 (90)
12:07:52.997194 IP (tos 0x0, ttl 128, id 35196, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:07:52.997271 IP (tos 0x0, ttl 128, id 35197, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:07:52.997288 IP (tos 0x0, ttl 128, id 35198, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:07:53.624703 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 172.24.219.122 (00:15:5d:57:94:84 (oui Unknown)) tell 172.24.208.1, length 28
12:07:53.624760 ARP, Ethernet (len 6), IPv4 (len 4), Reply 172.24.219.122 is-at 00:15:5d:57:94:84 (oui Unknown), length 28
12:07:55.670434 IP (tos 0x0, ttl 4, id 44166, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:07:58.677451 IP (tos 0x0, ttl 4, id 44167, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:08:01.144852 IP (tos 0x0, ttl 128, id 35199, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:01.695076 IP (tos 0x0, ttl 4, id 44168, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:08:01.900856 IP (tos 0x0, ttl 128, id 35200, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:02.425450 IP (tos 0x0, ttl 128, id 35201, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:02.664403 IP (tos 0x0, ttl 128, id 35202, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:03.182333 IP (tos 0x0, ttl 128, id 35203, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:03.937345 IP (tos 0x0, ttl 128, id 35204, offset 0, flags [none], proto UDP (17), length 78)
    172.24.208.1.netbios-ns > 172.24.223.255.netbios-ns: UDP, length 50
12:08:04.699387 IP (tos 0x0, ttl 4, id 44169, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:08:07.710596 IP (tos 0x0, ttl 4, id 44170, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137
12:08:10.735360 IP (tos 0x0, ttl 4, id 44171, offset 0, flags [none], proto UDP (17), length 165)
    172.24.208.1.60913 > 239.255.255.250.1900: UDP, length 137

Where 172.24.208.1 is my host machine's IP and 172.24.219.122 is my wsl ip.

Any help us greatly appreciated.

Below is the output for ping -

PING google.com (142.250.185.238) 56(84) bytes of data.
^C
--- google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1024ms```
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.