Windows 10: Citrix killed Network access to NAS / Linux servers - now fixed !!

Hi folks
I tried all the standard stuff to get access to NAS / Linux machines from W10 including re-enabling SMB1 and killing the auto removal of SMB1 -- nothing worked.

Then I had a brain storm -- get rid of CITRIX (I can run that as a VM for access to work remote desktop)

rebooted

Guess what -- access immediately to my 3 NAS type servers. Note for NAS to access windows also check the SERVER as well as CLIENT box - CLIENT allows W10 to access SAMBA on NAS, SERVER allows NAS to access windows shares.






Windows Networking is a real pain but for the moment working now.

Don't know what CITRIX did but it's staying on a VM from now on !!!!

Update : the VM I've installed CITRIX on has the original network problem !! but NAS access isn't needed on that VM. The main problem is solved though.

Cheers
jimbo

:)

 

Windows 10 November Update - cannot see other network devices

The most persistent news I have on these issues is that my Linux Samba server still does not show in the Network Neighborhood on the Windows 10 machines.

My home network (Workgroup) consists of 2 desktops, 1 laptop and 1 Surface Pro 3 all on the latest Windows 10 1511 build. And 1 Linux machine that I upgraded this week to Fedora 23 and Samba 4.3.1.

The Linux machine also serves as the WINS server and a VPN server. Thus offering remote access to the Windows based shares.

After the upgrading of the Windows machines several weird and peculiar connectivity problems turned up. Machines not showing, not able to connect to shares, printers (wired to the Linux machine) not reachable. Long waits on restoring persistent shares mapping
to drives.

I'd subsequently checked, reset and/or reconfigured all networking related settings like hostnames, workgroup name, protocol settings, etc.

End of the story is that everything is working as it should without any serious issues.

From the Linux machine I can access all the Windows based hosts and shares again. And all Windows 10 machines are shown to be part of the Windows Network.

Windows 10 machines now do show in each others Network Neighborhood. Persistent share to drive mappings work as a charm again. No gibberish output for nbtstat -r anymore. Also the Linux host, share and printers can be reached by name from all my machines
again.

I did not disable any SMB version setting anywhere. I do even expect everything is communicating based on the latest SMB v3.11 level which is supported by the now installed Samba 4.3.1.

Perhaps here a huge benefit having a home made Linux based 'NAS' which gives maximum flexibility in upgrading and configuring. Could be much different from NAS devices with much older Samba releases embedded.

As said. The only persisting minor issue is the Linux Samba server not being visible in the Windows 10 Network Neighborhood.

 

things not working after threshold november update!!!

ok guys thanks for all your help so far....but i was able to fix my animated wallpapers with a patch from 3planesoft.....but i,m still having problems with operating a simple workgroup network with this one uptated machine......i only did the update to one
machine to test it and it still wont see all the computers on my network.....if i access them directly through explorer by typing \\diagnosticpc\ then i have access, but the network window will not show all the pc's on my network.....i cant see my linux nas
server running cifs/smb protocal either but i still have access to it....all i gota do is \\nasserver\ and theres my files....but i open network window and nothing shows up....alll my other machines are running windows 10 pro 64 bit RTM and they work just
fine and can see all the other machines on the network including the Linux nas server....but the one machine i did the nov update to will not see some or all of them depending on the day or the way i've accessed them......also if i remote desktop into my backuppc
then it shows up in the network window but otherwise it doesnt!......i have 4 desktops and a laptop all running win10 64 bit RTM and one nas4free 16tb nas server. all on a high speed gigabit network. and i did the update on one of them. (GAMINGPC) there is
nothing wrong with my network and all the drivers in all the machines are up to date as far as windows is concerned. this is really really annoying and i'm not gonna upgrade any more of my machines with the nov update untill this bug is resolved!

as always thank you,

Jason