LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

actionimageupdater

I am using actionimageupdater in conjunction with Internet Toolkit . when I use localhost I am able to control the VI from browser. But not when I use my IP address. It gives an error "access denied" although I can see other
pages on my server. I have made sure the following:

1.In my *.acl files, I use * for access and * deny.
2. In my internet toolkit configuration, made sure to allow access to everyone and all VI's.
3. Made sure the .jar, .html, and .acl files are in the root document directory.
4. started the HTTP server before starting the ImageUpdater server.

Earlier several months ago when I had downloaded the same zip file "imageupdater.zip" from NI web site and tried it had worked from any IP adress. But I am unab
le to repeat that now!

It would be a great help if a National Instruments engineer or anyone else can help me solve this mystery...

Many thanks
0 Kudos
Message 1 of 4
(2,773 Views)
Are you getting access denied for the web page you are trying to access or for that Java applet? If its for the webpage itself, then don't even worry about *.acl files. Its going to end up being soemthing with the G web server config files and permisions. Some of it gets a little tricky. Look through the pdf for the toolkit for what options you have.
0 Kudos
Message 2 of 4
(2,773 Views)
Only for that Java applet. The web page loads normally. So the G web server config files are okay.

After I posted the message, I re-installed labVIEW , ITK and imageupdate server . Now it seems to work okay. But there is one thing I have noticed and that is the image update server messes up with the port (defualt 80) of the http server. ie., the G web server stops , saying 'the port is not accessible'. When the port number is changed to anything other than 80, it starts working. This problem has occured two times. Both the times I have solved it by re-installing all applications. I would like to know if this has happened to any one else.
0 Kudos
Message 3 of 4
(2,773 Views)
I believe I have the answer to this problem.

Your .acl files are incorrect. You want to ALLOW all users (*) and deny no one (blank). Since you have a * in your deny section, all users are denied. The servers check the allow first, and then the deny, so the deny overrides the allow if there is any overlap (for example, a * in allow section and a www.ni.com in the deny allows all users except www.ni.com)

Mark
0 Kudos
Message 4 of 4
(2,773 Views)