|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | RE: [ECS] Remote applet access problem Rob Hicks Fri, 14 Apr 2000 11:06:06 -0600 |
Hi Mark.
I don't think your problem is as easy to fix as explicitly providing the
port number. It seems that you have already done that.
I suspect that that your Java programs are not getting the port number and
that you don't have any other http services (even at port 80) running on
your machine that they can resolve. One way to test this assumption is to
load a conventional web server at port 80 or, if you don't have any other
http services loaded on your machine, change your ECS_PORT value to 80 and
then try using a simple http request. If the Java programs are not getting
the port number, when you make this change, they should resolve to the
standard http port, 80, and you'll know that you need to make sure that they
are picking up the "new" 3000 port number.
Regards,
Rob Hicks
Voice: 801-226-1346
Email: robhicks@utah-inter.net
-----Original Message-----
From: Dario Greggio [mailto:adpm@ipsnet.it]
Sent: Friday, April 14, 2000 10:06 AM
To: ecs-list@netbloc.com
Subject: Re: [ECS] Remote applet access problem
Mark Gilmore wrote:
>
>
> I get the feeling that I am missing something obvious.
> I note that the addr in message below does NOT include the port #
> (3000).
> Any ideas ? Thanks.
Could it be so obvious? :-))
If you don't enter a port#, any browser will default to port 80
(decimal).
So, you should either change the setting for ECS (as I did with my
Joshua) or force the ":3000" in the remote address. But in the second
case you may have proxy troubles or things like those.
So, unless you (or anybody else) is having a Web server installed, I
suggest changing it. Proxy (such as Wingate) don't have this problem, as
you can always move them to another port (there is no default, 8080 is
just a suggestion).
Did you incorporate also a FTP server, or mail server, or telnet server?
They are less useful than HTML/JAVA, but you could use FTP or telnet to
get (or set) status in text-only window mode. Or you could get emails to
alert the user. It's fast (faster than Java!! You did a great job!) and
easy in C++.
--
Ciao,
Dario
--
ADPM Synthesis sas - Torino
--
http://www.geocities.com/adpm99
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects