No warning on open sessions
We are having issues with some of our connections. These connections have VPNs that kill our local network for various reason. What happens is:
* Click Open Session
* VPN Connects and writes a "Open VPN" log entry
* VPN waiting period pop-up occurs and during this wait, the VPN fully connects
* Warning pops up to say that cannot connect to database and confirm that we are VPNed out
* RDP session opens, but no "Open Session" log entry is written, as we now cannot talk to the DB
* At this stage, anyone else can connect to the same connection, and they receive no warning about currently being in use as the session log entry didn't occur
* Once we finish and close the session, there is no Open Session log entry to update, and we can't access the database at this stage to update it anyway
* VPN Closes, and Close VPN log entry is written.
Alternatively, if the VPN waiting popup finishes prior to the VPN connection being finalised, then we do get the Open Session log entry being written, but when we close the session, the Open Session log entry does NOT get updated with the End Date/Time so other users will get a warning that someone is already connected when they are not.
Cheers,
Danny
All Comments (3)
Hi Danny,
I understand your issue but I don't have any solution. Do you have an idea?
David Hervieux
Yep, I do. It would be good if the opening the session wrote both the Open VPN and Open Session log entries at the same time. Once the VPN was opened and the session actually opened, it could update the Open Session's start date if necessary.
Then when you close the session, we either need some sort of queue so that we keep trying to insert the end date for the Open Session until it works, or when the Close VPN log entry gets written it can also check to see if the Open Session is still open, and close it if it is (sort of in the same way that connecting over the top of an active Open Session entry writes the End Date on the Open Session getting clobbered.
It would probably be easier to add the smarts to the opening and closing of the VPN rather than trying to implement a queue that gets retried until successful.
Does that make sense?
Hi Danny,
I have entered a feature request with your suggestion. I think it could work.
David Hervieux