• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help with RC5 on networked machine

Rickr

Senior member
Hello:

I have a computer on my home network that will NOT fetch/flush to Mika's teamanandtech server. It works fine when I use the 'default' server, but I get this error when I try to use Mika:

Connected to teamanandtech.dhs.org:80
via http proxy 192.168.0.1:4480
NetUpdate::unable to assert handshake integrity

Here is the config file on that machine:

[parameters]
id=rickr@inetarena.com

[networking]
firewall-type=http
firewall-host=192.168.0.1:4480
nettimeout=20
dialup-watcher=passive
autofindkeyserver=no
keyserver=teamanandtech.dhs.org

[rc5]
randomprefix=212
fetch-time-threshold=4

[misc]
project-priority=RC5,OGR=0,DES=0,CSC=0

[triggers]
restart-on-config-file-change=yes
pause-on-no-mains-power=no

[buffers]
frequent-threshold-checks=3
 
Replace the

teamanandtech.dhs.org

with

proxy80.teamanandtech.com

or

proxy.teamanandtech.com

and report the results...🙂

Good Luck!
 
Rickr:

spounds like you've got problems accessing the port number...

have you tried changing the flush address to: proxy80.teamanandtech.com ?

that's the address to the pproxies on the RR that has port 80 open... that way you can still track your stats on Mikas...

Oh, and change the client to flush using port 80 as well...

Hope this works!

With love and respect your fellow TA member

Two-Face
 
Thanks for the replies, but still no luck. Now I am getting this error:

Unable to send request (-1.168)



It is probably a problem with my proxy software.

 
Why do you have the port set at 4480...Why not 80 (http)?

If you can get though with a browser, you should be able to get through with the client 🙂
 
4480 is my firewall(proxy server) HTTP port. The kicker is that it does work with the distributed.net:80 server.

 
Back
Top