A client of mine has hit this very issue. He writes: >> In addition to the dropped connections, it has also been reported 4D will freeze up for a brief period and become unresponsive, then after about 15-20 seconds will begin responding again. No problems like this reported with 16.4 on the same network.<<
I can confirm this same issue on v17r3 on Windows 64 bit client and server running Windows Server 12r2 Datacenter. In addition, the server will refuse connection until somebody touches the server admin window at which point it will accept connections again. -- Douglas von Roeder 949-336-2902 On Wed, Apr 24, 2019 at 10:39 AM John DeSoi via 4D_Tech < [email protected]> wrote: > It is a link-local address (see > https://en.wikipedia.org/wiki/Link-local_address), sometimes called > self-assigned. There is nothing wrong with DHCP. As I mentioned in the > previous message, you get this for WiFi on the Mac when Wifi is not > connected or marked as inactivated. Seems strange, but hopefully it does > not impact anything. > > John DeSoi, Ph.D. > > > > On Apr 24, 2019, at 11:28 AM, Peter Bozek <[email protected]> wrote: > > > > 169.x.x.x seems like a self-assigned address, could it be you have some > problem with DHCP? > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
