Windows 10 access

[KevinG]

Upgraded, great job, but now cannot see Beyonwiz in Windows 10 file explorer. All other network features eg iceTV OK and test network said all OK.

Network shows other servers but not Beyonwiz, I have rebooted everything a couple of time

[MrQuade]

You can still go to the Explorer address bar and type in \\beyonwizt4\ (if you have a T4) and get to the wiz over the network, all that is happening is that the wiz has not been found by your network's master browser yet.

Firstly, make sure your wiz is in the correct workgroup. Press MENU->Setup->Network->Samba->MENU

Second but is a bit trickier. You need to find out which device on your network is the master browser and figure out why it apparently doesn't like listing the Wiz.

It's best to see if you can force an always-on device like a NAS to be the master browser rather than a PC or laptop that gets switched on and off all the time.

See how you go with step 1 then we can explore (HA!) other options.

[KevinG]

Thanks \\beyonwizt4\ works, will investigate other options

[MrQuade]

Thanks \\beyonwizt4\ works, will investigate other options

No worries.

Here is a link to a site that can help you determine your network's SMB master browser.
https://scottiestech.info/2009/02/14/ho ... workgroup/

[raymondjpg]

You can still go to the Explorer address bar and type in \\beyonwizt4\ (if you have a T4) and get to the wiz over the network, all that is happening is that the wiz has not been found by your network's master browser yet.

I don't think that is all there is to it. I have two Windows 10 installations, one of long standing in a virtual machine, and a recent installation on my LAN. Neither installations list my T2 under Network in the file explorer. Running some network utilities in Win 10 pick up the T2 in scans, and one of the utilities clearly lists my desktop PC, which runs Windows 7, as the Master Browser. That is as it should be, the desktop PC is always on.

The desktop PC clearly lists my T2 as BEYONWIZT2 under Network in the file explorer.

The command "net view" throws a System error 58 in both Windows 10 installations. I don't think that is purely by coincidence. This error has been termed "the mystery error" because it is difficult to track down a cause, but I suspect the culprit is Microsoft!

In the past some users have reported the issue that Windows 10 cannot see some networked devices, but can see others, and that on occasion those network devices that could not be seen have mysteriously re-appeared overnight. As Microsoft has a take it or leave it policy with regard to updates for Windows 10 it is possible that this issue was triggered by some update, and might possibly be redressed by some future update. I'm not holding my breath.

And yes, a network drive to \\BEYONWIZT2 can still be mapped under the Windows 10 installations if need be.

[MrQuade]

The command "net view" throws a System error 58 in both Windows 10 installations. I don't think that is purely by coincidence. This error has been termed "the mystery error" because it is difficult to track down a cause, but I suspect the culprit is Microsoft!

Agreed. If Windows is generating those sorts of errors, then all bets are off.

[peteru]

Get a Linux based router to provide proper DNS resolution integrated with a DHCP server to your entire network and live a happy life.

[MrQuade]

That solves name resolution issues, but doesn't help with Windows Explorer being able to list SMB servers. That's all tied up with the SMB browser functions and not directly related to DNS.

(Edit: Something in my previous reply attempts was being Error 403'd by the forum software, it seems I am unable to quote your post)

[prl]

...
(Edit: Something in my previous reply attempts was being Error 403'd by the forum software, it seems I am unable to quote your post)

Sometimes binary search through post fragments is the only way to find out just what Sucuri is taking umbrage at today.

[peteru]

I'm pretty sure that Windows will have an easier time of it if the low level stuff is working properly. If you can't resolve "beyonwizt4" in the first place, then your chances are a lot slimmer.

[MrQuade]

IIf you can't resolve "beyonwizt4" in the first place, then your chances are a lot slimmer.

Definitely agreeing with you on that point, but in this case the name is indeed resolving correctly already.

[raymondjpg]

In the past some users have reported the issue that Windows 10 cannot see some networked devices, but can see others, and that on occasion those network devices that could not be seen have mysteriously re-appeared overnight. As Microsoft has a take it or leave it policy with regard to updates for Windows 10 it is possible that this issue was triggered by some update, and might possibly be redressed by some future update. I'm not holding my breath.

My T2 returned to the Windows 10 Network fold after I installed some updates a couple of days ago. I'd say it is premature to congratulate Microsoft on this resurrection.