sas user login session is very slow to open

[Jacques Carriere]

Good day,

I have 2 new server running sas,
1- rx4040 (4CPU 1299MHz /16Gb ram) slow logins
2- RP5405 (4CPU 650MHz / 16GB ram) fast logins

The difference in opening a sas user login session on both servers is quite different and extremely anoying. SAS users use Exceed to login and the difference in operning all the required SAS display screens could be 10-20 seconds. But, once you are logged in the sessions seem to be normal. The RX server is running HPux v2 11.11, and the RP HPux v1 11.11. Why this difference and can it be solved?

[Luk Vandenbussche]

Hi,

Our you sure your network settings are OK.
Is FTP speed to the server normal?

Is the switch port speed the same as the lan card?

You can check your lanspeed with

lanadmin -x 0

[Jacques Carriere]

yes the speed is ok

PA Risk server
Current Config = 100 Full-Duplex MANUAL (fast one)


Itanium server # lanadmin -x 0
Speed = 100 Full-Duplex.
Autonegotiation = Off. (slow one)

[Mel Burslan]

I am not familiar with SAS and its login and initial startup procedures but, if it is doing any kind of unix login authentication in this process, i.e., deciding if this user is authorized to login to this unix machine, using the password authentication method, you need to compare the networking settings of these two machines. And this is only valid, if both machines are running on the same local area network. If one is in Timbuktoo and the other one is here on your back yard, this may not be a good comparison but if they reside in the same data center and their networking is pretty much the same, you may need to consider comparing these files

/etc/hosts
/etc/nsswitch.con
/etc/resolv.conf

also make sure the routing tables are not wildly different (netstat -rn shows you the routing tables if you can not remember the command)

if you can provide more details, you can get more answers I am sure.

[Jacques Carriere]

the difference is only noticed when a sas user opens a session using Exceed.

[Mel Burslan]

is the fast server and the slow server are on the same subnet ?

[Bill Hassell]

Start testing without Exceed (Xwindows). Anything to do with Xwindows requires critical network and authentication features to work correctly. Try logging on to the slow server with telnet. Does it take 20-30 seconds to get a prompt? Then you have the classic DNS failure due to telnet authentication. The slow server is trying to validate the PC that is rying to connect and the DNS server in the 'slow' system cannot resolve the IP address of the PC into a name. This is especially common with Windows-based DNS servers (the admins don't understand that a reverse lookup is required for security).

Compare /etc/nsswitch.conf and /etc/resolv.conf on both machines. Then take the IP address of the incoming PC and use nslookup to see what name is provided for this IP address. If there is no record, then telnet will hang for about 20 seconds before giving a login prompt. To elminate the delay, the DNS servers need reverse lookup records for all DHCP as well as server addresses in the domain.

[Pete Randall]

On the fast server, put a "sleep 15" in /etc/profile. Then they will be the same and no one will complain anymore!

;%)


Pete