Asked by:
cant forward ports 443 or 4125

Question
-
I'm having problems forwarding the ports 443 and 4125. I have forwarded port 80 to my server. The Dlink dir-655 does not give me any info to say they are not open when I check at sheildsUP! it says they are closed but port 80 is open.
I have tried this with upnp on and off.
Any help would be great.Wednesday, August 12, 2009 11:44 PM
All replies
-
I'm having problems forwarding the ports 443 and 4125. I have forwarded port 80 to my server. The Dlink dir-655 does not give me any info to say they are not open when I check at sheildsUP! it says they are closed but port 80 is open.
I have tried this with upnp on and off.
Any help would be great.
First, I would make sure you disable uPnP on your router (so that eliminates that as a possible problem). Second, are you sure you forwarded all 3 ports to your server's IP address? If so, have you ever changed any settings from the server desktop (specifically anything related to IIS)? If nothing else, you could try temporarily disabling Windows Firewall on your server, then check Shields Up! again and see what it reports for those 3 ports. (Just make sure to turn the firewall back on once you're done checking.)Thursday, August 13, 2009 2:06 AMModerator -
I have tried with
Firewall on and off
uPnP on and off combined with firewall on and off
I forwarded all 3 to the whs server on my network, tried with 3 seperate entries 80 443 4125 and as one entry 80, 443, 4125
both times failed.
also tried with router firewall on and off and remote access turned on and off, also tried with upgraded firmware.
The weird thing is that with the 120 day trial this all worked flawlessly.
I didn't do anything with IIS, looked into it but could not find anywhere to play around with it.Thursday, August 13, 2009 2:09 PM -
Just to make sure:
Did you validate, that you forwarded to the correct IP address of your server? After a fresh installation this is often not the same as before, if not configured manually.
Best greetings from Germany
OlafThursday, August 13, 2009 8:59 PMModerator -
Thank you Olaf,
No the IP of the server did not change. I am going to reinstall everything and give it another go.
Cheers from CanadaFriday, August 14, 2009 11:33 AM -
I have the same router with the ports forwarded. check the port forwarding page under advanced. If the ports are enabled the check box next to the entry will be ticked. I have an entry for each port and have 8912, 55000, 56000, 80, 443 and 4125 open and everything seems to work fine.Friday, August 14, 2009 12:31 PM
-
I have the same router with the ports forwarded. check the port forwarding page under advanced. If the ports are enabled the check box next to the entry will be ticked. I have an entry for each port and have 8912, 55000, 56000, 80, 443 and 4125 open and everything seems to work fine.
FYI, the first three ports you have listed are normally not required in order for WHS to work (certainly not needed to access your server from outside your LAN). Unless it's absolutely essential for those to be open for your server to work, I would strongly recommend removing those entries ASAP.Saturday, August 15, 2009 3:40 AMModerator -
What? Microsoft help for WHS says to open those ports if auto config fails. How do I access my WHS outside my lan without the ports open or the auto config working?
FYI, the first three ports you have listed are normally not required in order for WHS to work (certainly not needed to access your server from outside your LAN). Unless it's absolutely essential for those to be open for your server to work, I would strongly recommend removing those entries ASAP.Saturday, August 15, 2009 7:42 PM -
You may have read this for opening the ports in the Windows Firewall o the server, which may be necessary in the unsupported scenario, if client and server are not in the same IP subnet.
But opening these ports to the Internet is not a good idea.
Best greetings from Germany
OlafSaturday, August 15, 2009 8:17 PMModerator