Hi,

Did a deja search, searched the Boinc wiki, and searched the Boinc/SETI web
boards, but only found a few vague references to this problem by others.

This is with the newest Windows Boinc,  (5.2.13).   Its more of an annoyance
than anything else, but would be nice to figure out what the problem is.

With Windows Boinc 5.2.13, after I bring up "Select Computer" from the menu
bar and try to enter a hostname, Boinc either locks up or become very
sluggish.  By "sluggish", I mean when there is a very long delay between
entering a character in the field and when it displays.  It might be like a
minute per character.  After the hostname is put in, it takes a good five
minutes to actually connect.  Most of the time, it doesn't get that far
though, it just locks up entirely.

All the computers across the LAN are config'd correctly.  All the
remote_hosts.cfg files are setup the way the should be.  All the
gui_rpc_auth.cfg files are the way I want them to be.  I'm not doing
anything exotic other than TCP/IP and file sharing, and don't have any other
protocols running.  None of the software firewalls should be causing any
problems either.   Everything is setup correctly.

All other network (LAN) applications work beatifully, including "add-on"
type stuff for Boinc -- even applications that allow remote management of
Boinc across a network.  Its only Boinc itself that has a problem.

I had this problem in the past (also with 5.2.13) and "cleared it" by
re-installing Boinc.  This time, re-installing didn't fix it.  Before
re-installing, I even went through the registry by hand to delete everything
Boinc related, such as the MRU lists.  Never had this problem before 5.2.13

The only recent network change that I made was "retiring" one of my
computers.  When they "retire", they get wiped clean, Linux installed, and
go into a closet to join the other "retirees".  Then on, they are mainly
just file servers -- but also run Boinc.  I really don't think this had to
do anything with Boinc on the windows computers though, because Boinc
continued to work fine for a couple weeks afterwards.

All the Linux computers have Boinc installed as a user (boinc).  They are
all running Samba.  I have no problems at all seeing them from the Windows
computers, or seeing the Windows computers from the Linux computers.   I can
even ssh into any of them and bring up the Boinc GUI, exporting the display
to the Windows computers (using XManager as the X11 server on the Windows
computers) with no problem.  All of them can show the Boinc stats of
anything on the network and work beautifully.

Its just the Windows Boinc that gives problems.  (WinXP and Win98).   Both
Windows computers are completetly malware free.  Network is config'd
correctly and runs beatifully.  All the software/hardware firewalls are
config'd correctly.   Everything works across the network, except Boinc's
"remote management" coming from Windows.

Its not a major issue, as on one of Linux boxes, I have BoincPHP-GUI
installed and running (using Apache httpd) -- which allows remote Boinc
configuration using just a web browser.  It also can be pointed towards any
other computer running Boinc on the network.  (Yes, it is secured.  The
httpd can only be accessed on my LAN.)  I actually like the web approach
better than pulling up a Boinc client, but why the Boinc client (Windows)
locks up is bugging me.

Anyone have this problem also?

Thanks!