Port numbers

[Keith]

Hi

I need some advice about my port number and domain name.

I have purchased a domain www.gocars.co.nz and I want that to point directly to my NT program.  The server that I am running on has IIS listening on port 80 and I have built my program with port 8092.  When I quote the IP address of the server with the 8092 port number my program works fine and I have been testing in this mode.

I now want to go into production and would like gocars.co.nz to point to the program (through some internal 'address translation (?)).

What are my options (if any) and what is the implementation:

1.  gocars.co.nz:8092
2.  <ip address>:8092
3.  gocars.co.nz
4.  Dedicate a server so that I can use port 80
5.  Other 

Thanks

Keith

[terryd]

HI Keith. Unless you have another website using port 80 on this computer I would definitely recommend removing the IIS service and using port80.
Unless you have a dedicated audience whom you can school in opening ports if your selected port is rejected by their firewall using non-standard ports for a website in the wild is definitely something I would not recommend.
You can certainly have your application and database on one server and have another just to run the application and which would then be the server that the internet URL will connect to but the same issue would still apply if IIS (or Apache) is hogging port 80 on the new server.

My opinion:  http://www.gocars.co.nz

[Poul]

if you have access to your DNS you can try domain and /or sub-domain forwarding with port numbers:
eg:
        gocars.co.nz   ==>   http://yourIP:8092
or
        admin.gocars.co.nz   ==>  https://yourIP:8092/adminpage
        test.gocars.co.nz   ==>  https://yourIP:8091/Testlogin
        dev.gocars.co.nz   ==>  http://differentIP
 
You can use with or without masking - but test carefully, with masking, on occasion i have seen different behaviors.
but when it works it works well.

poul

[mmelby]

I agree with Terry. However if you are really stuck on using different ports, another option would be to redirect port 80 to your application port. This can either be done in IIS or using a webpage.

[Keith]

Hi Terry, Michael and Poul,

Thanks for looking at this. 

Comments have clarified the position and I am sure that I will be able now to work out a solution.

Cheers

Keith