Stalling on “Searching for Interface”

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #241
    AvatarAnonymous
    Member
    • Total Post: 162
    • Jacked into The Matrix
    • ★★★★★★

    G’day

    First off, great site you have here, i’ve found the info provided so far to be really valuable.

    Ok

    We purchased a couple of Wyse V90 terminals for use in our environment. I’ve just installed Rapport v4.4.1 onto a standalone XP SP1 workstation.

    I am able to remote shadow/shutdown/reboot the units and that all appears to be ok. When I tell it to pull down an image via PXE – it schedules the job and reboots the device.

    The device then begins to load via PXE however it hangs on

    Contacting Server [400](02)
    Searching for Interface … +-(HTTP)

    and does nothing.

    I noticed in services that HServerInit is not started – if I start it, it just stops again although doesn’t give an error in event viewer. That said, I ran the diagnostics through Rapport and it verfies that HServer is running and ok (and I get a result when I go to http://192.168.0.1/hserver.dll?&V99)

    Both the Rapport server and terminal are on a private network with no firewalls or port blocking. I’m using DHCP Turbo so don’t think I need any special DHCP settings.

    What could I be missing here?
    Thanks!

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

    Just wanted to report back and let everyone know that the problem was fixed with a complete reinstall of Rapport.

    An interesting fact is that under C:inetpubftproot the config files and folder structure were not reinstalled to a sub folder called “rapport”, they were reinstalled directly into C:inetpubftproot

    According to the guys at WYSE, this folder structure and files should be in a folder called “rapport”

    However, as noted, it is fully working and I am able to push and pull images without a problem.

    Cheers

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

    For the record

    It wasn’t anything to do with the Web Server as the error message would suggest.

    As above, it was because the config files couldn’t be correctly located in the FTProot path.

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