Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
slow login
- Thread starter bitbybit
- Start date
Hi
Do you have DNS configured? I mean any entry is there in the /etc/resolv.conf?
If so check your network connections are proper and working fine.
If not do you have disk quota enabled ?
If so check your disk quota.
JSiva jsnair@lycos.com
Do you have DNS configured? I mean any entry is there in the /etc/resolv.conf?
If so check your network connections are proper and working fine.
If not do you have disk quota enabled ?
If so check your disk quota.
JSiva jsnair@lycos.com
Kat,
Well you could look at the /etc/motd file, cat it to make sure that it is not corrupted, I have seen that many times in the past.
Also examine /etc/profile and /etc/environment these files are executed post AIX login.
Best of luck.
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
Well you could look at the /etc/motd file, cat it to make sure that it is not corrupted, I have seen that many times in the past.
Also examine /etc/profile and /etc/environment these files are executed post AIX login.
Best of luck.
PSD
IBM Certified Specialist - AIX V4.3 Systems Support
IBM Certified Specialist - AIX V4 HACMP
We had this problem and found it was related to our DNS servers. They didn't want to mess with those, so what we did was in /etc added a file netsvc.conf with a line in it "hosts=local, bind" (without the quotation marks). Then added a line to /etc/hosts for every workstation accessing the server. This tells the system to check /etc/hosts first for name resolution.
Works for us because there are a relatively small number of workstations accessing this server (<50). And even if I forget to add a new workstation to /etc/hosts, it can still access, it just gets the slow login until I add it in.
Cheers, D.
Works for us because there are a relatively small number of workstations accessing this server (<50). And even if I forget to add a new workstation to /etc/hosts, it can still access, it just gets the slow login until I add it in.
Cheers, D.
We had this problem and found it was related to our DNS servers. They didn't want to mess with those, so what we did was in /etc added a file netsvc.conf with a line in it "hosts=local, bind" (without the quotation marks). Then added a line to /etc/hosts for every workstation accessing the server. This tells the system to check /etc/hosts first for name resolution.
Works for us because there are a relatively small number of workstations accessing this server (<50). And even if I forget to add a new workstation to /etc/hosts, it can still access, it just gets the slow login until I add it in.
Cheers, D.
Works for us because there are a relatively small number of workstations accessing this server (<50). And even if I forget to add a new workstation to /etc/hosts, it can still access, it just gets the slow login until I add it in.
Cheers, D.
No
I had a different kind of experience, when the network cable was damaged and there was an entry in the resolv.conf and if I login in the CDE it will wait a long time to get into the screen. If I remove the entry in resolv.conf it went fast. But in command line it worked fine even without the network connected and there was an entry in resolv.conf.
JSiva jsnair@lycos.com
I had a different kind of experience, when the network cable was damaged and there was an entry in the resolv.conf and if I login in the CDE it will wait a long time to get into the screen. If I remove the entry in resolv.conf it went fast. But in command line it worked fine even without the network connected and there was an entry in resolv.conf.
JSiva jsnair@lycos.com
- Status