I have a webserver running under a virtual machine on build 10130. The virtual machine is running on a separate virtual IP address range to the main network. The IP address of the virtual webserver is 192.168.172.99. Spartan wont connect to this and says 'Hmm we can't reach this page'. The virtual machine is running on VM Workstation. Note that IE11 works fine.

Any ideas on the cause of this please and how to solve it. I've seen some 'fixes' to get Spartan to see localhost but this only seems to work on the loopback address. CheckNetIsolation LoopbackExempt -a -n=Microsoft.Windows.Spartan_cw5n1h2txyewy

This doesn't work as in affect the virtual machine is on a separate network and not the loopback address. The network type under VMware workstation is 'host-only'.

Cheers

Steve

• Moved by Brandon RecordsModerator 13 hours 6 minutes ago Moved to more appropriate forum.

Youve posted this thread under the Windows 10 Phone Technical Preview forum. It will be moved to the correct Windows 10 Insider Preview forum for PC builds.

I would also recommend submitting this issue via the Windows Feedback app to alert the appropriate development teams.

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

• Proposed as answer by Michael ShaoMicrosoft contingent staff, Moderator 50 minutes ago

Carpangler,

Windows 10 build 10159 is available to the fast ring, you may consider to upgrade to this version and check the things out.

http://blogs.windows.com/bloggingwindows/2015/06/30/whoa-another-pc-build/

Regards

Hi

I've checked the latest download of windows 10 last night and the issue still remains. Are there any other options I could try to resolve this. Note that IE11 on Windows 10 works perfect and can see the virtual machine, but Spartan cannot.

Cheers

Steve