Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


4955 posts

Uber Geek
+1 received by user: 103

Trusted

Topic # 239933 11-Aug-2018 17:15
Send private message

I am trying to help out a friend who has a legacy application that must be run in Windows XP (the upgrade to a Windows 10 version is prohibitively expensive) so I thought running XP in a Hyper-V VM would be the best way. That way he can his his application in the VM and use Windows 10 for everything else. His applications connects to another desktop running Windows XP which is the server side.

 

That seemed to work okay and now (almost a year later) and now want to virtualise the server also so I can replace the server hardware.

 

Did the usual stuff like install Windows 10, added Hyper-V, created a vhdx file and created a XP VM using that file. I also added a legacy network adapter pointing to the default switch (like this)

 

 

where the default switch is configured as follows

 

 

and the Intel Dual Band Wireless is the NIC for the host Windows 10 machine.

 

On the XP machine if I use DHCP for the NIC it gives me a 196 address which is clearly invalid.

 

If I code and address in my host machine subnet there is no connectivity and if I code an address in the Hyper-V Switch the same.

 

In the Windows 10 machine I have this switch defined (created when Hyper-V was added I guess)

 

 

but I don't understand why it has an IP address which isn't in the same subnet as my Windows 10 machine (which is in the 192.168 subnet).

 

If I change the IP address of the switch it just adds another IP address so it has two.

 

Annoyingly I got this working a year ago but can't recall what I did and the machine I did it on isn't at hand to check.

 

Can anybody see what I am doing wrong?

 

Thanks

 

 

 

 

 

 





System One: Popcorn Hour A200,  PS3 SuperSlim, NPVR and Plex Server running on Gigabyte Brix (Windows 10 Pro), Sony BDP-S390 BD player, Pioneer AVR, Raspberry Pi running Kodi and Plex, Panasonic 60" 3D plasma, Google Chromecast

System Two: Popcorn Hour A200 ,  Oppo BDP-80 BluRay Player with hardware mode to be region free, Vivitek HD1080P 1080P DLP projector with 100" screen. Harman Kardon HK AVR 254 7.1 receiver, Samsung 4K player, Google Chromecast

 


My Google+ page 

 

 

 

https://plus.google.com/+laurencechiu

 

 


Create new topic
543 posts

Ultimate Geek
+1 received by user: 106


  Reply # 2071852 11-Aug-2018 18:27
Send private message

Yep,

On the screen shot you have the switch set as internal not external

It will only communicate with it's self and other vms using the same v switch

Clint

gzt

10254 posts

Uber Geek
+1 received by user: 1576


  Reply # 2071854 11-Aug-2018 18:27
Send private message

What is the objective? Windows XP with direct network access or Windows XP with network access only to the host machine for things like fileshare between the machines?

Btw hyperv supports copy paste to host now. Slow but fine for most things. Hardly need network for that.

gzt

10254 posts

Uber Geek
+1 received by user: 1576


  Reply # 2071855 11-Aug-2018 18:35
Send private message

Sorry didn't read properly first time. Looks like you want both xp machines talking to each other on a private network on the same host with no external access required.



4955 posts

Uber Geek
+1 received by user: 103

Trusted

  Reply # 2071883 11-Aug-2018 20:41
Send private message

Thanks. You are right that I need machine A running Windows 10 but with a XP VM running the legacy client application to talk to machine B now running XP but wantting to switch that to Windows 10 with the server side application running in a XP VM.  The reason is the XP machine is getting a bit slow and running a XP VM in an Intel NUC I5 8GB RAM is going to be much better.

 

Your suggestions led me to success, thanks.

 

Since all my Hyper-V ethernet adapters were messed up, I removed Hyper-V and re-installed it. This gave me this strange default switch with a the IP address not in my subnet.

 

 

And for some reason in Hyper-V it is bound to the WiFi adapter on the NUC, not the ethernet adapter and cannot be changed.

 

 

But based on your suggestion, in Hyper-V I created a new switch bound to the ethernet adapter and made it external. I then added a legacy ethernet adapter to the XP machine and chose that switch

 

 

Now when I bring up the XP VM and manually add an IP address for the adapter in my subnet, it all works!

 

Thanks a lot. I don't do this often to remember but will take notes now for the future :-)

 

 





System One: Popcorn Hour A200,  PS3 SuperSlim, NPVR and Plex Server running on Gigabyte Brix (Windows 10 Pro), Sony BDP-S390 BD player, Pioneer AVR, Raspberry Pi running Kodi and Plex, Panasonic 60" 3D plasma, Google Chromecast

System Two: Popcorn Hour A200 ,  Oppo BDP-80 BluRay Player with hardware mode to be region free, Vivitek HD1080P 1080P DLP projector with 100" screen. Harman Kardon HK AVR 254 7.1 receiver, Samsung 4K player, Google Chromecast

 


My Google+ page 

 

 

 

https://plus.google.com/+laurencechiu

 

 


Meow
8011 posts

Uber Geek
+1 received by user: 4005

Moderator
Trusted
Lifetime subscriber

  Reply # 2071892 11-Aug-2018 23:03
Send private message

If you can, avoid getting them on the internet. You can configure a vswitch with a static IP on each host (without a gateway IP) so the app can speak to the "server".

Just err on the side of caution as Windows XP has not had updates for years and is terribly insecure.




Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.