Have the clients tried connecting using a Custom address… 192.16..1.150:19813 for example? I have found that for some of my windows installations This was necessary to make a connection, after which the recent connection created can be used.
John John Baughman Kailua, Hawaii (808) 262-0328 john...@hawaii.rr.com > On Jul 19, 2019, at 4:17 AM, Jody Bevan via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I do not have access to the Windows Server Administration window (only to 4D > Server Window). 4D Server has been working fine there. A restart of the 4D > Server to put up an application update, (that works on a server in our shop) > and now the clients cannot see 4D Server broadcasting. > > I have gone into 4D server to ensure that it is broadcasting on 19813 and the > 4D Admin window says that it is. It even shows network activity in that > window. No clients can connect to the server. A 4D Client running on the > server computer cannot connect either. > > If I had access to the Windows Server Administration window I would poke > around to try and find something (like the firewall on) causing this. > > Any pointers on what I should check for? > > I am not used to having client controlled servers. > > Jody > ARGUS Productions Inc. > ********************************************************************** > 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 > ********************************************************************** ********************************************************************** 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 **********************************************************************
