Having trouble getting XP Network to work in Win 10 VM

banger · 13 Jan 2020

Hi I have searched for this problem quite extensively and came accross the Ten Forums Tutorial for getting XP/Vista to communicate with the host Win 10 machine by using "Legacy Network Adaptor" which doesn't throw any errors up but browsers in XP VM cant communicate with the router which is a problem but not major.

The main thing I want to do is to be able to share files between the guest and host. I have my other Win 10 machines on the LAN able to share files between computers but I am struggling with guest and host. Help? V1909 and XP SP3

Samuria · 13 Jan 2020

What VM are you using as they are different some like virtual box you have to load additions

banger · 14 Jan 2020

Using Hyper V as I cant get anything else to run. Virtual box just freezes on boot and VM Player says I have to disable Hyper V which is the only thing that works with the XP I have.

banger · 18 Jan 2020

Bump

jimbo45 · 19 Jan 2020

banger said:

Hi I have searched for this problem quite extensively and came accross the Ten Forums Tutorial for getting XP/Vista to communicate with the host Win 10 machine by using "Legacy Network Adaptor" which doesn't throw any errors up but browsers in XP VM cant communicate with the router which is a problem but not major.

The main thing I want to do is to be able to share files between the guest and host. I have my other Win 10 machines on the LAN able to share files between computers but I am struggling with guest and host. Help? V1909 and XP SP3

Hi there

@banger

to those still using XP VM's and want to share folders with NAS drives - especially large TB volumes you need in the SAMBA system on the NAS to set max protocol="NT1" in the smb .conf file (latest SMB versions give error if you say SMB1 or SMBV1)
and also specify in the SAMBA config file (/etc/samba.smb.conf) : (in [global] section)

lanman auth=yes
ntlm auth=yes

To share with W10 ensure on the W10 system SMB1 is enabled. The Windows XP VM if it also needs LAN access should be set to used BRIDGED networking (VMWare / VBOX / QEMU/KVM) or use EXTERNAL (not the default) Switch if using HYPER-V

Having trouble getting XP Network to work in Win 10 VM-xplan.png

As for browsers on XP I think FF and Chrome might still work -- IE won't do the trick to a lot of sites any more (at least that old version in XP won't) and there's no reason really to have an XP VM communicate with the router other than for it to get an IP address --should do automatically if you enable DHCP to assign IP addresses.

If using wifi XP probably will struggle if using adapters with 5Ghz bands - unless you can install a satisfactory driver -- Ethernet no problem though, and depending on the Virtual Machine software you use the "Virtual ethernet adapter" probably will be able to handle wifi from the host adapter.

Cheers
jimbo

Bree · 19 Jan 2020

I have an XP VM in Hyper-V. As has been said, you need a Legacy network adapter connected to a external switch (the default switch will only give internet access).

On any W10 machine with a share you want to connect to from XP, the SMB 1.0/CIFS Server must be enabled in Windows Features. The SMB 1.0/CIFS Client is required if you wish the W10 machine to be able to see and use a share on the XP machine.

You'll need to find another browser for XP. The IE6 as supplied in XP cannot handle https sites. There are very few sites left that still support http.

You may have problems with the Master Browser, if so you can connect to shares on a W10 machine by IP address rather than machine name.

Having trouble getting XP Network to work in Win 10 VM-xp-can-see-w10-shares.png

banger · 19 Jan 2020

Have enabled external adapter in Hyper V and connected to Gbe Family network and I have shares available on the host but XP does not see them, what gives?

Bree · 19 Jan 2020

banger said:

Have enabled external adapter in Hyper V and connected to Gbe Family network and I have shares available on the host but XP does not see them, what gives?

Have you enabled SMB 1.0/CIFS Server on the host?

banger · 19 Jan 2020

Yes which required a reboot but still no go.

Bree · 19 Jan 2020

Try connecting to the host's IP address rather than looking for its name. in the format: \\192.168.1.xxx