I«d like to know if the Juniper have a docummentation about problems using VPN SSL in a Workstation using a Virtual OS.
I can«t make the SAM works in a VM.
could you give us some more info?
As I understand it now, you're running a VMware VM under Workstation (Linux, Windows, ...?) and the OS in the VM has trouble running SAM (WSAM, JSAM?).
And what exactly is the problem? Do you have a e.g. have WSAM destination that you cannot reach, although you have configured it in the SA?
Thanks in advance,
Yes I have a workstation using Windows XP (Virtual) , and nothing that I use through the Secure Application manager works. I can«t see the access log.
Hi Ricardo, thanks for clearing that up.
- create a role that is assigned to the user and allows usage of the WSAM?
- create a resource profile that allows acces to certain destinations and/or access by certain applications? OR
- create a resource policy that allows access?
Personally, I prefer the profiles as they are easily configurable (Resource Profile -> SAM -> WSAM Destinations)
And before I forget... can you reach the SA by using the https://sa.domain.tld/ ?
And can you reach the destination from the SA itself? (Troubleshooting -> Tools -> ping destination)
Best of luck!
Alex, Thank you for your fast answer
I tested the same rules using other workstation and work well.
The problem is only when I use Virtual Machines.
Thats why my question.
I've a little troubling connecting myself, but you should try this knowledge base article if it's available:
Im using a 3G modem (USB), but the machine that' s conneccting in this modem is the Virtual Machine, is not the fisical machine.
We make logins and access the Webbookmarks, but is not possible to use the applications (with SAM).
Ricardo NIlsen Moreno
JNCIA-FW / JNCIA-SSL / ITIL V3 Foundations
recap, just to make sure:
- the VM has direct access to the USB port (forwarded from the host OS) and has 3G drivers and software installed
- 3G looks working fine (bookmarks etc.) and I'm assuming WSAM is not crashing,
- the host OS or other physical machines are ableto connect and use WSAM as it should be.
So: WSAM simply cannot reach its destinations.
Did you try connecting 3G modem to another physical system and connect WSAM?
Possibly, you may have problems with overlapping IPs:
- assume your destination is server.domain.local on 10.1.1.1/8
- and 3G address is e.g. 10.0.0.25/8
Your DNS probably resolved fine but WSAM is trying to connect to the the IP ont the 3G subnet, instead of the remote destination.
Do you have the 3G card in PPP or Ethernet mode? I've seen better results whem these cards were put into Ethernet mode.
I don't see why this wouldnt work. I've used a 3G modem connected to a VMware system in the past, and it worked fine.