its not “.patchbox” , its “patchbox.”
I assume since its working for ‘some’ (ive no idea what percentage) of us, that patchbox OS is publishing its name to the network, but for some reason on some network setups that name resolution is not working…
patchbox. what is going on is there is no domain name declared.
e.g. often it would be something like patchbox.local
(this is mac, can’t remember what windows default is)
and because the patchbox name is not in the same domain as your computer (e.g. .local), it needs a full qualified domain name (FQDN) , because your computer will add its default domain if you dont.
(e.g. ping patchbox on a mac, will try patchbox.local which is not its name!)
interestingly on bela, when it registers its name it does register it in the local domain … so perhaps this is something that patchbox OS could do?
that said, Ive seen similar questions on Bela about name resolution, so its not perfect either.
I think unfortunately all of this is not only related to how patchbox is installed/setup, but also how your network and your OS is setup
anyway, this should all be on a new ‘patchbox OS’ topic, so that others can see it, and chime in,
to see if any common theme is found…
similarly Ive not had any issues with the hotspot, just works on my windows and macs ,
(note: I think my default, when connected via a hotspot, you wont automatically gain access to the ‘host’ computers internet connection … you might have to share it - I’ve had issues with this on Bela!)