DNS Config and Blocked Ports

Hi Everyone,

This issue isn't directly with the nopCommerce framework, but non-the less hopefully somebody could help me out, this is always my first port of call for help from this great community.

Setting up a new nopCommerce site on my Windows Server 2008 R2 running IIS 7.5, Installed I have 5 separate IP addresses all linked to nopCommerce sites using port 80 and port 443 for SSL.

Now I've just added an extra IP address for another nopCommerce site in development but I just can't get it to connect to the server getting the error ERR_CONNECTION_REFUSED in the browser, checked the DNS with the domain, and setup on IIS all appears to be fine, been scratching my head for a few days on this until I checked the ports usign this tool: https://networkappers.com/tools/open-port-checker#.XmKBKJOeQUE
It looks like port 80 is closed for the new IP address, but all the other IP addresses using port 80 work fine, why would this be the case, and would anybody know how to fix it?

As always much appreciated for any help on this despite not being a nopCommerce question :-)

Cheers

Nick

Not a lot to go on, but some things to double check:

Can you browse the new site by IP, e.g. 192.168.0.1:80

Port 80 open in any hardware / software (Windows) firewall for new IP

Port bindings correct in IIS for new site (highlight site, click "bindings" under Edit Site on rights side)

Any server management software like Plesk for IP configuration (controls which site uses which IP)?

Any auto-forward to https: settings without a cert installed?

Do you have RDP access?  Can you browse site on the server itself using the links provided in IIS in the bottom right?  

From the command line run "netstat -n -a -b" and check: which addresses are listening on port 80 which process is doing the listening

Hi,

Thanks for getting back to me, I've answered your questions below:

Can you browse the new site by IP, e.g. 192.168.0.1:80 - NO

• Port 80 open in any hardware / software (Windows) firewall for new IP - Yes the port is used by another 5 IP addresses, and working fine.

• Port bindings correct in IIS for new site (highlight site, click "bindings" under Edit Site on rights side) - Bindings set to the correct settings

• Any server management software like Plesk for IP configuration (controls which site uses which IP)? - No access the server via Remote Desktop

• Any auto-forward to https: settings without a cert installed? - No Cert installed

• Do you have RDP access? - YES

• Can you browse site on the server itself using the links provided in IIS in the bottom right?  - NO

• From the command line run "netstat -n -a -b" and check: which addresses are listening on port 80 which process is doing the listening - Tried this and the port is not listed for port 80

some more things to try:
https://serverfault.com/questions/591373/iis-site-not-visible-under-80-port
https://serverfault.com/questions/884456/cant-connect-to-site-in-iis-through-dns-alias-but-can-connect-through-localhos
https://serverfault.com/questions/293699/windows-server-2008-r2-iis-7-refuses-all-outside-tcp-connections/295328

Many thanks for your help,

I used this in the command prompt under Admin rights netsh http add iplisten ipaddress=X.X.X.X
and the port is now open and works fine.

Thanks again, have a great weekend :-)

Nick

that's awesome, nice work!