Windows 10: Networking woes again !!!!

Hi there

I think people have MISUNDERSTOOD the problem.

It's NOT W10 accessing other computers -- W10 can see and access the other computers (including another W10, Linux, W7, XP and W8.1) both REAL and Virtual.

IT'S THE OTHER WAY AROUND. (FROM computer X TO W10).

The problem is other than W8.1 and W10 computers the other machines CANNOT ACCESS W10's even though they can see them on the network.

Access only seems to be possible if you actually type in an IP address (IPV4 type on a LAN such as 192.168.1.x). Doesn't work via Hostname.

Might work on a domain -- that's overkill for a HOME network which usually has 3 computers active at any one time.

So "peeps" - please try ACCESSING the W10 machine FROM a computer with an earlier OS than W8.1 -- for example W7 and if possible a Linux machine too.


Cheers
jimbo

 

I see what you mean.

When I ran the Troubleshooter it gave me this message:

 

Hi there

Thanks for testing --it's often difficult to describe accurately and understandably what a Network problem is - especially if it partially works.

Note you can still access W10 Shares FROM from Linux / XP / W7 by typing in the IP address of the W10 name -- from Linux get it via NSLOOKUP (PING returns some sort of silly address) and on windows machine itself IPCONFIG works.

I hope this is fixed before final release - I don't want to maintain manual hostnames and addresses in various config files.

Note VMWARE is also releasing VMWARE Workstation 11 and the update for VMPLAYER next month so NAT and BRIDGED networking might be fixed when running VMWARE on a HOST W10 machine.

So two problems - SHARING FROM Linux / W7 /XP etc machine TO W10 (It's OK from W8/W10 to W10) and when installing VMWARE on a W10 HOST networking doesn't work.

Cheers
jimbo

 

My VMware Player is set to NAT.
I haven't tried "Host Only" or "Bridged".

I can't access W10 from Linux Mint using the IP Address either, as Caja rejects it as a valid path, no matter how many slashes I include before it.
I also tried to access it using Firefox (on LM17) but that failed too.

Using "smbclient" in the Terminal shows the correct shared folders on the W10 VM.

 

I've got Networking running now.

It was a PEBKAC issue. *Redface
W10 INCOMING connections - missing network protocols

 

Kari; the words legacy adapter caught my eye.
Shipinomore here. I installed Ubuntu and no problems and connected to the internet.
then I installed Vista home premium and noticed a note that said I should use a legacy adapter and not the Realtek that worked with Ubuntu.
right now I am trying to find out if legacy is something in the bios? I thought I have seen it there.
I am using a
HP Touchsmart AIO 23
8 gig memory
putting all files created by Hyper V on a ext. 2t hard drive.
any help would be appreciated.
Larry

 

Legacy adapters in Hyper-V work exactly as normal Hyper-V virtual adapters, and they are connected to exatcly the same virtual switches than normal virtual network adapters. The difference is in what and how they emulate.

From Microsoft TechNet:

Example from my Vista vm. After creating the vm and noticing it did not have network connectivity, I removed the "normal" Hyper-V network adapter and added a legacy adapter:



Then I connected this legacy adapter to my external LAN switch which uses the host's Realtek NIC:




You don't have to / need to create different virtual switches for legacy adapter. Read more about Hyper-V virtual switches: Hyper-V Virtual Switch Manager.

 

Kari thank you for the help on the Legacy issue I wrote earlier. I went back and read your change in the TUT and now my Vista works. Also Suse 13.2 and Ubuntu 14.04LTS
Larry. Shipinomore

 

Again Kari as I was reading you and Jimbo I saw the change in the tut and I had a install going on another machine and when it finished I did as you wrote and it works great.
Larry