I set the WiFi to "Inactive" using the small popup at the bottom of the list and rebooted the computer. That removed it from the ifconfig list and the server no longer shows the self assigned IP.
I suspect the 4D 17 networking issues are related to computer sleep and/or the new network layer implementation of putting connections to sleep on the server after an inactivity timeout (the default is 20 seconds). I tested two changes over the past week: - Prevent the computer from sleeping when 4D Client is running. - Disable the connection inactivity timeout - SET DATABASE PARAMETER(Idle connections timeout;0). The logs showed only one client session that was aborted. I also ran a client test for over a week that implemented delays on both the client and server side ranging from a minute to 2 hours. No issues. I had previously tried setting Idle connections timeout to 5 minutes. That did not help, there were still aborted connections. If this is not a 4D Server problem, I'm not sure what else could be done to fix it. There were no issues like this with 4D 16.4. This is a single switch network, no routers are involved. The switch is about 6 months old and has no configurable settings. John DeSoi, Ph.D. > On Apr 24, 2019, at 2:09 PM, Charles Miller via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > If it shows as active, that may be part of the problem. I found many > moons ago similar issues when one of my customers had new server with > to NIC cards. It seems what happens is that client connects to 1, > inactive for period of time, goes back and tries using 2, crash just > as you are having. There used to be terminal command to combine two > NICs into one on a MAC. Have you tried restarting the machine. You > should not have a real IP on ethernet connection and self assigned on > wifi. Something is not adding up > > Regards > Chuck > > On Wed, Apr 24, 2019 at 12:28 PM Peter Bozek via 4D_Tech > <4d_tech@lists.4d.com> wrote: >> >> On Wed, Apr 24, 2019 at 4:06 PM John DeSoi via 4D_Tech <4d_tech@lists.4d.com> >> wrote: >> >>> No, just Ethernet is enabled. WiFi and the other connection types are not >>> connected (red dot). But that just helped me answer the question. If I >>> disable WiFi on my laptop, the server shows a 169.254.X.X link-local >>> address. I wonder why and if that could be a source of problems. >>> >>> It shows a red dot, "not connected", but it is active according to >>> ifconfig: >>> >>> en10: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 >>> ether a6:e9:75:40:77:fa >>> inet6 fe80::10be:87e1:3ea2:51c7%en10 prefixlen 64 secured scopeid >>> 0x17 >>> inet 169.254.132.126 netmask 0xffff0000 broadcast 169.254.255.255 >>> nd6 options=201<PERFORMNUD,DAD> >>> media: autoselect (100baseTX <full-duplex>) >>> status: active >>> >>> > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
