Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile Insider

Page 45 of 56 FirstFirst ... 35434445464755 ... LastLast

  1. Posts : 5,833
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       #440

    Thanks for that, @Kari. I'm glad to keep things simple and use one account on all devices.

    I searched the Hub on this subject to no avail. Lots of reports on the opposite with no-sync problems. Have yet to search on the Insider forums yet and will do later. Have to step out for awhile.
      My Computers


  2. Posts : 1,481
    W10 22H2 19045.3031
       #441

    Maybe related or not? My financial advisor sends me a monthly newsletter and has done so for at least 15 years. It goes to the same email address that I have had for at least that amount of time. Now it is being received by 3 other email address, all repeat of the original email. I have an isp email(outlook), gmail, juno and a msn address. This is happening from other people that send me email. Checked with financial advisor, they only have one address??. Noticed this starting ~3 months ago..weird to me.
      My Computers


  3. Posts : 26,416
    Windows 11 Pro 22631.3374
       #442

    meebers said:
    Maybe related or not? My financial advisor sends me a monthly newsletter and has done so for at least 15 years. It goes to the same email address that I have had for at least that amount of time. Now it is being received by 3 other email address, all repeat of the original email. I have an isp email(outlook), gmail, juno and a msn address. This is happening from other people that send me email. Checked with financial advisor, they only have one address??. Noticed this starting ~3 months ago..weird to me.
    You do not have them linked to your Outlook Account do you?
      My Computer


  4. Posts : 29,078
    Windows 10 21H1 Build 19043.1023
       #443

    Josey Wales said:
    You do not have them linked to your Outlook Account do you?
    Josey, I have Office 365 on all three of my computers. I also get email on both MS accounts via Outlook.

    Is this what you're talking about?
      My Computer


  5. Posts : 1,481
    W10 22H2 19045.3031
       #444

    Josey Wales said:
    You do not have them linked to your Outlook Account do you?
    Not that I am aware of? but I do have some of them that have an account within outlook, while others are web based.
      My Computers


  6. Posts : 26,416
    Windows 11 Pro 22631.3374
       #445

    Wynona said:
    Josey, I have Office 365 on all three of my computers. I also get email on both MS accounts via Outlook.

    Is this what you're talking about?
    In the free Outlook you can add other email accounts such as Gmail, ISP mail and such. I do not do that all I get is outlook,com mail.
      My Computer


  7. Posts : 2,832
    Windows 10 Pro X64
       #446

    Hi,

    Wouldn't that be Outlook.Live.com ?
    That's what use for mail anyway and it often annoys the hell out of due to it hanging while runnning long scripts, probably the add banners.

    Cheers,
      My Computers


  8. Posts : 155
    Windows 10, Debian Devel, FreeNAS, Zentynal
       #447

    Win10IP (last 3 builds)-Network Folder Shares-SMB/Auth Issue-Linux


    I have a 'what should be an easy issue to resolve' networking/share access question for you guys.

    Does anyone have any issues with accessing folder shares NOT using the Homegroup/Wizard method, but rather the 'advanced' or 'let me' set up sharing manually method - as in right clicking on a folder/drive and go to sharing and selecting the share name and permissions manually ?

    Below is what I can do and cannot do since the last three Win10 IP builds. Thirty years in the IT/PC/COMMS field as an RF Engineer and I cannot figure out why this is an issue. Now bear in mine I have NOT done much on-line research yet, so perhaps I am overlooking something that is new within these latest builds, however, I don't see that being the case.

    Can someone (the more the better) try setting up a Win10 IP (last 3 builds) share and then try to access it (via their MS Log-In account) from a Linux or BSD box via SMB/CIFS using 1/2/3 a protocol and let me know what happens?

    Can/Cannot Do

    Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-fat-tux.png Any Linux Box Accessing a share in Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-win10.png Last 3 IP builds - others OK
    NO
    Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-fat-tux.png Any Linux Box Accessing a share in Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-win10.png Any non-IP box
    OK
    Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-win10.png (Last 3 IP builds) Accessing a share in Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-win10.png Any non-IP box OK
    Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-win10.png Win10 box (IP and non IP) Accessing a share in Announcing Windows 10 Insider Preview Build 16232 PC + 15228 Mobile-fat-tux.png Any Linux box OK
    Note: IP refers to Insider Preview in this case.


    Here is what I DO know:


    • This is NOT an issue with respect to SAMBA/CIFS or versions thereof - the protocol in itself or on the Linux end.
    • This is NOT a Linux networking or authentication issue.
    • This is NOT an issue when trying to access a box with an active 'Local Windows user account' vs. an MS account.
    • This is NOT a mis-configured services option on my end.

    Thus, I conclude (without diving into anything yet) that it has to deal with:


    • Win10 (at least the last 3 IP versions - for myself) and/or
    • Authentication (on the Windows side) and/or
    • Incoming requests only - as outgoing requests or attempts to access shares on other boxes work just fine.



    To access ANY Win10 box with a local user account from Linux, you merely need to enter:

    smb:\\IP addy or win box host name\share - e.g. smb:\\voip\archive
    or smb:\\192.168.0.x\archive - Providing all machines are using the same workgroup.

    To access ANY Win10 box (earlier IP builds or non IP builds) with an active Microsoft Log-in Account from Linux, you need to enter:
    smb:\\IP addy or win box host name\your user account@\share name - 'your user account@' does not (at least in previous cases) need the full IP address. The '@' after your user name should suffice, however, I found that using it in previous builds would work whereas not work without it.

    There are different methods of the above protocol when accessing a MS Account Win10 box depending on authentication options and other Domain settings if one is being used.


    From my iPod 6, I had no problems accessing the Win10 IP box with earlier IP builds using:

    \\WORKGROUP\<user name> - That's it. This was from the app 'FileExplorer' and it filled in the host name upon auto-discovery of any box I had turned on. In my case, WIN10IP was the host name of the IP box.


    The error I get from my iPod: Socket Connection Error
    The error I get from any Linux box: Timeout on server - 192.168.0.7 (The IP of the Win10 IP Build 16232 box)


    Okay....Thanks guys.

    Feel free to move this post into the most appropriate forum.

    Tim
    ARS N9NU
      My Computers


  9. Posts : 17,661
    Windows 10 Pro
       #448

    N9NU said:
    Can someone (the more the better) try setting up a Win10 IP (last 3 builds) share and then try to access it (via their MS Log-In account) from a Linux or BSD box via SMB/CIFS using 1/2/3 a protocol and let me know what happens?
    Why on earth would I try to access Windows shares from Linux using a Microsoft account to authenticate me? Of course I use \\W10-PC_Name\UserProfileName instead.

    Example: If user John Doe with Microsoft account John.Doe@AnyEmailProvider.com used as Windows sign-in account wants to access his shares on that Windows machine from a Linux machine, he should use the user profile name instead of Microsoft account email. As Windows trunkates user profile names to five characters, John's user profile name will be JohnD.

    John would have no issues in accessing the Windows shares with \\JohnsMonsterRig\JohnD, using John.Doe@AnyEmailProvider.com account's password.

    Kari
      My Computer


  10. Posts : 155
    Windows 10, Debian Devel, FreeNAS, Zentynal
       #449

    Noooo.....perhaps I mistyped. Lemme check my post.

    I never had a problem using the method you posted: \\JohnsMonterRig\JohnD, using John.Doe@AnyEmailProvider.com account's password.

    In my case: smb:\\win10IP\n9nu@ WORKED JUST FINE. No need for the rest of the email address.

    My Linux machine (any of the 5) will not recognize the Win10IP machine AT ALL. Im not the only one who's having this issue. I just looked.

    You were reading what I posted wrong. It's my fault. I DID say:

    To access ANY Win10 box (earlier IP builds or non IP builds) with an active Microsoft Log-in Account from Linux, you need to enter:

    smb:\\IP addy or win box host name\your user account@\share name
    - 'your user account@' does not (at least in previous cases) need the full IP address. The '@' after your user name should suffice, however, I found that using it in previous builds would work whereas not work without it.


    What I meant is accessing a Win10 box when it's logged into with an MS account FROM a Linux box, you need to do it a bit differently VS. when a Win machine is logged into with a local user account

    My user name is: n9nu and the Win10IP box ID is: WIN10IP

    In my case, since a few builds ago, my Linux box cannot access OR SEE that Win10 IP box. ALL other Win boxes can be accessed just fine.

    Also...I can access every other Win box from my Linux boxes simply by issuing: smb:\\ip address\share name

    Everything stopped working (inbound to this box) three builds ago. That's it. Outgoing, all okay. Even from a non IP PC to this IP box it takes at least 35 seconds for the password/user name pop up box to come up....whereas before it was immediate.

    I will search and figure out whats going on.


    UPDATE: MSDN has what I need. Thank you. It seems there is an issue for some users.
    Last edited by N9NU; 05 Jul 2017 at 15:16.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:52.
Find Us




Windows 10 Forums