Re: hide ip address of website (no domain name)

From: Jeffrey C. Keyser (jkeyser@perfectorder.com)
Date: 11/30/01


Date: Fri, 30 Nov 2001 16:43:29 -0500
From: "Jeffrey C. Keyser" <jkeyser@perfectorder.com>
To: julia@cgia.state.nc.us

julia@cgia.state.nc.us wrote:
>
> hi all
>
> i have just had a webserver 'dropped' on me to
>
> administer, and being new to administering
>
> iis5/w2k sp2, i could use some advice.
>
> i've been surfing around various security sites all
>
> day and haven't hit paydirt yet - or it could be that i'm
>
> just too new to recognize the answer and need
>
> someone to spell it out for me :)
>
> here's the most burning (currently) question i have:
>
> how can i hide the ip address in the url address line
>
> of an end users browser when someone visits my
>
> website AND hide both the ip & netbios name of my
>
> webserver from any other programs/scanners/etc ?
>
> will proxy server installed on the box or using host
>
> headers work, & if so, what do i need to do to set it
>
> up properly.
>
> here's what i got to work with:
>
> 1) server has no domain name, just an ip address
>
> 2) it serves only a single ArcIMS website & does
>
> nothing else
>
> 3) i got no firewall software or hardware at the
>
> moment (would welcome free or low cost
>
> suggestions. yes, i know you generally
>
> get what you pay for, but small, cost-recovery
>
> govt agencies have no $$ to work with)
>
> 4) we aren't using active directory and we dont have
>
> an nt domain, just a workgroup - our name server
>
> is not running a microsoft OS.
>
> 5) iis lockdown tool was installed before ArcIMS
>
> webmapping software was installed & configured.
>
> (ArcIMS uses java servlets and the viewer
>
> application uses lotsa javascript and has
>
> various communications going on between
>
> various parts of it that are not on port 80. it is
>
> notoriously easy to screw up when you're tyring
>
> to harden up your webserver, so that's always
>
> an iffy situation.)
>
> many thanks in advance for any help
>
> anyone can provide,
>
> julia

How about installing on of the open source firewalls in front of it and
using port redirection? As far as the NetBT is concerned, it should
NEVER be running on a web server in the first place. Aside from
improving host security, you'll get better performance from the services
that you do need when disabling all the services that you don't. Using
Win2K/IIS, this box could probably use all the help it can get. :)

Example: Assign the above mentioned IP address to the external interface
of the firewall and redirect the inbound port 80 request to the web
server which would get a private (RFC 1918) address. All non-essential
ports should be dropped.

Good luck,

-- 
Jeffrey C. Keyser



Relevant Pages

  • Re: Security Problem...
    ... > It is listening on port 80 because I never turned off port 80, ... >> Your computer is listening on TCP 80. ... >> If this was a compromise that came through IIS web services, installing ... >> secure a server, all mentioned in the links I gave you]. ...
    (microsoft.public.security)
  • Re: Need a second web-server but got only one ip-number on the outside.
    ... > I have only one ip-number on the outside. ... Make sure your first webserver isn't listening on ALL ports, ... such as 88 or 8080 or any other unused port in your internal network. ... Also make sure that the people using the new server add the ...
    (alt.linux)
  • Re: unable to connect using https
    ... > I have IIS5 running on same server as the certificate ... > server, all latest patches. ... > to the local default webserver and am able to edit the ... > port 443 in website and advanced. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ISA port filtering
    ... Forgot to mention - there is no router on this network. ... I need to open up port 80 but with IP restrictions so it is not ... I've never worked with an ISA server and understand this ... server that needs to 'push' out data to our webserver. ...
    (microsoft.public.isa.configuration)
  • Re: Access OWA From Outside Network
    ... Another thing I'd do if you want to use OWA accross the Internet ... port rather than 443. ... worrying about if you want to use 443 on your regular web server. ... Our external DNS entry points to our webserver. ...
    (microsoft.public.exchange2000.general)