Rapport not pushing config?

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #125
    Avatarqmanol
    Member
    • Total Post: 3
    • Newbie

    Hi,

    I’m having some trouble with Rapport 4.4.1

    I’ve given it an XPSP2 box all to itself, as I’ve had all sorts of ridiculous problems with Rapport before, and knowing the need for hotfixes with 2003 server decided to give it the easiest environment possible.

    I installed IIS, IIS FTP, SNMP, and then let rapport do MDAC and SQL.

    At first, it would only detect machines via SNMP. So I did some digging, and added the DHCP option for the HServer agent to our main DHCP server. In addition, for some reason I had to put the .asp page to the top priority in the IIS default page list to get the HServer to validate in a diagnostic. I still cannot get any logs from it in the Rapport service logs window.

    I am trying to pull a configuration file from a 3235LE, (Which has registered with the HServer) and the job is just sitting in the scheduled tasks, even though it should have started immediately. Any ideas?

    #8651
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    OK, assuming its on a clean box with nothing else using IIS it should be straight forward.

    Are there any errors in the event log on the PC? In the rapport console if you right click on the master software resository and use test connection does it work? I have never seen changing the default page for IIS having an effect as rapport uses an ISAPI filter in the IIS root for comunications not web pages.

    Finally you can try droping an email to Wyse Tech Support and ask for the Rapport 4.4.1 hotfix rollup file HF04041032905.zip. This can fix a few problems with the hservice,

    Cheers,

    -TT

    #8652
    Avatarqmanol
    Member
    • Total Post: 3
    • Newbie

    OK, I have been away for a few days, and in the interim, it seems to have started working. I _hate_ when that happens.

    Now, however, the DHCP and TFTP logs are blank. DHCP is not (I think) an issue – I would rather modify our main DHCP server manually than rely on the rapport DHCP proxy.

    The only relevant error in the log was this warning: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

    The timestamp there seems to coincide with my config push/pull. I wonder if turning the DHCP off would help alleviate the issue? It’s also quite possible that discovery had not yet finished, and was choking the HServer.

    #8653
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, you have struck the reason why you should put Rapport on a server version of Windows – the inbuilt 10 concurrent connection limit of Workstation versions of Windows.

    Not much you can do to get around this, try discovering less devices also try the streams hack here:

    http://www.lvllord.de/?lang=en&url=tools&PHPSESSID=ba5daa5d703928da766182f495098bd6

    Really though use Windows 2003 without a SP, install Rapport and apply the SP1 to windows and you are away. I tend to use Rapport in VMware boxes so as to have clean machines without the hardware.

    -TT

    #8654
    Avatarqmanol
    Member
    • Total Post: 3
    • Newbie

    Unfortunately, we are not really in a position to use a 2003 box at this point – to say nothing of the issues involved of taking one of them offline for a while to rebuild. Basically, we had a spare XP box, and used it. I have no issue with this feature, as it’s only an issue in the first giant discovery.

    What I am now trying to find is a way for the XPe boxes to pick up the rapport server address from DHCP like the CE ones do. Is this possible?

    #8655
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    OK, the XPe boxes will use the same 186 option tag to update themseleves with the Rapport option tag. Once they are discovered they will re-boot once to update the terminal with the change and you are away. Have a look at the Rapport downloads section if you need a document on setting up the 186 option tag,

    -TT

    #8695
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    I have the same issue this thread originally started out with…devices not able to PXE boot though they seem discovered correctly as PXE capable. We have multiple vlans and i have been using ip helpers to help the devices find the rapport server (windows server 2003 sp1). Am able to register packages successfully, but the device fails to pxe boot and finish the task (pull or push). I’ve seen the articles on cisco switch issues and will look into this as we do use their gear…not sure if i can change anything without breaking something else, but we’ll see. Just throwing my experience into the forum and if anybody has any new insight, please respond as well.

    #8696
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    What device are you tring to PXE image? Currently you can PXE push/pull Linux and XPe devices only…

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