Pi Segment on my work machine was giving network errors, didn't want to upload or download, but I restarted it and everything was ok again. All my pending uploads went up and I stocked my cache again.
AMD Users Alchemist
Moderator
Pi Segment on my work machine was giving network errors, didn't want to upload or download, but I restarted it and everything was ok again. All my pending uploads went up and I stocked my cache again.
2009 MULTI CORES CONTEST STATS
http://neogen.amdusers.com/contest2009/contestoverall.htm
CHRISTMAS QUEST CONTEST STATS
http://neogen.amdusers.com/contest2008/xmascontest.htm
http://neogen.amdusers.com/contest2008/stats.png (snapshot)
FEBRUARY '08 RACE STATS
http://neogen.amdusers.com/contest2008/racefeb08b.htm
http://neogen.amdusers.com/contest2008/racefeb08nb.htm
Member
I found this problem before. That may contribute to a component the client use to connect the server and it always remember the IP resolved from pisegment.vicp.net. It's okay when server is connected. But when server is temporarily down, this domain may refer to 127.0.0.1. If the client just connect the server in this time, it will remember the 127.0.0.1 and try to connect it foreverOriginally Posted by NeoGen
I have not found any options to force the client to resolve the domain so the client still suffer this problem.
Anyway, it will be handled after deployment for server will have a static IP.
Posting Permissions
Reply With Quote