Labview crashes remote access

i am trying to connect to a vi that I created using remote panels. I am able to connect to very simple panels, but not the vi that I created.
Labview just closes, giving the error "A problem occured with Labview 8.0.1 development system etc etc do you want to send the error report to microsoft."
The labview that crashs is on the client machine. Both machines have the 8.0.1 development system on them. I uninstalled and reinstalled the development system on the client computer but I still received the same error. I also reinstalled the 8.0.1 runtime engine.
I made sure that all of the same toolkits are installed. I recomplied the national instruments folder twice (that was a waste of 6 hours ).
The vi that I am running on the server machine does not have any errors and runs perfectly.
Usually the vi will start loadiung and then crash when it tries loading the NI_matrix.lv.lib (or at least that is the last vi that I see it loading). I tried coping the library from the server to the client machine, but that did not help.
Any hints on how to connect to the remote panel with out crashing
Kenny
Kenny

I was able to access the vi through internet explorer, just not the development evironment.
I can post the code, but it is very large program and I have third party drivers in it which I call immediatly, so unless you have the daq units connected to the compiuter, you will get an error that it cannot read from the devices. Also, I am saving to a database (.udl/.dsn) file. Do you think that this could be the reason??
Kenny
Kenny

Similar Messages

Labview crashes with access violation(0xc00000050at EIP=0x7c8219a6

when i poen my project in labview ,it crashes with "access violation(0xc00000050at EIP=0x7c8219a6.why is this happening?how can i open my project?

Probably nothing to do with it but I had some dodgy memory, and windows would complain that there was an error to do with that exact memory location: c0000005

Remote access in LabVIEW

Recently, I received the Compact DAQ that I bought. The CDAQ is connected to a remote computer that does not have labview, but remote system does have MAX and LV run time engine. I am trying to access that remote CDAQ on my local machine through LabVIEW, but it doesn't work.
For my GPIB and serial instrument on the remote sysem, I can access them through VISA server. I can see all these instrument on my local machine, except for the CDAQ. I thought I could see the CDAQ on my local machine through VISA server, similar to how I see the GPIB and serial instrument on my remote machine. I guess this is not the case.
All I want to do is to access my CDAQ that is connected to a remote computer on my local machine. What are the different ways to achieve this?
Kudos and Accepted as Solution are welcome!

Can you give me a little more information on your setup. Which cDAQ chassis is in question?
If I understand you correctly, you want to connect to the cDAQ using another computer, do you have DAQmx installed on the remote computer. Again, how is the cDAQ connected to your system?
Regards,
A. Zaatari
National Instruments
Applications Engineer

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

LabVIEW Crashes while closing the VI

Hi all,
I am experiencing a labVIEW crash everytime I close my VI after running it. what the VI is doing is, it communicates with an opal kelly board through the okFrontPanel.dll and reads some data from it and displays it in the front panel. The vi runs fine and I get the results as well. But after stopping the vi, when i try to close the vi, labVIEW crashes.
Has anyone faced such an issue? I would appreciate if anyone can help me fix this issue.
Thanks and regards,
Nitz
(P.S: I am not able to upload the code due to restrictions and also its a quite lengthy code to create a sample vi to replicate the scenario)
Solved!
Go to Solution.

A crash is usually an indication that something inside the DLL is touching an area of memory which it shouldn't be touching. The fact that the VI runs fine is incidental. It seems that in this case the DLL touches something which is only affected when LV needs it when closing the VI. I think the only thing you can do about it on the LV side is make sure you allocate large enough buffers for variable length parameters the DLL uses. I'm assuming you don't have access to the source code of the DLL?
Try to take over the world!

LabVIEW crash on startup

splash screen appears briefly, then labview crashes. I've tried a repair using the CDs but the problem persists. PXI-8110 dual-boot, I have windows and LV2011 on C:\ and Real-Time OS on D:\ I've recently been booting to RT by changing the BIOS settings, today I changed the BIOS back to boot windows, but now LabVIEW is broken. lvlog.txt copied below. What would you recommend I try next ? I'm guessing my use of the RT OS has upset something.
#Date: 23 Dec 2011 10:46:52
#OSName: Windows Vista (TM) Business
#OSVers: 6.0
#OSBuild: 6000
#AppName: LabVIEW
#Version: 11.0 32-bit
#AppKind: FDS
#AppModDate: 06/22/2011 11:12 GMT
#LabVIEW Base Address: 0x00400000
23/12/2011 10:46:55.541
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 4d84c03d-143c-4705-8479-8fae2dedb5f9
ExceptionCode: 0xC06D007E
0x01AA0EC9 - LabVIEW <unknown> + 0
0x01AA1408 - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x76E59F8E - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
Solved!
Go to Solution.

Hello,
I am unsure as to why using the RT partition was to break LabVIEW in windows unless you ran some code which made changes to the LV dependent files on the other partition. Were you accessing the C partition from the RTOS?
You mentioned you tried a repair, have you tried a complete re-install of LabVIEW in windows?
I would suggest that you did a complete re-install of all NI software. I have attached instructions and a copy of 'msiBlast' so you can do a nice clean re-install.
Let me know how you get on with this, or if you have already tried a uninstall/reinstall.
Kind Regards,
Nick C.
Cardiff University

Why does MAX say %22The remote access list on this system is blank%22%3F

I am building and deploying a real-time data acquisition/control system using LabVIEW RT (2012 SP1) and a PXI controller. I've tested my software, and it runs fine, now that I've figured out how to build stand-alone executables for both the Host and RT Target systems.
Due to a bug on the RT side (which I hope I've now fixed), I needed to "rebuild" my PXI Controller, reinstall LabVIEW RT and related software, and reconfigure all of the Tasks in MAX (version 5.5). To save the Configuration (and simplify reconfiguring the Tasks and Channels), I tried to export the configuration using the Configuration Export Wizard in MAX. However, there were some (minor?) inconsistencies in some of the devices (such as NI-488.2) between the Host and Remote systems that generated some errors. I was able to correct this by asking MAX to do a Reset Configuration Data on the Host, and those problems went away.
After exporting the NI Configuration Export File for my PXI, I decided to use MAX to Create Reports on both my Host and Remote PXI systems. While reviewing the PXI's report, I noticed that the last entry in the report, called "Security", reads as follows:
"The remote access list on this system is blank. This means that no remote system has access to this system."
What does this mean? Where is the "remote access list on this system", and how is it maintained? Note that I haven't (yet) tried deploying my (formerly-working) Project to this (rebuilt) Controller, but I haven't made changes in LabVIEW, itself.
If I look at the Properties of the RT Target in Project, the VI Server properties (still) show TCP/IP enabled (port 3363) with Machine Access given to "*" (all machines) and, similarly, all Exported VIs allowed access.
Am I missing something? Can I safely ignore the above Security report entry generated by MAX, or is there a hidden setting I need to find and change?
Bob Schor
Solved!
Go to Solution.

Norbert_B wrote:
Bob,
i am not sure about your situation, but it seems to me that it is connected to "Security" Settings. Please refer to the help in MAX, topic "Logging into your System".
Norbert
I agree, but I've never heard about "Security Settings" in MAX. When I first read your note, I went looking and couldn't find "Logging into your System". I came back a day later, was going to write a "There is not such topic!" reply, but fortunately I looked again, and found it. I suspect the reason I never ran into this was that my controllers were all using older BIOSes -- I'd just "rebuilt" this controller, including updating its BIOS, and ran into the Login prompt for the first time ...
Thanks for pointing me in (what turns out to be) the right direction!
BS

Why does LabView crash when unloading my DLL (reentrant calls)?

I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine. All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
OR
Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
OR
Your DLL is only called from one, non-reentrant VI
OR
Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
Hopefully this information can help you out in some way.
J.R. Allen

LabVIEW crashes when trying to use VISA controls

When I try and place VISA controls onto the front panel or a constant into the block diagram LabVIEW crashes and says that LabVIEW.exe caused an error and that LabVIEW must be restarted. Is there some setup required in order to use VISA or is there something wrong with LabVIEW?

I saw something that sounded exactly like this myself on two PC that where running some kind of "Eveidence Eleminator" software that got its hooks into everything.
I never did get it running on those two machines.
I saw something similar when trying to access a serial port that was hanging off of a USB gizmo.
We downloaded the latest and greatest version of the driver for the USB to serail device
and
upadted NI-VISA to the latest and greatest.
Then everything worked.
It was just like you mentioned, LV looks fine right up until you drop a VISA control.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

LabVIEW crashes when I paste to the diagram

When I paste a part of one diagram to another, Labview 7 crashes with "The thread 'Win32 Thread' (0x910) has exited with code 0 (0x0).
Unhandled exception at 0x0084d46e in LabVIEW.exe: 0xC0000005: Access violation reading location 0x8168592c."

In any particular order? What about NI-DAC? Reinstalling LabView is a pain, as I have the NI-CAN pack I would have to re-install.
There is another machine that has LabView 7 on it. When saving a VI, I have seen a message "Bad Patch", and then it will not run the code. I find if I edit the diagram, I can then get it to run the code.
A screen shot of the code? It would require many screen shots of the code.
For now, I intend to be carefull about saves and copies.

Remote access to multisim

Hi all,
Is there any way to invoke multisim from Labview? Or is there any way to access Multisim remotely? Because Labview has a webserver capability, so we are wondering if we can remote access multisim from Labview.
Thank you!!

One of the new features in Multisim v10 is that it has an ActiveX API that you can call to automate Multisim. We are in the process of creating all the documentation that a user might need in order to understand how to use it. Once we're finished (summer) we will make all the information available on the Technical Library: http://zone.ni.com/devzone/cda/tut/p/id/5579
Nestor
National Instruments

LabVIEW crashes on a system with LV2009SP1 and LV2012 installed.

If I launch LV2009SP1 and close it with or without doing any operation, it crashes with nixnet.dll.
If I do the same with LV2012, it crashes saying "Exception : Access violation (0xC0000005) at EIP=0x5600AE01"
What's wrong with my installations?

Hello iCat,
Thanks for posting at NI forums! Have any of these versions ever worked? Do you have the X-net driver installed? What is your operating system (32/64 bits)? When LabVIEW crashes, it should generate an error log file, is it possible for you to post it? I’m linking some information about the location for that file. Have you tried uninstalling and reinstalling the software?
KB Where is the Error Log File Saved After a LabVIEW Crash?
http://digital.ni.com/public.nsf/allkb/7E9EBE4CA3B6DCE786257633005E7121?OpenDocument
Best Regards,
Alina M

Releasing hardware resources on LabVIEW crash

Hi all,
I am using PXI chassis with many DAQ cards, mux, ARINC,RS-422 etc.
It is a common problem that in the event of LabVIEW crash, the hardware resources are not released and the system should be restarted to access the resources again.
Scenario:
LV1 is the main LabVIEW program that opens the harware resources.
LV2 is a separate LabVIEW program (a utility) runs as a separate process.
Now if the LV1 opened few references to the hardware devices and shares these references to the LV2.
In the event of LV1 process crash, LV2 still runs; can the LV2 process close the open references?
Can LV2 process release the resources opened by LV1?

It really depends a little. Even XP was fairly good about releasing normal OS objects such as all kind of handles (files, synchronizationo objects, GDI objects, etc). But once kernel resources get involved things get a lot more trickier and I really doubt there is an universal way for an OS to make sure even such resources get properly closed on process termination without a very intensive, expensive and performance hungry bookkeeping. And I don't see the average user wanting to pay that price in performance all the time for the incidential case when the system crashes.
So in general it is safer to restart the OS after a crash even if the system seems to work fine, This is definitely true if your application has been involved in some way with directly invoking kernel drivers, which any application that interfaces to NI (and other manufacturers) hardware basically does. I'm not saying that NI couldn't possibly improve that in the user space part of those drivers somehow. However the effort for that could be pretty expensive and the perceived advantage would be small for most end users.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Remote Access VPN Clients Cannot Access inside LAN

I have been asked to set up remote access VPN on an ASA 5505 that I previously had no invlovement with. I have set it up the VPN using the wizard, they way I normally do, but the clients have no access to anything in the inside subnet, not even the inside interface IP address of the ASA. Thay can ping each other. The remote access policy below that I am working on is labeled VPNPHONE, address pool 172.16.20.1-10. I do not need split tunneling to be enabled. The active WAN interface is the one labeled outside_cable.
: Saved
ASA Version 8.2(1)
hostname ASA5505
domain-name default.domain.invalid
enable password eelnBRz68aYSzHyz encrypted
passwd eelnBRz68aYSzHyz encrypted
names
interface Vlan1
nameif inside
security-level 100
ip address 192.168.100.1 255.255.255.0
interface Vlan2
nameif outside
security-level 0
pppoe client vpdn group dataDSL
ip address 76.244.75.57 255.255.255.255 pppoe
interface Vlan3
nameif dmz
security-level 50
ip address 192.168.9.1 255.255.255.0
interface Vlan10
nameif outside_cable
security-level 0
ip address 50.84.96.178 255.255.255.240
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
switchport access vlan 10
interface Ethernet0/2
switchport access vlan 3
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
ftp mode passive
clock timezone CST -6
clock summer-time CDT recurring
dns server-group DefaultDNS
domain-name default.domain.invalid
same-security-traffic permit intra-interface
object-group service Netbios udp
port-object eq 139
port-object eq 445
port-object eq netbios-ns
object-group service Netbios_TCP tcp
port-object eq 445
port-object eq netbios-ssn
object-group network DM_INLINE_NETWORK_1
network-object host 192.168.100.177
network-object host 192.168.100.249
object-group service Web_Services tcp
port-object eq ftp
port-object eq ftp-data
port-object eq www
port-object eq https
object-group network DM_INLINE_NETWORK_10
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_11
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_2
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_3
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_4
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_5
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_6
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_7
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_8
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network DM_INLINE_NETWORK_9
network-object host 192.168.9.10
network-object host 192.168.9.4
object-group network VPN
network-object 192.168.255.0 255.255.255.0
access-list outside_access_in extended permit icmp any host 76.244.75.61
access-list outside_access_in extended permit tcp any host 76.244.75.61 eq ftp
access-list outside_access_in extended permit tcp any host 76.244.75.61 eq ftp-data
access-list outside_access_in extended permit tcp any host 76.244.75.62 eq www
access-list outside_access_in extended permit tcp any host 76.244.75.62 eq https
access-list outside_access_in extended permit tcp any host 76.244.75.59 eq www
access-list outside_access_in extended permit tcp any host 76.244.75.59 eq https
access-list outside_access_in extended permit tcp any host 76.244.75.60 eq www
access-list outside_access_in extended permit tcp any host 76.244.75.60 eq https
access-list outside_access_in extended permit tcp any host 76.244.75.58 eq www
access-list outside_access_in extended permit tcp any host 76.244.75.58 eq https
access-list dmz_access_in remark Quickbooks
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_6 host 192.168.100.5 eq 56719
access-list dmz_access_in remark Quickbooks range
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_7 host 192.168.100.5 range 55333 55337
access-list dmz_access_in extended permit udp object-group DM_INLINE_NETWORK_8 host 192.168.100.5 eq 1434
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_9 host 192.168.100.5 eq 49398
access-list dmz_access_in remark QB
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_10 host 192.168.100.5 eq 8019
access-list dmz_access_in extended permit udp object-group DM_INLINE_NETWORK_2 host 192.168.100.5 eq 2638
access-list dmz_access_in extended permit udp object-group DM_INLINE_NETWORK_11 host 192.168.100.5 object-group Netbios
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_3 host 192.168.100.5 object-group Netbios_TCP
access-list dmz_access_in extended deny ip host 192.168.9.4 host 192.168.100.5 inactive
access-list dmz_access_in extended permit udp object-group DM_INLINE_NETWORK_4 any
access-list dmz_access_in extended permit tcp object-group DM_INLINE_NETWORK_5 any
access-list dmz_access_in remark Printer
access-list dmz_access_in extended permit ip 192.168.9.0 255.255.255.0 object-group DM_INLINE_NETWORK_1
access-list dmz_access_in extended permit tcp 192.168.9.0 255.255.255.0 any object-group Web_Services
access-list dmz_access_in extended permit udp 192.168.9.0 255.255.255.0 any eq domain
access-list dmz_access_in extended permit icmp 192.168.9.0 255.255.255.0 192.168.255.0 255.255.255.0 echo-reply
access-list dmz_access_in extended permit icmp 192.168.9.0 255.255.255.0 192.168.100.0 255.255.255.0 echo-reply log disable
access-list dmz_access_in remark QB probably does not need any udp
access-list dmz_access_in extended permit udp host 192.168.9.4 host 192.168.100.5 eq 55333 inactive
access-list dmz_access_in remark QB included in other rule range
access-list dmz_access_in extended permit tcp host 192.168.9.4 host 192.168.100.5 eq 55333 inactive
access-list dmz_access_in remark May be required for Quickbooks
access-list dmz_access_in extended permit icmp host 192.168.9.4 host 192.168.100.5
access-list CAD_capture extended permit ip host 192.168.9.4 host 192.168.100.5
access-list CAD_capture extended permit ip host 192.168.100.5 host 192.168.9.4
access-list inside_nat0_outbound extended permit ip any 192.168.255.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip any 192.168.255.0 255.255.255.240
access-list inside_nat0_outbound extended permit ip any 172.16.10.0 255.255.255.240
access-list inside_nat0_outbound extended permit ip any 172.16.20.0 255.255.255.240
access-list cad_supplies_RAVPN_splitTunnelAcl standard permit 192.168.100.0 255.255.255.0
access-list cad_supplies_RAVPN_splitTunnelAcl standard permit 192.168.9.0 255.255.255.0
access-list dmz_nat0_outbound extended permit ip any 192.168.255.0 255.255.255.0
access-list outside_cable_access_in extended permit icmp any host 50.84.96.182
access-list outside_cable_access_in extended permit tcp any host 50.84.96.182 eq ftp
access-list outside_cable_access_in extended permit tcp any host 50.84.96.182 eq ftp-data
access-list outside_cable_access_in extended permit tcp any host 50.84.96.183 eq www
access-list outside_cable_access_in extended permit tcp any host 50.84.96.183 eq https
access-list outside_cable_access_in extended permit tcp any host 50.84.96.180 eq www
access-list outside_cable_access_in extended permit tcp any host 50.84.96.180 eq https
access-list outside_cable_access_in extended permit tcp any host 50.84.96.181 eq www
access-list outside_cable_access_in extended permit tcp any host 50.84.96.181 eq https
access-list outside_cable_access_in extended permit tcp any host 50.84.96.179 eq www
access-list outside_cable_access_in extended permit tcp any host 50.84.96.179 eq https
access-list Local_LAN_Access standard permit host 0.0.0.0
access-list vpnusers_spitTunnelACL extended permit ip 192.168.100.0 255.255.255.0 any
access-list nonat-in extended permit ip 192.168.100.0 255.255.255.0 172.16.20.0 255.255.255.0
pager lines 24
logging enable
logging buffered informational
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu dmz 1500
mtu outside_cable 1500
ip local pool VPN_IP_range 192.168.255.1-192.168.255.10 mask 255.255.255.0
ip local pool VPN_Phone 172.16.20.1-172.16.20.10 mask 255.255.255.0
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
nat-control
global (outside) 10 interface
global (outside_cable) 10 interface
nat (inside) 0 access-list nonat-in
nat (inside) 10 0.0.0.0 0.0.0.0
nat (dmz) 0 access-list dmz_nat0_outbound
nat (dmz) 10 0.0.0.0 0.0.0.0
static (inside,outside) 76.244.75.62 192.168.100.25 netmask 255.255.255.255 dns
static (dmz,outside) 76.244.75.61 192.168.9.123 netmask 255.255.255.255 dns
static (dmz,outside) 76.244.75.59 192.168.9.124 netmask 255.255.255.255 dns
static (dmz,outside) 76.244.75.58 192.168.9.4 netmask 255.255.255.255 dns
static (inside,dmz) 192.168.100.0 192.168.100.0 netmask 255.255.255.0
static (dmz,outside) 76.244.75.60 192.168.9.10 netmask 255.255.255.255 dns
static (inside,outside_cable) 50.84.96.183 192.168.100.25 netmask 255.255.255.255 dns
static (dmz,outside_cable) 50.84.96.182 192.168.9.123 netmask 255.255.255.255 dns
static (dmz,outside_cable) 50.84.96.180 192.168.9.124 netmask 255.255.255.255 dns
static (dmz,outside_cable) 50.84.96.179 192.168.9.4 netmask 255.255.255.255 dns
static (dmz,outside_cable) 50.84.96.181 192.168.9.10 netmask 255.255.255.255 dns
access-group outside_access_in in interface outside
access-group dmz_access_in in interface dmz
access-group outside_cable_access_in in interface outside_cable
route outside_cable 0.0.0.0 0.0.0.0 50.84.96.177 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.100.0 255.255.255.0 inside
http 204.107.173.0 255.255.255.0 outside
http 204.107.173.0 255.255.255.0 outside_cable
http 0.0.0.0 0.0.0.0 outside_cable
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set TRANS_ESP_3DES_SHA esp-3des esp-sha-hmac
crypto ipsec transform-set TRANS_ESP_3DES_SHA mode transport
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_cable_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_cable_map interface outside_cable
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto map inside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map inside_map interface inside
crypto isakmp enable inside
crypto isakmp enable outside
crypto isakmp enable outside_cable
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
crypto isakmp policy 30
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
telnet 192.168.100.0 255.255.255.0 inside
telnet timeout 5
ssh 192.168.100.0 255.255.255.0 inside
ssh 204.107.173.0 255.255.255.0 outside
ssh 204.107.173.0 255.255.255.0 outside_cable
ssh 0.0.0.0 0.0.0.0 outside_cable
ssh timeout 15
console timeout 0
vpdn group dataDSL request dialout pppoe
vpdn group dataDSL localname [email protected]
vpdn group dataDSL ppp authentication pap
vpdn username [email protected] password *********
dhcpd address 192.168.100.30-192.168.100.99 inside
dhcpd dns 192.168.100.5 68.94.156.1 interface inside
threat-detection basic-threat
threat-detection statistics port
threat-detection statistics protocol
threat-detection statistics access-list
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
webvpn
group-policy DefaultRAGroup internal
group-policy DefaultRAGroup attributes
dns-server value 192.168.100.5
vpn-tunnel-protocol IPSec l2tp-ipsec
group-policy cad_supplies_RAVPN internal
group-policy cad_supplies_RAVPN attributes
vpn-tunnel-protocol IPSec
split-tunnel-policy tunnelspecified
split-tunnel-network-list value cad_supplies_RAVPN_splitTunnelAcl
group-policy VPNPHONE internal
group-policy VPNPHONE attributes
dns-server value 192.168.100.5
vpn-tunnel-protocol IPSec
split-tunnel-policy excludespecified
split-tunnel-network-list value Local_LAN_Access
client-firewall none
client-access-rule none
username swinc password BlhBNWfh7XoeHcQC encrypted
username swinc attributes
vpn-group-policy cad_supplies_RAVPN
username meredithp password L3lRjzwb7TnwOyZ1 encrypted
username meredithp attributes
vpn-group-policy cad_supplies_RAVPN
service-type remote-access
username ipphone1 password LOjpmeIOshVdCSOU encrypted privilege 0
username ipphone1 attributes
vpn-group-policy VPNPHONE
username ipphone2 password LOjpmeIOshVdCSOU encrypted privilege 0
username ipphone2 attributes
vpn-group-policy VPNPHONE
username ipphone3 password LOjpmeIOshVdCSOU encrypted privilege 0
username ipphone3 attributes
vpn-group-policy VPNPHONE
username oethera password WKJxJq7L6wmktFNt encrypted
username oethera attributes
vpn-group-policy cad_supplies_RAVPN
service-type remote-access
username markh password nqH+bk6vj0fR83ai0SAxkg== nt-encrypted
username markh attributes
vpn-group-policy cad_supplies_RAVPN
tunnel-group DefaultRAGroup general-attributes
default-group-policy DefaultRAGroup
tunnel-group DefaultRAGroup ipsec-attributes
pre-shared-key *
tunnel-group DefaultRAGroup ppp-attributes
authentication ms-chap-v2
tunnel-group cad_supplies_RAVPN type remote-access
tunnel-group cad_supplies_RAVPN general-attributes
address-pool VPN_IP_range
default-group-policy cad_supplies_RAVPN
tunnel-group cad_supplies_RAVPN ipsec-attributes
pre-shared-key *
tunnel-group VPNPHONE type remote-access
tunnel-group VPNPHONE general-attributes
address-pool VPN_Phone
default-group-policy VPNPHONE
tunnel-group VPNPHONE ipsec-attributes
pre-shared-key *
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum 1500
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
service-policy global_policy global
prompt hostname context
Cryptochecksum:8b25ecc61861a2baa6d2556a3679cc7c
: end

Hi,
You have your "group-policy" set so that you have excluding some networks from being tunneled.
In this access-list named Local_LAN_Access you specify "0.0.0.0"
Doesnt this mean you are excluding all networks from being tunneled? In other words no traffic goes to your tunnel.
This access-list should only contain your local LAN network from where you are connecting with the VPN Client. If you dont need to access anything on your local LAN while having the VPN on, you don't even need this setting on. You could just tunnel all traffic instead of excluding some networks.
- Jouni

Is there a way of remote accessing 'Games and More' on a mobile?

I am new to the forum, please excuse me if I am in the wrong space!
Is there a way of remotely accessing/executing Java applications that are residing in the 'Games and More.' folder on a mobile device?
e.g. Java application is downloaded into 'Games and More' and there is a requirement to execute the program from an ODP (On-Device-Portal). The ODP is external to the 'Games and More' folder but within the same mobile device.
Many thanks
Ian

IVM wrote:
Is there a way of remotely accessing/executing Java applications that are residing in the 'Games and More.' folder on a mobile device? No.
db

Labview crashes remote access

Similar Messages

Maybe you are looking for