Cannot ftp etc

[Carlo Henrico_1]

Can anyone help please. Until now have been able to ftp, telnet etc to server (L1000, 11.00) but suddenly been getting funny problem. If you try to ftp it says "Connect to servername." and after a long time times out.

Telnet also does not work.

[Tommy Palo]

To start with:
Can you still ping to the server from the machine you are trying to connect from ?

[Carlo Henrico_1]

Yes, I can still ping, and established sessions still remain in. No new sessions work.

Carlo

[Danny Engelbarts]

There's a number of possabilities here, check wether you can telnet to the machine from another server or PC on the same HUB, if you can there might be a problem on the network.
Otherwise check the network cables, or try a lanscan and see wether all the lan interfaces are up.

[Tommy Palo]

Turn on inetd connection logging:
# inetd -l

and check if you can see any traces of the connection attempt in the syslog (/var/adm/syslog/syslog.log)

[Michael F. Dick]

Hi,

you say it says connected to hostname.well, that means the connection actually made it through (the syn, syn-ack, ack). otherwise, you wouldn't see that message.

Besides checking the cables, hub, nic (which are a possebility), check your dns (it seems to be waiting for a reverse lookup). just put the host you are telneting from in the host file of the host you are telneting to.. if it works, you have a name resolution problem..

just my $02

Michael

[Danny Engelbarts · Accepted solution]

What are the results of pinging the machine?
Try to ping to the IP-address and to the hostname and see if both work. if ping hostname doesn't it's probably DNS.

Greetz, Danny.

[Rita C Workman]

It sounds very much like a lookup problem, especially since both ftp & telnet have same problem.
More than likely your nsswitch file goes first to files then to DNS....
I would run the nslookup command for both the IP AND then the servername...If you aren't getting the same results, then (and I believe this is the problem) your /etc/hosts file needs to be checked...it's either got a typo or it's out of order and hitting something else before it gets to the correct servername.
But you should see that when you run those nslookups.

Just a thought,

[Carlo Henrico_1]

It seems it was nothing to do with the server but rather our DNS server which was not too well - trust Micro$oft!