Re-Connect Errors

[Bridge_Bain]

On all WinXP machines I have tested, all have had the same issue. If disconnected or signed-off with out exiting the program, BBO will NOT EVER successfully re-connect. [it hangs at the (re)connecting message for as long as I do not kill the process.] It does not matter if it was BBO trying an auto-reconnect on its own, if I am returned to the “Login” window, or if I am returned to the “main menu” window. To get back on, I must EXIT the program completely and restart the client. I have not tested this on my Windows 2000/2003 systems. They are servers with restricted use. I have tested on other people’s WinXP system with the same result as on my systems. This “bug” has existed for several (possibly all) versions. It just was not critical enough to both to write about.

 

Thank you.

 

The Bain

 

Also posted under Suggestions for the Software. I am new, so I am not clear where to post this problem. Sorry.

[uday]

Hi.

 

You login, then click the back button until you logout and return to the 1st BBO screen (the one with the 3 huge buttons). Then you click login again, and it hangs?

 

This is not a prob w/all XPs , whatever it will turn out to be.

 

When you say "they are servers with restricted use" are you referring to the failing machines?

 

Is there anything unusual about your connection on the failing machines?

How are they connected to the internet? Are you using an account with restricted permissions ?

 

uday

[dogsbreath]

hi Uday..

I regularly have what sounds like a similar 'problem' .. never bothered to report it since there is an easy work-around and no-one else seemed to be 'suffering' from it.

.. If i get logged-off for 'inactivity', or occassionally when I lose connection, the client 'stub' Netbridgeview.exe does not 'die'' . Clicking on the BBO icon then starts a second instance of netbridgeview.exe. The symptoms are severe system degredation on my machine .. maybe different symptoms on other people's hardware.

 

After any 'unusual' disconnect I simply click up the Task Manager window and check for Netbridgeview.exe .. and kill the process(es) if it/they exist ..before attempting to re-connect to BBO .. this always fixes the problem.

The task-manager always shows 0 or close to 0 system-idle in this situation.

 

The first time I tried this, it took ages for the task-manager to appear (probably 'cos the machine thrashing!) and i had several copies of netbridgeview.exe running.. so a machine with a lower amount of RAM may behave differently I guess.

 

I'm usually connected from a P4 laptop with 1Gb RAM , XPpro with latest patch-set applied.

 

If i attempt to shutdown the machine when this situation does exist, i get a Windows error msg about the 'stub' and have to kill it manually ..unfortunately I dont have the exact msg to hand.. will look for it if it's important.

 

This looks like an XP error/problem to me since your server can hardly 'kill' processes on my machine.. I've seen similar situations on Unix servers when a client dies or terminates abnormally ..fixed by some TCP/IP config option .. maybe some difference in user's Windows config contributes to this issue but I have no expertise in this area ..

 

Rgds Dog