Windows 10: Networking woes again !!!!

Hi there

Why can't Windows Networking just be like Linux - nice GUI to configure SAMBA (or even use S.W.A.T), click on shares and it's done and works every time !!!!.

Strange scenario now with HYPER-V

HOST OS (W10) can access REAL W8.1 machine, and W10 VM running on HYPER-V.

VIRTUAL VM W10 on HYPER-V can access REAL W8.1 Machine but NOT HOST W10 REAL machine (???!!!)

W8.1 REAL machine can access VIRTUAL W10 machine but again not W10 HOST machine (???!!!)

All on same LAN - both W8.1 and the W10's are x-64 Enterprise version.

Something certainly screwed up -- I did two COMPLETE FRESH installs from the ISO.

(Strange situation where the VM can be accessed but NOT the HOST).

My Virtual NIC switch is OK .

HOST and VM (both W10) can access Internet.

I think I'll give this up -- C'mon Ms why not grab those folks at Red Hat or Novell to sort your Windows networking code -- their stuff seems to work straight out of the box).

My main problem with Windows networking (apart from the major fact it doesn't work) is that it's ALWAYS unpredictable -- each boot up or install you can never be sure if it's still going to work !!!!

Cheers
jimbo

:)

 

Location Woes Again

I can confirm this...it has not been able to locate my phone for at least 3

weeks now. GPS is turned on, and I've made no changes to the phone.

Bob

 

Location Woes Again

I posted several weeks ago about a problem with MyPhone and the location system where it would fail to properly located my phone. The problem lasted several weeks. Jack was kind enough to help me by forwarding the issue to the Microsoft team. Few days after,
everything was working fine - even better than before since the location precision went from 1.6 kilometer to about 20 meters.

Now, the location is failing again. It has not been working for at least 3 weeks. And again, my hardware/software combination did not change.

Can someone explain to me what is the problem?

How can it work for months and then fail again several weeks?

 

Jimbo, to clarify, is this correct:

• Three machines, a w10 rig, a w8 rig and a w10 vm on w8 rig
• w10 rig can access both w8 rig and w10 vm on it
• w10 vm can access its host (w8 rig) but not w10 rig
• w8 rig can access its guest w10 vm but not the w10 rig

 

Hi there

That's correct -- W10 install from NEW on both W10 rig and W10 VM.

TWO physical machines - W8 and W10 - VM is on W10 rig.

(Also posted in another thread - on RDP Windows installer won't let me install programs - that could be a bit of a pain in the you know where if you logon to the HOST machine and then do it through the HYPER-V console.).

Cheers
jimbo

 

OK, so I got that vm wrong, it's on w10 rig not on w8.

I will create this setup and test, will be back although it might take some time.

 

Hi there.

Thanks Kari

We'll eventually get it all worked out and fixed -- on the whole I think Ms have given us a reasonably good preview to play with -- some frustrations - but it IS probably even pre-alpha software so Ms did have some courage to let this out of the door.

Some people are even using it as their Main OS !! but I wouldn't do that at this stage.

I notice that with an INTEL PRO NIC (The decent one !!) the networking seems to be a bit more user friendly - I'm setting up the W10 rig (Host) on an INTEL machine instead of the ASUS Mobo with AMD CPU and gigabyte NIC that I've been using. AMD based computers always give me more grief - but this was an older spare machine --I'll probably keep it for an XP dedicated legacy machine !!!!.

Cheers
jimbo

 

I'm "some people" *Smile. Win10 TechPreview as main (only) OS on my main desktop and laptop, and on a spare HP ProBook laptop I mainly use for testing.

 

Hi there

a local school some time ago threw out 7 desktops -- I offered to take them to the dump -- of course I kept them !! -- I cannabalized 3 of them which I use as testing rigs -- 3 X 16GB RAM and a shedload of HDD's. The 7 were all "Not working" originally - but removing some memory sticks and swapping around HDD's I got 3 working again. Nice FREE testing gear.

Some people have more money than sense. !!!

Cheers
jimbo

 

jimbo the local school has your money. It's called taxes.

Your lucky to fall into such a gift.
If the local school would of paid somebody to do what you did to get some system running it would of cost more than getting new desktop in labor charges alone.

Free testing computers and spare parts. I'm envious.
I live across the street from a school. I'm thinking I might do some trolling across the street and offer some help.

 

Hey Jimbo, I got 3 real machines and 2 virtuals (VMWare and Hyper-V). Not a single issue on network sharing. All 3 real machines see the 2 virtuals and the 2 virtual see the 3 real machines and tested file sharing across network including NAS. Everything is "A" okay... *Smile





Thank you @Kari for the step by step tutorial. This is my first time to use Hyper-V. I installed Win 7 Home Premium. However, Legacy Network Adapter did not work. I have to use the first method for Win 7 Ultimate and I got network connection right away. Thank you very much!

Cheers!

 

Funny, my test earlier tonight made me edit the tut *Smile. Until a few hours ago it told to select the legacy adapter only for Vista SP1 or earlier, and normal for Vista SP 2 and later (that's the way I have learned it). Then I tested with Seven Home Premium and could only connect it with legacy adapter which then made me to edit the tutorial!

The test I mentioned:

 

Hi there

@Bad robot

Did you try on a REAL W10 machine connecting a W10 VM on VMWARE 10 - Did you get ANY networking to work (I couldn't get ANYTHING in VMWARE when using a W10 HOST - no NAT / NO Bridged -- the adapters would not start ).

I couldn't get any LINUX server either to connect to ANY W10 machine (real or Virtual) but the W10 machine COULD access the LINUX shares so not a complete disaster. The Linux machines could SEE the W10 machine and came back with the user name and password screen but then timed out.

A Virtual W8.1 Machine running on Linux (using VMware) COULD access W10 though !!!

I think this might be something to do with "Certificates" -- is there a way of disabling that whole kybosh. I'm running the ENTERPRISE version so it might be an added layer of built in security.

However entering the full SMB address //jim@192.168.1.111 (address of the W10 VM) from a Linux server DOES give access so DNS too is hosed up somewhere along the line -- pinging greyfox (name of the remote W10 machine) returns different IP address to the actual address.



Cheers
jimbo

 

I don't have VMware installed on Win 10 real machine but this Win 10 real machine and the Win 10 virtual machine (VM on Win 8 host) and see and share file with each other.

I haven't tried on Linux yet so I can't comment.



@Kari, the Win 7 Home Premium on Hyper-V had an erratic network connection last night (it disconnects itself). So this is the network configuration right now and so far I'm not having any issues:

 

Once I set my DNS server to the IP address of my friend's Linux PC (it has a local DNS server) I could connect my W10TP VM to my host PC and my friend's PC without any issues.

Note:
I'm running W10TP on the Linux version of VMware Player (on Linux Mint 17).

Playing a video via the network:



I love the new "Window Snap" options. *Biggrin