Member Avatar for shibendu_kr

hi guys

i have a small network of 2o systems . 7 pc has wired connection and rest are configured wireless . i can access the wireless pc with their ip address but not able to acces with their name. please help me.

  • 3 Contributors
  • 2 Replies
  • 67 Views
  • 10 Hours Discussion Span
  • Latest Post Latest Post by DimaYasny

Dani AI

Generated

Hi — building on the prompts from and : if a host is reachable by IP but not by name, the cause is almost always name resolution, not routing. Small Windows networks use a mix of DNS (domain-joined), NetBIOS/WINS, and link-local discovery (LLMNR on Windows; mDNS/Bonjour on non-Windows). Wireless clients commonly end up on a different SSID/VLAN, get different DNS/WINS settings, have NetBIOS turned off, run a Public network profile (which disables discovery), or sit behind AP "client isolation" — any of these will prevent name advertising or name lookups.

Practical checks and fixes to try immediately:

  • Confirm how name access is attempted (ping, UNC path like \computername, RDP). Reachable-by-IP but not by name implies resolution failure.
  • Check DNS: run nslookup <computername> from a working PC to see if an A record exists. If not, ensure the client is configured to register its A record with DNS (DHCP or client-side registration).
  • Check NetBIOS: use nbtstat -A <ip> and verify NetBIOS over TCP/IP is enabled on the wireless adapter if relying on NetBIOS name resolution.
  • Check Windows network profile and enable Network Discovery / File and Printer Sharing where appropriate. Ensure firewall settings are not blocking name services or SMB.
  • If wireless and wired are on different subnets, broadcasts (NetBIOS/LLMNR) will not cross; use a central DNS or WINS, or configure DHCP/router to publish hostnames. AP guest/client isolation will also block peer discovery—disable it if inter-client access is required.
  • Temporary workarounds: add hosts file entries or static DNS entries on the local DNS server/router.

Microsoft troubleshooting notes on Windows name resolution and the mDNS specification are useful background:

RFC 6762 — Multicast DNS (mDNS)

Recommended Answers

All 2 Replies

Member Avatar for DenisOxon

Hi,

Can we have a bit more info please ?

Like what access do you want ?

What happens when you try ?

What OS are they all running ?

Any error messages ?

Denis

Member Avatar for DimaYasny

static or dynamic IPs?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.