Riccardo71
asked on
error when logging to ssl port other than 443
Hi, I have a problem for a client that has to connect to a secure website on a port 8443.
I ran isa_tpr.js as I read in other request and configured the two port requested, 8443 e 9000. when I try to connect to the website from the server it works fine, but if i try to connect from the client it doesn't work. so the error is a rule that miss and I don't know what for a kind of rule I have to do. the client can go in internet on normal web page. it has a proxy configured that is the sbs 2003 with isa 2004
I ran isa_tpr.js as I read in other request and configured the two port requested, 8443 e 9000. when I try to connect to the website from the server it works fine, but if i try to connect from the client it doesn't work. so the error is a rule that miss and I don't know what for a kind of rule I have to do. the client can go in internet on normal web page. it has a proxy configured that is the sbs 2003 with isa 2004
ASKER
The error is always the same
error code 502 proxy error. the specyfied secure socket layer (ssl) port is not allowed. isa server is not configured to allow ssl request from this port. most web browser use port 443 for ssl request.(12204)
but when I try from the server it opens the web site correctly
error code 502 proxy error. the specyfied secure socket layer (ssl) port is not allowed. isa server is not configured to allow ssl request from this port. most web browser use port 443 for ssl request.(12204)
but when I try from the server it opens the web site correctly
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, I've read the article that it explains only of the server configuration but nothing is said about specifical configuration for the client. I've done it and the server can navigate in the ssl page.but the client is blocked. the client can navigate in http pages but when I try the ssl page with port 8443. I'm blocked with the usual message. I've tried in a test virtual environment. I will try by the customer and perhaps It will function. bye
Hi I would expect the server to be able to navigate as it wont be going throught the web proxy service it would have a direct connection out to the internet? Give it a go let us know how you get on.
ASKER
I think You have understood the problem. infact the server has non proxy, instead the client has the proxy configuration and so has to be. so, what type of rule have I to do to let navigate the client?
thanks in advance
thanks in advance
It is not a rule that is blocking this as such as the client can connect to http and i assume standard https sites, the problem is ISA will only connect to https sites on standard 443 so if you have a non standard SSL port like 8443 you need to add it to ISA's range of ports which you do by running the script in the KB article above.
Just to confirm you must run this on the ISA server itself not the client machine.
ASKER
ok. The first time I've tried, I used a script called isa_tpr.js, which I found mentioned in this website. It has functioned only for the server, I don't know why. Perhaps My test environment had some problems. Know I've tried with the method of the article 283284 and it runs fine. I will try to the customer and I will come back to confirm. hi
Whatis the exact error?