Windows 10: 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

:)

 

Want day of week, date and time in small taskbar

Thanks Alan, my problem is completely solved thanks to your help. T-Clock Redux does exactly what I want. (If only there were such simple solutions to all my W10 woes!)

 

Location Woes Again

I can confirm this...it has not been able to locate my phone for at least 3

weeks now. GPS is turned on, and I've made no changes to the phone.

Bob

 

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!!

 

Go into Feedback and Me too all the networking reports.

 

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!

 

RailTech, what did you do to the hosts file?

 

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.

 

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

 

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.

 

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.

If I ping by IP address, responses are all IPV4:

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.

 

Same here. I just noticed this yesterday.

 

Hi there

The MEGA disadvantage with that scheme is that you have to have FIXED IP addresses on your network --OK if you never re-boot but if you use DHCP and have IP addresses assigned automatically then this method is no good.

You need something that can resolve computer names on your network so whatever IP is assigned on the Lan the situation will work.

You can usually always MANUALLY in any case connect to a remote computer if you have the logon permission via \\ipaddress\resource (e.g D or whatever), Networking should make this unnecessary though and it's still not 100% satisfactory when mixing computers with Local and Ms accounts.

Some people have had success by disabling IPV6 addressing -- but not sure if that's a good idea as a lot of ISP's are starting to use IPV6 now - although they will have to have some conversion mechanism to remain compatible with IPV4 for some time yet.

I think it's still obvious that as far as HOME Networking is concerned Ms still has a bit of work to do to get this working seamlessly and predictably.

(Funny how Linux has always seemed to have no trouble at all with even complicated setups whereas Windows sometimes has a problem just connecting TWO LOCAL computers !!!!).

Cheers
jimbo

 

I disagree... It's not funny that "two local" computers cannot connect... *Sad*Mad

I agree with the rest of your posting, especially with the part about predictability of the network connections. Some apps rely on data on other systems and W10 dropping the connection in the middle of work is nuts. Just don't use W10 for work... *Tongue