13 replies to this topic

[Marius Coetzee]

Does anybody know how to set up WebClient so you can connect to it via the internet. We're getting 'Connection Refused' when trying, so I'm geussing the settings on the IIS side is being set up wrong (Pointing to the services.html file).
Our (totaly useless) service provider people says the port is open and the IIS is working so the WebClient Service must be buggy - I think they're incompetent.

Internally it is working like a dream!

I've been trough the documentation, and I've got 2hours to get this working with no help comming from our service provider or network administrator, so ANY help will be much appreciated.

Marius

[Cleve Haynes]

Hi

If it works internally, then it stands to reason that the problem lies in ISS or your firewall - assuming this is setup the same as your internal Webclient.

Are you using ISS internally too? Or are you using the webserver that comes with Webclient?

All I can think of right now is to check your port settings, in both webclient and IIS.

Webclient when installed chooses port 8192 by default. Each service that you create usually has this port number assigned within the url in the service setup - so check your Webclient service setup too.

Cleve.

[Vol Yip]

I have the following experience but I don't know if it is similar to your case:

I have the Server / IIS installed. And all internal clients can access the server without any problem. However, when I have to access the server through Webclient outside me internal network, the connection doesn't get through. I have to add the port number 8080 at the end of the url in order to let my webclient(s) which outside my internal LAN to get through.

Vol

[Peter Davies]

Hi

I'm not an expert here but...

In the first web based client - Javasuite, the HTML screens let you log in but the actual connection was telnet.

If I were you I'd try enabling the telnet port n your firewall (usually port 23) & then trying again.

Pete

[Marius Coetzee]

Cleve,

Thanks for your reply!

While cheking the port numbers I noticed that it was useing the wrong server name in my services.html file. Maybe from a old Beta version.

Anyway. Everything is running smoothly now, thanks again for your help.

Marius

[Marius Coetzee]

Vol,

I think it is the same problem I'm having.

When setting up WebClient it assume the internal server name.
I thought at first it was only in my services.html file (which I changed to the external IP), but now found it is in more than one place.

I did a text search for the internal name and changed all to the external IP address.

We will continue testing today, and if it doesn't work I'll try your idea (By changing: 'http://address.com' to 'http://address.com:8080'?)

Thanks for the tip!

Marius

[Marius Coetzee]

Peter,

I understand your point.
I just thought that we connect to the WebClient server, and it handles the telnet connection.

BUT, as I'm not an expert in any area I'll enable the telnet port ASAP.

Thanks!

Marius

[Vol Yip]

Hi, where do your find this services.html file? Maybe that helps me to resovle me problem too. Thanks.

[Marius Coetzee]

Under Microsoft Windows 2000 server, I installed WebClient in the C:Inetpub (and not the default 'Program Files')directory, thus the services.html (takes you to client log on) file and the index.html (takes you to the administrator log on) file can be found under C:InetpubPROIVWebClientappServerwebRootWebClient directory.

Another file I changed, but can't remember what it is for is the project.ini file found under the C:InetpubPROIVWebClientappServerscriptRootWebClient directory.

HTH

Marius

[Peter Davies]

Marius

You should test with/without port 23 open.

If it works without port 23 - then that is better. There's a bit of a security hole if you leave telnet enabled on your firewall.

Best regards

Pete

[Marius Coetzee]

Peter,

Thanks for the warning. For the time we only want to get this working so we can test it. Once we understand the setup more we'll work on setting up with max. security.

Thanks again.

Marius

Attached Files

•  SocketError.zip   2.57KB   52 downloads

[Marius Coetzee]

Oops, the attachment was meant for my next post

[Marius Coetzee]

OK, I thought it was working but when connecting I get the error displayed in the attached file.

'ProLive' is the internal DNS name for the machine where the proiv server is running (i.e. the 'Host'), I tried changing it to the internal IP address, but this causes the 'Connection to ProIV' message to display, and then stay there without any network traffic.

Does anybody have an idea what I'm doing wrong?
According to Peter Davies help, our telnet port is open. The OCX get downloaded fine. I've also tried Vol Yip and Cleve Haynes' suggestions which solved 90% of my problems.

Once again: any help will be much appreciated.

Thanks in advance,

Marius

PS. Haven't thought of it before; but we will ask ProIV Support if they've got tips for us how to set everything up and post any help they provide here.

Attached Files

•  SocketError.zip   2.57KB   41 downloads