Came across a problem with the 1.0b server, went to run the exe, firewall alerted me that server wanted access to the internet, which is fair enough because cyril you said it wanted access via port 200 or 2000. Anyway let it have access and now firewall refuses to let the server send any signal and is throwing up an alert every 2 seconds:
"Attempt to connect to local computer using the TransScout Trojan Horse Blocked"
So the firewall is picking us the signals as a Trojan Horse. I think this problem will need to be overcome in the next version pretty soon, because I cant even test it fully without the thing giving me tonnes of errors while the firewall is up.
There is the possibility of me altering my firewall settings to not detect this kind of behavior from this program but I feel that users that may want to use this program may be put off by the idea.
Firewall = Norton Internet Security 2003 with all latest patches.
Anyways to fix this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yeah, this is the same pb you had with the FBDaemon server.
your firewall is wrong.
the server is not accessing the internet, just connecting to your own computer
So you should find a way to tell your f/w to leave your own address open port 2000 toward your own address...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mel,
could you re-post this message in the support-request Tracker?
I've customized it on purpose.
The main reason is that this forum is dedicated to developers (web and source code) and is not visible from the end-users/testers.
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys
Came across a problem with the 1.0b server, went to run the exe, firewall alerted me that server wanted access to the internet, which is fair enough because cyril you said it wanted access via port 200 or 2000. Anyway let it have access and now firewall refuses to let the server send any signal and is throwing up an alert every 2 seconds:
"Attempt to connect to local computer using the TransScout Trojan Horse Blocked"
So the firewall is picking us the signals as a Trojan Horse. I think this problem will need to be overcome in the next version pretty soon, because I cant even test it fully without the thing giving me tonnes of errors while the firewall is up.
There is the possibility of me altering my firewall settings to not detect this kind of behavior from this program but I feel that users that may want to use this program may be put off by the idea.
Firewall = Norton Internet Security 2003 with all latest patches.
Anyways to fix this?
yeah, this is the same pb you had with the FBDaemon server.
your firewall is wrong.
the server is not accessing the internet, just connecting to your own computer
So you should find a way to tell your f/w to leave your own address open port 2000 toward your own address...
Mel,
could you re-post this message in the support-request Tracker?
I've customized it on purpose.
The main reason is that this forum is dedicated to developers (web and source code) and is not visible from the end-users/testers.
thanks