LO has no problems opening files with a path like \\machine.local\share\file.odt or \\192.168.1.2\share\file.odt but it can't deal with \\machine.\share\file.odt or \\machine.local.\share\file.odt although those are also valid in Windows for machine.local. All of the above path types allow me to browse the shares and open the same files with other programs such as MSO. Tried with machines running Windows 10 21H1 and 20H2, LO 7.2.2.2 and 7.2.4. Also tried with MacOS where this problem did not occur.
Mike: having noticed your work about Windows part, especially path management part, thought you might be interested in this one. (perhaps already fixed in one of your commits?)
I have no access to a network with Windows shares, other than own home system that I attempted to open in Explorer using a \\MYSYSTEM\share UNC (successfully) and \\MYSYSTEM.\share - the latter showed a login prompt, and refused my login/password. Reading the specs, I don't see a definite answer. 1) File path formats on Windows systems [1] tells that "If a segment ends in a single period, that period is removed" in "Trim characters" section; but that section relates to relative path segments, as clear when reading the context, discussing normalization of .. and ...; nowhere on that page, a system name is identified as "segment". 2) Naming conventions in Active Directory for computers, domains, sites, and OUs [2] discusses NetBIOS names and DNS names; the former can't have leading periods (but other restrictions are not mentioned), while for former, the period may only separate DNS parts, and trailing period is explicitly forbidden. For NetBIOS names, if trailing dots are allowed to be part of a name, that would mean that \\SERVER and \\SERVER. are *different* names. I do not know how to get a definite answer about proper normalization of server part of UNC - please share if you find a good reference. Thanks. [1] https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats [2] https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou
I would like to clarify the use case of \\machine.\share - it forces Windows to accept "machine." as a FQDN and not auto-resolve it into machine.domain.com. when "machine" is part of a different domain than the client connecting/resolving the address. The workaround is to use the real FQDN of machine: "machine.otherdomain.local" but "machine." is quicker/neater IMO. You could also add DNS suffixes in Windows network interface settings to avoid this server name lookup problem.
there is a workaround suggested in comment -> https://bugs.documentfoundation.org/show_bug.cgi?id=146607#c3 this bug is being set as NEEDINFO. can you please perform the workaround to ensure if the issue is still seen? alternatively, if the issue is still seen you can add the steps performed along with the observations and set this bug to UNCONFIRMED. Hello, Thank you for reporting the bug. Can you please confirm if the issue still exists in the latest build? Could you please try to reproduce it with a master build from https://dev-builds.libreoffice.org/daily/master/ ? You can install it alongside the standard version. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build.
(In reply to sockseight from comment #4) > there is a workaround suggested in comment -> > https://bugs.documentfoundation.org/show_bug.cgi?id=146607#c3 It seems that you post to multiple issues, without really considering what specifically you suggest to do; and needlessly change the issue status, which may result in an unexpected/unneeded resolution INVALID, if your questionable comments will not be addressed. Specifically, here and e.g. in bug 146337 comment 7, you point to comments made by *original issue authors* as "workarounds"/"instructions", as something that "should resolve the issue". Did you actually took a second to think about it?
my apologies for any inconveniences caused. i am new to contribution of bug triaging. hence forth i will approach cautiously.
Dear Sven Ollino, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Sven Ollino, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp