2
I am trying to use port 7777 for my dns web hosted site but i seem not to be able to connect to the website when i do that. It tries to log into my router? It brings up the user name and password to input to enter my router webpage.
If i use the default 80 port then my website comes up without a problem.
I have added the port to my routers port forwarding table with the servers IP both 80 and 7777 port (but not at the same time).
I've changed my bindings to use port 7777 in IIS manager.
I am also using No-Ip.com for my IP change (if it ever does).
How can i change the default port 80 to a custom port number without it trying to log into my router when i input my domain name url?
The no-ip settings i have to choose from is:
or Port 80 Redirect?
Not sure if that's the problem or not but if i change it to 7777 for Port Redirect it still does not work and changes my domain name from www.xxxxxx.com to xxx.xxx.xxx.xx:7777 which doesn't look nice.
My routers port settings:
You need to forward port 7777 to the IP that has the website. There are already a million answers on how to do this. Not even worth a downvote. – Piotr Kula – 2012-10-29T15:03:37.280
@ppumkin: I have added the port to my routers port forwarding table with the servers IP both 80 and 7777 port (but not at the same time). – StealthRT – 2012-10-29T15:06:20.337
Your tagging is a little misleading, what version of windows exactly are you using? – Journeyman Geek – 2012-10-29T15:07:56.950
@JourneymanGeek: Windows Server 2012 but it seems to have the same setup as Win Server 2008 R2 from what i can tell. – StealthRT – 2012-10-29T15:08:30.740
Ye- fantastic so what is the problem? – Piotr Kula – 2012-10-29T15:08:54.887
@ppumkin: When i change the port to 7777. Change the port fowarding to 7777 for the server ip in my router and then visit the web site of my domain name my routers login box comes up.... It should go to the IIS 8 default website like it was doing on port 80. – StealthRT – 2012-10-29T15:10:10.583
Yes - because port 7777 was not forwarded to the correct place. Sounds like a crap router to me. – Piotr Kula – 2012-10-29T15:12:47.737
Look- Nobody can be bothered any more to write a "how to diagnose port forwarding issues" any more OK. It is obvious there is a problem with the port forwarding hardware. You are doing the right thing- there is nothing special about it. Did you power down and up the router? – Piotr Kula – 2012-10-29T15:16:01.680
@ppumkin: Its a Netgear 6300 router [http://www.netgear.com/R6300]. Thanks for your suggestions. – StealthRT – 2012-10-29T15:22:44.910
@ppumkin; JourneymanGeek: Updated OP. – StealthRT – 2012-10-29T15:30:07.790
Umm - Right so you just need to forward PORT 80(incomming to router) -> PORT 7777(incomming to webserver) (problem solved) 5 bux – Piotr Kula – 2012-10-29T15:37:44.510
@ppumkin: How would i port 80 to 7777 in my router? That's not possible? It only has a range from xx-xx for port. – StealthRT – 2012-10-29T15:43:18.090
@ppumkin: Updated OP again with netgear port settings. – StealthRT – 2012-10-29T15:46:05.403