I would like to hear from anyone using v16 in a WAN environment.

Frankly every time I have tried out v16 or for that matter any v15 R release I 
have been shocked at how poor the network connection stability has been.

It seems to stem from the new networking layer and certainly it seems to be 
more stable when the legacy  networking checkbox is checked but frankly it 
scared me off being an early adopter.

I now have a little time to look at this again but wanted to gather some 
information from the community before I proceed with more testing.

Are there any recommended settings and configurations I should look at?  Some 
background:

All our servers are running on Windows Servers mixture of 2008 and 2012.
- 90% are dedicated hosted servers with a few in-house servers
- Multiple databases run on our hosted servers on separate ports
- WAN connection for each server is dedicated 100Mb
- Client connections vary from domestic grade ADSL, Virgin Cable and Leased 
lines
- Clients are a mixture of platforms 90% Windows 7, 8 & 10 and 10% OSX

We have occasionally had issues with certain clients broadband connections but 
all in all v15 stability has been good.

Issues I was seeing with v16 were:
- Client connection timeout errors
- Clients which had logged off, showing as connected to the server

Am I missing some key documentation in this area or maybe some new networking 
layer tech note?

Regards,  Dougie
________________________________________________________

telekinetix Limited- J. Douglas Cryer
Phone : 01234 761759  Mobile : 07973 675 218
2nd Floor Broadway House, 4-6 The Broadway, Bedford MK40 2TE
Email : [email protected] <mailto:[email protected]>  Web : 
http://www.telekinetix.com <http://www.telekinetix.com/>
________________________________________________________
 

**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to