Windows (10) Home Network Not Working with SagemCom FAST Router

Tony Hedge 1 Reputation point
2020-10-30T11:25:14.78+00:00

I have 3 Windows 10 Home Edition (latest upgrade) PCs on a WiFi Network in my home. They have been File Sharing successfully for years. Recently my router failed and I swapped it out for TalkTalk's latest 'Super-Router', their words not mine, a SagemCom FAST 5364 Router. Since installing the Sagemcom router my 3 PCs fail to see each other on my network, so cannot File Share etc.

I have investigated and find the following:-

a) One of my PCs has a Hostname "Study_Mk_3" and an IP Address "192.168.1.12". I can 'ping' the IP Address successfully, but I cannot 'ping' the Hostname successfully

b) I tried to lookup the IP Address 192.168.1.10 using the Command Prompt utilities "nslookup" and "nbtstat":-
nslookup failed to resolve the IP Address to the Hostname.
nbtstat succeeded in resolving the IP Address 

  See screenshot below. Does anyone know how to interpret these finding and tell me what might be wrong with my setup?

36363-nslookup-ping-nbtstat-screenshot.jpg

Windows 10 Network
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Network: A group of devices that communicate either wirelessly or via a physical connection.
2,273 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sunny Qi 10,901 Reputation points Microsoft Vendor
    2020-11-02T06:52:52.977+00:00

    Hi,

    Thanks for posting in Q&A platform.

    Firstly, please check Network Discovery and Share settings. Make sure you have turned on network discovery and file and printer sharing.

    If the issue still existed, I would like to confirm the following information with you.

    1. May I know how do you access to the shared folder? By \IP address\share or \hostname\share?
    2. What's the result of nslookup hostname?
    3. Regarding of the result from provided screenshot, please refer the following info:

    1). For result of nslookup 192.168.1.10: Non-existent domain

    This command means you sent a reverse query to DNS server to query the IP address to hostname, and the non-existent domain means the reverse lookup zone for domain "1.168.192.in-addr-arpa" is not existed in DNS server.

    2). For result of nbtstat -A 192.168.1.10

    This command is related to NetBIOS name resolution. If the computer needs to know the NetBIOS name or domain name of the IP address, it will first look up the local Host file and NetBIOS cache, and then connect to the DNS server for resolution. If none of these methods cannot complete the resolution, it will sent out the request via broadcast to resolve the corresponded NetBIOS name.

    Best Regards,
    Sunny

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Amin AbuDahab 1 Reputation point
    2021-11-16T09:36:43.11+00:00

    I know this is an old post and you probably have figured it out by now but I had the same problem and this is how I solved it:
    Your computer names do not match those on your router, if you look at the home screen of your router page you'll find different names (e.g. PC-20).

    Change the name to match those of your PCs and it should solve it.

    It's not a super modem, It's a shitty modem !

    0 comments