Sponsored Content
Full Discussion: Telnet failed to localhost.
Top Forums UNIX for Beginners Questions & Answers Telnet failed to localhost. Post 303011618 by drysdalk on Saturday 20th of January 2018 05:50:56 PM
Old 01-20-2018
Hi,

Port 514 is the port for the syslog service, as you seem to have already determined. However, in those instances where a local logging service is configured to listen for incoming connections on port 514 it almost always uses UDP rather than TCP, so you can't test this by attempting to telnet to the port.

Exactly how you'd configure this all to work depends on your exact version of UNIX/your Linux distribution, what software you're using for logging, and of course if there is some external firewall that could be in the way even if your own local firewall definitely is not. But the best way to test it is to try to generate a logged event on a remote system that you have configured to log to your syslog server, and see if something gets logged or not.
This User Gave Thanks to drysdalk For This Post:
 

10 More Discussions You Might Find Interesting

1. Linux

apache@localhost.localdomain

Hello, I am ltrying to find the config file to modify a parameter for apache (I guess). Here, when sending mail using php web form I get a copy of all mail sent from that form, but here is a sample of what I get : From : apache@localhost.localdomain To : myemail@host.com Subject : Mail ... (2 Replies)
Discussion started by: qfwfq
2 Replies

2. UNIX for Advanced & Expert Users

localhost problem!

hello guys, this morning when I start my pc (gentoo) I get some strange errors about localhost. "Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName" ... Apache the same for my aplications, I have to use the full address of my pc instead of... (1 Reply)
Discussion started by: georgeplus
1 Replies

3. Ubuntu

fail to telnet localhost 106

Hi folks, Ubuntu 7.04 server amd64 On running; $ telnet localhost 106 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused $ netstat -an | grep 106 $ sudo netstat -an | grep 106 both no printout Pls advise where shall I check and how to fix... (22 Replies)
Discussion started by: satimis
22 Replies

4. Shell Programming and Scripting

Webpage to Telnet via Perl and Expect: Telnet problem?

Somewhat long story: I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage. This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies

5. UNIX for Dummies Questions & Answers

Can't Open Display localhost:0.0

I'm trying to connect to my linux server but I'm having some major problems. The server had OEL 5 installed and my local pc is running Windows XP. I'm using PuTTy to connect to the server with Xming running on my loacl machine. I login as root and run the following command - export... (5 Replies)
Discussion started by: garethnsolomons
5 Replies

6. UNIX for Advanced & Expert Users

DIG uses localhost

Hi, I have these entries in the /etc/esolv.conf: ------------ domain xxxxxx search yyyyyy nameserver 127.0.0.1 nameserver aaaaaaaaaaaaaaaa nameserver bbbbbbbbbbbbbbbb ------------- When I use 'dig' or 'nslookup' command, like 'dig yahoo.com' it uses the localhost as the server. I... (2 Replies)
Discussion started by: chaandana
2 Replies

7. Solaris

Timeout: No Response from localhost

Hi All! I having an issue when trying to run snmpwalk, so the following command it returns an error: bash-3.00# /usr/sfw/bin/snmpwalk -v 2c -c public localhost sysDescr.0 Timeout: No Response from localhost bash-3.00# I have checked also: bash-3.00# svcs -a | grep sma online ... (2 Replies)
Discussion started by: fretagi
2 Replies

8. Debian

Waiting for localhost.

I am getting the message - waiting for localhost. Here are some diagnostic steps I have tried .... root@meow:/home/ethan# cat /var/www/cgi-bin/httpd.conf ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/jkj ServerName 127.0.0.1:80 Listen xx.xx.xx.xx:80 Listen 127.0.0.1:80 ... (1 Reply)
Discussion started by: Meow613
1 Replies

9. Shell Programming and Scripting

Cannot find localhost

I get a "not found" error from this localhost/choice.php ethan@meow:~$ ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.025 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.036 m and this ethan@meow:~$ mysql -u... (4 Replies)
Discussion started by: Meow613
4 Replies

10. Shell Programming and Scripting

Tcl / expect need to attempt telnet if failed ssh

Morning and Happy New Year to all. I am in a situation where I need to connect to a list of devices that are using either telnet or ssh. I want to try to telnet, if I receive any of the following I want to attempt ssh : "Connection refused" "Connection timed out" timeout expiration ... (3 Replies)
Discussion started by: popeye
3 Replies
rpc.nfsd(8)						      System Manager's Manual						       rpc.nfsd(8)

NAME
rpc.nfsd - NFS server process SYNOPSIS
/usr/sbin/rpc.nfsd [options] nproc DESCRIPTION
The rpc.nfsd program implements the user level part of the NFS service. The main functionality is handled by the nfsd kernel module. The user space program merely specifies what sort of sockets the kernel service should listen on, what NFS versions it should support, and how many kernel threads it should use. The rpc.mountd server provides an ancillary service needed to satisfy mount requests by NFS clients. OPTIONS
-d or --debug enable logging of debugging messages -H or --host hostname specify a particular hostname (or address) that NFS requests will be accepted on. By default, rpc.nfsd will accept NFS requests on all known network addresses. Note that lockd (which performs file locking services for NFS) may still accept request on all known network addresses. This may change in future releases of the Linux Kernel. -p or --port port specify a diferent port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049. -N or --no-nfs-version vers This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support both NFS version 2,3 and the newer version 4. -s or --syslog By default, rpc.nfsd logs error messages (and debug messages, if enabled) to stderr. This option makes rpc.nfsd log these messages to syslog instead. Note that errors encountered during option processing will still be logged to stderr regardless of this option. -T or --no-tcp Disable rpc.nfsd from accepting TCP connections from clients. -U or --no-udp Disable rpc.nfsd from accepting UDP connections from clients. nproc specify the number of NFS server threads. By default, just one thread is started. However, for optimum performance several threads should be used. The actual figure depends on the number of and the work load created by the NFS clients, but a useful starting point is 8 threads. Effects of modifying that number can be checked using the nfsstat(8) program. Note that if the NFS server is already running, then the options for specifying host, port, and protocol will be ignored. The number of processes given will be the only option considered, and the number of active nfsd processes will be increased or decreased to match this number. In particular rpc.nfsd 0 will stop all threads and thus close any open connections. NOTES
If the program is built with TI-RPC support, it will enable any protocol and address family combinations that are marked visible in the netconfig database. SEE ALSO
rpc.mountd(8), exports(5), exportfs(8), rpc.rquotad(8), nfsstat(8), netconfig(5). AUTHOR
Olaf Kirch, Bill Hawes, H. J. Lu, G. Allan Morris III, and a host of others. 7 Aug 2006 rpc.nfsd(8)
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy