Networking woes again (W10)

Page 1 of 2 12 LastLast

  1. Posts : 11,247
    Windows / Linux : Arch Linux
       #1

    Networking woes again (W10)


    Hi there

    Networking connectivity seems to get broken every so often -- I have shares on two W10 machines (Local accounts) that connect just fine. If I come back to the computer say 45 mins later I get the computers can see each other but cannot connect to the shares --- Windows cannot access \\Computername.

    A bit of messing around and Refreshes --then eventually they connect again. I don't want (and shouldn't have) to do this if I go away and say watch TV for an hour and then come back to the computer(s).

    Is there perhaps a timeout that drops connection if unused for a certain period -- if so how do I override it.

    Ms THIS IS UNACEPTABLE Networking is BROKEN seriously -- please FIX.

    Cheers
    jimbo
      My Computer


  2. Posts : 1,937
    win 10 Insider
       #2

    Good luck with your exhortation to MS, jimbo! I've found that if you want the TV to hear you, you have to shout REALLY LOUD so maybe it's the same with MS!!
      My Computers


  3. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #3

    Go into Feedback and Me too all the networking reports.
      My Computers


  4. Posts : 1,937
    win 10 Insider
       #4

    Done a few of those.
      My Computers


  5. Posts : 494
    Win 10 Pro x64 versions
       #5

    I solved my issue with this by editing the Windows Hosts file. The only problem now is that if I shutdown the PC, and restart again say the next day the network must be scanned which takes several minutes (roughly 10 for me to scan 12TB) before acces to any shares or even a credentials logon box appears. That is unacceptable for one and for another during the scan process Windows complains that it cannot access the resource or that I do not have permissions to access. Ok, give me my login box and I will gladly logon but don't make me wait forever before you do so!
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    RailTech, what did you do to the hosts file?
      My Computers


  7. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #7

    I just tried connecting to my Windows 7 web server and first got an access denied. Hit F5 then when I click on it, I got the expected login prompt. Entered userid and password and am now able to access all shares on that system.

    I wonder why I don't get the logon prompt for the Windows 8 computer, unless it's because I do have a MS account setup there but I use the local account all the time.
      My Computers


  8. Posts : 494
    Win 10 Pro x64 versions
       #8

    Hi,

    I edited the hosts file to tell Windows that my NAS is a locally attached device. I am providing a link that discusses how to do this in Win 10 as it is a bit different than previous versions of the OS. Basically you will use NotePad to edit the file. At the bottom of the file you will position the cursor a couple of lines below the existing entries and you create a line showing your NAS IP address followed by a Tab space followed by Your NAS name.

    Example :

    192.168.1.XXX MyNAS

    Windows networking looks to the hosts file to resolve name spaces so basically your telling Windows Look Here Dummy! Works well when DNS is not configured properly or is slow/non respondent for any reason with locally attached devices.

    Here's the link:

    Easily Edit the Hosts File in Windows 10 - Petri
      My Computer


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #9

    Okay, thanks.

    That would have worked (maybe) for my 3 computer network too. Can't try it now as all is working correctly.

    Hmmmm, I wonder if it would speed things up? Guess I'll try it and see.

    Edit: It does seem to speed up access to my other computers. Atleast it doesn't take as long for the green scan bar to finish.
      My Computers


  10. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #10

    Interesting. I'm on my laptop, named Laptop (amazing hey!).
    I have two other computers, Desktop and Webserver.

    I just tried pinging them by name from a Elevated Command prompt on the Laptop and all the responses were IPV6 addresses.

    C:\Windows\System32\drivers\etc>ping webserver

    Pinging Webserver [fe80::821:b8c:5c3c:6649%7] with 32 bytes of data:
    Reply from fe80::821:b8c:5c3c:6649%7: time=3ms
    Reply from fe80::821:b8c:5c3c:6649%7: time=3ms
    Reply from fe80::821:b8c:5c3c:6649%7: time=3ms
    Reply from fe80::821:b8c:5c3c:6649%7: time=3ms

    Ping statistics for fe80::821:b8c:5c3c:6649%7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms

    C:\Windows\System32\drivers\etc>ping desktop

    Pinging Desktop [fe80::e4ce:c4d0:863:53e5%7] with 32 bytes of data:
    Reply from fe80::e4ce:c4d0:863:53e5%7: time=8ms
    Reply from fe80::e4ce:c4d0:863:53e5%7: time=3ms
    Reply from fe80::e4ce:c4d0:863:53e5%7: time=3ms
    Reply from fe80::e4ce:c4d0:863:53e5%7: time=3ms

    Ping statistics for fe80::e4ce:c4d0:863:53e5%7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 8ms, Average = 4ms
    If I ping by IP address, responses are all IPV4:

    C:\Windows\System32\drivers\etc>ping 192.168.1.2

    Pinging 192.168.1.2 with 32 bytes of data:
    Reply from 192.168.1.2: bytes=32 time=5ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=3ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=5ms TTL=128
    Reply from 192.168.1.2: bytes=32 time=3ms TTL=128

    Ping statistics for 192.168.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 4ms

    C:\Windows\System32\drivers\etc>ping 192.168.1.3

    Pinging 192.168.1.3 with 32 bytes of data:
    Reply from 192.168.1.3: bytes=32 time=5ms TTL=128
    Reply from 192.168.1.3: bytes=32 time=4ms TTL=128
    Reply from 192.168.1.3: bytes=32 time=3ms TTL=128
    Reply from 192.168.1.3: bytes=32 time=3ms TTL=128

    Ping statistics for 192.168.1.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 3ms

    I have no idea what that means or if it has an impact on this problem but I thought it was interesting.

    Edit: Doesn't mean anything, works the same from Win 7 or 8.1.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:34.
Find Us




Windows 10 Forums