Hi,
I have 1 customer with 4 servers. I connect with SonicWALL VPN client to that customer. I have setup the VPN connection on all 4 servers as the following:
Open: Connect if unable to ping
Close: On session close
Type: SonicWaLL Global VPN
VPN Group: <customer name> (the same on all 4 connections)
When I connect first to server1, the vpn connection is made and after that the rdp connection. Then I connect to server2, it connects to the desktop immidately.
Now, when I close the connection to server1, if immidiately closes the vpn connection, while the connection to server2 is still open.
Am I doing something wrong in my settings, or is this not working?
Kind regards,
Ray
edited by Rayman on 6/3/2011
Hi,
No this should work fine. There must something when you close the connection. How do you close it? Is it an embedded RDP?
David Hervieux
I right click the connection (server1) and choose close session. After this the VPN connection disconnects. Server2 is still connected.
I use embedded rdp yes.
Ray
Hi,
If I send you a special version with some debug message, would you do a test for me?
David Hervieux
Hi David
We are having the same issue but have the machines pointing to an existing VPN session which is just using the Microsoft VPN
Gaz
Oh,
Maybe it's the problem, you must enter in each RDP session the VPN group name and not just link it, is it the case?
David Hervieux
Hi David,
Of Course I'm willing to test, no problem.
I have entered in each session the same VPN Group name as the VPN name.
Kind regards,
Ray
Hi David,
Do you still need me to test something?
Kind regards,
Ray
What was the result when your entered the same vpn group name in each session?
David Hervieux
I did allready enter the same group vpn in each session....
VPN Group name for each session is the same as the vpn connection name for each session. I have tried to change the vpn group name to something else for each session, but still same result.
Ray
edited by Rayman on 6/9/2011
Do you mind to try a special version with debug messages?
David Hervieux
No problem!
Can you try this version and do a simple test (open multi connection for the same vpn group) and give me the message (you can do ctrl-v to copy the message)
http://remotedesktopmanager.com/download/Setup.RemoteDesktopManager.6.1.4.0a.exe
David Hervieux
Hi,
It crashes on startup:
Standard Edition 6.1.4.0
InvalidOperationException - Kan geen tijdelijke klasse genereren (resultaat=1).
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
error CS0119: bool is een type, wat ongeldig is in de gegeven context
bij System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)
bij System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)
bij System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)
bij System.Xml.Serialization.XmlSerializer.GenerateTempAssembly(XmlMapping xmlMapping, Type type, String defaultNamespace)
bij System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
bij System.Xml.Serialization.XmlSerializer..ctor(Type type)
bij Devolutions.RemoteDesktopManager.Managers.SerializationManager.GetSerializer(Type type)
bij Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToString(Object value)
bij Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToFile(String fileName, Object value)
bij Devolutions.RemoteDesktopManager.Managers.OptionManager.DoSaveOptionsObject(String fileName, String backupFileName, Object data)
bij Devolutions.RemoteDesktopManager.Managers.OptionManager.SaveOptions()
bij Devolutions.RemoteDesktopManager.Managers.OptionManager.DoLoadOption()
bij Devolutions.RemoteDesktopManager.Managers.OptionManager.LoadOptions()
bij Devolutions.RemoteDesktopManager.Managers.ApplicationManager.InitializePhaseOne(String[] args, ApplicationDescriptor applicationDescriptor)
bij Devolutions.RemoteDesktopManager.Program.Main(String[] args)
Sorry, it's now fixed and updated
David Hervieux
Hi,
On start of the first session, I get this message:
---------------------------
---------------------------
New VPN group createdKlomp (VPN)
---------------------------
OK
---------------------------
On start of the second session, with the same Group VPN I get no message at all, it connects fine.
Now, I disconnect the first session (right click session, disconnect).
I get this message:
---------------------------
---------------------------
Closing By Result VPN:Klomp (VPN)
---------------------------
OK
The second session now locks up, because the vpn connection is disabled.
Kind regards,
Ray
---------------------------
So, it's appear that the second connection does not flag the group. I thought of something, is it possible that it's only open it if it's unable to ping?
David Hervieux
Yes, that's possible. I have set all session to connect if unable to ping. This way, when I start a random session it connects my vpn.
Ray
I think that's the problem. RDM does not invoke the VPN architecture, so the VPN group is not flagged. Can you do the test for one session just to confirm? If it works, I will be able to find out a solution.
David Hervieux
Hi,
Youre right, that's the problem. If I setup the session to allways connect (and not connect if unable to ping), the first session connects fine. When I open the second session it tries to open the vpn sonicwall connection again, this results in a broken and then re-established connection.
After that, I'm connected to 2 servers. When I disconnect the first session, the vpn does NOT disconnect. It will disconnect fine after the second session is disconnected.
I really hope that it is at all possible to get this working it set to connect if unable to ping (or not try to connect again when set to allways connect..).
Thank you for your trouble.
Kind regards,
Ray
Excellent, I just wanted to confirm the problem. I will be able to fix this, I pretty sure it's a simple modification in our code.
David Hervieux
Great news, if you need me to test again, that's fine.
Ray
Anything new on this?
Have yoy tried the beta?
David Hervieux
Hi,
I missed the beta completely :).
It's working on 6.4.8.0 and 6.5.0.0. You're a genius!
Kind regards,
Ray