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
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
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
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
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
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
6 matches
Mail list logo
