WSDD Discovers client in NOTJOINED #123
Replies: 2 comments 3 replies
-
So the discovery process is working correctly? "NotJoined" is an information that is provided by the discovered device. The device seems to provide an empty DisplayName property. That's why you only see 'discovered in'. The DisplayName would be seen between these two words if it was non-empty.
I think there is a misunderstanding on what wsdd or the WSD protocol in general are doing here. With the discovery mode, other WSD compliant devices are searched and reported if they are found. This is what the protocol was designed for. The term "device" does not imply it is a Samba host. It can be a printer, scanner, (IP) camera or similar thing. Generally, you won't be able to "access" them via smb clients unless they run Samba, e.g. Note that wsdd does not check for the device type during discovery.
I do not see a Python or wsdd issue here. Connectivity issues are likely related to your network setup, but IMO this is not the best place to discuss these. |
Beta Was this translation helpful? Give feedback.
-
|
I understand that WSD is for discovering and samba is for accessing. I have smbd running, but when I disable nmbd, 2 PCs disappear . I have opened the ports on the client and server's firewall per the instructions (3702, 5357 and relevant protocol), nothing in the logs dropped or rejected from those ports, even cleared the firewall to be sure that wasnt the issue. I still get NOTJOINED. Also made sure SMB2 was running on both clients and smb.conf had the appropriate max/min protocol lines |
Beta Was this translation helpful? Give feedback.
-
Right. Just to be clear: The intended use case is to run wsdd on a Linux machine that runs Samba, e.g. for file serving purposes. In this typical scenario, wsdd helps the Windows clients (or more precisely, the user on the Windows machine) to find the Samba machine. Also, Samba enabled the access to the files in this typical scenario but actually the access is performed by the Windows clients. You can also use the Samba client to access Samba servers or Windows machines. Nevertheless, I am not sure if I understand your problem right. Could you please describe what you intend to achieve and answer the questions below?!
Where do the 2 PCs disappear? AFAIK, nmdb has nothing to do with wsdd.
What do you expect to see instead of "NotJoined"?
What are the clients you are referring to? Since you mention the smb.conf, I assume they are Linux machines
You are starting wsdd in order to discover other WSD compliant devices. This appears to succeed and wsdd prints the information it could get from the detected device. Note that the "NotJoined" is not something wsdd comes with, but it is an information provided by the device: Lines 662 to 664 in c87819b Please also note that a WSD compliant device may not serve files. Besides that: You don't have to run wsdd under root privileges. This is a potential security risk. |
Beta Was this translation helpful? Give feedback.
-
|
You can also use the Samba client to access Samba servers or Windows
machines.
Nevertheless, I am not sure if I understand your problem right. Could you
please describe what you intend to achieve *and* answer the questions below?
…---
Just want all my devices to use WSD so I can stop using SMB1.
I have smbd running, but when I disable nmbd, 2 PCs disappear .
Where do the 2 PCs disappear? AFAIK, nmdb has nothing to do with wsdd.
---
I can sort the Win10 Network tab by discovery method.Two win10 clients are
detected using NETBIOS when the other win10 client and one Ubuntu server
are listed under WSD.
---
I have opened the ports on the client and server's firewall per the
instructions (3702, 5357 and relevant protocol), nothing in the logs
dropped or rejected from those ports, even cleared the firewall to be sure
that wasnt the issue. I still get NOTJOINED.
What do you expect to see instead of "NotJoined"?
--
Truthfully, Im not 100% sure as Im not that familiar with the WSD log
messages. So the client is "NOTJOINED" to what?
---
Also made sure SMB2 was running on both clients and smb.conf had the
appropriate max/min protocol lines. Is there anywhere else I might look to
solve this?
What are the clients you are referring to? Since you mention the smb.conf,
I assume they are Linux machines
--
Sorry for not making that more clear. I have 3 Win10 clients and a printer
on an Ubuntu Server.
---
The current log is: sudo wsdd -D -4 -i eth1 -v--
---
You are starting wsdd in order to discover other WSD compliant devices.
This appears to succeed and wsdd prints the information it could get from
the detected device. Note that the "NotJoined" is not something wsdd comes
with, but it is an information provided by the device:
https://github.com/christgau/wsdd/blob/c87819bda08acbe5913057770cc393c788577fb7/src/wsdd.py#L662-L664
---
I have disabled SMB1 on the win10 devices in question, and enabled SMB2-3
via powershell and verified its active.
---
Please also note that a WSD compliant device may not serve files.
Thats why I kept SMBD running. I shut down NMBD for testing purposes.
--
Besides that: You don't have to run wsdd under root privileges. This is a
potential security risk.
Ok thanks, Ill keep that in mind.
----
I'm missing something, and its annoying me lol
Thanks,
Kevin
On Tue, Mar 1, 2022 at 1:27 PM Steffen Christgau ***@***.***> wrote:
I understand that WSD is for discovering and samba is for accessing.
Right.
Just to be clear: The intended use case is to run wsdd on a Linux machine
that runs Samba, e.g. for file serving purposes. In this typical scenario,
wsdd helps the *Windows* clients (or more precisely, the user on the
Windows machine) to find the Samba machine. Also, Samba enabled the access
to the files in this typical scenario but actually the access is performed
by the Windows clients.
You can also use the Samba client to access Samba servers or Windows
machines.
Nevertheless, I am not sure if I understand your problem right. Could you
please describe what you intend to achieve *and* answer the questions
below?!
I have smbd running, but when I disable nmbd, 2 PCs disappear .
Where do the 2 PCs disappear? AFAIK, nmdb has nothing to do with wsdd.
I have opened the ports on the client and server's firewall per the
instructions (3702, 5357 and relevant protocol), nothing in the logs
dropped or rejected from those ports, even cleared the firewall to be sure
that wasnt the issue. I still get NOTJOINED.
What do you expect to see instead of "NotJoined"?
Also made sure SMB2 was running on both clients and smb.conf had the
appropriate max/min protocol lines Is there anywhere else I might look to
solve this?
What are the clients you are referring to? Since you mention the smb.conf,
I assume they are Linux machines
The current log is: sudo wsdd -D -4 -i eth1 -v
You are starting wsdd in order to discover other WSD compliant devices.
This appears to succeed and wsdd prints the information it could get from
the detected device. Note that the "NotJoined" is not something wsdd comes
with, but it is an information provided by the device:
https://github.com/christgau/wsdd/blob/c87819bda08acbe5913057770cc393c788577fb7/src/wsdd.py#L662-L664
Please also note that a WSD compliant device may not serve files.
Besides that: You don't have to run wsdd under root privileges. This is a
potential security risk.
—
Reply to this email directly, view it on GitHub
<#123 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT3ZTA3CZTLUU5IVZQMXT6DU5ZOQDANCNFSM5H57UHCA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
So you want the two Windows Client to be detected via WSD? If so, then this is not an issue related to wsdd. You have to change the configuration of Windows: The "Function Discovery Resource Publication" service needs to be started (and enabled) in order to announce a Windows host using the WSD protocol.
The devices are not joined to whatever the device consider to be joinable. That might be a AD domain or a Windows workgroup. But actually, I would not care about this. As I already noted, this information ("NotJoined") is provided by the device. |
Beta Was this translation helpful? Give feedback.
-
When I run wssd (installed with APT) thi found this in the logs:
wsdd[21607]: 2021-11-12 18:05:28,195:wsdd INFO(pid 21607): (IP) .:3702(eth1) - - "ProbeMatches urn:uuid:0975e9a1-3cda-4663-ba2c-47d8327bd400 UDP" - -
Nov 12 18:05:28 server wsdd[21607]: 2021-11-12 18:05:28,210:wsdd INFO(pid 21607): discovered in NotJoined on x.x.x.x%
(Clientname and IP are correct for the machine)
I get this for 2 machines and neither are accessible with either hostname or IP..
I opened up the ports on the firewall, and it did work perfectly for about a day. I updated python to 3.7 with no errors, removed the apt and github package as completely as I could and reinstalled it using the instructions here.
It reports as Ubuntu 16.04 even though Ive done a dist upgrade.
IF any light could be shed on this Id appreciate it.
Beta Was this translation helpful? Give feedback.
All reactions