WS-Discovery went bye-bye (again)

[TimBaeten]

Greetings all, I had a SMB share setup and working, meaning I could find it from Win11 machines using its name, mount it and perform file operations to/from it. Now I can only get to it via IP address. I did some searching and I don't think anything matches, but I tried the various suggestions to no avail. I am running core 13.0-U6, can't say when it stopped but it was recently.

Turning on NetBIOS-NS makes it so the windows machines can see it, but I would guess by using legacy instead of WS-Discovery.

Any thoughts. Thanks. Tim (I had this same issue summer of 22)

 

[Davvo]

I run mine issueless with \\NAME, which makes me think your issue is networking-oriented; my TN system has a static ip.

 

[TimBaeten]

I run mine issueless with //NAME, which makes me think your issue is networking-oriented; my TN system has a static ip.

I did to, until sometime in the last week. The IP of my TrueNAS is/has been the same. No changes to the network topology nor devices/firmware (I checked to see if there was a silent fw upgrade). This started before U6 and updating to it didn't help.

 

[anodos]

It might be a device on the network that's violating specs for the protocol in a way that isn't being properly handled by wsdd. I've seen this before and have improved error handling in the past. You can review logs and maybe check whether wsdd is running.

 

[TimBaeten]

It might be a device on the network that's violating specs for the protocol in a way that isn't being properly handled by wsdd. I've seen this before and have improved error handling in the past. You can review logs and maybe check whether wsdd is running.

I don't see a wsdd log in /var/log, I have restarted the wsdd service.

 

[anodos]

I don't see a wsdd log in /var/log, I have restarted the wsdd service.

If it occurs again, you can leave the application running in foreground in tmux session (assuming for some reason you're not getting logs).

 

[TimBaeten]

If it occurs again, you can leave the application running in foreground in tmux session (assuming for some reason you're not getting logs).

I seem to be able to recreate this, so once I stop the wsdd service and open a tmux session, how do I manually run wsdd in it?

 

[anodos]

I seem to be able to recreate this, so once I stop the wsdd service and open a tmux session, how do I manually run wsdd in it?

Run command wsdd.py -v should at least give you some initial clues about what's going on.