W10 INCOMING connections - missing network protocols

Page 2 of 2 FirstFirst 12
  1. lehnerus2000's Avatar
    Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #11

    I meant that I must have typed the address incorrectly:

    //192.168.118.128

    instead of:

    smb://192.168.118.128
      My Computer

  2. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #12

    My bad .

    You get it working without IP, with computer names?
      My Computer

  3. lehnerus2000's Avatar
    Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #13

    VM To VM Works Too


    Kari said:
    My bad .

    You get it working without IP, with computer names?
    It was "My bad", not yours. :)

    I have also been able to connect an XP VM to the W10TP VM (on LM17 Host) and share files each way (using Windows Explorer and File Explorer).

    I haven't tried connecting by typing in the PC names yet.
    I'm assuming that Windows Explorer and File Explorer use the PC names by default (based on previous usage).

    W10 INCOMING connections - missing network protocols-networking-w10-vm-xp-vm.png

    W10 INCOMING connections - missing network protocols-networking-xp-vm-w10-vm.png
      My Computer

  4. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #14

    Hi there

    That doesn't explain why I can't connect a W7 or XP machine either to a W10 (Virtual or real - Virtual on HYPER-V OR VMware).

    I have no trouble with the IP addresses - just with computer name . All computers in same workgroup with same user id and passwords.

    Have deleted Samba password file - re-installed SAMBA and re-configured - same problem as before.

    I'll re-install the Linux distro and try again WITHOUT the security updates - and I'll try "Clean" VM's -- I.e nothing added after install apart from VMWARE tools for the VMWARE VM's.



    Cheers
    jimbo
    Last edited by jimbo45; 12 Oct 2014 at 05:31.
      My Computer

  5. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #15

    One thing with networking between Linux and Windows is that when using MS account (Windows 8 or later) to sign in to Windows, you should not use it in networking. Use instead the \\ComputerName\UserName format.

    You geeks know this, I just explain it for any future readers: In case of an MS Account, the Windows sign in name and account profile name (username) are two different things. If you sign in to Windows on PC named MyMonsterRig using an MS account dick.doe@example.com and prior to creating the Windows user account you have edited your MS account profile to show your sender name as Richard Doe, your Windows user profile name will most probably be Richard.

    In this case, you would have these three different usernames:
    • Windows sign in name: dick.doe@example.com
    • Windows username (local): Richard
    • Windows username (networking): \\MyMonsterRig\Richard
    Last edited by Kari; 12 Oct 2014 at 06:21.
      My Computer

  6. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #16

    Hi there

    Something's really weird now -- not sure if it's Linux or Windows updates that cause problems --Moral never update more than ONE thing at a time or you'll get onto a hopeless mess


    To logon to Windows 8.1 share now at the logon box I have to type workgroup/username for my username !!!
    It does work though -- still can't get W10 access via computer name - absolutely no problem via IP.

    Anyway it's a FREEZING Sunday so nothing much to do so I'm installing the OPENSUSE 13.2 RC1 (it's about to be released as FINAL in approx. two weeks) on ONE machine, Creating a W10 on another machine and W8.1 on a third with a W7 and XP as VM's on this one (via VMWARE). I can't run VMWARE on W10 currently as the networking (VMware's) doesn't work. VMware workstation 10.

    Now with 3 clean physical systems with just base installs they should all be 100% clean.

    SAMBA is robust enough -- it's been around since "Pontius was a Pilot" - any biblical scholars should understand that !!.

    will post back later of results -- at least it's something to do before the next break. !!!

    Cheers
    jimbo
      My Computer

  7. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #17

    @jimbo45, as far as I have understood OpenSUSE 13.1. is already final? From OpenSUSE:

    openSUSE 13.1: Ready For Action!

    Dear contributors, friends and fans: The release is here! Eight months of planning, packaging, adding features, fixing issues, testing and fixing more issues has brought you the best that Free and Open Source has to offer, with our Green touch: Stable and Awesome.
      My Computer

  8. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #18

    Kari said:
    @jimbo45, as far as I have understood OpenSUSE 13.1. is already final? From OpenSUSE:
    Hi there
    I meant OPENSUSE 13.2 it's at RC1 but that should be 99.999% identical to the final coming in 3 weeks.


    Cheers
    jimbo
    Attached Thumbnails Attached Thumbnails W10 INCOMING connections - missing network protocols-opensuse13.2.png  
      My Computer

  9. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #19

    OK.

    I am not a big Linux fan but if I had to name my favorite distros it would be OpenSUSE and CentOS.
      My Computer

  10. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #20

    Hi there
    I like centos too but I've found multi-media works better with OPENSUSE - especially using my older music streamer (old Logitech squeezebox system) and integrates nicely with my phone too --I'm sure centos could work just as well but I've used opensuse for ages.

    Anyway building my test environment - I'm going to get to the bottom of the W10 networking one way or another.

    Incidentally VMWARE is coming out with VMWARE workstation 11 also in November so those trying VMWARE on a NATIVE W10 system should have that part of networking fixed.

    W10 runs HYPER-V quite nicely though.

    Cheers
    jimbo
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 06:06.
Find Us




Windows 10 Forums