Member Avatar for Laneyh

Hi
Does anyone have or know where I can find some idiotproof instructions on
setting up IIs websites to be viewed externally (over the internet).

The content is built using asp pages and sits on either SQL or Oracle
I am ok with setting the site and corresponding database up and can then view the instance using Localhost , the machine name or the internal IP address.

What I need to know is how to publish it or set it up so that people external to our network can view it over the internet.

The server only has one network card so I guess there will be an external and internal ip address. I was going to use www.whatismyip.com to establish the external address

I'm a bit stuck as my colleagues who would know this are not in the office and not due to be for some time.


Any help appreciated.
Regards
Elaine

  • 4 Contributors
  • 5 Replies
  • 217 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by inderjeetsd

Dani AI

Generated

Building on ’s question and ’s note about forwarding, here’s a short, practical checklist to make an IIS site reachable from the Internet — and the minimal safety points to avoid exposing a development box.

  1. Give the server a fixed LAN address (static IP or a DHCP reservation) so the router always forwards to the same machine — do this in Windows Network settings. (Change TCP/IP settings). (support.microsoft.com)

  2. Verify the IIS site has the correct binding (IP/port/host header) so it will respond on port 80/443. Use the Bindings dialog in IIS Manager or appcmd for scripted changes. (IIS site bindings docs). (learn.microsoft.com)

  3. Allow HTTP/HTTPS in the Windows firewall (example PowerShell) and confirm IIS is listening:

New-NetFirewallRule -DisplayName "IIS HTTP In"  -Direction Inbound -LocalPort 80  -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "IIS HTTPS In" -Direction Inbound -LocalPort 443 -Protocol TCP -Action Allow

# quick listen check
netstat -an | find ":80"

(Windows Firewall cmdlet reference). (learn.microsoft.com)

  1. Add NAT/port‑forward rules on your router to forward external 80/443 to the server’s LAN IP (on a DI‑604 this is done in the Advanced → Virtual Server section). Test with an external port-check tool. (DI‑604 manual / port‑check). (manualslib.com)

  2. If your ISP gives a dynamic public IP, use a Dynamic DNS service (No‑IP or DuckDNS) so people can use a hostname instead of a changing IP. (noip.com)

Security notes: don’t publish a WAMP/XAMPP dev box as-is — these bundles are configured for convenience, not production. Use IIS with production hardening (least privilege, SSL, patched OS, restricted DB access). See IIS security best practices. (apachefriends.org)

If anything above is already done but external access still fails, check: router WAN IP vs. public IP, ISP blocks on port 80, and whether your router supports NAT loopback (testing from inside can be misleading).

Recommended Answers

All 5 Replies

Member Avatar for it2051229

yup.. we have the same problem :(

Member Avatar for jbennet

you need to get your router to forward all port 80 (web) requests to the server. You also need to open the required ports in both your software and hardware firewalls.

Member Avatar for it2051229

ok.. am using WAMP. My Computer is connected in a router(D-Link DI-604) which has a static IP address. How can i give people from the outside of my router access to my server?? and uhhmm i'm a newbie in configuring routers... :(

Member Avatar for jbennet

its a bad idea to open WAMP to the net. WAMP is for development only. Its not secure

Member Avatar for inderjeetsd

:'(help me to publish my iis server over internet . Please send me a suitable solution of my problem . My email id is .

Please help m e.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.