cancel
Showing results for 
Search instead for 
Did you mean: 

Login issue

 
fizan
Super Advisor

Login issue

team,

when i try to take a remote session the hp-server responds very slowy.

loginas: test1
it takes 120 secs for asking password.

passwd:

thanks.
8 REPLIES
Michal Kapalka (mikap)
Honored Contributor

Re: Login issue

hi,

it could be a problem with DNS or NIS issue.

mikap
fizan
Super Advisor

Re: Login issue

# cat /etc/resolv.conf
domain accrcb.corp
nameserver 160.173.16.4

when i am trying to ping to this ip it continously pinging, so i suggest no issues with the DNS.
Steven Schweda
Honored Contributor

Re: Login issue

> [...] remote session [...]

Which kind of "remote session"? Telnet?
RSH/remsh? SSH? ...???

> when i am trying to ping to this ip it
> continously pinging, so i suggest no issues
> with the DNS.

I suggest testing the DNS before deciding
that there are no problems with the DNS.

On the server, try:
nslookup


Or, try a Forum search for keywords like
slow telnet
and read some the very many old, similar
threads.
merieux
Frequent Advisor

Re: Login issue

Hi ,

Do you have some nfs file system ? what dmesg command return ?
fizan
Super Advisor

Re: Login issue

Dec 8 16:59
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 5.
0 sba
0/0 lba
0/0/1/0 hcd
0/0/1/0.1 hub
0/0/1/1 hcd
0/0/1/1.1 hub
probe: port 1 overcurrent 0x0
probe: port 2 overcurrent 0x0
0/0/1/2 ehci
0/0/2/0 side_ba
0/0/2/0.0 side
0/0/2/0.0.0 tgt
0/0/2/0.0.0.0 sdisk
0/0/2/0.0.7 tgt
0/0/2/0.0.7.0 sctl
0/0/2/0.1 side
0/0/2/0.1.7 tgt
0/0/2/0.1.7.0 sctl
0/1 lba
c8xx BUS: 2 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
0/1/1/0 c8xx
0/1/1/0.0 tgt
0/1/1/0.0.0 sdisk
0/1/1/0.1 tgt
0/1/1/0.1.0 sdisk
0/1/1/0.7 tgt
0/1/1/0.7.0 sctl
c8xx BUS: 3 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
0/1/1/1 c8xx
0/1/1/1.2 tgt
0/1/1/1.2.0 sdisk
0/1/1/1.7 tgt
0/1/1/1.7.0 sctl
0/1/2/0 igelan
0/2 lba
0/3 lba
0/4 lba
0/4/1/0 PCItoPCI
Initializing the Ultra320 SCSI Controller at 0/4/1/0/4/0. Controller firmware version is 01.03.35.69
0/4/1/0/4/0 mpt
0/4/1/0/4/0.2 tgt
0/4/1/0/4/0.2.0 stape
0/4/1/0/4/0.7 tgt
0/4/1/0/4/0.7.0 sctl
Initializing the Ultra320 SCSI Controller at 0/4/1/0/4/1. Controller firmware version is 01.03.35.69
0/4/1/0/4/1 mpt
0/4/1/0/4/1.7 tgt
0/4/1/0/4/1.7.0 sctl
0/4/1/0/6/0 iether
0/4/1/0/6/1 iether
0/6 lba
0/7 lba
0/7/1/0 asio0
0/7/1/1 asio0
8 memory
16 ipmi
128 processor
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/4/1/0/6/0
iether2: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/4/1/0/6/1

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x20000; start = 314208, size = 4194304
Starting the STREAMS daemons-phase 1
Create STCP device files
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2095104 Kbytes, lockable: 1480300 Kbytes, available: 1716828 Kbytes

#
dmesg output
fizan
Super Advisor

Re: Login issue

when i am taking telnet its gud fast and conecting immdeatly.
fizan
Super Advisor

Re: Login issue

nslookup to that ip is saying non-existent domain.
Bill Hassell
Honored Contributor

Re: Login issue

The 20 second delay is due to a DNS failure. The ping to the DNS server only indicates that the box is running. nslookup and nsquery must return the IP address *and* the hostname for your local machine (another system or your PC). Assuming you are using a PC and the PC's name is pc123 and the IP address is 12.34.56.78, then these 4 commands must return normal results:

nslookup pc123
nslookup 12.34.56.78
nsquery hosts pc123
nsquery 12.34.56.78

If any of this fails, your DNS server is not providing your PC's information and there will be a timeout (20-30 seconds) for every DNS server listed in /etc/resolv.conf. In other words, your DNS server is not accurate.


Bill Hassell, sysadmin