| Author |
 Topic  |
|
zinpin
Junior Member
Australia
202 Posts |
 Posted - 02 October 2003 : 18:05:41
|
I'm starting to get this now,  I think...
But first let me answer some of the questions, I'm running a hardware firewall (netgear fr114p) i had a look at all the settings though and I don't think it has a port forwarding option. It has rules which i have macked about with but that's about it.
Next, i have tried the http://xxx.xxx.xxx.xxx:443 trick but im still getting a page not found unfortunately.
I have also checked if port 8080 is open and from what i can see it seems to be closed.
I have checked the port availability by going to http://scan.sygatetech.com/prestealthscan.html and the report comes up with port 443 as the only one open.
But still when i type http://xxx.xxx.xxx.xxx:443 comes up with page not found.
I guess I can't make a move until i get this working... :(
|
 |
|
|
sr_erick
Senior Member
USA
1318 Posts |
Posted - 02 October 2003 : 18:16:29
|
| Ah so you can actually run this on a seperate server and it will translate from between that server and the webserver but from that server to the user, they don't know a thing. Cool! |
Erick
Snowmobile Fanatics
|
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 18:21:13
|
quote:
Originally posted by zinpin
I'm starting to get this now, I think...
But still when i type http://xxx.xxx.xxx.xxx:443 comes up with page not found.
I guess I can't make a move until i get this working... :(
Have you actually set up the website in IIS to accept traffic on port 443 ? since by default it will not (unless using https) |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 18:24:34
|
quote:
Originally posted by sr_erick
Ah so you can actually run this on a seperate server and it will translate from between that server and the webserver but from that server to the user, they don't know a thing. Cool!
Yes, it is very cool, I write a lot of custom webservers which if IIS is running can not run on port 80, unfortunately publishing on ports other than 80 can be very troublesome for users accesing from behind firewalls, so the octagate forwarder is invaluable. |
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 02 October 2003 : 18:36:27
|
quote:
[i]Have you actually set up the website in IIS to accept traffic on port 443 ? since by default it will not (unless using https)
How do i do that Huwr, I think that's what Im missing. |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 18:49:04
|
| ok, open the properties page for the website, it should open at the 'Web Site' tab you should see an input box for 'TCP Port', change it from 80 to 443 |
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 02 October 2003 : 18:54:57
|
Thanks Huwr, I tried but gives me the following error
"the ssl port can not be the same as the tcp port"
|
|
|
|
sr_erick
Senior Member
USA
1318 Posts |
Posted - 02 October 2003 : 18:57:39
|
| did you set the tcp port to 443? You can't have them both set the same. One is meant for port 80 and the other for 443...in this case you won't be using tcp port, just ssl. |
Erick
Snowmobile Fanatics
|
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 02 October 2003 : 19:10:11
|
it wont accept it. I cant remove the existing ssl port from the Advanced configuration (buttons are grayed out) in order to change the tcp to 443.
I'm sorry for my ignorance on this. |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 20:08:46
|
| unfortunately, the only way tochange the ssl port is by installing a certificate |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 02 October 2003 : 21:33:38
|
| If you can't remove 443 from being the SSL port on the Advanced configuration then I'm afraid this won't work at all no matter what you try without using true SSL :( None of my sites have an SSL port even defined so it lets me put 443 in as a regular port (IIS6), I presume your running IIS on XP then ? |
Kiwihosting.Net - The Forum Hosting Specialists
|
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 02 October 2003 : 21:45:14
|
Sorry for the delay in reply, Im using Win2k service pack 3 with IIS.
How come though that some of you can change the tcp value. Is there a setting that I left behind? What if I do a clean install of win2k would that give me back the functionality? |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 21:51:10
|
quote:
Originally posted by HuwR
unfortunately, the only way tochange the ssl port is by installing a certificate
Once you have installed a certificate, it will allow you to change the ssl port to something other than 443, you can then use 443 for the standard tcp port.
Any free or temp cert should allow you to change the ssl port.
You could probably change it by editing the IIS Metabase, but this would be more difficult and prone to disaster |
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 02 October 2003 : 22:00:39
|
| thank you HuwR and to all for your help and quick response to this. I guess Ill be off to try and find a free or temp certificate...Any suggestions? |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 02 October 2003 : 22:02:56
|
| I'm pretty sure most SSL suppliers will issue test certificates |
|
|
|
Topic |
|
Topic Locked
