Viewing networked XP computer from Win 10 pro 64 bit

[#1]

As some of you are aware I am now the proud owner of a Win 10 laptop as I needed a laptop at very short notice

As I am now back home I need to connect to an existing network (not called homegroup) which consists of an XP 32 bit machine and a Win7 64 bit machine which see each other and also see the Win10 laptop but the laptop can't see the XP computer

[#2]

Is this any use to you @Oldjim

http://www.tomshardware.co.uk/faq/id-3114774/set-join-workgroup-windows.html

[#3]

been through all the options and still can't see the XP computer

[#4]

You'd be good to go if you put Linux on the W10 effort.

[#5]

What version of Windows 10 are you running @Oldjim?

[#6]

Win 10 pro 64 bit as per the thread title

[#7]

OK, I knew that @Oldjim, just wanted to see if you were reading the posts!

What do you get when you go to : Network & Internet > Network & Sharing Centre > Advanced Settings?

I have this:

[#8]

exactly as I have it set

[#9]

Well then @Oldjim I can't explain why it doesn't work. The only other thing I can think of would be that that the Windows 10 machine is on a different network, but that would be odd. What does:

ipconfig /all

Tell you on these machines?

[#10]

Is the workgroup the same? iirc XP Home devices used MSHOME as default rather than WORKGROUP.

[#11]

Yes the workgroup is the same although the one on the XP machine it is lower case with an upper case first letter whereas in 10 it is all caps

This may be part of the problem

Name:    WiFi
Description:    Intel(R) Dual Band Wireless-AC 3165
Physical address (MAC):    58:fb:84:18:84:d1
Status:    Operational
Maximum transmission unit:    1500
Link speed (Receive/Transmit):    72/72 (Mbps)
DHCP enabled:    Yes
DHCP servers:    192.168.1.254
DHCP lease obtained:    ‎29 ‎May ‎2017 15:30:37
DHCP lease expires:    ‎30 ‎May ‎2017 15:30:37
IPv4 address:    192.168.1.105/24
IPv6 address:    fe80::b047:846:7784:ee9a%9/64
Default gateway:    192.168.1.254
DNS servers:    192.168.1.254
DNS domain name:    home.gateway
DNS connection suffix:    home.gateway
DNS search suffix list:    
Network name:    Billion-8800NL
Network category:    Private
Connectivity (IPv4/IPv6):    Connected to Internet / Connected to unknown network

[#12]

I run Win7 Pro with XP available in a virtual window. I also have Win10 available (on a dual boot - well it was a freebie!!!). When I first set up the XP window I couldn't connect to my home network. While I have no idea where I found the answer (although I suspect MS Help pages) it was to do with the name of the Home group being different in Win7 and XP (as previously mentioned). Could the names be case sensitive?

Brian

Edit : there are any number of guides listed on Google

[#13]

Further to my last post I found the following

http://www.tomshardware.co.uk/answers/id-2017431/networking.html

Now, while it refers to Win8.1 & XP it has a couple of suggestions that might be worthwhile trying. Confirm what each machine is listing as it's WORKGROUP (On XP > Control Panel > System. Don't know about Win10)

If they are the same, scroll down to "BEST ANSWER" on the above link and try that suggestion.

Brian

[#14]

Can you access shares on the XP machine from the Win 10 machine.

If you try and access \\ipaddress of XP machine\share name

what happens?

If that fails to see the XP machine, then there is a network issue - unlikely as the XP machine can see the Win10 one

if it fails with access problems then it may be a permissions issue, if it works then it's probably a "browse master" issue.

[#15]

@Oldjim - You might want to try turning off the IPv6 protocol in your network card setting as it thinks you're connected to an unknown network and may be getting in the way.