tftp Transfer timed out-Ignite

[SM_3]

HostA#tftp HostZ
tftp>get /var/opt/ignite/INDEX
Transfer timed out.

I'm configuring an Ignite Server (Host Z)
I have followed the steps laid down in Ignite UX Startup Guide for SA, Chapter 1+2


I have searched upon this topic and found that others have similar problems.
I have a tftp entry in /etc/passwd
inetd.conf entry
moved the /var/adm/inetd.sec for time being

I can get the /var/opt/ignite/INDEX using tftp locally (using tftp localhost)
but not over the network
tftp Transfer timed out is what I get

This causes problems in Ignite GUI as well.

Can anyone help?

[Sridhar Bhaskarla]

Hi,

You would need to see if there is any firewall blocking the tftp.

Check if you can go through by using "telnet your_ignite_server 69".

Try from the servers that are in the same subnet as of the ignite server. Also check your /var/adm/inetd.sec or "tcp_wrappers's /etc/hosts.deny /etc/hosts.allow if you are using.

-Sri

[Bill McNAMARA_1]

Search for tftp in:

http://software.hp.com/products/IUX/faq.html

and verify your entries in the inetd.conf in particular.

Later,
Bill

[SM_3]

I can telnet to the Ignite server.

I have checked the entries in inetd.conf:

tftp dgram udp wait root /usr/lbin/tftpd tftpd /opt/ignite /var/opt/ignite/INDEX /var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd

[Sridhar Bhaskarla]

Hi,

"just telnet" to the server alone will not help. "telnet ignite_server 69" above meant connecting to your ignite_server at port 69. "tftp ignite_server" is not a valid test as it doesn't actually validate the tftp server.

Since you are able to do a "tftp localhost" and retrieve the INDEX file, I feel your inetd.conf file and general permissions are ok.

So, I believe it might be your firewall.

-Sri

[SM_3]

#telnet pilot 69
Trying...
telnet: Unable to connect to remote host: Connection refused

Mmm.

[SM_3]

we have a couple of machines on a LAN, with no firewall

[Sridhar Bhaskarla]

In fact, I was wrong to ask you to test the port 69 through telnet. It won't matter and my apologies.

What is your Server's IP in your ignite configuration?.

Do instl_adm -d > ignite.cfg

edit ignite.cfg and see what is listed there.

If it shows up a different address than your ignite server's IP, then you will need to correct it and reapply the config by using

instl_adm -f ignite.cfg


Please post your status,

-Sri

[SM_3]

# more ignite.cfg
# instl_adm defaults:
# NOTE: Manual additions between the lines containing "instl_adm defaults"
# and "end instl_adm defaults" will not be preserved.
server="168.141.170.99"
netmask[]="255.255.0.0"
#route_gateway[0]="192.168.254.254"
route_destination[0]="default"
# end instl_adm defaults.
run_ui=false
control_from_server=true

IP address looks ok

[Elli Wang]

SM:
Since it works for localhost, have you tried "tftp hostz" on hostz? Also double-check the name resolution of hostz on hosta.

Hope this helps.
Elli

[maros]

Hi SM,

Did you run inetd -c ?

You need to run this command for changes in inetd.conf to take effect.

Hope this helps.

Maros

[SM_3]

Yes tried:
Host A>tftp Host A
that works

did run inetd -c

all the other r commands work
but not tftp

[Elli Wang]

SM:
I though your Igntie server is HOST Z? Have you try "tftp hostz" on the HOST Z?
Are Host A and Z in the same subnet? Maybe try another server in the same subnet?

Elli

[SM_3]

Sorry
HostZ>tftp Hostz
>get /var/opt/ignite/INDEX
works

as does
HostZ>tftp localhost


BUT from another system
tftp transfer timed out

systems are on the same subnet

[Elli Wang]

SM:
If you are pretty sure there is no inetd.sec or other wrapper/filter (double-check) and the name resoultion is correct (tftp ip_of_HostZ from HostA). I'm out of ideas. Turn on trace when do tftp. Run a network trace. Have you tried another server besides HostA?

Elli

[SM_3]

yes tried from another server

What I should have said from the start was that I have 2 old machines, 705 + 710.

I'm looking into rbootd-hoping this is the solution.

nevertheless tftp should work at multi-user level

will let you know what happens

thanks

[Sridhar Bhaskarla]

Hi (Again),

Try setting up the server through Ignite GUI.
It's weird that you are able to tftp using the localhost but not from the remote host. Are you sure you are not using tcp_wrappers (hosts.allow|hosts.deny)?

(no more points please)

-Sri

[SM_3]

I have set-up the Ignite server ok via GUI


But client cannot read INDEX file using tftp.Error tftp timed out


I'll have to look at this later on, machine in different location.

Also I'll need to check if rbootd is running, since client cannot see Ignite Server.

I'm not using the wrappers.

Going over to location now.