On Feb 20 23:36, Martin Wege via Cygwin wrote: > On Thu, Feb 20, 2025 at 9:37 PM Corinna Vinschen via Cygwin > > And here's the problem. It works fine for me on all shares, be it SMB, > > Samba, or NFS: > > > > https://cygwin.com/pipermail/cygwin/2025-February/257438.html > > > > > Maybe the hostname resolution in fhandler_netdrive::exists() failed? > > > > If so, it would be a problem on your side. > > Does `nslookup ember.data4.local' return a valid address? > > > > I just pushed a patch to print a debug statement in strace output > > to see what error code GetAddrInfoW returned. > > The code in > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=df307349a09e6f1ba75c78b1427dcea40f435e6e;hp=8a8fb570d7c5310a03a34b3dd6f9f8bb35ee9f40 > is not going to work, because you only give ret as argument, but not > "name+2" as hostname.
Yeah, it was obviously too late yesterday. The patch was wrong twice. I pushed a patch for the patch which should show up in the just building cygwin-3.6.0-0.381.g8cc55d819bb7 test release. > And speaking of the "hostname", is this the \\hostname\path of an UNC? > In that case this will not work with WebDAV/SSL or WebDAV with custom > port, which might be \\webdavserver@SSL\path or > \\webdavserver@23456\path, or \\webdavserver@SSL@23456\path > You need to replace the L'@' with L'\0' before calling GetAddrInfoW(), > or it is not going to work with WebDAV I never saw that before. Is that syntax really usable? I just spent half an hour trying to connect to a nextcloud instance using this syntax, but to no avail. https://... works. I have a local patch removing this at-sign, but I would first like to hear if this is really usable and used. Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
