Posted by Tom Fulton on March 06, 2018 at 09:25:04:
A large end-user of ours is one of the very old ones - Qbox to Novel to Windows network. There earliest conversion off the Qbox to PC network involved the operations manager assigning routable static IPs. They are currently replacing servers, going to a VMWare virtualized environment and re-configuring for proper internal IP addresses. So, there Comet server that has always been communicating on a routable address 184.108.40.206 now has a second card communicating on 10.10.0.4. Their ini file is pointing to the 220.127.116.11 address. They have a mix of user PCs. They are using DHCP for the internal addressing - we've had discussions on this and they may be converted to static, but that's besides the point. Their issue is this - the Win10 user workstations now configured on the internal DHCP run Comet with no issue. The Win 7 PCs drop their Comet connections. It may be in 5 minutes, 40 minutes or a couple of hours, but they drop. I will be upgrading Comet Services ( from 16.0 to 18.0 ) and their version of Comet which is relatively new. I am in the process of assembling logs and wireshark reports. Any ideas right off the bat?
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.