Rapport Log Error

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #197
    Anonymous
    Inactive
    • Total Post: 161
    • Jacked into The Matrix
    • ★★★★★★

    Hi

    I’ve set up Rapport and it’s working fine, we’re using the Enterprise install and everything is looking well.. except I cannot seem to register an image from a device.

    I schedule a job, the 9455XL terminal reboots, gets an IP, starts the PXE boot and I see it all happening, then suddenly it reboots. The only inkling I have is the error in the log:

    [TFTP] – Read Error from xxx.xxx.xxx.xxx 2070 – closed session

    I’ve tried pretty much everything on the forums, installed all of the hotfixes and updates, set my permissions and so on. The funny thing is that it used to work 100% in testing. Has anyone seen this before – I am so close to making this work!

    Thanking You

    Craig

    #8849
    Anonymous
    Inactive
    • Total Post: 161
    • Jacked into The Matrix
    • ★★★★★★

    Hello again

    Since I posted a few days ago I think I found out what was happening here.

    I UDP scanned my subnet where Rapport resides. I found TFTP services running on some enterprise Unix hosts (seems that it was part of the default install on those, hmm). After getting these disabled, I could get the image to finally pull.

    I can only surmise the broadcast responses were getting lost somewhere with these other TFTP servers. I can’t be sure, but before checking I did other testing using free TFTP clients with Rapport. Sometimes I could grab files, other times it would time out. Now it seems OK.

    #8851
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Wow, awesome Craig. Thanks so much for the update. I would have never looked for rouge TFTP servers.

    Weird thing was today I had almost the same issue and it turned out to be that the network guys had forwarded every UDP broadcast from every VLAN to the Rapport server and it caused TFTP to fail (same message). Removing the forward all and just using the IP helper with a few ports fixed it.

    Don’t you love networking sometimes?

    Nice one!
    -TT

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.