F5F Stay Refreshed Power Users Networks Unable to reach "PC Name," however "Lan IP" is reachable.

Unable to reach "PC Name," however "Lan IP" is reachable.

Unable to reach "PC Name," however "Lan IP" is reachable.

Pages (3): Previous 1 2 3 Next
X
Xythorn
Member
66
06-22-2023, 11:54 PM
#11
Open the command prompt. Run an nslookup for HOSTNAME to check resolution. Note that Windows relies on NETBIOS over broadcast, which may fail across different subnets.
X
Xythorn
06-22-2023, 11:54 PM #11

Open the command prompt. Run an nslookup for HOSTNAME to check resolution. Note that Windows relies on NETBIOS over broadcast, which may fail across different subnets.

I
iwkooo
Junior Member
49
06-23-2023, 11:10 PM
#12
Also, network discovery is active on both systems. https://www.windowscentral.com/how-confi...ndows-10-0
I
iwkooo
06-23-2023, 11:10 PM #12

Also, network discovery is active on both systems. https://www.windowscentral.com/how-confi...ndows-10-0

C
crazypotpie
Member
225
06-24-2023, 12:42 AM
#13
I received that as my initial confirmation. I also turned on the Function Discovery features and configured them to automatically think about it.
C
crazypotpie
06-24-2023, 12:42 AM #13

I received that as my initial confirmation. I also turned on the Function Discovery features and configured them to automatically think about it.

J
Jaewan14
Junior Member
39
06-24-2023, 01:36 AM
#14
Are you sure your computer has both those IP addresses? The third part differs—244 versus 254. **I must admit, I’m confused; it seems they’re being translated to public IPs, which points to a DNS problem.**
J
Jaewan14
06-24-2023, 01:36 AM #14

Are you sure your computer has both those IP addresses? The third part differs—244 versus 254. **I must admit, I’m confused; it seems they’re being translated to public IPs, which points to a DNS problem.**

G
GBLeon
Member
150
06-29-2023, 09:23 AM
#15
The server's IPv4 address is visible in the initial image.
G
GBLeon
06-29-2023, 09:23 AM #15

The server's IPv4 address is visible in the initial image.

B
ByFeNix1350
Senior Member
502
06-29-2023, 08:32 PM
#16
I also executed the same command on my laptop, and it produced the identical outcome. However, your laptop doesn’t seem to experience the same problem.
B
ByFeNix1350
06-29-2023, 08:32 PM #16

I also executed the same command on my laptop, and it produced the identical outcome. However, your laptop doesn’t seem to experience the same problem.

S
SuperC859
Member
53
06-30-2023, 10:03 AM
#17
DNS tips here: 1. Use "ipconfig /flushdns" to clear old DNS records
2. Check configured servers with "ipconfig /all"
3. Nslookup doesn't require the -verify flag
4. Try "resolve-dnsname DESKTOP-8Q0UO6R" in PowerShell to see output
5. Think about renaming that Desktop—it sounds awkward, especially with the numbers. Good luck reading it late at night.
S
SuperC859
06-30-2023, 10:03 AM #17

DNS tips here: 1. Use "ipconfig /flushdns" to clear old DNS records
2. Check configured servers with "ipconfig /all"
3. Nslookup doesn't require the -verify flag
4. Try "resolve-dnsname DESKTOP-8Q0UO6R" in PowerShell to see output
5. Think about renaming that Desktop—it sounds awkward, especially with the numbers. Good luck reading it late at night.

T
TalemStudios
Junior Member
32
07-02-2023, 02:45 AM
#18
Flushing the DNS didn't fix the issue. Here's what I get from powershell
T
TalemStudios
07-02-2023, 02:45 AM #18

Flushing the DNS didn't fix the issue. Here's what I get from powershell

P
Petseal812
Junior Member
24
07-09-2023, 09:04 AM
#19
Turn off IPv6, Windows will rely on that (the AAA record), which seems improperly set, while the IPv4 record appears valid after clearing DNS.
P
Petseal812
07-09-2023, 09:04 AM #19

Turn off IPv6, Windows will rely on that (the AAA record), which seems improperly set, while the IPv4 record appears valid after clearing DNS.

S
sandieaak
Member
182
07-09-2023, 09:18 PM
#20
Run Notepad with admin privileges, access c:\windows\system32\drivers\etc\hosts (no extension). Add this at the end: 192.168.1.9 Desktop-8Q0UO6R The best way to resolve this is to set up or adjust DNS on your router (192.168.1.1). The issue on your laptop stems from using NETBIOS, which isn't functioning properly on the desktop either. Relying solely on NETBIOS isn't a reliable fix.
S
sandieaak
07-09-2023, 09:18 PM #20

Run Notepad with admin privileges, access c:\windows\system32\drivers\etc\hosts (no extension). Add this at the end: 192.168.1.9 Desktop-8Q0UO6R The best way to resolve this is to set up or adjust DNS on your router (192.168.1.1). The issue on your laptop stems from using NETBIOS, which isn't functioning properly on the desktop either. Relying solely on NETBIOS isn't a reliable fix.

Pages (3): Previous 1 2 3 Next