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
**********************************************************************

Reply via email to