Windows 10: How to Map a XP client PC to a windows 11 PC to a public directory

HI I have a PC that has Windows 11 OS I have several PCs on my LAN network In part, using the Windows 11 PC as a file server that has a directory in the public folder I have no problems mapping to that directory with Windows 7, 8 and 10 My problem is the PCs that are XP when I try to connect to that Windows 11 PC it errors out on XP clients, says it does not have the rights to map to it and to contact admin of Windows 11 PC These same XP client PCs have no problems mapping a drive on another PC with Windows XP or 7 How do I correct this, so they also can map a drive of the Windows 11 PC ?Is th

:)

 

Windows 7 Professional & Windows XP Pro Networking

Hell, I am new to TPU forums so bear with me *Smile . We had a time clock program that we used on Windows XP Pro that required the Data folder of the program (in program files) to be shared (by the host computer) and mapped to (by the client computers). We are now using 3 Windows 7 PC's and 2 Windows XP PC's. The Host Computer (Server) for this program is now on a Windows 7 machine, I am able to share the directory and map to it on the other 2 Windows 7 machines. My problem is I can see the directory on the 2 Windows XP machines but the XP machines won't allow me into the folder...access denied, make sure you have permission.

As I said i'm new to the TPU forums (although I have been watching this site for a long time now) I will be greatful for any help anyone can provide. (Let me know if you need any more info)

Mike

 

windows xp installation and dual core am

could someone please list the steps they follow to install windows with a dual core processor and windows xp service pack to. I'm reletively new to amd dual core and i feel i'm missing a step. All help will be appreciated. thanx

 

Can access just the public folder

I tried the command but it does not return anything, This should me that no SMB protocol is active right?

In the meantime I tried 'Turn Windows Feature on and off 'on the w10 PC-A (the one which can communicate with the NAS) and PC-A and make the same. PC-A. For Both, SMB/CIFS1.0 file sharing support is unchecked now. As a result I can just see JUST the Public folder on PC-B (to me this means that SMB is working and there are access problems somewhere)

I cannot understand why the command you suggest returns void on PC-B ...
On PC-A I get

ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
192.168.1.34 multimedia PC-******\***** PC-******\***** 3.1.1 7

so the next step is to enable SMB 3.1.1 on PC-B

https://docs.microsoft.com/en-us/win...le-smbv1-v2-v3

Thanks much

- - - Updated - - -

I also did this experiment on PC-A, where I mapped to a network drive z: the \\<nas-ip>\multimedia successfully
I tried to map another folder on disk x: and this did not work *Sad (i.e. it is attempting to connect since minutes ...)

- - - Updated - - -

I also tried to map the network drive using QNAP Finder Pro Two alternative methods to map the shared folder as the network drive in Windows | QNAP but still does not work. The list of mappable folder is empty. Differently from PC-A where I cann see the dirs in the NAS suited to be mapped

- - - Updated - - -




The smbd.log report from the PC-B