TCP Port Setup for Proxying?

I would like to set up a few machines to go through a firewall to contact the PrimeNet server. My sniffer traces show the Prime95 client contacting the PrimeNet server on TCP ports in the low 1000s (i.e. 1067,1119,1120,1121). How could I adjust the port number to (80, 443, etc.), one that is not blocked by a firewall? This would allow me to run continuous, automated (non-sneakernet) testing on PCs behind the firewall without requiring email intervention from George. (How)/Is this possible with a current version of Prime95, or is this functionality planned in a future release? Or, is there some other method of accomplishing this same goal without a dialup or open internet connection?

--Exahertz

[Paulie]

Are you using a proxy server? Then you can follow the instructions in the readme.txt file that comes with Prime95.

Or are these machines in a DMZ or a firewall that blocks outbound established connections? You could create an rule to allow any outbound connection to the primenet server that is established from the internal interface.

Most firewalls now days NAT outbound, and include an established allow rule.

Hope this helps!

[dsouza123]

You could try the following

Create the file
primenet.ini
in the same directory/folder that has the other .ini files for Prime95

put in the following lines
ProxyHost=http://www.mersenne.org:80
ProxyPass=

additionally you could also add
Debug=1
which will produce more detailed information
on the attempt to communicate in prime.log

also this line
UseFullURL=2

from the file UNDOC.TXT the description of parameter values.
-------------------
UseFullURL=n

where n is
0 for use relative URLs,
1 for use full URLs,
2 for try full URL and if an error is returned try a relative URL.
The default setting is 2.
Note that a full URL is always sent when using a proxy server.
--------------------