Error opening tftp (Timed out)

[Yadhu Tony]

Hello,

I installed a new router and trying to backup the initial configuration to our tftp server. But getting the error " %Error opening tftp://172.17.0.39/corporate-confg (Timed out)"

I can ping the tftp server from router. There is no firewall in between router and tftp server. Other network devices in the same subnet can upload / download from tftp server. Only this router can't use the tftp. I tried to install a seperate tftp server and tried but no hope with the freshly installed router. Router running config is attached. Please help me.

Regards,
Tony

[Leo Laohoo]

 maybe an AV.

I agree with John.  Maybe a mis-configured anti-virus could be the culprit.

[InayathUlla Sharieff]

Hi,

I believe the TFTP server is able to reach the router.

At this point you are left with the following options:

-Take a packet capture on your pc

-run a netstat -an on the pc

-Then run the command on the router, let it timeout and look at the packet capture.

I suspect you will not see anything regarding TFTP port and hence this will mean that either you have a FW on the PC either somewhere along the path between your switch and your PC.

If you see TFTP communications, post the packet capture, if you don't fix your FW issues.

Regards

Inayath

[InayathUlla Sharieff]

BTW,

R u able to push any config from your router to TFTP server?

[Yadhu Tony]

Hi Inayath,

Thank you for the reply.

Yes, TFTP server is able to reach the router.

This is what I did before capturing the packets:

CORPORATE#copy running-config tftp:

Address or name of remote host []? 172.17.0.84

Destination filename [corporate-confg]? RunningConfig.txt

.....

%Error opening tftp://172.17.0.84/RunningConfig.txt (Timed out)

Please see the packet captured during TFTP transfer.

Frame 88: 68 bytes on wire (544 bits), 68 bytes captured (544 bits)

Ethernet II, Src: Cisco_4e:16:e0 (50:57:a8:4e:16:e0), Dst: Pegatron_1e:e0:bc (70:71:bc:1e:e0:bc)

Internet Protocol Version 4, Src: 172.17.0.5 (172.17.0.5), Dst: 172.17.0.84 (172.17.0.84)

User Datagram Protocol, Src Port: 55701 (55701), Dst Port: tftp (69)

Trivial File Transfer Protocol

No.     Time        Source                Destination           Protocol Length Info

     89 7.028513    172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 126: 82 bytes on wire (656 bits), 82 bytes captured (656 bits)

Ethernet II, Src: Smartlin_05:37:c3 (00:17:7c:05:37:c3), Dst: Pegatron_1e:e0:bc (70:71:bc:1e:e0:bc)

Internet Protocol Version 4, Src: 172.17.0.6 (172.17.0.6), Dst: 172.17.0.84 (172.17.0.84)

Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info

    127 11.971420   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 131: 106 bytes on wire (848 bits), 106 bytes captured (848 bits)

Ethernet II, Src: Cisco_4e:16:e0 (50:57:a8:4e:16:e0), Dst: Pegatron_1e:e0:bc (70:71:bc:1e:e0:bc)

Internet Protocol Version 4, Src: 172.17.0.5 (172.17.0.5), Dst: 172.17.0.84 (172.17.0.84)

Transmission Control Protocol, Src Port: ssh (22), Dst Port: 12098 (12098), Seq: 105, Ack: 1, Len: 52

SSH Protocol

No.     Time        Source                Destination           Protocol Length Info

    132 13.028167   172.17.0.5            172.17.0.84           TFTP     68     Write Request, File: RunningConfig.txt, Transfer type: octet

Frame 132: 68 bytes on wire (544 bits), 68 bytes captured (544 bits)

Ethernet II, Src: Cisco_4e:16:e0 (50:57:a8:4e:16:e0), Dst: Pegatron_1e:e0:bc (70:71:bc:1e:e0:bc)

Internet Protocol Version 4, Src: 172.17.0.5 (172.17.0.5), Dst: 172.17.0.84 (172.17.0.84)

User Datagram Protocol, Src Port: 55701 (55701), Dst Port: tftp (69)

Trivial File Transfer Protocol

No.     Time        Source                Destination           Protocol Length Info

    133 13.028426   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 184: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)

IEEE 802.3 Ethernet

Logical-Link Control

Internetwork Packet eXchange

IPX Routing Information Protocol

No.     Time        Source                Destination           Protocol Length Info

    185 17.973359   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 236: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)

Ethernet II, Src: Cisco_af:3d:ae (64:9e:f3:af:3d:ae), Dst: Broadcast (ff:ff:ff:ff:ff:ff)

Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info

    237 23.073258   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 277: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)

Ethernet II, Src: Micro-St_9f:b1:ba (00:24:21:9f:b1:ba), Dst: Broadcast (ff:ff:ff:ff:ff:ff)

Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info

    278 28.173310   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 309: 70 bytes on wire (560 bits), 70 bytes captured (560 bits)

Ethernet II, Src: HewlettP_f1:6d:db (b4:b5:2f:f1:6d:db), Dst: Pegatron_1e:e0:bc (70:71:bc:1e:e0:bc)

Internet Protocol Version 4, Src: 172.17.0.28 (172.17.0.28), Dst: 172.17.0.84 (172.17.0.84)

Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info

    310 33.173138   172.17.0.84           172.17.0.5            TFTP     46     Acknowledgement, Block: 0

Frame 363: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)

Ethernet II, Src: Ibm_c1:82:9c (e4:1f:13:c1:82:9c), Dst: Broadcast (ff:ff:ff:ff:ff:ff)

Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info

    364 38.273610   172.17.0.84           172.17.0.5            TFTP     63     Error Code, Code: Unknown (9), Message: Timeout occured.

No, I am not able to push any config from router to TFTP server.

Regards,
Tony

[avi]

Hi yadhu,

The running configurattion will be save in nvram: & not in flash:

Please see the your configuration files name in nvram: by dir nvram:

Then copy this file,

Please post the command dir nvram:

[InayathUlla Sharieff]

Hi Yadhu,

Can we try using the FTP or Solarwinds software?

In regards to the TFTP these are the only options when we have bidrectional connectivity from PC to device.

Few things which we check are:

->Verify that the TFTP server is open on your PC. Also, make sure the file is in the root directory (from the TFTP application software menu bar, choose View > Options).

-> Make sure the file is in the root directory of the TFTP server and they you have entered the correct filename. (Make sure of characters in that file).

->Try to eliminate extraneous networking complexities between the router and the TFTP server, such as hubs and switches, or reduce the hop count between the router and server. This may involve moving the TFTP server or setting up a new server on a network segment topologically closer to the router, or on the same LAN segment as the router.

->This issue can also occur if the file size is larger than 16MB since the Cisco IOS TFTP client cannot transfer files larger than 16MB in size. For more information, refer to the document Cisco IOS TFTP Client Cannot Transfer Files Larger than 16MB in Size.

->Finally, if these actions fail to resolve the problem, try to use different TFTP server software or use FTP.

-> Try to use any laptop which doesn have AV installed or upload solarwinds and check the same.

HTH

REgards

Inayath

[Yadhu Tony]

Hi Inayath,

Thank you for your help. 

As you suggested I tried FTP instead of TFTP. The same result occured, only this particular router can't write file in ftp server but other devices can do that. I tried with all the possible ways that you have mentioned on your  post but still the router is giving the same result. I am sure that this have something to do with the router because I used several systems, TFTP servers and connections.

Since it is urgent I used a USB thumb drive to copy files to the flash and that only worked out. I am going to open a TAC request to check with this issue. Thanks again for your time.

Regards,
Tony

[Harish Kumar Khanchandani]

I had the same issue. Do the following to resolve the issue :

1. Create the Inbound firewall rule on desktop. Allow the UDP port 69

2. Configure ip tftp source-interface GigabitEthernet in global mode

3. issue the command copy tftp: flash instead of copy tftp:/x.x.x.x/x.x.x.x.bin bootflash:

[CT2NCMike]

Anyone get this figured out?  We have two 3560s, configured identically.  I can copy the new code version from TFTP on switch-2 but not switch-1.  It just times out.  I can ping the TFTP server and I can copy a txt file no problem but when we try to copy the code, it times out.  Firewalls aren't the issue.  I've tried renaming the file, re-downloading the file from Cisco, etc. 

[nikhil kumar1]

Changed  PKTTIMEOUT = 99999999 and it worked for me. I was in trouble since yesterday. But it worked with ASA 5508 in ROMMON mode.

[SHIBI V DEV]

From same PC have you tried to copy RunningConfig from any other router or Switch?

[jay.johnson1]

I'm sure you've figured this out by now, but in the event you want to disregard the messages in the future, you can always type "no service conf" from a global command prompt.

Jay

[04Davies_A01]

This maybe a bit obvious but is the box the tftp server is sitting on multi-homed?

I had issues with tftpd listening on the wrong interface even though the correct one was selected, I practically ripped my hair out sorting that one out, but Nmapping the box tftpd was on revealed that indeed it was listening on the wrong interface, my resolution was to remove  tftp's install files *properly*, reboot then reinstall, its been working fine since, -hope that helps

[Vi2]

I am new to the CCENT track and up to the point where I start backing up my IOS.  I ran into this same problem and after disabling my firewall it immediately worked. Which Windows version do you have and how did you go about disabling your firewall (forgive me for asking but I like double checking).  If you have already found a solution just let me know.

[glendale101]

The tftp server could be blocked from within the Cisco device.  Check for any acl that might cause this.

#show ip access-lists

#show ip access-lists interface gigabitEthernet 0/0

etc