Re: Private addresses on public network

From: Anders Pettersson (anders.pettersson@avitec.se)
Date: 07/31/02


To: Octavio / Super <alvarezp@doogie.ods.org>
From: Anders Pettersson <anders.pettersson@avitec.se>
Date: 31 Jul 2002 11:17:04 +0200

Octavio / Super <alvarezp@doogie.ods.org> writes:

> Hello, everybody!
>
> Let's say I have a network, whose computers are connected directly to
> the Internet (meaning that when they have a public IP address, they
> can connect to any place, with no firewall or NAT in between (only the
> corresponding router)).
>
> Now, let's say that I set some (or all, whatever) of those computers
> to have an IP address which does not correspond to my block, (either
> standard private addresses (e.g. 192.168.x.x) or any other
> non-standard IP address (e.g. 92.0.x.x which must belong to
> somebody)).
>
> Q: Is there any way of connecting to them from an external network? I
> mean, are they exposed to any security threat as if they were
> configured with their [normal] public IP address?

That's what the command route is for. By adding a route to your
network someone should be able to connect to any of those
machines. The same is true even if you have them sitting behind a
gateway, sometimes even with nat NAT (network address translation)
unless you do some firewalling.

-- 
Anders Pettersson, Test Engineer, AVITEC AB http://www.avitec.se/



Relevant Pages

  • Re: Networking over mains cables
    ... router works with NAT ... I googled 'NAT' which put me through to the Wikipedia ... It basically means that the computers on your network are hidden ...
    (comp.sys.acorn.networking)
  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)