Ian:
Heya.
I'm having trouble connecting two systems via my own echoServer, and the
demo one. When I use my own echoServer, I get:
Quickly: what version echoServer? And, what's running on
the server and viewer side of the connection? If you have those
application and echoWare version strings, that always helps.
02Oct07 13:50:19 ========================================
02Oct07 13:50:19 Get new msg: sockfd=376, datalength=255
02Oct07 13:50:19 Get MSG_PROXY_FIND_PARTNER: m_socketfd=376,
userId=xxxxx, appId=0f??bbT???"_T{????E????N????????x?
Wild. I have seen errors like this before in the demo
echoServer logs, but they are usually transient errors that
never repeat. Was the Viewer client behind a web-proxy? If so,
what type of proxy?
The client responds with "Partner not found".
I can see why. :)
I also get the same problem with the demo echoServer, although, since I
can't see the logs, I can't verify that the same error is occuring.
I can: what's the userID you're trying to connect with?
I've also tried using echoVNC 2.1, and it worked, but when I attempt
to connect to my system behind my proxy, the screen never shows up.
Sorry: which side of the connection was running echoVNC 2.1?
And, was Vista involved?
Also, when attempting to connect through the echo servers, and the
systems are on the same subnet, I get Partner not found errors. When
I attempt direct connections and the system is behind a proxy, of
course, it doesn't connect.
Can you provide your echoServer log file, when the error
occurs?
Lastly, I'm a little confused about the use of the "UserID" field in
the echoVNC client and echoServer program. Is it the name of the user
set up in the echoServer, or is it the it the name of the system that
I'm identifying from the client? If I'm connecting multiple clients
to my echoServer, then they can't all have the same UserID, yet thats
the name that shows up as the connection when I connect to my server.
Here's how it works: when a client logs into an echoServer, it
provides a "userID request", and a password. Based onn the password, the
echoServer authenticates the connection. *After* it's authenticated, the
echoServer checks to see if the requested userID is unique. If it's not,
it appends a number to the end of the userID (whatever the lowest
number is that makes it unique), and then returns that actual userID
to the client. So, if a group already has "bob, bob1, bob2, and bob3"
logged in, if you try to login again as "bob", you will actually be
assigned the name "bob4".
This capability is supported in the 1.6x versions of the
Windows echoServer. The 1.6x version for Linux will be ready near the
end of this month.
cheers,
Scott-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
