Hi all, I implemented a csm-s in bridge mode in an existing environment for http loadbalancing. Everything is working fine until a client requests a reporting feature at the webservers. The webserver starts a java application which opens a connection...
Hi all, I have a CSM-S module in a Cat65xx system and working on my design. The MSFC is on the client side and the server and client side at the CSM should be in the same subnet (so bridge mode!?). How can I integrate the SSL daughtercard (DC)? Can I...
Hello community, for a customer we changed the user authentication in the VPN client from a password based to a certificate based solution. For this change we needed an update of the VPN client version from 4.04. to 4.7. to use the new introduced cer...
Hi all,I use VPN client 4.0.5(D) and try to attempt a connection with certificates to a Conc.3000. If I start the connection I get errors in the log window (see below).The error messages starts with log entry 84 with Failed to sign hash: ...Does some...
Hello,I have a VPN 3060 concentrator and a mixed VPN client environment (NT with client 2.5.2, XP with client 4.0.3 and some more). After an update of the concentrator to the actual version 4.1.7F the old clients version (2.5.2) can not longer estab...
Hi Gilles,many thanks for your advice. The vserver matching vlan 70 works perfect now. The question is, why I have to configure a vserver just for vlan 70. Shouldn't the other solution work either??? Anyway, tanks a lot for your help :o)
Hi Gilles, the missing policy is just an copy and paste error by myself. In the real config, the policy is applied to the vserver. Anyway I will try your suggestion and will feed back if this works. Many thanks for your answer, Thomas.
Jon, yep that is exactly what I'm thinking too. I have to check with the customer. Will let you know if I find it out. Many thanks for your time,Thomas.
Hi, thanks for your quick answer.Maybe I'm reading something wrong but I can't see the difference between our configs!?Ooooo, during the reading I see my mistake. In my attachment is the failure - I didn't changed the 172.28.147.133 to 1.1.147.133 ;o...
Thanks both of you for your replay. Jon, I planned exactly the same configuration like you. Last week I configured the csm and the dc in this way but got a strange result (my confs as attachments - IP changed to 1.1): A client starts with a connect t...
