Sponsored Content
Operating Systems Solaris cannot telnet/ftp to solaris machine by straight cable makes problem .. Post 302188226 by mahadib on Wednesday 23rd of April 2008 02:54:11 AM
Old 04-23-2008
cannot telnet/ftp to solaris machine by straight cable makes problem ..

Hi All,

1. modify /etc/default/login file as

make commented # console=

2.put my laptops ip at both

/etc/inet/ipnodes and /etc/host file



still i can login via telnet/ftp through a DB9-serial cable, but when i tried
through a lan stratight cable directly connected that machine to my laptop;
cannot do. this is ultra A25 machine runned with solaris10.

please makes me ensure , where i am wrong. i am a newbie here.. I also got another suggestion as follows. is this okay?

-------------------------------------
By default , the solaris inetd deamon does not log the IP address of the machines that are connecting to Solaris Server . To enable the logging of all the IP addresses of machines connecting to the server and the connection time the following changes can be incorporated

1. cd /etc/init.d
2. vi inetsvc
3. Change the last line in the file, ie
/usr/sbin/inetd -s &
to /usr/sbin/inetd -s -t &

4. Stop and Start that script

./inetsvc stop
./inetsvc start

5. vi /etc/syslog.conf
6 . Add the following line
deamon.notice /var/adm/name_of_log_file ( the two fields should be seperated by tabs )

7. touch /var/adm/name_of_log_file
8. kill -HUP syslogd

After these changes are made all connections that are started through the inetd deamon ( Telnet , FTP ) etc will be logged to the new file created

This is also very useful for auditing purposes with NTP protocol enabled which gives us a consistent time throughout the enterprise, accountability can be implemented in the organisation.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Telnet Problem with Solaris (SunOS 5.7)

Hi, I have been facing a telnet problem with our SunOS 5.7 box. Initially we were facing porblems in login both from the console as well as through telnet. The machine was hard-booted after which login from console is possible, but telnet connection is not. The error that is displayed is... (1 Reply)
Discussion started by: manoj_gopal
1 Replies

2. UNIX for Dummies Questions & Answers

Installing Cable Modem on Irix Machine.

Ok I am new to this and wondering if there is any way of connecting a cable modem to an SGI that is running IRIX 6.5 and how to do it... (1 Reply)
Discussion started by: Acidjack
1 Replies

3. Shell Programming and Scripting

Solaris 9 - Ftp problem

I was wondering if anyone can help me out with a Solaris 9, FTP problem. The problem is this. One of our scripts recently attempted to send files to a MS server, using FTP, and some error occurred. Because the script didn't trap for errors we didn't know about the problem until things started... (3 Replies)
Discussion started by: BCarlson
3 Replies

4. Solaris

Solaris 9.0 (x86 on AMD Opteron) reboots after i FTP through Telnet

Hi All, I have installed Solaris 9 on on an AMD Opteron based server. The server is rebooting after i perform the following: - Logon to Solaris 9 AMD box through telnet or putty - ftp to any other box suppose box A where the FTP server is running - After logging in to the box A through... (1 Reply)
Discussion started by: jsvarma
1 Replies

5. Solaris

strange problem regarding zip/unzip from window to solaris machine

Hi , I faced a very strange problem when I unzip a zip file on my solaris workstation. Actually I wanted to transfer a folder, say it TEST which contains some sub-folders inside it from windows to solaris machine. So I zipped this folder to TEST.ZIP on my windows machine. Then from my... (11 Replies)
Discussion started by: Raj Kumar Arora
11 Replies

6. Solaris

Unable to login using ssh,telnet onto my solaris machine with solaris 10 installed

Hi, I am unable to login into my terminal hosting Solaris 10 and get the below error message "Server refused to allocate pty ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory " Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies

7. Solaris

installation problem solaris,windows,suse on same machine

Hi all, Previously I had both opensuse 11.3 and Windows XP SP2 on my PC, there was no problem at all.I was able to access all documents in Windows from opensuse. Now when I wanted to install solaris 10 on the same machine there were 2 problems ... 1. Windows is not accessible from solaris... (3 Replies)
Discussion started by: M.Choudhury
3 Replies

8. Hardware

Serial connection CAT5 instead of RS232 and Null Modem or Straight cable.

Hello, I want to connect a VT520 terminal to p3 linux box. I have two questions regarding the connection. First, is it possible to use RJ45 instead of RS232 cable. (with DB9 pin to RJ45 and DB25 to RJ45 converter). Second point is that; do i need null modem cable or straight cable... (5 Replies)
Discussion started by: vectrum
5 Replies

9. UNIX for Advanced & Expert Users

FTP While transfering files to local machine to remote machine

Hi Am using unix Ksh Am getting the problem while transferring zero size files through the script . When i transfer zero size files from local machine to remote machine manually i can able to do it . My question its beause of zero size files am not able to transfer through script ? or its... (2 Replies)
Discussion started by: Venkatesh1
2 Replies

10. Linux

Unable to connect to Server machine from a client machine using ftp service

Hi, Could you please help me with the below issue.. I'm running RHEL6 OS on both server (192.168.0.10) and client machines (192.168.0.1). I'm trying to connect to server from the client machine using ftp service. I have installed vsftpd daemon on both the machines. I'm getting... (4 Replies)
Discussion started by: raosr020
4 Replies
inetd.conf(4)						     Kernel Interfaces Manual						     inetd.conf(4)

NAME
inetd.conf, inetd.conf.local - The default configuration files for the inetd daemon SYNOPSIS
The default configuration file for all cluster members is: /etc/inetd.conf The configuration file for a specific member in a cluster is: /etc/inetd.conf.local The inetd.conf.local file is a Context-Dependent Symbolic Link (CDSL) and must be maintained as such. See the System Administration manual for more information. DESCRIPTION
If the inetd daemon is started without specifying an alternate configuration file, the inetd daemon reads the inetd.conf file and inetd.conf.local file, in this order, for information on how to handle Internet service requests. For this reason, if an entry exists in both configuration files, the entry in /etc/inetd.conf.local overrides the entry in /etc/inetd.conf. The inetd daemon reads its configuration files only when the inetd daemon starts or when the inetd daemon receives a SIGHUP signal. Each line in theinetd configuration files defines how to handle one Internet service request. Each line is of the form: ServiceName SocketType ProtocolName Wait/NoWait UserName ServerPath ServerArgs (Note: The backslash and the continuation of information on to a second line is for display purposes only. In the configuration file, the entries appear on a single line.) These fields must be separated by spaces or tabs. Continuation lines are terminated with a (backslash). Comments are denoted with a # (number sign). The fields have the following meanings: Specifies the name of an Internet service defined in the /etc/services file. For services provided internally by the inetd daemon, this name must be the official name of the service. That is, the name must be identical to the first entry on the line that describes the service in the /etc/services file. Specifies the name for the type of socket used for the service. You can use either the stream value for a stream socket, the dgram value for a datagram socket, the raw value for a raw socket, the rdm value for a reliably delivered message socket, or the seqpacket value for a sequenced packet socket. You can also use xstream and xdgram to permit the transparent mode of connections for stream and datagram sockets, respectively. Currently, only applica- tion gateways for firewall services use the transparent mode of connection. Specifies the name of an Internet protocol defined in the /etc/protocols file. For example, use the tcp value for a service that uses the TCP/IP protocol and the udp value for a service that uses the UDP protocol. When you use a tcp or udp value, inetd creates AF_INET sockets; this is the default behavior. If you want inetd to create AF_INET6 sockets, use the tcp6 or udp6 value. The inetd daemon maps these values to the tcp and udp protocol names internally. For RPC services the field consists of the string rpc followed by a slash (/) and one of the following: An asterisk (*) One or more nettypes One or more netids A combination of nettypes and netids If you specify an invalid nettype, it is treated as a netid. For example, if you specify rpc/*, it specifies the service uses all the transports supported by the system. Contains either the wait or the nowait instruction. For datagram servers, specify wait. This instructs the inetd daemon to wait for a datagram server to read at least one datagram from the socket before exiting. Single- threaded datagram servers process all incoming datagrams, then they time out (for example, comsat, biff, and talkd). Multithreaded datagram servers read one datagram from the socket, create a new socket, then fork and exit (for example, tftpd). For servers using stream sockets, specify nowait for multithreaded servers. This instructs inetd to accept connection requests and pass a newly accepted socket that is connected to the client of the service to the server. Specify wait for single-threaded servers. This instructs inetd to pass the listening socket to the server and wait. The server must accept at least one connection request before exiting. Specifies the username that the inetd daemon should use to start the server. This variable allows a server to be given less permission than root. Specifies the full pathname of the server that the inetd daemon should execute to provide the service. For services that the inetd daemon provides internally, this field should be internal. If you want to disable this service, this field should be disable in the /etc/inetd.conf.local file. Specifies the command line arguments that the inetd daemon is to pass to the server specified in ServerPath. The arguments to ServerPath should be just as they normally are, starting with the name of the program. For services that the inetd daemon provides internally, this field should be blank. EXAMPLES
The following are sample entries in the /etc/inetd.conf file for an inetd daemon that: Uses the ftpd daemon for servicing ftp requests on an AF_INET6 socket Uses the talkd daemon for ntalk requests on an AF_INET socket Provides time requests internally on AF_INET6 sockets ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd ntalk dgram udp wait root /usr/sbin/talkd talkd time stream tcp6 nowait root internal time dgram udp6 wait root internal How you enable and disable services in a cluster depends on the number of cluster members. The following two examples show the same clus- ter that has three members (0, 1, and 2), but shows two diferent methods to accomplish the same goal. Choose the method most suitable to your cluster environment. If you want to enable the ftpd daemon on all cluster members except member 2, do the following: To enable the ftpd daemon for all members, enter the following in the /etc/inetd.conf file: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To disable the ftpd daemon for member 2, enter the following in the /etc/inetd.conf.local for member 2: ftp stream tcp nowait root disable If you want to disable the ftpd daemon on all cluster members (the whole cluster), but enable it on members 0 and 1, do the following: To disable the ftpd daemon by default for the whole cluster, enter the following in the /etc/inetd.conf file: #ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 0, enter the following in the /etc/inetd.conf.local file for member 0: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 1, enter the following in the /etc/inetd.conf.local file for mem- ber 1: ftp stream tcp nowait root /usr/sbin/ftpd ftpd Member 2 does not have an ftpd entry in its /etc/inetd.conf.local file. Therefore, the ftpd daemon is not started. RELATED INFORMATION
Commands: biff(1), comsat(8). Daemons: inetd(8), talkd(8), tftpd(8). Files: protocols(4), services(4). delim off inetd.conf(4)
All times are GMT -4. The time now is 10:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy