Proxy Problem

[wpolly]

How could I use a proxy server to connect to the ECM Servers?
( Because direct connection always fails)

[smh]

Originally posted by wpolly
How could I use a proxy server to connect to the ECM Servers?
( Because direct connection always fails)

The ecmclient/server use port 8194 (i think tcp, dunno about udp) to communicate. Make sure that port isn't blocked.

[wpolly]

That is not a port problem.
The university firewall simply blockes all the direct connections abroad.
I am browsing web pages using a HTTP proxy.

What could I do now?

[wblipp]

Originally posted by wpolly
The university firewall simply blockes all the direct connections abroad.
I am browsing web pages using a HTTP proxy.

Somebody in your company manages the company proxy server. That person could, if he wanted to, configure the company proxy server so that connections on port 8194 were routed to wblipp.dynu.com. If that happened, then you would put the name or address of the proxy server in the configuration file (ecmclient.cfg), and things would work.

But unless you work in a very small or a very unusual company, they aren't going to reconfigure the company proxy server for the convenience of a project with no business applications. So we need to figure out a way that doesn't use port 8194.

The best idea I've come up with is to put together a little batch file that will run the ecm program over and over, sending the output to a file. Once or twice a week you email the output file to me, and I manually update the counts in the ecm server.

The selected numbers should be far from the next B1 transition so that the project doesn't overrun your work level before you report in. Natural choices right now would be
C149 at B1=11M
C271 at B1=3M
C853 at B1=1M
C2566 at B1=250K

If this is acceptable to you, I'll create the batch file and put links on the download page.

[wpolly]

Originally posted by wblipp
Somebody in your company manages the company proxy server. That person could, if he wanted to, configure the company proxy server so that connections on port 8194 were routed to wblipp.dynu.com. If that happened, then you would put the name or address of the proxy server in the configuration file (ecmclient.cfg), and things would work.

But unless you work in a very small or a very unusual company, they aren't going to reconfigure the company proxy server for the convenience of a project with no business applications. So we need to figure out a way that doesn't use port 8194.

I'm not in a COMPANY but a UNIVERSITY.
If the ECMClient program HAS an ability to use proxy server to connect then I can simply use the the school HTTP Proxy(No matter which port I was going to connect to. It accepts the connection to port 8194 as well as port 80).

But if if doesn't have one, then I'll have to use the manual method.

[wblipp]

Originally posted by wpolly
then I can simply use the the school HTTP Proxy(No matter which port I was going to connect to. It accepts the connection to port 8194 as well as port 80).

But if if doesn't have one, then I'll have to use the manual method.

It sounds like you don't have access to a general proxy server; you need a protocol converter to work through the http proxy server. ElevenSmooth doesn't create its own tools - we use tools from the net. The ECM server and client are from the ECMnet project, and they don't support http. The source code is available, but that sounds like a bigger project than I can take on at this time.

I'm working on the manual method. It should be available for testing soon.

[xilman]

Originally posted by wblipp
It sounds like you don't have access to a general proxy server; you need a protocol converter to work through the http proxy server. ElevenSmooth doesn't create its own tools - we use tools from the net. The ECM server and client are from the ECMnet project, and they don't support http. The source code is available, but that sounds like a bigger project than I can take on at this time.

I'm working on the manual method. It should be available for testing soon.

It sounds as if you are confusing the port with the protocol. You can run pretty much any protocol you like on pretty much any port you like. As long as both the server and the client speak the same protocol on the same port, everything should work.

The solution should be obvious. Find a mutually accessible port (both 80 and 8080 are commonly open most everywhere) then configure both ecmclient and ecmserver to use that port. Of course, the machine running the server can't have anything else listening on the same port ...

Why do you think the port is configurable in the corresponding .cfg files?


Paul

[wblipp]

Originally posted by xilman

The solution should be obvious. Find a mutually accessible port (both 80 and 8080 are commonly open most everywhere) then configure both ecmclient and ecmserver to use that port.

Is it really this simple? The proxy servers I've used always had a single fixed destination for things that were not http. You configured the applications to connect to the server machine, and you configured the server machine to know the real destination. My understanding was that http is different because there is a standard for communication with the proxy server to tell it the final destination. Since the ecmclient program doesn't know about this communication standard, I thought that it can't signal through the http proxy server.

To check this, I need to run the ecmserver on port 80. With a growing number of users already using port 8194, I don't want to take that down. The ECMserver supports a slave mode that has different ports for upstream and downstream, so it should be possible to configure a machine to listen on port 80 and communicate with the master on port 8194. But when trying to set this up, I get an error message that you cannot run multiple copies of this application.

Will somebody volunteer to run a test case for wpolly to see if Xilman is right? I've attached a zip file with the new ecmserver.exe and the ecmserver.cfg files. All you need do is unzip them, run the ecmserver program, then tell wpolly your internet address (you can find this with the ipconfig program inside a command prompt box). Tell me, too, and I'll check the setup is working independent of the proxy server issue.

[wblipp]

Wpolly,

Nobody has stepped forward yet to test if the Port 80 method works. While waiting for a volunteer to help us test that, you can try the stand alone process:

http://home.earthlink.net/~elevensmo...own.html#Alone

[smh]

Originally posted by wblipp
Nobody has stepped forward yet to test if the Port 80 method works.

I might be able to help.

I've set up a server at port 80 and was able to connect from an office pc using the msproxy client. Without this client no communication was possible.

This pc is my home (test) server, and is not running the whole day. I'll PM my ip adress to both of you, but there's no guaranty that the server is up at the time you might try. If things are not working PM or e-mail me so we can agree on a time to try things out.

[BotXXX]

I have also a server running on different ports. But i try to explain how i set it up.

I have one machine which runs one instance of the ecmserver on the default port (8194). No other ports are configured on this machine. But on my firewall i redirect all outside TCP traffic that comes in on the ports 23, 80, 110 and also 8194 to the ecmserver.

Since i use a firewall with routing options all traffic on the outside TCP ports 23, 80, 110 and 8194 is forwarded to the local ecmserver on port 8194. Thus it is possible to connect on these ports and contact the same server.

But indeed the communication of the ecmnet setup is not http compliant. And thus if your proxy checks which type of traffic it is and only allows http trafic this won't work. Since all other than http traffic will be blocked. There is some software out there that can tunnel traffic over a http proxy but i can not found it at the moment and i never got it working at a place where they were using a proxy with only http access.

-edit-
pfff ofcourse after clicking to fast on the place reply button i forgot to note the IP where this server runs at. But note that it is NOT a ElevenSmooth server, it has loaded different numbers for different purposes.
IP: 217.19.25.214
Ports: 23, 80, 110 and 8194