Oh, red faced with pie on it on this one. We tested the application on a server in our office. Unknown to me the application was being run on port 19833.
Unknown to me this port setting travels with the structure file to our client’s server. I thought I had checked that, but likely did not pay enough attention to the detail that it ended in ’33’ instead of ’13’. Something so simple. I had them check the Windows Firewall, and numerous other things. Thanks John Baughman, Ed Glassgow, and Paul Dennis for your replies. In the end good news, nothing strange, just a simple setting that I neglected to set back. Now wiser. Guess I have been away from setting up servers for too long. Jody Bevan > On Jul 19, 2019, at 8:17 AM, Jody Bevan <jody.be...@gmail.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 **********************************************************************
