From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:7445:: with SMTP id o66-v6mr9235744itc.20.1542962475666; Fri, 23 Nov 2018 00:41:15 -0800 (PST) X-Received: by 2002:aca:308d:: with SMTP id w135mr244170oiw.0.1542962475468; Fri, 23 Nov 2018 00:41:15 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!2.eu.feeder.erje.net!4.us.feeder.erje.net!feeder.erje.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!q69no31990itb.0!news-out.google.com!v141ni70ita.0!nntp.google.com!q69no31988itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 23 Nov 2018 00:41:15 -0800 (PST) In-Reply-To: <83ec2d38-c9a0-4bbc-82e2-456e108680c7@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=136.163.203.5; posting-account=g0yTkgoAAADdZGEYyZahxGlO3EkjH0Wv NNTP-Posting-Host: 136.163.203.5 References: <83ec2d38-c9a0-4bbc-82e2-456e108680c7@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <939cb592-9807-4637-844c-b3a42a43b1a2@googlegroups.com> Subject: Re: GNAT Sockets UDP problem on Windows 10. From: Petter Fryklund Injection-Date: Fri, 23 Nov 2018 08:41:15 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:54876 Date: 2018-11-23T00:41:15-08:00 List-Id: Den fredag 23 november 2018 kl. 07:27:45 UTC+1 skrev Petter Fryklund: > Hi all, >=20 > I get socket error 10051, network unreachable when trying to send on Wind= ows 10. Everything works fine on Windows 7. Also, Delphi programs work fine= on Windows 10. What is special with GNAT Sockets and what do I do to overc= ome this hurdle? >=20 > Regards, > Petter When creating the reproducer I first found out that I mistakenly had copied= code from a TCP client that also did Connect. When that was fixed I found = that I had made an unnecessary Bind of the sending socket (as a response to= the compiler warning that the socket was read but not initialized), stran= gely this was alright on W7, but not on W10. We are now fine (for now ;-) Regards, Petter