24 hour rally - Page 7

em99010pepe · 2008-02-09, 20:03

Quote:

Originally Posted by gd_barnes

There are all home machines. There is no firewall. I'm stupid with this stuff. What do you mean by how are they are connected? I wouldn't know anything about 'opening' a port. Can you give detailed instructions?

EDIT: The two Athlon's are running Windows Vista. But still one of them worked fine in testing last night so I don't understand this.

I don't know how to work with Vista. On windows XP go to control panel/firewall settings/exceptions and add a new exception port.

ET_ · 2008-02-09, 20:04

Quote:

Originally Posted by gd_barnes

There are all home machines. There is no firewall. I'm stupid with this stuff. What do you mean by how are they are connected? I wouldn't know anything about 'opening' a port. Can you give detailed instructions?

If you are running Windows XP SP2, there is an embedded firewall running.

Go to Start, Control Panel, Windows firewall. You can deselect the firewall or go to the Exceptions tab. Add program llrnet, add port [whatever you selected on that machine]

Luigi

gd_barnes · 2008-02-09, 20:06

OK, ONE of the two machines just quit sleeping and is now working. The one with ports 6993 and 6994 is running now. Still waiting for the one with ports 6996 and 6997. I'll check the firewall on it.

I thought about making them all 6999 and 6998 on the individual machines but didn't want to take any chances. I'll remember that for future reference.

em99010pepe · 2008-02-09, 20:08

Can you change the username of that machine to gd_barnes111 to be more easy to track you down? I'm here with the server console open...

gd_barnes · 2008-02-09, 20:14

Thanks for info. I checked the firewall settings. LLRnet was already checked as allowed. Who really knows? Computers have their own minds at times. My kid's exact same Athlon machine is now running fine but mine is not. I'll give it an hour. If it doesn't quit sleeping, I'll try it one more time and if that doesn't work, I'll put it back on sieving.

So 5 cores running now...try to get 7.

Gary

gd_barnes · 2008-02-09, 20:14

Quote:

Originally Posted by em99010pepe

Can you change the username of that machine to gd_barnes111 to be more easy to track you down? I'm here with the server console open...

OK, I'll try that. It'll be just a minute or so.

EDIT: With the ID of gd_barnes111, one is connecting and one is initializing right now. It sure takes a long time. It wasn't this long last night.

EDIT2: 4 mins. later; 1 is STILL initializing and the other one is STILL connecting??????????

em99010pepe · 2008-02-09, 20:16

Let's bet how many pairs we will test in 24 hours?

Quote:

Originally Posted by gd_barnes

OK, I'll try that. It'll be just a minute or so.

Thanks.

ET_ · 2008-02-09, 20:18

Quote:

Originally Posted by em99010pepe

Let's bet how many pairs we will test in 24 hours?

35.000?

Luigi

gd_barnes · 2008-02-09, 20:22

Port 6996 is now sleeping again. Port 6997 is STILL connecting. It's been > 5 mins. now since I attempted a start with an ID of gd_barnes111.

Something is clearly messed up. I'm wondering if I need to reload LLRnet on my machine. I still don't get it...this machine tested 20-25 pairs in testing over the last day or two with no problem.

em99010pepe · 2008-02-09, 20:23

Quote:

Originally Posted by gd_barnes

Port 6996 is now sleeping again. Port 6997 is STILL connecting. It's been > 5 mins. now since I attempted a start with an ID of gd_barnes111.

Something is clearly messed up. I'm wondering if I need to reload LLRnet on my machine. I still don't get it...this machine tested 20-25 pairs in testing over the last day or two with no problem.

Move to sieve, I also don't understand...sorry.

gd_barnes · 2008-02-09, 20:27

Now, my 3.2 Ghz P4 is sleeping. It's also not being sent any k/n pairs. It's now been waiting for 15 mins. And this one ran fine for over an hour.

There has to be a server issue. Have we overloaded the server? It's not dolling out work like it should.

I'm now down to 4 cores running now; and 2 of those are slow Athlon cores.

2008-02-09, 20:08	#70
em99010pepe Sep 2004 2830₁₀ Posts	Can you change the username of that machine to gd_barnes111 to be more easy to track you down? I'm here with the server console open... Last fiddled with by em99010pepe on 2008-02-09 at 20:08

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
24 hour news	davieddy	Soap Box	4	2011-12-19 19:35
mfaktc slows on WinXP after about an hour	Christenson	GPU Computing	5	2011-05-27 21:47
Prime 95 shuts down itself after exactly 9:22 hour	Unregistered	Information & Answers	13	2009-09-02 05:11
! hour limit on editing	davieddy	Lounge	7	2009-09-01 15:57
1 buck an hour	crash893	Hardware	6	2009-06-18 01:45

2008-02-09, 20:06	#69
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	OK, ONE of the two machines just quit sleeping and is now working. The one with ports 6993 and 6994 is running now. Still waiting for the one with ports 6996 and 6997. I'll check the firewall on it. I thought about making them all 6999 and 6998 on the individual machines but didn't want to take any chances. I'll remember that for future reference.

2008-02-09, 20:14	#71
gd_barnes May 2007 Kansas; USA 24233₈ Posts	Thanks for info. I checked the firewall settings. LLRnet was already checked as allowed. Who really knows? Computers have their own minds at times. My kid's exact same Athlon machine is now running fine but mine is not. I'll give it an hour. If it doesn't quit sleeping, I'll try it one more time and if that doesn't work, I'll put it back on sieving. So 5 cores running now...try to get 7. Gary

2008-02-09, 20:22	#75
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	Port 6996 is now sleeping again. Port 6997 is STILL connecting. It's been > 5 mins. now since I attempted a start with an ID of gd_barnes111. Something is clearly messed up. I'm wondering if I need to reload LLRnet on my machine. I still don't get it...this machine tested 20-25 pairs in testing over the last day or two with no problem.

2008-02-09, 20:27	#77
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	Now, my 3.2 Ghz P4 is sleeping. It's also not being sent any k/n pairs. It's now been waiting for 15 mins. And this one ran fine for over an hour. There has to be a server issue. Have we overloaded the server? It's not dolling out work like it should. I'm now down to 4 cores running now; and 2 of those are slow Athlon cores.