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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SCO OpenServer 5 Slow Login and Slow Spooling

Status
Not open for further replies.

coreysan

Programmer
Jul 24, 2006
7
US
I use a standard telnet connection to an in-house sco openserver 5 unix box to work on the command line using csh and ksh. I'm more of a DBA than a network admin guy, but I have been trying to figure out why it takes at least a minute before getting a login prompt through telnet, and why a print request would take about 1 minute to accept.

How can I begin to research this problem?

Thanks for any response!
 
takes at least a minute before getting a login prompt through telnet
The more likely is a DNS issue.
What happens if you telnet with IP address instead of hostname ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Another thing to check: is your telnet client station know by the SCO host ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Thank you so much for replying. I have been using a 3rd party telnet program called "PowerTerm," and I use the
actual IP address, but still get the problem.
In addition, we have a development pc with openserver5 that runs well, and when I attempt to telnet from the development pc to this one, I get the lengthy login problem.

Would you suggest I start reading up on DNS issues with a book, or is there something on the internet to introduce me to this whole thing?
 
Have a look at the /var/adm/syslog file.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886
 
Wow - I followed up on your advice about DNS, and found an internet article concerning the file /etc/resolv.conf.

I discovered that our nameserver ID was wrong!! When I changed it, the problem vanished!

Thank you VERY much for pointing me in the right direction.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top