🚀 go-pugleaf

br wrote:

> I have a Cisco 1750 router for outside access.  There is a Unix box sitting
> on the LAN, which consist of one NT box and Win98 worksations.
>
> The NT box is only connected to the network right now. It isn't doing
> anything.
>
> The Unix box has a static IP.  I'd like to give access to the Unix box via
> telnet from the outside. I can access it from within the LAN.  However, it
> is not seen on the LAN when viewing through network neighborhood, I think
> because it does not have a computer name.  The is no access to its IP from
> outside of the LAN.  Has any done something like this?
>
> brettr

Seems like NT boxes have a tendency to do nothing for the most part :-)
If you want to see it in network neighborhood within your local subnet, then
you will need samba which provides Server Message Block/Common Internet Files
System (SMB/CIFS).  Go to www.samba.org for more information on samba.
Assuming that when you say outside, this means from anywhere on the internet
other than your subnet...
If you want to make the unix box available to the outside world, you will have
to provide a route to the internet through your router.  This will involve
getting a registered "real" internet  IP address (with a name like
"joesunixbox.net" and setting up the router to route traffic for the specific
IP address to the unix box.  See www.internic.com for more information on
this.
Alternately, if the unix box is attached to an Internet Service Providor (ISP)
service such as AOL, it should then have a IP address that can be connected to
(via telnet, ssh or other) from the outside via it's dot address (such as
204.71.200.245).  It will support your subnet very well in this configuation.
What are you doing for security?  You may need to provide a firewall using
selective filtering and IP masquerading which are both available out of the
box on most linux systems.

In general, read about the following topics to get a background
Samba - SMB (Windows computer name and network browsing stuff)
ipchains - for IP filtering, and routing.
DNS and BIND - resolving IP adresses through host names on the internet and
intranets.

Hope this helps.

--
Kenneth W. Zahorec
kzahorec@neo.rr.com
Discover Linux today!