09-03-2010
This might be the the server DNS setting problem. Assuming it can't reach a dns server, suggest is use your previous method to solve it
Quote:
"add IP address and machine name to /etc/hosts".
10 More Discussions You Might Find Interesting
1. Solaris
When I ssh to my box, an Ultra 5. I get prompted for password immediately. I enter it and have to wait sometimes a full minute for it to prompt for a password.
The same thing happens when i try to ftp to the box, it will say connected, but it takes forever to prompt for password, and... (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies
2. UNIX for Dummies Questions & Answers
Running open solaris on a e420 that I recently picked up. Having issues sshing to it from either of my Linux boxes as its very slow to login (from the solaris box to the linux box it connects just fine.
Here is the output of ssh -vvv. I have hightlighted where it seems the slowdown is. Does... (0 Replies)
Discussion started by: creedog
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Quick question, I'm messing about with a test box at work (system v)
Basically I telnet to the server.
Get the following :
SunOS 5.9
login: (my name)
Password: (my password)
Last login: Thu Feb..... yada yada
(At this stage it takes over a minute to come to display the... (5 Replies)
Discussion started by: kenny123m
5 Replies
4. Solaris
Hi All,
I have problem when i write my user name to login to my server late (about 10 min) to give me field of password
if u know how i can solve it?
Thanks (4 Replies)
Discussion started by: mass1123
4 Replies
5. Solaris
I'm facing a problem when trying to ssh to SUN servers with solaris OS,it takes a long time until prompted for password ..after connecting to the server everything work fine..how can I solve this issue??? (11 Replies)
Discussion started by: mm00123
11 Replies
6. Shell Programming and Scripting
I have some sample code that's supposed to ssh to another machine using Net::SSH::Perl, execute a command, and print
the output of that command. It's very basic, and it works. However, I noticed that upon logging in:
$ssh->login('username','password');
It takes roughly 10-13 seconds to... (2 Replies)
Discussion started by: mrwatkin
2 Replies
7. Solaris
Hi, I have the following issue, when I tried to login to an Openindiana remote server through ssh It takes to long to ask me for the password. So i tried -v and I realize that sshd hangs here " debug1: SSH2_MSG_SERVICE_ACCEPT received " for at least 2 minutes. Then I can log in and everything is... (2 Replies)
Discussion started by: piukeman
2 Replies
8. HP-UX
Hi experts,
We are getting slow ssh session connections at HP-UX 11.31 servers.
We have set the parameters that maybe will affect , and commented at other theads at config file sshd_config :
UseDNS no
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost no
GSSAPIAuthentication no.
... (7 Replies)
Discussion started by: SapBasisSystem
7 Replies
9. UNIX for Advanced & Expert Users
Version: Oracle Enterprise Linux 6.3
Running on VMWare Workstation
When I login to my Linux VM from putty, the third line prompting for password comes only after few seconds.
login as: root
Access denied
root@192.168.0.235's password: ---> It takes around 5 seconds to get this prompt
I... (1 Reply)
Discussion started by: John K
1 Replies
10. Red Hat
Hi all,
I´m replacing an old linux enterprise redhat 4.5 by a new one linux enterprise redhat 6.
In both I use rexec as a communication between the front end and the user.
In the old one, when the user connects, the communication establishes quickly (less than 3 sec). But in the new one, the... (1 Reply)
Discussion started by: mig28mx
1 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)