Having trouble getting XP Network to work in Win 10 VM

Tried the IP of the host machine but "folder not found"

See if you can connect in the other direction then. Create a folder on the XP VM, set file permissions to full control for Everyone, share it and tick the box to allow network users to change the files. On the host enable SMB 1.0/CIFS Client. See if you can connect to it from the host.

Make sure that the XP VM is in the same Workgroup as the host machine. You may not see see it's name on the network at first, it has to announce itself to the master browser. That may take a few minutes. If it doesn't appear try connecting using its IP address.

I have found that XP machines can be a little temperamental about networking on a Win10 network, but you should be able to connect to its shares even if it can't connect to a Win10 share.

banger said:

...it seems something more fundamental than sharing folders.

Sounds like the virtual switch is not working. Do you have any other VMs? A Win10 one perhaps? Does the virtual switch work for them?

I'd start by checking the XP VM has obtained an IP address, mine get's its IP address by DHCP from my router. In the VM open a command prompt and see what IPCONFIG says. This is what I see. The default gateway is my router's IP address. I'm using an external switch connected to my host's wifi adapter.

I have a Win 10 guest which is working fine. Win XP guest adapter properties are set manually, IP 192.168.1.155 and gateway is 192.168.1.1 which is my router. When I check the status for the XP adapter received bytes are zero so XP is not seeing the router. I have legacy adapter on XP guest but when I set to automatic DHCP it says limited connectivity so I set it up with a manual address.

banger said:

..When I check the status for the XP adapter received bytes are zero so XP is not seeing the router. I have legacy adapter on XP guest but when I set to automatic DHCP it says limited connectivity so I set it up with a manual address.

Well, if the virtual switch works with other guests it can only be the XP's IP settings. I'm at a loss to explain it, mine works fine on automatic and I've never had to change it.

This is driving me crazy I came across a blog that said to mount the XP Guest drive on Win 10 host and pull files off the drive that way. This doesn't work either, cant find any files I have created.

Hi folks

@banger

why not try using VMWare player (free) or Virtual Box also free . (Temporarily disable HYPER-V if using those of course).

XP runs perfectly easily as a VM on these systems without issue. I'd always start with these first before messing around with more complex things like HYPER-V.

Check also if the XP's IP address is within the permitted IP range dished out by your router - you can test this by powering off the VM and manually assigning the HOST to that IP address.

Personally unless there's a very specific reason to have the VM on a fixed IP address on your Lan I'd just let the router assign IP addresses automatically via DHCP as suggested above by @Bree.

cheers
jimbo

banger said:

This is driving me crazy I came across a blog that said to mount the XP Guest drive on Win 10 host and pull files off the drive that way. This doesn't work either, cant find any files I have created.

One way to transfer files without a network connection is to create a new virtual disk in Hyper-V Manager. This .vhd can be mounted in the host to transfer files to or from it. Then dismount it in the host, attach it as a second hard drive in the VM using the SCSI Controller in Settings so that the VM can use it.

The advantage of using a second hard drive is that you don't risk messing up the VM's own drive. If the second drive is formatted as Fat32 or ExFat then there are no ntfs permissions to worry about either.

@jimbo I have tried VM Player and Virtual Box. VM player complains about Credential guard even when Hyper V is removed and Virtual Box gets to the Welcome screen of XP and freezes without being able to go any further.

@Bree I thought of this as a solution but trying to add a SCSI disk proves impossible. XP just doesn't detect the SCSI drive. I have tried various methods of creating a data drive but XP refuses to see the disk. Even running the add hardware wizard fails to see it.