Telnet can't!
Morten Liebach
I have just done my first NetBSD ftp-install (1.4.2), and it went great.
But I can't use telnet!
This is fatal, since my ISP, stofanet.dk, requires me to telnet to a
log-on server to get on-line (no, I can't use ssh :-().
What happens is; I `telnet 192.168.30.2 259', and nothing happens.
This is the command that works from Linux, OpenBSD and Win98, so I feel
it should in NetBSD too (a slight assumption, but according to the
manpage it _is_ the right thing, the IP and port is right). :-)
I then tried putting 192.168.30.2 in /etc/hosts, but still no joy.
If I log on from Linux and reboot to NetBSD there's no problems, and I
can ftp-install packages etc., so it seems the network setup is OK.
The only thing I can think of now is that telnet might not use
/etc/hosts (that it has something to do with DNS)?
If that is so, how can that behavior be changed?
Thanks for your time!
Regards
Morten
--
UNIX, reach out and grep someone!
David Brownlee
Telnet should use both hosts and dns - you can change that
with nsswitch.conf (man nsswitch.conf).
Your command looks fine - what output do you get - can you
ping the log-on server OK?
David/absolute
-- www.netbsd.org: A pmap for every occasion --
Todd Whitesel
> /etc/hosts (that it has something to do with DNS)?
> If that is so, how can that behavior be changed?
You can probably fixing it by correcting /etc/resolv.conf,
but in the meantime: edit /etc/nsswitch.conf and change
hosts: dns files
to
hosts: files dns
Then make sure your /etc/hosts file names the machine, and use the name.
Todd Whitesel
toddpw @ best.com
Morten Liebach
/etc/nsswitch.conf was _it_!
I never knew what that file was for, but now I do.
Great!
Thanks to Steve, David and Todd for pointing the answer out to me.
Regards
Morten
--
"Our scientific power has outrun our spiritual power. We have guided
missiles and misguided men (Martin Luther King, Jr.)"
Frederik Meerwaldt
Is the service enabled in the /etc/inetd.conf??
--
Best Regards,
Freddy
=====================================================================
Frederik Meerwaldt Homepage: http://www.freddym.org
Bavaria/Germany OpenVMS and Unix Howtos and much more
FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX
David Maxwell
> On Thu, Jul 20, 2000 at 06:43:44PM -0700, Todd Whitesel wrote:
> > > The only thing I can think of now is that telnet might not use
> > > /etc/hosts (that it has something to do with DNS)?
> > > If that is so, how can that behavior be changed?
> >
> > You can probably fixing it by correcting /etc/resolv.conf,
> > but in the meantime: edit /etc/nsswitch.conf and change
> > hosts: dns files
> > to
> > hosts: files dns
It should certainly work the other way as well, but if your network
has no internet access (and no local nameserver) the two minute delay
while the DNS times out will make it feel like it's not going to work.
--
David Maxwell, da...@vex.net|da...@maxwell.net --> Mastery of UNIX, like
mastery of language, offers real freedom. The price of freedom is always dear,
but there's no substitute. Personally, I'd rather pay for my freedom than live
in a bitmapped, pop-up-happy dungeon like NT. - Thomas Scoville
Bill Studenmund
> Is the service enabled in the /etc/inetd.conf??
Not by default anymore, but that only affects incomming connections. The
initial thread was telnet to another host not working, which works/fails
independent of how inetd.conf is set up.
It sounds like the problem was DNS not set up right and telnet was timing
out on doing DNS on the address.
Take care,
Bill
Frederik Meerwaldt
> Not by default anymore, but that only affects incomming connections. The
> initial thread was telnet to another host not working, which works/fails
> independent of how inetd.conf is set up.
Sorry. I have misunderstooden the thread, and I thought, that he had
problems with incoming connections.