The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Re: [OT] scanning a server


  • Subject: RE: Re: [OT] scanning a server
  • From: "Paul Gale" <groups@xxxxxxxxxxxxxxxx>
  • Date: Thu, 15 Apr 2004 18:34:49 +0100

Ah, I didn't make myself very clear - the servers (x2) have NAT IP
addresses but the router has a number of rules to forward two public IP
addresses through to various services running on the servers.

I know what rules are enabled on the router as I wrote them but just wanted
a way of double checking it's all working OK and I've not inadvertently
left a hole open etc.

I did try NMap but it looks far too complex with a steep learning curve - I
just wanted something quick to setup and use that gives a reasonable level
of checking/reporting.

Any ideas?

Paul.



> -----Original Message-----
> From: Patrick Lidstone [mailto:patrick@xxxxxxx]
> Sent: 15 April 2004 17:37
> To: ukha_d@xxxxxxx
> Subject: [ukha_d] Re: [OT] scanning a server
>
> --- In ukha_d@xxxxxxx, "Paul Gale" <groups@s...>
wrote:
> > But Shieldsup doesn't allow you to enter an IP address does it?
> i.e. If my servers are behind a NAT router only the router IP will be
> used.
>
> If you machines are behind NAT they should be using private IP
> addresses (e.g. 192.168.x.x). Since these addresses are non-routable,
> it would serve no purpose trying to test them from any location on
> the public side of your router.
>
> Patrick
>
>
>
>
> UK Home Automation Meet 2004 - BOOK NOW!
> http://www.ukha2004.com
>
> http://www.automatedhome.co.uk
>
> Member Offers - http://www.freeranger.co.uk/ukha
> Yahoo! Groups Links
>
>
>
>
>





UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.