Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem?
On Sat, 2011-10-15 at 20:38 +0200, vasek@spsmb.cz wrote:
Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem? <snip> I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John
Dne 15.10.2011 20:56, John A. Sullivan III napsal(a):
On Sat, 2011-10-15 at 20:38 +0200, vasek@spsmb.cz wrote:
Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem? <snip> I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package).
On Sat, 2011-10-15 at 22:40 +0200, vasek@spsmb.cz wrote:
Dne 15.10.2011 20:56, John A. Sullivan III napsal(a):
On Sat, 2011-10-15 at 20:38 +0200, vasek@spsmb.cz wrote:
Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem? <snip> I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John
<snip>
I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). <snip> Hmm . . . smells like libssh. I wonder if it's related to another problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John
Dne 15.10.2011 23:01, John A. Sullivan III napsal(a):
Dne 15.10.2011 20:56, John A. Sullivan III napsal(a):
On Sat, 2011-10-15 at 20:38 +0200, vasek@spsmb.cz wrote:
Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem? <snip> I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John
<snip> I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). <snip> Hmm . . . smells like libssh. I wonder if it's related to another
On Sat, 2011-10-15 at 22:40 +0200, vasek@spsmb.cz wrote: problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
x2go client 3.99.0.1 under ubuntu (with new libssl) works, but not under windows.
On Sun, 2011-10-16 at 03:52 +0200, vasek@spsmb.cz wrote:
Dne 15.10.2011 23:01, John A. Sullivan III napsal(a):
Dne 15.10.2011 20:56, John A. Sullivan III napsal(a):
On Sat, 2011-10-15 at 20:38 +0200, vasek@spsmb.cz wrote:
Hello,
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed. I use debian squeeze and x2go server from http://packages.x2go.org/debian.
3.01.18 under ubuntu with no problem
Where is the problem? <snip> I've noticed the exact same thing. I assumed it was because I am using 3.0.1-5 on the server side and there was a backwards compatibility issue so I postponed investigation until I have a chance to upgrade the server side - John
<snip> I use most recent x2go server (3.0.99.6). Only 3.01-4 client from http://www.x2go.org/index.php?id=7 works (3.01-2 should work but there are trojans inside of installation package). <snip> Hmm . . . smells like libssh. I wonder if it's related to another
On Sat, 2011-10-15 at 22:40 +0200, vasek@spsmb.cz wrote: problem we are seeing in Linux with the newer clients; we are constantly dropping SSH sessions. Sound, file sharing, printing, all those functions which rely upon the reverse ssh forwarding all break after a while. Suspending and resuming the session restores them - John
<snip>
x2go client 3.99.0.1 under ubuntu (with new libssl) works, but not under windows. <snip> It works for us too under Squeeze in the sense the session is established and all works initially. However, after a while, the sound stops. Does this happen to you? - John
x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under windows 7. Session is established but connection timeout. On the server side in log: sshd[1903]: error: connect_to localhost port 30001: failed.
Two things I've had problems with that sound similar:
Symantec antivirus on 64-bit Windows 7 seems to interfere with x2go clients newer than 3.0-13, even if Symantec antivirus is completely disabled. Try 3.01-13 from http://code.x2go.org/releases/binary-win32/x2goclient/pre-git/ or uninstall antivirus. Microsoft Security Essentials (free for personal use) worked with 3.99.0.1 on W7 x64 last time I tried.
If the server that you're connecting to also is a client (ClientA -> ServerA -> ServerB), there could be a port conflict. Default incoming port 30001 is already in use by an outgoing tunnel on the same port. Try modifying /usr/bin/x2gostartagent on ServerA and change the port interval from 30000 to 30200. Do the same on ServerB, but use
- Close all existing client sessions to/from the servers in the chain and try again.
Cheers, Daniel
Dne 16.10.2011 07:13, Daniel Lindgren napsal(a):
> x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working under > windows 7. Session is established but connection timeout. On the server > side in log: sshd[1903]: error: connect_to localhost port 30001: failed. Two things I've had problems with that sound similar:
Symantec antivirus on 64-bit Windows 7 seems to interfere with x2go clients newer than 3.0-13, even if Symantec antivirus is completely disabled. Try 3.01-13 from http://code.x2go.org/releases/binary-win32/x2goclient/pre-git/ or uninstall antivirus. Microsoft Security Essentials (free for personal use) worked with 3.99.0.1 on W7 x64 last time I tried.
If the server that you're connecting to also is a client (ClientA -> ServerA -> ServerB), there could be a port conflict. Default incoming port 30001 is already in use by an outgoing tunnel on the same port. Try modifying /usr/bin/x2gostartagent on ServerA and change the port interval from 30000 to 30200. Do the same on ServerB, but use
- Close all existing client sessions to/from the servers in the chain and try again.
Cheers, Daniel
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus. And the server is not also client. Now, after some time I can not connect from linux client 3.99.0.1 too, but it looks like another problem, it looks like corrupted sqlite db:
Oct 16 11:45:47 tserver snoopy[20587]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/bin/sed]: sed -e s/:/PP/g Oct 16 11:45:47 tserver snoopy[20588]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2goinsertsession]: /usr/lib/x2go/x2goinsertsession 128 tserver vasek-128-1318758347_stDGNOME_dp24 Oct 16 11:45:47 tserver snoopy[20590]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20593]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/perl]: perl Oct 16 11:45:47 tserver snoopy[20594]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/bin/date]: date +%s Oct 16 11:45:47 tserver snoopy[20597]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/bin/sed]: sed -e s/:/PP/g Oct 16 11:45:47 tserver snoopy[20598]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2goinsertsession]: /usr/lib/x2go/x2goinsertsession 1232 tserver vasek-1232-1318758347_stDGNOME_dp24 Oct 16 11:45:47 tserver snoopy[20600]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20602]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20604]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20605]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2gosqlitewrapper.pl]: /usr/lib/x2go/x2gosqlitewrapper insertsession 128 tserver vasek-128-1318758347_stDGNOME_dp24 Oct 16 11:45:47 tserver snoopy[20607]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20609]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20612]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/perl]: perl Oct 16 11:45:47 tserver snoopy[20613]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/bin/date]: date +%s Oct 16 11:45:47 tserver snoopy[20614]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2gosqlitewrapper.pl]: /usr/lib/x2go/x2gosqlitewrapper insertsession 1232 tserver vasek-1232-1318758347_stDGNOME_dp24 Oct 16 11:45:47 tserver snoopy[20617]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/bin/sed]: sed -e s/:/PP/g Oct 16 11:45:47 tserver snoopy[20618]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2goinsertsession]: /usr/lib/x2go/x2goinsertsession 129 tserver vasek-129-1318758347_stDGNOME_dp24 Oct 16 11:45:47 tserver snoopy[20620]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:47 tserver snoopy[20623]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/perl]: perl Oct 16 11:45:47 tserver snoopy[20624]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/bin/date]: date +%s Oct 16 11:45:47 tserver snoopy[20627]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/bin/sed]: sed -e s/:/PP/g Oct 16 11:45:48 tserver snoopy[20628]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2goinsertsession]: /usr/lib/x2go/x2goinsertsession 1233 tserver vasek-1233-1318758347_stDGNOME_dp24 Oct 16 11:45:48 tserver snoopy[20630]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:48 tserver snoopy[20632]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:48 tserver snoopy[20634]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:48 tserver snoopy[20635]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2gosqlitewrapper.pl]: /usr/lib/x2go/x2gosqlitewrapper insertsession 129 tserver vasek-129-1318758347_stDGNOME_dp24 Oct 16 11:45:48 tserver snoopy[20637]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:48 tserver snoopy[20638]: [uid:0 sid:14565 tty:/dev/pts/0 cwd:/root filename:/bin/cat]: cat /var/log/auth.log Oct 16 11:45:48 tserver snoopy[20639]: [uid:0 sid:14565 tty: cwd:/root filename:/usr/bin/tail]: tail -n 200 Oct 16 11:45:48 tserver snoopy[20641]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/bin/x2gobasepath]: x2gobasepath Oct 16 11:45:48 tserver snoopy[20644]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/usr/bin/perl]: perl Oct 16 11:45:48 tserver snoopy[20646]: [uid:1000 sid:18704 tty: cwd:/home/vasek filename:/bin/date]: date +%s Oct 16 11:45:48 tserver snoopy[20645]: [uid:1000 sid:1832 tty: cwd:/home/vasek filename:/usr/lib/x2go/x2gosqlitewrapper.pl]: /usr/lib/x2go/x2gosqlitewrapper insertsession 1233 tserver vasek-1233-1318758347_stDGNOME_dp24
Dne 16.10.2011 11:51, vasek@spsmb.cz napsal(a):
Dne 16.10.2011 07:13, Daniel Lindgren napsal(a):
>> x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working >> under >> windows 7. Session is established but connection timeout. On >> the server >> side in log: sshd[1903]: error: connect_to localhost port >> 30001: failed. Two things I've had problems with that sound similar:
Symantec antivirus on 64-bit Windows 7 seems to interfere with x2go clients newer than 3.0-13, even if Symantec antivirus is completely disabled. Try 3.01-13 from http://code.x2go.org/releases/binary-win32/x2goclient/pre-git/ or uninstall antivirus. Microsoft Security Essentials (free for personal use) worked with 3.99.0.1 on W7 x64 last time I tried.
If the server that you're connecting to also is a client (ClientA -> ServerA -> ServerB), there could be a port conflict. Default incoming port 30001 is already in use by an outgoing tunnel on the same port. Try modifying /usr/bin/x2gostartagent on ServerA and change the port interval from 30000 to 30200. Do the same on ServerB, but use
- Close all existing client sessions to/from the servers in the chain and try again.
Cheers, Daniel
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus. And the server is not also client. Now, after some time I can not connect from linux client 3.99.0.1 too, but it looks like another problem, it looks like corrupted sqlite db: I am sorry, latest disfunction under linux was caused by disk quotas, my mistake; but under Windows still does not work.
Dne 16.10.2011 12:27, vasek@spsmb.cz napsal(a):
Dne 16.10.2011 11:51, vasek@spsmb.cz napsal(a):
Dne 16.10.2011 07:13, Daniel Lindgren napsal(a):
>>> x2go client 3.99.0.1 (and 3.99.0.0 and 3.01.18) is not working >>> under >>> windows 7. Session is established but connection timeout. On >>> the server >>> side in log: sshd[1903]: error: connect_to localhost port >>> 30001: failed. Two things I've had problems with that sound similar:
Symantec antivirus on 64-bit Windows 7 seems to interfere with x2go clients newer than 3.0-13, even if Symantec antivirus is completely disabled. Try 3.01-13 from http://code.x2go.org/releases/binary-win32/x2goclient/pre-git/ or uninstall antivirus. Microsoft Security Essentials (free for personal use) worked with 3.99.0.1 on W7 x64 last time I tried.
If the server that you're connecting to also is a client (ClientA -> ServerA -> ServerB), there could be a port conflict. Default incoming port 30001 is already in use by an outgoing tunnel on the same port. Try modifying /usr/bin/x2gostartagent on ServerA and change the port interval from 30000 to 30200. Do the same on ServerB, but use
- Close all existing client sessions to/from the servers in the chain and try again.
Cheers, Daniel
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus. And the server is not also client. Now, after some time I can not connect from linux client 3.99.0.1 too, but it looks like another problem, it looks like corrupted sqlite db: I am sorry, latest disfunction under linux was caused by disk quotas, my mistake; but under Windows still does not work.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
However, after a while, the sound stops. Does this happen to you? - John No.
2011/10/16 vasek@spsmb.cz <vasek@spsmb.cz>:
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus.
Have you tried 3.01-13? Don't think I've tried 3.01-11, can't say if it should work or not.
You should also try uninstalling AVG antivirus to verify that it's not the problem.
Cheers, Daniel
Dne 16.10.2011 14:59, Daniel Lindgren napsal(a):
2011/10/16 vasek@spsmb.cz<vasek@spsmb.cz>:
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus. Have you tried 3.01-13? Don't think I've tried 3.01-11, can't say if it should work or not.
You should also try uninstalling AVG antivirus to verify that it's not the problem.
Cheers, Daniel
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev You are right, AVG Free 2012 was the problem, exactly AVG Link-Scanner component. It is quite suspicious :-) Is there any way to run it together with avg free? .. or will be released any fix of x2go client?
Microsoft Security Essentials is a much better free alternative to AVG if you can run it.
On Sun, Oct 16, 2011 at 7:58 AM, vasek@spsmb.cz <vasek@spsmb.cz> wrote:
Dne 16.10.2011 14:59, Daniel Lindgren napsal(a):
2011/10/16 vasek@spsmb.cz<vasek@spsmb.cz>**:
I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus.
Have you tried 3.01-13? Don't think I've tried 3.01-11, can't say if it should work or not.
You should also try uninstalling AVG antivirus to verify that it's not the problem.
Cheers, Daniel ______________________________**_________________ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/**mailman/listinfo/x2go-dev<https://lists.berlios.de/mailman/listinfo/x2go-dev>
You are right, AVG Free 2012 was the problem, exactly AVG Link-Scanner component. It is quite suspicious :-) Is there any way to run it together with avg free? .. or will be released any fix of x2go client?
______________________________**_________________ X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/**mailman/listinfo/x2go-dev<https://lists.berlios.de/mailman/listinfo/x2go-dev>
--
- Ben S.
Dne 16.10.2011 18:37, Benjamin Shadwick napsal(a):
Microsoft Security Essentials is a much better free alternative to AVG if you can run it.
On Sun, Oct 16, 2011 at 7:58 AM, vasek@spsmb.cz <mailto:vasek@spsmb.cz> <vasek@spsmb.cz <mailto:vasek@spsmb.cz>> wrote:
Dne 16.10.2011 14:59, Daniel Lindgren napsal(a): 2011/10/16 vasek@spsmb.cz <mailto:vasek@spsmb.cz><vasek@spsmb.cz <mailto:vasek@spsmb.cz>>: I tried 3.0-11, which also does not work. I do not use symantec, I use AVG free antivirus. Have you tried 3.01-13? Don't think I've tried 3.01-11, can't say if it should work or not. You should also try uninstalling AVG antivirus to verify that it's not the problem. Cheers, Daniel _______________________________________________ X2go-Dev mailing list X2go-Dev@lists.berlios.de <mailto:X2go-Dev@lists.berlios.de> https://lists.berlios.de/mailman/listinfo/x2go-dev You are right, AVG Free 2012 was the problem, exactly AVG Link-Scanner component. It is quite suspicious :-) Is there any way to run it together with avg free? .. or will be released any fix of x2go client? _______________________________________________ X2go-Dev mailing list X2go-Dev@lists.berlios.de <mailto:X2go-Dev@lists.berlios.de> https://lists.berlios.de/mailman/listinfo/x2go-dev--
- Ben S.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev Some users use McAfee which also does not work. I thing disabling or replacing antivirus products is not the right way to solve it.
Kaspersky Anti-Virus for Workstations MP4 (Business variant) seems to also interfere with x2GO!
Disabling it brought me one more step ner the finnish.
Using WinXP Prof in AD-Domain with 10MBit Connection and KAV 6 WKS-DE MP4.
Alexander Täffner <darkalex <at> firesplash.de> writes:
Kaspersky Anti-Virus for Workstations MP4 (Business variant) seems to also interfere with x2GO!
Disabling it brought me one more step ner the finnish.
Using WinXP Prof in AD-Domain with 10MBit Connection and KAV 6 WKS-DE MP4.
Setting an Exception for x2GO's Program Directory isd enough for Kaspersky to let it work!
But: at least on debian you have to install kde-core even if you want to start gnome... Seems as there is something of it needed by x2go:
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
Yes I selected GNOME (and it starts)!
On Fr 25 Nov 2011 09:10:16 CET Alexander Täffner wrote:
Alexander Täffner <darkalex <at> firesplash.de> writes:
But: at least on debian you have to install kde-core even if you
want to start gnome... Seems as there is something of it needed by x2go:
Is that server or client where you had to install kde-core?
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
That does not relate to packages that need to be installed. The cache
name is just a name that tricks libnx well enough...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hello all,
As you know, X2Go client on windows have problems with some antivirus programs. I have invested some time in investigation of this problem. It seems like QTcpSocket have problems if antivirus software running on the machine. The closed sockets are not accessible directly after closing, but only after finishing of owner process. I have replaced QTcpSocket with WinSocks and it seems to work now. I have successfully tested it with Avast. Please test it with your antivirus software and give your feedback.
You can download a new version of client here: http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.0.2-se...
regards, alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
I've successfully tested 3.99.0.2 with Symantec Endpoint Protection (11.0.6 MP3) on Windows 7 x64, I haven't been able to use any version later than 3.01-13 with SEP on W7 x64 until 3.99.0.2.
Also no problems with Microsoft Security Essentials, but MSE has worked with all versions of x2goclient that I've tested.
Thanks for tracking this down and fixing it!
Cheers, Daniel
-
Alexander Täffner -
Benjamin Shadwick -
Daniel Lindgren -
John A. Sullivan III -
Mike Gabriel -
Oleksandr Shneyder -
vasek＠spsmb.cz