Windows 10: XP being able to discover W10 computers on my private network

This one will be a no-brainer for you folks...

Up until a recent security update for XP that I loaded maybe a week or less ago, I had no problems at all.

I can not explore my workgroup ("Buffy", just to irritate my wife) from my XP computer (both the XP and the W10 computers are on wired connections), but if I enter the W10 computer and share (\\ComputerName\C) in as a "Map Network Drive" to the XP computer, I connect.

When trying to browse from the XP computer I go into File Explorer, navigate up to Desktop, then select "My Network Places". The right-hand pane shows nothing. In the left I click "View WorkGroup Computers": I get an error message stating:

Buffy is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The service has not been started.

I have assigned the XP machine to the BUFFY WorkGroup, but it seems to me that once long ago I changed some TCP/IP settings or the like that made easy communication possible. Any help is greatly appreciated, I have a horrid headache from going in circles on this.

Moderator: I am always on my W10 machine, but in writing this I see it is really an XP issue. If it should be in a different forum, please accept my apologies and I would like to respectfully ask you to help me by moving it to where it should be.

:)

 

xp cannot communicate with 10

In my private network I have both xp computers and windows 10 computers.

My xp computers cannot connect to the w10 computers or use printers connected to the w10 computers:

The other way around works well. The w10 computers can connect to the xp computers and use their files.

This is a common problem, very much discussed on the internet, which was introduced by the upgrade to w10 (not before that).

This problem is of course very frustrating.

I have seen solutions mentioned (same workgroup name), which however does not work for me.

Can someone here help me?

Should some special network protocols be used?

What does Microsoft say?

 

Network discovery issue

Just bought a new PC running Windows 10 and when I added it to my private network it is only discovering the other PC's running windows 7. I have a PC running server 2008 and one old one running XP. I cannot figure out how to make them discover-able on the
new PC. If I go to the server or the PC running XP the can access the new one with windows 10 but I cannot access them on the new PC. Any thoughts. Microsoft is telling me to delete my entire network and start over, which I think is the complete wrong answer
and a lot of work.

 

Run this tool on the xp and 10 pcs NetBScanner - NetBIOS scanner it will often kick things into life failing that does it see the other pcs and who is the master browser?

 

I was hoping, but no success...

Interestingly, when run on the XP computer it recognized the W10 computer to be the Master Browser, and saw its resident computer (the XP computer), but when run on the W10 computer it saw the XP computer but did not see the W10 computer!

 

It looks like a firewall issue on the XP machine. Did you enable Files & Printers sharing?
On the W10, open a command prompt and type
NET VIEW
You should see a list of connected machines.
Type PING (name of XP machine)
Do the same on the XP machine but PING the W10

 

In testing I did turn the Windows Firewall OFF for quite a while-

On NET VIEW I get "The service has not been started."

With executing the PING commands I get fairly identical responses on each -
Reply from 10.0.0.x: bytes=32 time<1ms TTL=128

The reply on NET VIEW has me suspicious though...

 

Is netbios running on all pcs? Windows doesnt look for pcs on th enetwork it asks the master browser whos out there so the MB must be uptodate for it to work

 

I just checked the Advanced TCP/IP Settings and the NetBIOS is set to the Default. If I recall, this was a setting I once tweaked a year or two ago, forcing it to Enable. Worth a try...

 

Both computers seem to be able to ping each other.Type NET START on the machine where you got "The service has not been started." and post the list of services that are currently operating. Use NET START >C:\Services.txt and post the content of C:\Services.txt

BTW, would you mind changing the post title for XP *NOT* ...

 

These Windows services are started:

Application Layer Gateway Service
Ati HotKey Poller
Automatic Updates
COM+ Event System
Computer Browser
Cryptographic Services
DCOM Server Process Launcher
DHCP Client
Distributed Link Tracking Client
DNS Client
Error Reporting Service
Event Log
Fast User Switching Compatibility
Help and Support
HID Input Service
HTTP SSL
ImDisk Virtual Disk Driver Helper
IPSEC Services
Logical Disk Manager
Machine Debug Manager
Network Connections
Network Location Awareness (NLA)
PDFProFiltSrvPP
Plug and Play
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry
Secondary Logon
Security Accounts Manager
Security Center
Server
Shell Hardware Detection
SSDP Discovery Service
System Event Notification
System Restore Service
Task Scheduler
TCP/IP NetBIOS Helper
TeamViewer 12
Telephony
Terminal Services
Themes
User Profile Hive Cleanup
WebClient
Windows Audio
Windows Firewall/Internet Connection Sharing (ICS)
Windows Image Acquisition (WIA)
Windows Management Instrumentation
Windows Time
Wireless Zero Configuration
Workstation

The command completed successfully.

 

If NET VIEW wasn't working where did you get the names to ping?

Please post an untouched trace of every command you're asked to type. There is no personal/confidential information involved.

Check the network adapter on each machine: For TCP/IP v4 / Advanced TCP/IP Settings / WINS Tab / Tick ENABLE NetBIOS over TCP/IP

Double check you have enabled file sharing and NetBIOS. On each machine type:
NET SHARE
NET VIEW

Any network setting you change on your XP machine requires a restart.

 

I know the names of my computers...

Will proceed as instructed soon, putting out the morning business "fires"!

 

Set Enable NetBIOS over TCP/IP on the XP machine, restarted, verified setting. Verified Enable NetBIOS over TCP/IP on the W10 machine.

Following are all results except on the XP machine the response to the NET VIEW command was:
"The service has not been started."

XP - NET SHARE:

Share name Resource Remark

-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers
IPC$ Remote IPC
Bruce C:\Documents and Settings\Bruce
C C:\
My Documents C:\Documents and Settings\Bruce\My Documents

SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS

Silver My Documents
C:\My Documents
Printer XPSPort: Spooled Microsoft XPS Document Writer
Printer2 DocuCom PDF Port: Spooled ScanSoft PDF Create!
Printer3 Nuance Image Printer W Spooled PaperPort Image Printer
Printer4 Send To Microsoft OneN Spooled Send To OneNote 2007
Printer5 DocuCom PDF Port: Spooled DocuCom PDF Driver
Printer9 Microsoft Document Ima Spooled Microsoft Office Document Image Wr
The command completed successfully.


W10 - NET VIEW:

Server Name Remark

-------------------------------------------------------------------------------
\\PUMBAA
\\SILVER Silver Dell
The command completed successfully.


W10 - NET SHARE:

Share name Resource Remark

-------------------------------------------------------------------------------
ADMIN$ C:\Windows Remote Admin
IPC$ Remote IPC
C$ C:\ Default share
E$ E:\ Default share
D$ D:\ Default share
C C:\
D D:\
E E:\
Users C:\Users
The command completed successfully.

 

Hi there

not sure why you should have any problems with XP seeing W10 (or vice versa).

I'm using W10 CU edition (1703) plus two Linux media servers - zero problems with connectivity between all of them (both ways from all computers to each other).

I didn't do anything other than just install W10 Cu edition with the bog standard Windows defender. No extra firewalls etc.

Here's the network view from the XP machine. (OK it's running in a VM - I don't have a spare physical machine for running XP - but it's the same principle).





Cheers
jimbo