>From: Scott Best Sent: Sunday, June 12, 2005 4:17 PM > Heya. A lot of Win98 users are seeing the same issue you are >(including the machines I've tested it on). Thanks for the update.
> In the meantime, please try this: instead of using your Windows >echoServer, please try using the Linux echoServer at the demo site Did it. It worked...connected through the demo site. Just about 20 minutes ago +/-. But you know... I didn't think through this very well...and had a revelation today at work when I tried it. It's not a programming issue for you (maybe a future feature though?). Here's what happened: I brought the "good" machine (W2K, the one that I had working yesterday from home) into work. The problem, though is that nothing goes directly out -- everything goes through the proxy server. So I plugged this "foreign" machine into the network and had to put the proxy server into the browser to even get it to Google. But I tried echovnc anyway, and of course it couldn't see 65.2.150.32 (or whatever my bellsouth DSL was at the moment - stay at home moms are good for something!). The machine was there because I could hit the web server on my bellsouth DSL machine, but only AFTER I answered a userid/password/domain prompt from the browser/proxy server. So not only would the echovnc app have to allow for a proxy server, it would also have to handle the domain userid password challenge. Sounds like a big job to me. --Dale-- ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
