Problems uploading to Mika... *Fixed & flushed!*

[GeoffS]

I have a small herd at work behind a firewall. Usually, everything goes fine. This morning I check my stats and they look like the dog's breakfast. Zip into work and find that about 3/4 of the herd is getting the error message

NetUpdate::Unable to assert handshake integrity

Others at work, on the same lan, behind the same firewall, with the same hardware and software configuration, are connecting with no problems. Any ideas out there? I'm cracking random blocks at a furious rate and am getting backed up... poor pcs are looking constipated... I need to flush... BREAK ME OUT SOME EXLAX!

Seriously, any help would be appreciated!

 

[Engineer]

You could try to the keyserver to:

proxy.teamanandtech.com
port 2064

or if you need port80:

proxy80.teamanandtech.com
port 80

Good Luck!

(Round Robin pproxy)

 

[GeoffS]

Tried those... didn't work. I seem to be getting to the server because the error for a bad port out from behind the firewall issues a different (and faster) error message. Also tried a few suggested in the thread I had a couple of weeks back and they didn't work either. The thing that confuses me (aside from the fact that it is happening) is that it is not happening consistently.

 

[Engineer]

Just a temporary solution: On one of the PC's that does work, you can share the Distributed.net directory (all access) and then use that directory with Remote Buffers (pproxy is better, but takes longer to setup).

I.E...You share a directory under the following example as a guide (The PC used to share is names MainPC in the Ident section of the Network settings under control panel...The Distributed.net directory is shared as Distributed: //MainPC/Distributed/

In your clients, enter //MainPC/Distributed/ under the Remote Buffers Directory and Make sure to set Remote Buffers Disabled to NO!

I'm not sure about the other problems....

You can also share another directory or two and maybe point them to each other...If one runs out, it can get the blocks from one that still has them...I do this at home:

PC1 points to PC2 points to PC3 points back to PC1....(home round robin)

Good Luck

 

[ViRGE]

You might also want to give Dnet's main proxies a quick try. If you can't contact those, then you most likely have a more serious problem with your network.

 

[JonB]

Because it may be a DNS problem, try using just the IP address. Consider this temporary, since IP addresses have a bad habit of changing just when you can't get ready access to the PC.

proxy.teamanandtech.com is also known as 166.70.74.93

I got the address by "pinging" proxy.teamanandtech.com. Because of the "round robin" setup that rotates you to alternate team proxies, you get a different IP address EACH time you ping. The bad part is, only the address above would answer the ping. That could be firewall configuration, but they also could be down for some reason. Time will ultimately tell. Try the IP above before getting too frustrated.

This has fixed many similar problems in the past until the problem DNS refreshes itself.

 

[GeoffS]

Thanks guys... I haven't had the chance to see if the problem has resolved itself yet. I think I will try the shared directory idea and use a single PC to access the keyserver.

 

[GeoffS]

Well, turns out there was a small change to the network made on Friday evening that zapped my network connections. The good news is that I flushed about 6000 blocks this morning ... the bad news is that a large portion of them are random blocks I guess I'll have to wait and see how many actually get accepted by dnet.

Thanks again for all the help! I am now using proxy80 and it seems to be working great.