Operating System - HP-UX
1753851 Members
7371 Online
108807 Solutions
New Discussion юеВ

ftp and traceroute failures.

 
derek b smith_1
Regular Advisor

ftp and traceroute failures.

I have a mcsg server (11.11) at 192.168.97.106 and .6 as the package Ip addr. I am trying to ftp to 10.100.211.100 and it is timing out. Yet I have another server (AIX 5.2) that is able to ftp and tractroute to this Ip. I have some log files so any help would be greatly appreciated.

The first entry show what is missing from my HPUX server

thanks
derek

2 REPLIES 2
Steven E. Protter
Exalted Contributor

Re: ftp and traceroute failures.

does the target server have a syslog?

If hpux /var/adm/syslog/syslog.log

This transaction could be blocked on an hpux target server with /var/adm/inetd.sec entries that prevent ftp.

What needs to be determined is is the transaction being stopped on the client or the server.

Firewalls blocking certain ip addresses can do this.

problems with dns names resolution can cause this(/etc/resolv.conf)

Wondering if ping will work.

Try doing things by ip address and not hostname to eliminate dns issues.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
derek b smith_1
Regular Advisor

Re: ftp and traceroute failures.

Sep,

thank you for your insight, but during these attempts I turned on verbose mode in inetd.conf as ftpd -v after a kill and a restart of inetd with not log results! : (
My resolv.conf is ok and not corrupt as it is pointing to the same DNS server as the AIX server. syslog show nothing and ping does not work. there is nothing in ftpusers or in the inetd.sec file. I do realize firwalls can do this but after the trace from a network sniffer I cannot beleive it is a firewall issue.


thanks again, derek