NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
seanyan00
Sep 24, 2012Aspirant
Access my website from Inyernet
Hi all,
I can access my website www.mywebsitename.com in Lan. The site is bound to 8090/8091(https) in IIS7, and the (netgear fvs318g) router is open http/https to iis server ip:port 192.168.1.3:8090 and 8091 (in its firewall/LAN WAN rules). The domain name is soloved properly. The incoming internet(/yahoo) email can go through the routers firwall set (to 192.168.1.3:25, handled by exchange 2007, sbs 2008) . But access from internet to www.mywebsitename.com just hanging there. I opened the machine's (where IIS is located) firewall port 8090/1 or turned the firewall off. Any tips on troubleshooting?
TIA
-s
I can access my website www.mywebsitename.com in Lan. The site is bound to 8090/8091(https) in IIS7, and the (netgear fvs318g) router is open http/https to iis server ip:port 192.168.1.3:8090 and 8091 (in its firewall/LAN WAN rules). The domain name is soloved properly. The incoming internet(/yahoo) email can go through the routers firwall set (to 192.168.1.3:25, handled by exchange 2007, sbs 2008) . But access from internet to www.mywebsitename.com just hanging there. I opened the machine's (where IIS is located) firewall port 8090/1 or turned the firewall off. Any tips on troubleshooting?
TIA
-s
- Looks like redirect to other port of web sever machine doesn't work. Change back router's firewall setting to forward http/s request to 192.168.1.3:80/443. No issue anymore.
2 Replies
- seanyan00AspirantThe port scan
70.184.xxx.xxx is responding on port 25 (smtp).
70.184.xxx.xxx isn't responding on port 80 (http).
What i'm missing? I did similar firewall rules for both for inbound services.
Service Name
Filter
LAN Server IP Address
LAN Users WAN Users
Destination
Bandwidth Profile
Log
HTTP Allow Always 192.168.1.3:8090 ANY WAN1 NONE Always
HTTPS Allow Always 192.168.1.3:8091 ANY WAN1 NONE Always
SMTP Allow Always 192.168.1.3:25 ANY WAN1 NONE Never - seanyan00AspirantLooks like redirect to other port of web sever machine doesn't work. Change back router's firewall setting to forward http/s request to 192.168.1.3:80/443. No issue anymore.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!