Networking woes again (W10)

Same here. I just noticed this yesterday.

Railtech said:

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

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

jimbo45 said:

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

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