Telnet & Network issues 2

[eanda10]

I am running SCO Open server 5.0
as far as I know nothing has changed on my network but last week out of the blue when some of my users (NOT ALL !!) try telneting into my server there is a horrible delay close to 90 sec. before they get a log in prompt

I have brought down my whole network (all switches, computers, servers, printers, network copiers ) and am still having an issue

the users are on different segments of my network so I can't blame it on a switch going bad.

Does anybody a clue where I should go from here ?

 

[Annihilannic]

Try doing a reverse DNS lookup from your SCO server of one of the IP addresses these users are connecting from.

If it takes a long time to respond (regardless of whether the lookup is successful or not), that is most likely your problem. You'll then need to find out what's wrong with your DNS configuration.

Annihilannic.

 

[Annihilannic]

I probably should have said, to do a test lookup, type nslookup 1.2.3.4 where 1.2.3.4 is the IP address in question.

Annihilannic.

 

[eanda10]

Annihilannic -

I did a reverse lookup and got the following response I am not familiar with nslookup do know what I am looking at.

# nslookup 193.100.100.44
Server: ???.????????????.com
Address: 0.0.0.0

*** Request to ????.??????.com timed-out

NOTE: the ????? = just represent the our correct domain name

 

[Steve Bowman]

I have had this issue in the past and almost 100% of the time it IS dns related. I agree with Annihilannic. You did not say how long it took to get the nslookup reply. The issue is most likly the /etc/resolv.conf

the contents of mine is

domain ultraex.net
hostresorder local bind
nameserver 192.168.10.36

where nameserver is valid entry check to see if the dns address is responding correctly.

Steve Bowman
steve.bowman@ultraex.com

 

[eanda10]

do I have to reboot my server for this to take affect I pointed the /etc/reslov at my dns server

but I don't know why this started all of a sudden ?

 

[Steve Bowman]

Does not require a reboot you should at a #Prompt prompt be able to #ping

http://www.yahoo.com

and get replies if you do not the DNS is still not configured correctly another work around is to create a hosts file entry for all your workstations in /etc/hosts.

192.168.10.1 wk1
192.168.10.2 wk2
so on and so on for all WorkStations

Usally this only happens when the IP DNS Address is no longer valid. Did you make ANY other changes at all to the SCO or your Network?

Steve Bowman
steve.bowman@ultraex.com

 

[eanda10]

where would the sco DNS settings be besides /etc/resolv?

 

[eanda10]

Thank You Very Much !!!!!!

The problem is resolved