Re: Time out with securCRT 4.0 from Windows XP to RedHat linux

Michael Heiming wrote:
In comp.os.linux.misc Tony Lawrence <pcunix@xxxxxxxxx>:

Michael Heiming wrote:
In comp.os.linux.misc soup_or_power@xxxxxxxxx <soup_or_power@xxxxxxxxx>:
soup_or_power@xxxxxxxxx wrote:
Tony Lawrence wrote:
soup_or_power@xxxxxxxxx wrote:
Tony Lawrence wrote:
soup_or_power@xxxxxxxxx wrote:

I didn't have any problems with securCRT 4.0 running
on Windows XP until now. When I try to connect to the
RedHat linux server I get time out pop up. The sshd
was running on the linux server. I can ssh from
another linux server to this server in question. Can
someone please drop me a clue?


I got this following message from dig. I don't know if it is
successful. Thanks
$ dig -x

; <<>> DiG 9.2.2 <<>> -x
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12675

Any help please?

It means you don't have a DNS entry at all for, if
you had you should see some status like this:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24271

What you get is "NXDOMAIN". I'd suggest checking the DNS setting +
/etc/hosts on the Linux server you can connect from and adjust
your M$ box accordingly. Sound more like a problem with your doze
sw then a Linux problem.

No, he needs it on the Linux box he's trying to connect TO.

Indeed, sounds more likely, thx for your heads up. In any case it
seems his M$ box can't be resolved probably, sticking it in
/etc/hosts might help.


Another thought (easily checked with "arp" on the Windows box) would be
that Windows is confused and trying to go to some other machine.

Another possibility, running sshd in debug mode on the box he is
connecting to while watching the logs should give more clue, in
addition connecting with 'ssh -vvv ...' would help. But alas he
is using some doze software, I don't know and don't care about.

Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 73: Daemons did it

Many thanks for your kind help. The problem is solved now. I was using
a wrong subnet.