|
| Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free! |
telnet
|
Original Message
|
Name: ml
Date: November 2, 2001 at 02:01:07 Pacific
Subject: telnet
|
Comment: hi all when i telnet machine B from any solaris machine as $telnet (ip of machine) i received following message telnet: Unable to connect to remote host: Connection refused but i am doing telnet from to machine B to any solaris machine regards
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: prashant shah
Date: November 5, 2001 at 21:46:04 Pacific
|
Reply: Well, comment the line out of Console = /dev/console in the /etc/default/login. best wishes.
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: ripon
Date: November 11, 2001 at 03:12:12 Pacific
|
Reply: Hi there, commenting out “CONSOLE=/dev/console” in /etc/default/login file will allow remote login by root, but will compromise the security. By default, root is not used for remote login. While trying telnet to your machine B, did you use “root” account from other machines? If you were using “root” account while connecting to other machines from machine B, then probably /etc/default/login file in all your machines (except B) is like “#CONSOLE=/dev/console”. This “CONSOLE=/dev/console” line works on “root” account only for remote login. If you were trying, using non-root account for telnet and you could not login to machine B from other machines, please check the existence of a file named /etc/nologin in machine B. If this file exists in your machine (probably B), you would not be able to login to that machine via telnet using non-root account because right after entering the passwd, your connection would get closed by foreign host.
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: Mark M
Date: November 26, 2001 at 22:46:06 Pacific
|
Reply: If you're telnetting to the machine and just getting connection refused then this means that the machine is not accepting the incoming connection....(or most likely). Is the telnet service commented out in /etc/services by any chance? Can you ping out or connect to anything else from the machine that you're having a problem connecting to? Maybe someone's remapped the telnet port to something else? :) or maybe a windoze box has the same IP on the network as the nix box and is the one refusing a connection (seen this before). the /etc/default/login CONSOLE line only determines whether or not root login can be done remotely from a session. If you're not getting at least a Login: prompt then the problem is something more fundamental. on the problem machine perhaps do an ifconfig -a to see if everything looks okay, and also check that inetd is running. Also check /etc/inetd.conf to see if telnet is enabled, and also /etc/init.d/inetsvc for any anomalies (ie check that the bottom line isn't commented out). Maybe posting a bit more info would help. Are you running through a router, what IP ranges etc etc.. HTH Mark
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Gary Wilcox
Date: December 28, 2001 at 16:33:11 Pacific
|
Reply: I ran into a similar problem, where I couldn't telnet to my machine, after installing redhat Linux 7.2. It turned out that RH Linux 7.2 uses xinetd in place of inetd, and that the RH 7.2 release has all xinetd services disabled as the default. I just went into /etc/xinetd.d/telnet and changed "disable = yes" to "disable = no", rebooted my machine, and my machine started accepting telnet connections. Hope this helps, --Gary
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: Shashikant Sarada
Date: March 12, 2002 at 13:54:42 Pacific
|
Reply: I ran into a similar problem, where I couldn't telnet/ftp to my machine, I installed RH Linux 7.1. I know that RH Linux 7.1 has xinetd services disabled as the default. I just went into /etc/xinetd.d/telnet and changed "disable = yes" to "disable = no", rebooted my machine, and still problem persists. Please help, sarada
Report Offensive Follow Up For Removal
|
|
Response Number 6
|
Name: EBC
Date: March 30, 2002 at 10:43:06 Pacific
|
Reply: I have 2 machines connected as peer to peer. Machines are Solaris and Win2000. I could ping both servers respectively but when I try to telnet from the win200 box I get "Could not establish connection". I checked /etc/services and telnet is not commented out. All ip's are unique to each other. (Solaris Machine is .1 and Win200 is .2) I chceked ifconfig -a and I see loopback UP and hme0 (this is my nic) UP too. I checked /etc/inetd.conf and telnet is not commented out and telnet is running. To test my telnet, I consoled in to the solaris box and telnet to the "localhost" and I got in. This tells me that telnet services is running. I checked the last line of /etc/init.d/inetsvc if it is commented out and it wasn't.
So does anybody have any idead about this problem.
Report Offensive Follow Up For Removal
|

Post Locked
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
Go to Solaris Forum Home
Results for: telnet
Putty ssh and telnet failed Summary: Hi, When I use hub to hub solaris box and w2k box together, and I use static ip 192.168.1.1 on w2k box, on solaris /etc/hosts.allow set up ip 192.168.1.1. I can use putty for ssh and telnet. I assume ... www.computing.net/answers/solaris/putty-ssh-and-telnet-failed/3150.html
can't access the solaris by telnet Summary: Hai! everybody! We have a Sun Fire V100 server powered by solaris 9. Evryday morning,I can't access it by telnet .but before I go home I can do access it by telnet. when I press the keyboard ,the cons... www.computing.net/answers/solaris/cant-access-the-solaris-by-telnet/3354.html
Telnet problem Summary: I have 2 machines connected as peer to peer. Machines are Solaris 8 and Win2000. I could ping both servers respectively but when I try to telnet from the win200 box I get "Could not establish connecti... www.computing.net/answers/solaris/telnet-problem/1404.html
|
|

|