Date: Tue, 11 Aug 1998 09:22:45 -0400 (EDT) From: CyberPeasant <djv@bedford.net> To: gary.hall@mcg-graphics.com (Gary Hall) Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Internal networking problem Message-ID: <199808111322.JAA17202@lucy.bedford.net> In-Reply-To: <35CFF2AA.F3E919E@mcg-graphics.com> from Gary Hall at "Aug 11, 98 08:28:42 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Hall wrote:
> We have a FreeBSD machine which is used as an Intranet Server. We also
> have a number of other machines that connect to this via TCP/IP. We have
> another machine that acts as a router which is not a FreeBSD machine.
Please be more specific: is it Unix? or NT? Makes a big difference.
> When we try to connect to the FreeBSD machine internally via FTP or
> rlogin, the FreeBSD machine tries to connect to the Internet via our
> router. Our router then tries to dial up onto the Internet via ISDN.
> Until the connection is made, it refuses to accept any internal
> connections.
Yeah, a common symptom of misconfigured name resolution.
> All our internal machines are set up with the IP address 192.9.200.xxx.
> The gateway setting for the FreeBSD machine is set to the correct IP
> address of the gateway machine and the DNS setting is set to the DNS
> setting of our ISP. We wondered if this was the problem - should we have
> an internal DNS server or have we missed something elementary ?
192.9.200.xxx appears to be assigned to these names:
[this, BTW, looks to be a very lamely subnetted class C...]
[No name] (FARME-HST) FARMER1.FLOWERPAGE.COM 192.9.200.111
[No name] (NIKE4-HST) NIKE.BLACKMAXX.COM 192.9.200.17
[No name] (RAMES2-HST) RAMESH.COM 192.9.200.21
[No name] (RAVE3-HST) RAVE.OLIVERI.NET 192.9.200.251
[No name] (THOR81-HST) THOR.BLACKMAXX.COM 192.9.200.31
[No name] (HAMGE-HST) HAMGEC.KNLOGIN.COM 192.9.200.80
Central Data Corporation (BIF-CENDATA) BIF.CENDATA.COM 192.9.200.1
Central Data Corporation (BOOMER) BOOMER.CENDATA.COM 192.9.200.3
F.A. Davis Publishing Company (FADAVIS-HST) MIS.FADAVIS.COM 192.9.200.198
F.A. Davis Publishing Company (FADAVIS2-HST) ORDER.FADAVIS.COM 192.9.200.20
Quad Design Technology (QDT-HST)QDT.QDT.COM 192.9.200.2
Quad Design Technology (SAL-HST)SAL.QDT.COM 192.9.200.55
Use 192.168.X.X for an unregistered net, unless you're on that list.
You really need to do that now. If you're not using NAT, your return packets
will go to these people. This is a routing, not a name resolution problem.
(TCP/IP routing does not use names--numbers only!)
You do need resolver service of some sort.
named (aka BIND), part of a larger system of "name resolution".
If your internal network is small enough, your needs for name resolution
within the LAN might be met with /etc/hosts files. NIS provides a more
easily managed named alternative. NIS and /etc/hosts may not be available
for non-Unix systems, in which case you will probably need to set up
DNS/BIND, i.e. "named". This is picky but not difficult.
I would guess that you need to do some reading at this point, in
Greg Lehey's "Complete FreeBSD", the handbook, and possibly a book
on DNS.
Dave
--
Bedford County, PA -- 47,000 polite, friendly Appalachians,
4,000 of whom have concealed-carry permits.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808111322.JAA17202>