Windows 10: Networking too problematical - gone back to build 10149

Hi there

I've HAD it with Windows Networking and a mixture of Ms and Local accounts -- It's a TOTAL DOGS DINNER. Sometimes you can see computer, sometimes not - problem totally not re-produceable - and it seems really RANDOM.

So I've gone back totally to build 10149 with ONLY LOCAL ACCOUNTS apart from one machine on 10166 on a VM.

I'll wait until Ms sorts out Networking before restoring the 10166 or later builds.

I NEED the LAN and shares to operate PROPERLY - and it's NOT on W10. Without access to my servers / NAS from ALL machines on my LAN the system is for me NOT properly useable.

Can anybody explain this (build 10166)

Two machines running W10 with Ms accounts -- One can see the other but can't logon to shares. The other doesn't even SEE the second machine.

Both running x-64 build 10166 on REAL hardware (not VM's). Both being tested via Wireless connections. (My Wifi is plenty fast enough).

BLACKKDOG can SEE Redsquirrel and Logitech Media (Squeezebox) music server. Can't access shares though.

REDSQUIRREL can't even SEE BLACKDOG or even the Squeezebox / Logitech media server.

Both can get MEZZMO since I'm testing it locally on each machine.

Afraid I've LOST PATIENCE with this B/S -- 10149 everything works (Network that is) I can live with the other minor bugs.

Cheers
jimbo

:)

 

Which one is the latest preview build of Windows 10 for windows phone in India?

10149:

Hands on with Windows 10 Mobile build 10149 (And should you install?)

 

Lumia 635 refuses to install Windows 10 build 10166, also can no longer be seen by recovery tool

Save yourself many hours trying to update your Lumia 635 from Build 10149 to Build 10166.

Restore to 8.1 and do all your App updates too.

I worked for way to many hours with 10149 install and the update process refused to complete.

No real searchable error messages either.

Decided to Restore and now just waiting for the rolling Gears to mash up the bits and pieces into another attempt at Win 10 on my Lumia 635.

Hope this helps - Good Luck!

 

You may just need/want to set all accounts back to local rather than go back to an earlier version

At least on my systems, I only have problem with MS accounts to Local accounts shares mix.

What worked for me was to get all Local accounts working together again was to go to Control Panel >User Accounts >Manage Your Credentials and reset all the "Windows Credentials". I deleted the existing credentials and created new ones (re-entered each share's info) in the format "ComputerName\UserName", "UserName", "Password".

 

Hi there

Thanks for that --have restored the 10166 builds and carried outyour suggestion --works (finally).

All Local stuff working now -- I'm totally going to forget about Ms Accounts - I'll just keep a VM so I can pull in the insider stuff --create an ISO and update manually all other machines.

I'm surprised Ms hasn't spent more time on the network issue -- these days even small households have some sort of a LAN - especially where media streaming is concerned.

Cheers
jimbo

 

Well, call me stunned. I can't tell you how many hours I have spent trying to get two win 10 comps to see the shares of the third. All I could get was the 80070035, path not found error. The third could see all other shares, however.

These three comps all had MS accounts. With all three now on local accounts that ornery third's shares are visible. Words fail me.

What on earth was going on I ask myself? I thought I was doing the right thing by getting on to MS accounts. But I still have no idea why only one comp's shares were not able to be seen. I guess I will never know.

The bigger question, like you say jimbo, is will this be fixed? It has been a problem for several builds for me.

Thanks to CountryBumkin for suggesting the "solution". But still not happy*Sad

 

G'day mate

Agree with you -- was watching CRICKET yesterday in a boisterous Pub full of aussies -- can't be much further than between Iceland and NZ but was in UK as going to the tennis today in Wimbledon. Great game -- loved a comment by an English Fielder when an aussie batsman was out -- "Hey Mate there, turn your Bat the other way around --it's got the instructions on it !!!".

As an N.Z guy you should appreciate that comment !!!.

Still I hope that Ms WILL fix the networking stuff -- what is particularly irritating is that the whole problem of connectivity seems Random at best -- sometimes computers are visible sometimes not and all sorts of other problems in between.

However the OP's solution (or Work around) is good for the moment.

I don't also like the idea of the EMAIL address appearing on the Lock / Login screen when using an Ms account either -- but that's another issue --at least let's hope Ms fixes the networking first.

Cheers
jimbo

 

England totally crushed us.
Our bowlers were horrible (and our batsmen too for that matter). *Sad

 

Well, what did you expect after the Black Caps taught the Poms how to get out there and whack the ball? *Smile

 

Chose the wrong pub, jimbo!!

Yep, fair distance between Iceland and NZ!

With regard to the share problem, none of my comps had any problem seeing the other comps and the NAS. I just had that one problem with only one of the win 10 comps.

Mystere earlier explained that there was a difference between the MS and local login and I was certainly seeing that, but on only one machine. It looked like a permissions issue. However, all my comps started off with a local account, then were 'converted' to an MS one, so that made it hard to see why only one had the problem.

But, in any event, this issue shouldn't have occurred as it will cause a lot of grief after the 29th.

Perhaps MS should ensure that its diagnostic routine is geared up to fix the no path found problem, or at least explain it.

Still leaves us in limbo jimbo (sorry, couldn't resist that) as, what do you know, a Notification comes through now telling me to use the MS account or I won't get future updates. What's a guy to do??

I honestly don't think the RTM will fix this for me but I am happy to be wrong. I would also be happy if they could tell me what trick was needed to fix it myself.

Did you watch poor old Roger get beaten? Got a real soft spot for Roger.

Cheers.

 

More testing.

If the problem comp is on a MS account, and the probing comp is on a local account, the shares will display fine.
If the problem comp is on a local account, and the probing comp is on an MS account, the shares won't show.

The key factor seems to be whether the probing comp is on an MS account or not.

What that tells me is........ nothing!! At least nothing useful. Just maybe it means something to somebody else??

 

Hi there

Had a great weekend -- Wimbledon is brilliant -- not the cheapest gig in town but well worth a trip.

The aussies also weren't that horrible -- although why they were drinking FOSTERS when there was VB available (Victoria Bitter) which is actually a decent aussie beer still amazes me as Fosters Beer is just "Kangaroo Urination". Horror of horrors but even American Budweiser might be better -- no on second thoughts that's just "A Drink too far".

Back to the networking -- I think we'll have to live with it until RTM. Pity because for the rest W10 seems to be going in the right directions -- even EDGE now handles LOCALHOST type of addresses and isn't too bad either.

Cheers
jimbo

 

No guarantee this will be fixed for RTM. If not, disaster awaits.

Hoping fix will be in next pre-RTM release, hoping hoping hoping ...

 

Hoping here too!!

Looks like we will find out within a day or so.