Re: Clients cannot see v16 R6 on windows server

[Tim Nevels via 4D_Tech]

On Apr 13, 2018, at 2:00 PM, John Baughman wrote:

> First off, I think I found the problem. Looking at the Firewall rules I see 
> that the ports are being managed by application and I see both R5 and R6 are 
> listed twice. What I did not notice right off was that the action for R6 was 
> set to Blocked. I have changed it to Allow but will not be able to test it 
> for several hours. 4D must be creating these rules during installation as no 
> one here did it. Wonder why it set the action to blocked. The open ports 
> column for both versions is set to Any.


Hi John,

I have seen on some Windows systems — can’t be specific on exactly which 
versions, Window 10 for sure — the first time you run 4D Server a Windows 
system dialog box will be displayed telling you network ports are being opened 
and asks you to allow or block these ports. That is probably what created these 
Firewall entries. You only see the dialog one time and if you select the wrong 
option 4D Server will be deaf to network traffic. 

Tim

Tim Nevels 
timnev...@mac.com 
Innovative Solutions
785-749-3444


**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[Timothy Penner via 4D_Tech]

John,

> Someone else pointed out, I think off list, that I would have a conflict with 
> 19814. So I did a bit of testing with netstat. Based on the netstat results I 
> don’t believe that 4D is necessarily grabbing one below and one above the set 
> application port.

You are correct, 4D doesn't grab a port one *below* a configured port, but it 
does grab a port *above* the configured application port.

To be clear, we have the following *configurable* port options and their 
defaults:

SQL: 19812 (v11 default was 1919)
App: 19813+1 (the +1 is the DB4D port)

So by default, 4D listing on:

SQL: 19812 (configurable)
App: 19813 (configurable)
DB4D: 19814 (NOT configurable; this is inherited from the App port +1)

See also:

Tech Tip: 3 things to remember when deploying multiple 4D Servers to a single 
Win box
http://kb.4d.com/assetid=76660

Tech Tip: Changes to ports in 4D Server v11 SQL
http://kb.4d.com/assetid=51390

Tech Tip: Checking for open ports in 4D v11 SQL
http://kb.4d.com/assetid=76029

I hope this clears things up.

-Tim



**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[John Baughman via 4D_Tech]

Hi Janet,

First off, I think I found the problem. Looking at the Firewall rules I 
see that the ports are being managed by application and I see both R5 and R6 
are listed twice. What I did not notice right off was that the action for R6 
was set to Blocked. I have changed it to Allow but will not be able to test it 
for several hours. 4D must be creating these rules during installation as no 
one here did it. Wonder why it set the action to blocked. The open ports column 
for both versions is set to Any.

Someone else pointed out, I think off list, that I would have a 
conflict with 19814. So I did a bit of testing with netstat. Based on the 
netstat results I don’t believe that 4D is necessarily grabbing one below and 
one above the set application port.  

netstat listed the following ports with the ports the way I had 
them set on the 2 servers. The ports listed are the only 4D Server ports listed 
as listening…

(http server is not running)
1919 -   SQL Server port (listening even though it is not 
running)
19813 - Server 1 Application port 
19814 - Server 1 DB4D Port

9000 -   Server 2 http port 
19812 - SQL Server port  (listening even though it is not 
running)
19815 - Server 2 Application port
19816 - Server 2 DB4D port

Maybe Server 2 is continuing to listen on 19814 even though the 
SQL Server port is set 19812, and netstat is listing conflicted ports only 
once, but I don’t think so. Also if one below the application is in fact being 
grabbed by 4D, then 19812 would also be in conflict. I think my next netstat 
run confirms that 4D is not grabbing one below, only one above.

Just to be sure, I bumped Server 2 ports up 1 and changed it’s 
SQL Server Port as well to 1918 then redid the netstat…

(http server is not running)
1919 -   SQL Server port (listening even though it is not 
running)
19813 - Server 1 Application port
19814 - Server 1 DB4D

1918 -   SQL Server port (listening even though it is not 
running)
9000 -   Server 2 http port (Microsoft SQL Server is listening 
on port 80)
19816 - Server 2 Application port
19817 - Server 2 DB4D

Notice that there is no 19815 listed which is what I expected 
to see if in fact 4D was always grabbing the port one below the application 
port.

Like I said, I am in unfamiliar territory when it comes to networking 
especially on windows, but what I see using ntstat seems to make some sense.

Thanks for pointing out the possible conflict with 19814.

John



> On Apr 13, 2018, at 4:42 AM, Janet Jonas via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> When you specify port 19813, 4D is using 19812-19814. When you specify 19815, 
> 4D uses 19814-19816. The 2 4Ds may be clashing on port 19814.
> 
> JJ
> 
> 
>> 
>> Message: 12
>> Date: Thu, 12 Apr 2018 15:38:59 -1000
>> From: John Baughman <john...@hawaii.rr.com>
>> To: 4D iNug Technical <4d_tech@lists.4d.com>
>> Subject: Re: Clients cannot see v16 R6 on windows server
>> Message-ID: <b5748c33-c7f4-4a99-a2c3-a6d96f8b1...@hawaii.rr.com>
>> Content-Type: text/plain;charset=utf-8
>> 
>> Maybe I was not clear about the problem. 
>> 
>> In R5 the clients can connect to the servers. The server with 19813 shows in 
>> Available as expected, and connections with custom IPs to either sever work 
>> just fine.
>> In R6 the clients cannot connect to the servers at all, nothing is in the 
>> available tab and custom IPs do not work.
>> 
>>> On Apr 12, 2018, at 3:32 PM, John Baughman <john...@hawaii.rr.com> wrote:
>>> 
>>> I am not a very smart network guy, but if the R5 clients can connect to to 
>>> the R5 server:19815, wouldn’t the UDP port be open? Otherwise would not R5 
>>> have the same problem that R6 is having. What am I not understanding here.
>>> 
>>> John
>>> 
>>>> On Apr 12, 2018, at 3:12 PM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com 
>>>> <mailto:4d_tech@lists.4d.com>> wrote:
>>>> 
>>>> John,
>>>> 
>>>> Have you opened the UDP ports for 19815?
>>>> 
>>>> Randy Engle, Director
>>>> XC2 Software LLC – XC2LIVE!
>>>> 
>>>> 
>>>> I am trying to update a client running windows 2008 Server R2 Enterprise 
>>>> Service Pack 1 to R6. 
>>>> 
>>>> R5 works just fine, but in R6 clients cannot see the server. they are 
>

Re: Clients cannot see v16 R6 on windows server

[Janet Jonas via 4D_Tech]

When you specify port 19813, 4D is using 19812-19814. When you specify 19815, 
4D uses 19814-19816. The 2 4Ds may be clashing on port 19814.

JJ


> 
> Message: 12
> Date: Thu, 12 Apr 2018 15:38:59 -1000
> From: John Baughman <john...@hawaii.rr.com>
> To: 4D iNug Technical <4d_tech@lists.4d.com>
> Subject: Re: Clients cannot see v16 R6 on windows server
> Message-ID: <b5748c33-c7f4-4a99-a2c3-a6d96f8b1...@hawaii.rr.com>
> Content-Type: text/plain; charset=utf-8
> 
> Maybe I was not clear about the problem. 
> 
> In R5 the clients can connect to the servers. The server with 19813 shows in 
> Available as expected, and connections with custom IPs to either sever work 
> just fine.
> In R6 the clients cannot connect to the servers at all, nothing is in the 
> available tab and custom IPs do not work.
> 
>> On Apr 12, 2018, at 3:32 PM, John Baughman <john...@hawaii.rr.com> wrote:
>> 
>> I am not a very smart network guy, but if the R5 clients can connect to to 
>> the R5 server:19815, wouldn’t the UDP port be open? Otherwise would not R5 
>> have the same problem that R6 is having. What am I not understanding here.
>> 
>> John
>> 
>>> On Apr 12, 2018, at 3:12 PM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com 
>>> <mailto:4d_tech@lists.4d.com>> wrote:
>>> 
>>> John,
>>> 
>>> Have you opened the UDP ports for 19815?
>>> 
>>> Randy Engle, Director
>>> XC2 Software LLC – XC2LIVE!
>>> 
>>> 
>>> I am trying to update a client running windows 2008 Server R2 Enterprise 
>>> Service Pack 1 to R6. 
>>> 
>>> R5 works just fine, but in R6 clients cannot see the server. they are 
>>> connecting using custom addresses as there are 2 servers listening on 
>>> different ports, 19815 and 19813. In R5 19813 showa up in available and 
>>> they can connect to both using custom IP:port.
>>> 
>>> I have put them back to R5 until I can figure this out. Any ideas?
>>> 
>>> John
>>> 
>>> 
>>> John Baughman
>>> Kailua, Hawaii
>>> (808) 262-0328
>>> john...@hawaii.rr.com <mailto:john...@hawaii.rr.com>
>>> 
>>> 
>>> 
>>> **
>>> 4D Internet Users Group (4D iNUG)
>>> FAQ:  http://lists.4d.com/faqnug.html
>>> Archive:  http://lists.4d.com/archives.html
>>> Options: https://lists.4d.com/mailman/options/4d_tech
>>> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
>>> **
>> 
>> John Baughman
>> Kailua, Hawaii
>> (808) 262-0328
>> john...@hawaii.rr.com <mailto:john...@hawaii.rr.com>
>> 
>> 
>> 
>> 
>> 
> 
> John Baughman
> Kailua, Hawaii
> (808) 262-0328
> john...@hawaii.rr.com
> 
> 
> 
> 
> 
> 
> 
> --
> 
> Subject: Digest Footer
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **
> 
> --
> 
> End of 4D_Tech Digest, Vol 131, Issue 21
> 

**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[Paul Dennis via 4D_Tech]

Resolved I was missing the 4D extensions folder in the built client



--
Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[Paul Dennis via 4D_Tech]

I am getting something similar since I update to R6 this week. The
EnginedServer.4Dlink file is not being recognised on windows 7 but it ok on
win8. My 2 win7 clients always display the connect dialog but no servers are
present. They connect okay if I manually enter the details in custom. And
when I do this the EnginedServer.4Dlink is updated however restarting the
client and it does not connect automatically as was previously the case. I'm
going to post this to 4d Forum
Paul



--
Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html
**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[John Baughman via 4D_Tech]

Maybe I was not clear about the problem. 

In R5 the clients can connect to the servers. The server with 19813 shows in 
Available as expected, and connections with custom IPs to either sever work 
just fine.
In R6 the clients cannot connect to the servers at all, nothing is in the 
available tab and custom IPs do not work.

> On Apr 12, 2018, at 3:32 PM, John Baughman  wrote:
> 
> I am not a very smart network guy, but if the R5 clients can connect to to 
> the R5 server:19815, wouldn’t the UDP port be open? Otherwise would not R5 
> have the same problem that R6 is having. What am I not understanding here.
> 
> John
> 
>> On Apr 12, 2018, at 3:12 PM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com 
>> > wrote:
>> 
>> John,
>> 
>> Have you opened the UDP ports for 19815?
>> 
>> Randy Engle, Director
>> XC2 Software LLC – XC2LIVE!
>> 
>> 
>> I am trying to update a client running windows 2008 Server R2 Enterprise 
>> Service Pack 1 to R6. 
>> 
>> R5 works just fine, but in R6 clients cannot see the server. they are 
>> connecting using custom addresses as there are 2 servers listening on 
>> different ports, 19815 and 19813. In R5 19813 showa up in available and they 
>> can connect to both using custom IP:port.
>> 
>> I have put them back to R5 until I can figure this out. Any ideas?
>> 
>> John
>> 
>> 
>> John Baughman
>> Kailua, Hawaii
>> (808) 262-0328
>> john...@hawaii.rr.com 
>> 
>> 
>> 
>> **
>> 4D Internet Users Group (4D iNUG)
>> FAQ:  http://lists.4d.com/faqnug.html
>> Archive:  http://lists.4d.com/archives.html
>> Options: https://lists.4d.com/mailman/options/4d_tech
>> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
>> **
> 
> John Baughman
> Kailua, Hawaii
> (808) 262-0328
> john...@hawaii.rr.com 
> 
> 
> 
> 
> 

John Baughman
Kailua, Hawaii
(808) 262-0328
john...@hawaii.rr.com





**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
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: Clients cannot see v16 R6 on windows server

[John Baughman via 4D_Tech]

I am not a very smart network guy, but if the R5 clients can connect to to the 
R5 server:19815, wouldn’t the UDP port be open? Otherwise would not R5 have the 
same problem that R6 is having. What am I not understanding here.

John

> On Apr 12, 2018, at 3:12 PM, Randy Engle via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> 
> John,
> 
> Have you opened the UDP ports for 19815?
> 
> Randy Engle, Director
> XC2 Software LLC – XC2LIVE!
> 
> 
> I am trying to update a client running windows 2008 Server R2 Enterprise 
> Service Pack 1 to R6. 
> 
> R5 works just fine, but in R6 clients cannot see the server. they are 
> connecting using custom addresses as there are 2 servers listening on 
> different ports, 19815 and 19813. In R5 19813 showa up in available and they 
> can connect to both using custom IP:port.
> 
> I have put them back to R5 until I can figure this out. Any ideas?
> 
> John
> 
> 
> John Baughman
> Kailua, Hawaii
> (808) 262-0328
> john...@hawaii.rr.com
> 
> 
> 
> **
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **

John Baughman
Kailua, Hawaii
(808) 262-0328
john...@hawaii.rr.com





**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

Clients cannot see v16 R6 on windows server

[John Baughman via 4D_Tech]

I am trying to update a client running windows 2008 Server R2 Enterprise 
Service Pack 1 to R6. 

R5 works just fine, but in R6 clients cannot see the server. they are 
connecting using custom addresses as there are 2 servers listening on different 
ports, 19815 and 19813. In R5 19813 showa up in available and they can connect 
to both using custom IP:port.

I have put them back to R5 until I can figure this out. Any ideas?

John


John Baughman
Kailua, Hawaii
(808) 262-0328
john...@hawaii.rr.com





**
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**