10-24-2001
Something you may want to check is if the in.telnetd daemon is configured in the /etc/inetd.conf file. If it is commented or not there, that is probably why.
The line should look something like this (one line):
telnet stream tcp6 nowait root /usr/sbin/in.telnetd in.telnetd
Once that is there, you can either reboot, or run "kill -HUP <pid>" Where <pid> is the process id of the inetd process.
On Solaris 7 and 8, you can just run "pkill -HUP inetd"
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:cool: I need some assistance please. I'm setting up a SunOS 5.6 server and sofar I'm able to telnet into the unit but unable to telnet from it. Can anyone help me with this problem. When attempting to telnet from my SunOs to client
terminal I'm receving the following error, "Unable to connect to... (3 Replies)
Discussion started by: sharris82
3 Replies
2. Solaris
Greetings,
I have recently inherited 3 sun servers from a shop that my parent company closed. One of these servers is an old Ultra 1 running SunOS 5.6 that acts as a NIS server for the other two servers. This NIS server seems to boot OK and function properly as a NIS server. However, I can't... (6 Replies)
Discussion started by: SevenFortyOne
6 Replies
3. UNIX for Dummies Questions & Answers
Hi everybody
i am trying to telnet to sun server from win xp machine but getting message "x21 error connection closed by remote user". i had make changes in /etc/default/login & /etc/fuser file still i have not getting telnet access. my win xp machines ip is 10.205.121.177 & sun server ip is... (1 Reply)
Discussion started by: pshelke
1 Replies
4. AIX
Hi,
I encountered error when I telnet to my server.
Error is as follows:
telnetd: /bin/login: The file access permissions do not allow the specified action
I am able to ssh into my server and I have checked/verified /etc/security and /etc/inetd.conf. I restarted the inetd subsystem via... (1 Reply)
Discussion started by: chongkls77
1 Replies
5. Solaris
Hi guys,
After changing my workstation from domain rsm.renesas.com to my.renesas.local, I was unable to telnet to 1 of our Sun Solaris servers.
There r errors in the messages file:
Aug 15 17:35:26 rsmsso1.svc.rsm.renesas.com inetd: warning: can't verify hostname:... (12 Replies)
Discussion started by: *Jess*
12 Replies
6. UNIX for Dummies Questions & Answers
Dear All,
I have Compaq Alpha server running UNIX OS. with Old Hardware specification.
I had FTP conncetion using IP Switch ( FTP client ) to the Unix server in order to copy some files to my workstation. one day after closing the connection we noted that IT operations are not able to... (8 Replies)
Discussion started by: Arehan
8 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have two linux boxes and due to some reasons I have reinstalled OS in one of them. Now Iam unable to telnet one of them. I have included entries in /etc/hosts in both and Iam able to ping each other.
Am I missing anything here or I we need to install/activate telnet server ?
Thanks... (2 Replies)
Discussion started by: ssuhaib
2 Replies
8. Shell Programming and Scripting
Dear Friends,
I need to transfer few files from a Windows 2000 server to Sun Solaris system, connected in the same network. This copy should be done as a batch job without asking for password to be entered every time. How to make this possible ???
At present I am using cygwin in my laptop... (4 Replies)
Discussion started by: ks_reddy
4 Replies
9. Solaris
Hi,
I am unable to connect sun server, server model is sun fire v440
on server 2 ports are there.
serial management, and network management.
I would like to know how to connect serial port if I dont have com port on my system? and on Network Management no ip address is configured.
... (2 Replies)
Discussion started by: manoj.solaris
2 Replies
LEARN ABOUT ULTRIX
ntp.conf
ntp.conf(5) File Formats Manual ntp.conf(5)
Name
ntp.conf - Network Time Protocol configuration file
Description
The file is the configuration file for the Network Time Protocol (NTP) daemon, This file must be configured on your system before running
Any host names that you specify in the file must have an entry in the file, or an entry in the master database, if the database is being
served to your system by BIND/Hesiod or Yellow Pages.
The file has four entry formats:
trusting no
This entry guarantees that your system synchronizes only to the NTP servers identified in the peer and server entries specified. Dig-
ital recommends that all systems include the entry.
peer server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system may also provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP servers should be configured with entries.
server server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system can not provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP clients should be configured with entries.
peer /dev/null LOCL 1 -5 local
This entry identifies your system as a local reference clock. A local reference clock is the most accurate system clock available at
your site. If you receive time synchronization from the Internet NTP service, you should not include this entry on any of your sys-
tems. At most, one system in a set of nodes running should be identified as a local reference clock.
A host which specifies this entry should not specify any or entries.
Examples
This is a sample configuration file for an NTP client which receives time synchronization from the NTP servers: and Lines beginning with a
number sign (#) are comments.
#
# NTP Configuration File
# This file is mandatory for the ntpd daemon
#
#
#
# ** A L L **
#
# "trusting no" prevents this host from synchronizing
# to any host that is not listed below. It is recommended
# that all hosts include the line "trusting no".
#
trusting no
#
#
# ** S E R V E R **
#
# If you are configuring a server, use "peer" entries to
# synchronize to other NTP servers. For example, server1,
# server2, and server3.
#
#peer server1
#peer server2
#peer server3
#
#
#
#
# ** C L I E N T **
#
# If you are configuring a client, use "server" entries to
# synchronize to NTP servers. For example, server1, server2,
# and server3.
#
server server1
server server2
server server3
#
#
#
# ** L O C A L R E F E R E N C E C L O C K **
#
# If you are configuring a local reference clock, include the
# following entry and the "trusting no" entry ONLY.
#
#peer /dev/null LOCL 1 -5 local
#
See Also
ntp(1), ntpd(8), ntpdc(8)
RFC 1129--Internet time synchronization: The Network Time Protocol
Introduction to Networking and Distributed System Services
ntp.conf(5)