Re: Windows Server 2012 & 4D Server v17.2
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 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 **
Re: Windows Server 2012 & 4D Server v17.2
Did you change the install path on the server ? If so then its the firewall. In the Windows firewall you define either the ports to be open or for the application itself to accept connections. If you have changed the path then it will be treated as a new application and unable to accept connections. Is it not possible for them to give you temp RDP access to the control panel ? -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 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 **
Re: Windows Server 2012 & 4D Server v17.2
Tim: Thanks Jody > On Jul 19, 2019, at 1:09 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > On Jul 19, 2019, at 2:00 PM, Jody Bevan 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. > > Check the Application Server tab on the 4D Server Administration see if the > button at the top says “Accept new connections”. If it says that, then the > server has decided to reject connections. If you click the button the button > name should then change to “Reject new connections”. But that might not make > a difference. > > I’ve seen v17 sometimes go into reject connections mode for no known reason. > Clicking the button does not fix it. > > Try restarting the server machine. That is how I’ve fixed the reject > connection problem. > ** 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 **
Re: Windows Server 2012 & 4D Server v17.2
On Jul 19, 2019, at 2:00 PM, Jody Bevan 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. Check the Application Server tab on the 4D Server Administration see if the button at the top says “Accept new connections”. If it says that, then the server has decided to reject connections. If you click the button the button name should then change to “Reject new connections”. But that might not make a difference. I’ve seen v17 sometimes go into reject connections mode for no known reason. Clicking the button does not fix it. Try restarting the server machine. That is how I’ve fixed the reject connection problem. Tim * Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.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 **
Re: Windows Server 2012 & 4D Server v17.2
You need to be sure that the firewall is configured correctly.. I run both and have no issues but needed to open all the appropriate ports. Ed Glassgow glass...@pcisys.net On 7/19/19, 10:45 AM, "4D_Tech on behalf of JOHN BAUGHMAN via 4D_Tech" <4d_tech-boun...@lists.4d.com on behalf of 4d_tech@lists.4d.com> wrote: 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 ** ** 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 **
Re: Windows Server 2012 & 4D Server v17.2
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 **
