NetBIOS DNS
I'm trying to figure out how to get computer name resolution on my network.
I have a number of devices on my LAN, with device names "COMPUTER1" (IP 182.168.0.101), "COMPUTER2" (IP 182.168.0.102), etc. My router has IP 192.168.0.1. In this case, COMPUTER1 has a DHCP pool IP and COMPUTER2 has a permanent DHCP address reservation.
From COMPUTER1, I would like to be able to do a `ping COMPUTER2` and have it resolve the device name to the correct IP address. When I had the same devices on my consumer-grade ISP-provided modem/router device, this worked out of the box. On my ER8411 business router, it doesn't seem to work at all.
To clarify, from COMPUTER1, a `ping 192.168.0.102` works fine, but `ping COMPUTER2` times out with a "could not find host COMPUTER2".
Am I missing something obvious?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for posting in our business forum.
Have you examined the firewall on your router? Specifically, I mean the IGMP ping-related firewall. Can you paste a screenshot indicating these are allowed?
The router supports it and it should work as we have tested it.
- Copy Link
- Report Inappropriate Content
@Clive_A It's not a ping/firewall issue, it's a DNS issue.
I have a Windows machine with hostname "SERVER1" on the network, where the router (ER8411) has IP 172.18.0.1.
Running `nslookup SERVER1 172.18.0.1`, which forces it to use the router as the DNS server, returns:
```
Server: UnKnown
Address: 172.18.0.1
*** UnKnown can't find SERVER1: Non-existent domain
```
Other (normal) DNS queries with this same command, e.g.
```
> nslookup tp-link.com 172.18.0.1
Server: UnKnown
Address: 172.18.0.1
Non-authoritative answer:
Name: tp-link.com
Addresses: 2600:9000:215f:7400:0:275e:4840:93a1
2600:9000:215f:7a00:0:275e:4840:93a1
2600:9000:215f:6c00:0:275e:4840:93a1
2600:9000:215f:9000:0:275e:4840:93a1
2600:9000:215f:8600:0:275e:4840:93a1
2600:9000:215f:5200:0:275e:4840:93a1
2600:9000:215f:800:0:275e:4840:93a1
2600:9000:215f:dc00:0:275e:4840:93a1
54.192.51.8
54.192.51.93
54.192.51.2
54.192.51.85
```
- Copy Link
- Report Inappropriate Content
SomeNetEngineer wrote
@Clive_A It's not a ping/firewall issue, it's a DNS issue.
I have a Windows machine with hostname "SERVER1" on the network, where the router (ER8411) has IP 172.18.0.1.
Running `nslookup SERVER1 172.18.0.1`, which forces it to use the router as the DNS server, returns:
```
Server: UnKnown
Address: 172.18.0.1*** UnKnown can't find SERVER1: Non-existent domain
```
Other (normal) DNS queries with this same command, e.g.
```
> nslookup tp-link.com 172.18.0.1
Server: UnKnown
Address: 172.18.0.1Non-authoritative answer:
Name: tp-link.com
Addresses: 2600:9000:215f:7400:0:275e:4840:93a1
2600:9000:215f:7a00:0:275e:4840:93a1
2600:9000:215f:6c00:0:275e:4840:93a1
2600:9000:215f:9000:0:275e:4840:93a1
2600:9000:215f:8600:0:275e:4840:93a1
2600:9000:215f:5200:0:275e:4840:93a1
2600:9000:215f:800:0:275e:4840:93a1
2600:9000:215f:dc00:0:275e:4840:93a1
54.192.51.8
54.192.51.93
54.192.51.2
54.192.51.85```
I know what you are saying or the things you refer to.
There is no issue with the NetBIOS. Like I said, it worked.
One Work PC, one my laptop.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 193
Replies: 3
Voters 0
No one has voted for it yet.