On Dec 28, 2017, at 8:55 AM, Olivier Mascia <[email protected]> wrote: > >> Le 28 déc. 2017 à 15:42, Olivier Mascia <[email protected]> a écrit : >> >> I'll experiment with the fossil code here. Familiarizing with winhttp.c for >> now. > > I haven't yet come to bottom of it, but using IP (IPv4) in the URL (instead > of name) changes it all!!
That means your domain resolution configuration has a problem. The first lookup will take significant time even on a small quiet LAN, but throughout the entire remaining Fossil clone operation, it will remain cached in the local machine, so it should look it up again near-instantly. (See ipconfig /flushdns) If DNS isn’t working right, Windows might be falling back to NetBIOS name discovery or some other horrid case. > due to dual-stack being the norm on Windows, client connections loose time > trying IPv6 (generally preferred by Windows when DNS reports both AAAA and A > records for a name) before falling back to IPv4. Easy to try: uncheck IPv6 in the network control panel. I’ve seen that clear problems up on Windows before. If it does fix it, it might mean you need to set up IPv6 DNS. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
