Thanks for checking, and for tolerating my basic questions.
Since there are at least three pieces in the system (Viewer PC,
Remoted PC, and EchoServer), it's worth asking.
The "black screen" problem is, as you know, usually a fault
of how Windows deals with remote desktops, which conflicts with
VNC. So let's try this:
1. Please try connecting to the remote PC *from the same LAN*.
For example: use EchoVNC on PC1 on LAN1 to connect to PC2
on LAN2, and then open a VNC Viewer on PC2 and connect to
PC3, also on LAN2. It would be useful to know if PC3 is not
handling all VNC sessions, or just EchoVNC ones.
2. If you cannot connect to PC2 on LAN2 above, because of the
black screen problem, please adjust EchoVNC so that you can
use it to make Remote Desktop connections. Then connect to
PC2 with Remote Desktop instead of VNC. The downside of this
approach is that the remote user gets "locked out" and won't see
what's going on (they'll see a login screen). Again, this will help
isolate why VNC isn't working correctly.
I very much doubt it has to do with IP packet traffic. However,
to test this, please:
3. Adjust your echoServer so that it's listening to TCP 443 instead
of the default (TCP 1328). You'll need to add ":443" to the end of
the echoServer address to make it connect this way.
Please let me know if any of that helps.
cheers,
Scott
On Oct 20, 2008, at 8:47 PM, [EMAIL PROTECTED] wrote:
> Quoting "Scott C. Best" <[EMAIL PROTECTED]>:
>
>> 1. Exactly what version of EchoVNC do you have installed on
>> the remote-PC?
>
> LATEST means latest! Oh if you insist ;) latest as i can see here is
> EchoVNC 2.35 and Echoserver 1.65
>
>> 2. Exactly what flavor of Windows is running on the remote-PC?
>
> Didnt i mean Windows XP Professional SP2? version 2600... This
> helps? :)
> The same results are wit Windows XP Home edition SP2, where RDC is
> cutoff->
>
>> 3. Any chance that you're using Remote Desktop or Fast User Switching
>> on the remote PC? Those two things are famously incompatible with
>> any flavor of VNC, including EchoVNC.
>
> If problem was so simple i didnt waste my time to write it here,
> right?
>
> sory for ironics, but problems with those companies are killing me...
> My knowlegde is enough strong, to reject simple problems. Here I think
> I need to analyze TCP packets coming from remote PC to EchoServer, but
> TCP protocol knowledge is only basic... I can capture packets on our
> linux server, but wil this help???
>
>> thanks,
>> Scott
>>
>>
>> On Mon, 20 Oct 2008, [EMAIL PROTECTED] wrote:
>>
>>> Hi I found this amazing software on the web and planning to buy
>>> license of EchoServer.
>>> I was testing and using echovnc on most connections with
>>> EchoServer on
>>> my server. Everything works fine until ...
>>>
>>> We have some internet points which are managed by one Company
>>> "Alna"... This company uses VPN to connect all points to their
>>> domain
>>> server, and internet goes through web proxy, everything accept web
>>> over proxy is disabled... My organization uses specialized
>>> software to
>>> work so we asked this Company "Alna" to open some ports used by our
>>> spec.soft.
>>> In result this our software doesnt work properly (symptoms:
>>> connects,
>>> searches data in database, gets result, but when any data change is
>>> issued software cryes that connection is lost to database (over
>>> ports
>>> which they opened))
>>>
>>> The similar symptoms is with EchoVNC:
>>> connect through EchoServer:
>>> Status: Connecting...
>>> Status: Password requested
>>> after Logon
>>> Status: Password accepted
>>> Status: Connected
>>> Encoder ZRLE, Cache
>>> Speed: 0 kbit/s
>>>
>>> Traffic
>>> Bytes sent xxx
>>> Bytes Received after connection is static for example 119 bytes...
>>> Only when moving mouse data is sent to client, and mouse/keyboard
>>> actions is working on client but no data received from there ...
>>>
>>> I think those problems are connected, but the Company "Alna" and
>>> Internet provider wich gives VPN connection, are not generous and do
>>> not hurry to solve problem with our software...
>>>
>>> So, sorry for my english, but i hope you understand my problem, and
>>> maybe anyone know where the problem is? If I knew the problem then i
>>> can insist these companies to solve this.
>>>
>>> I am using EchoServer and EchoVNC latest versions. OS - windows XP
>>> Pro SP2
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
