Sharing a web server with Internet Connection Sharing

  • Thread starter news.cablespeed.com
  • Start date
N

news.cablespeed.com

I'm been playing around with publishing a web server to the Internet using
the Internet Connection Sharing feature of WinServer 2003 (yea, I know this
is a WinXP newsgroup, but I couldn't find a Win2K3 newsgroup).

I'm running ICS on the computer that server as my gateway to the Internet
and hope to publish a web server residing on my internal LAN.

In short, I entered the IP address of the my internal web server into the
service settings dialog and port 80 in the external and internal port
numbers boxes but it just doesn't work - port 80 isn't even opened on the
external interface as verified by a "Shields Up" scan at www.grc.com.

If I change the settings to publish a web server residing on the gateway
computer (the same machine running the ICS) then it works fine - port 80 is
opened on the external interface and I can connect to the web server w/o
problem.

The ICS is supposed to support publishing servers on the internal LAN. Can
anyone think of something I might be doing wrong???


Thanks
Trent
 
R

Roger Abell [MVP]

From your quick description it sounds like you may be trying
to use ICS correctly, I do not really know as I have not used ICS
on W2k3 server (think RRAS, NAT, ISA, IPsec filtering instead)

You may want to ask in a W2k3 newsgroup, most of which
begin microsoft.public.windows.server.* or are named for
the technology, like microsoft.public.windows.group_policy
These are not exactly W2k3 groups, but are the new groups
defined with W2k3 release to handle the areas for all server
versions moving into the future.
 
R

Roger Abell [MVP]

Not sure what happened to earlier reply, so here goes again.

From your quick description it sounds like you may be trying
to use ICS correctly, I do not really know as I have not used ICS
on W2k3 server (think RRAS, NAT, ISA, IPsec filtering instead)

You may want to ask in a W2k3 newsgroup, most of which
begin microsoft.public.windows.server.* or are named for
the technology, like microsoft.public.windows.group_policy
These are not exactly W2k3 groups, but are the new groups
defined with W2k3 release to handle the areas for all server
versions moving into the future.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top