Windows 10: Home Network with non-Windows Devices

My main desktop PC is Win10
I have another Win10 system, a Laptop
Then I have two Linux systems
And an Android Tablet with a File Manager App.

The Win 10 systems appear in their respective Network Maps, but I cannot open them:
In my Main Desktop, it simply says the Laptop Win10 machine is not accessible, contact admin etc for access rights etc

On the Win 10 laptop, when attempting to access the desktop Win10 system, I get a prompt for Username and password to open, but it will not take the password and just keeps re-opening the pop-up.

Neither Win10 machine 'sees' the Linux drives in the Network map, however if I manually address them, it WILL mount them (temporarily) and I can access. If I close the File manager and re-open, or open a new file manager, the linux drives will not be present and have to be added again manually inputting the address.
If I view (& even refresh) the network, folder, it will not see those drives in the right panel, but if previously manually added it will appear in the list of drives in the left pane.

I cannot open the Win10 systems is the Linux machines - same issue as my Win10 laptop (get prompt for username/password) but will not accept it

Same issue on the Android machine - it too 'sees' it in the map, but gives prompt for username/password which it does not accept.

i.e. NONE of my remote systems accepts the username/password to access the Main system, whether that remote be Win10, Linux, or Android.

All of this was integrated fine prior to win 10 upgrade.
It seems like I need to reset the network password, but that makes no difference.
As well as 'me', I have set the shares access to 'Everyone'

How can I recover this, especially on my 'main' machine, so I can access it from the remote systems.
Your help is appreciated!

:)

 

Connecting N97 to PS3

Ah, it seems it's something that S60 5th doesn't have yet. On the non-touchscreen Nseries phones, you can set up a wi-fi network as a "Home Network" and then share and sync media with computers and other devices (although I have trouble getting it to play
nice with Windows).

 

Lumia issue with Wi Fi connection.

Hello all. Any thoughts on this particular issue? Thanks



Nokia Lumia 900 Smartphone

Windows 7.8

OS - 7.10.8862.144

Firmware - 2175.2307.8862.13100

---------------------------------------------------------------------------

Home Network - Comcast.

Router/Modem - **** TG862

Encryption - WPA/WPA2-PSK-TKIP/AES

---------------------------------------------------------------------------

Issue:

Intermittent Home Wi-Fi since Phone firmware update around July 2013.

Symptom - Phone will not connect to Home (secure) Wi-Fi on its own. It will however, connect when my Laptop (Wi-Fi) is on or when I re-boot the modem.

There are two other household devices that use the network. An IPhone and an XBox (wireless). Neither of these have an effect on the Nokia as to connectivity.

The phone connects to other non secure Wi-Fi networks. I've not been able yet to try another secure network.

Summary:

Since

Since my upgrade to Firmware - 2175.2307.8862.13100

Nokia Lumia 900 works fine on non-secure public networks.

It will not connect to my Home secure network unless (Laptop Wi-Fi) is on or unless I re-boot the modem.

 

You cannot access the Android device without a third party app. As for Linux, you have to have Samba installed and shares set up in the Config file, or use the proper utility to allow for public sharing. If you have a firewall installed on the Linux machine, it can also keep someone from accessing shares.

The biggest item is that the workgroup needs to stay at "Workgroup" on all machines. As for Password & username. It will not allow if you do not have everything set up correctly to allow access across the network.

 

I did already mention that I have a File Manager app installed on the Android machines - I am not trying to access the Android from the Win10 machine, but WOULD like to access the Win10 from the Android. The win10 systems show up, just will not open
My Linux systems show up and are accessible on the Android File Manager with no issues.
But neither the Android machine, nor the Linux/Samba systems will accept the username/passwords to access the Windows 10 systems (which ARE visible on those non-windows systems network maps, just will not open because they will not accept the passwords)

In the interim from initial post, I removed each of the Win10 systems from the Homegroup and re-added them (including one of the linux machines which is dual-boot system, when booted in win10)
NOW the windows systems are all showing up and accessible to the other win10 systems on the network - but using same passwords on the Linux & Android machines does not work

Please note again that these devices were accessible when I had win7, no longer so with Win10
The 'WORKGROUP' is exactly that on all the systems.
Samba is installed and configured correctly on my Linux systems and note again that I have no problem seeing the non-windows systems.
i.e. the Win10 systems are allowing access to each other, but not to the non-Windows systems (which at least on the Linux systems, they were)
From Linux system I can try to "connect to server" and again it just rejects the Username and password

 

The solution is HERE

Great advice from a Linux user.

In my case the key was to simply add another 'user' on the Win10 systems as per part 3 [2] and by using those credentials, the win10 systems are now accessible from BOTH the Linux Machines AND the Android Tablet.

Kudos to the author.

 

Hi there

Remember also if you are using an Ms account rather than a LOCAL account on the W10 machines you need to ensure you have user names correctly configured -- it's usually of the form \\machinename\ms acccountname where the account name is the account name UP TO but NOT including the '@' in the email part of the account.

You can also see in the Windows Users directory what the user name should be if you get stuck.

I've spent HOURS on this whole mess in the past. I still find that with SAMBA the "C" (Windows) drive on W10 doesn't display properly -- all other shares are OK though. I don't have any shares on "C" except USERS folder - that one appears OK.

Cheers
jimbo

 

Thanks for added comments Jimbo - I'm with you on the "hours spend on this whole mess" *Biggrin
I am using a local account however.
It appears to have been because there was no password on the main User on the Win10 machine
I had been trying to access with both the Workgroup password and also 'none' (blank) per the main Windows log-in and it just does not like either of those. So I added a password to my main Win10 User and it now accepts the main User. I'm not clear on why it needs the User log-in password, rather than the Workgroup password however! (When I added the 'newuser' I had used the same password as that of the Workgroup, so thought I was using the 'Workgroup' password and did not immediately recognize that it was presumably the log-in password it was using)
I added a 'PIN' to the Win10 main User but the remote access will not take that, only the actual log-in password.

I tried 'sharing' the whole C (Windows) drive just to check for info for you:
with me, it mounts and displays correctly, showing ALL the folders in that drive, and all those folders have the sub-folders and individual files.
I just accessed the same way as other shares; in advanced sharing, gave it a name (c-drive) and set permissions to everyone, then successfully accessed with either my main User ID(now with added password) or the 'newuser' ID.
So no trouble there for me anyway.
What I DID notice however is that if I "connect to server" look at the 'whole' PC, I 'see' all the PC's drives listed as C$, D$, E$, F$, and G$ - but cannot access any of those - however the C and E, which I specifically shared with specific names "C-Drive" and "E-Drive" when I created those shares, DO show up and display the full contents of those drives.
Perhaps try giving your C 'share' a name and see if that helps?

For me, what remains now is to have the Windows Shares mounted on the Linux machines at start-up