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