V7 Client was announced quite a while ago. Diminishing support for v6 has also been mentioned.
Using the latest client has always been the best way make sure folding runs with the least problems.
Could not authenticate As. Server[Fixed]
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 10189
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: Could not authenticate As. Server[171.64.65.105]
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
-
- Pande Group Member
- Posts: 2058
- Joined: Fri Nov 30, 2007 6:25 am
- Location: Stanford
Re: Could not authenticate As. Server[171.64.65.105]
As Joseph mentioned above, we're looking into seeing what's going on. This is a bug (likely in the new AS) not an unannounced retirement of v6 clients, but as others have stated, the v6 client is very old and has limited functionality compared to the latest clients.
Prof. Vijay Pande, PhD
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
Departments of Chemistry, Structural Biology, and Computer Science
Chair, Biophysics
Director, Folding@home Distributed Computing Project
Stanford University
-
- Posts: 91
- Joined: Mon Jan 21, 2008 6:42 pm
Re: Could not authenticate As. Server[171.64.65.105]
Thank You for letting us know what's going on Dr. Pande!
-
- Posts: 188
- Joined: Fri Jan 04, 2008 11:02 pm
- Hardware configuration: Hewlett-Packard 1494 Win10 Build 1836
GeForce [MSI] GTX 950
Runs F@H Ver7.6.21
[As of Jan 2021] - Location: England
Re: Could not authenticate As. Server[171.64.65.105]
I'm getting this error, too..
I'm quite happy using the last V6 client producing steady output on my, no doubt aging, GTX460.
The 14K units banging through regularly seem to be efficient. I don't run much F@H on the dual CPUs as much less bang for power buck.
I hope the AS glitch is resolved soon.
No doubt later clients will sustain more throughput- but at over 10M aggregated points now, I feel I can keep ticking nicely on current V6 usage.
I'm quite happy using the last V6 client producing steady output on my, no doubt aging, GTX460.
The 14K units banging through regularly seem to be efficient. I don't run much F@H on the dual CPUs as much less bang for power buck.
I hope the AS glitch is resolved soon.
No doubt later clients will sustain more throughput- but at over 10M aggregated points now, I feel I can keep ticking nicely on current V6 usage.
Re: Could not authenticate As. Server[171.64.65.105]
See viewtopic.php?f=24&t=26794&p=269293#p269293
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
-
- Posts: 657
- Joined: Sun Nov 22, 2009 8:42 pm
- Hardware configuration: AMD R7 3700X @ 4.0 GHz; ASUS ROG STRIX X470-F GAMING; DDR4 2x8GB @ 3.0 GHz; GByte RTX 3060 Ti @ 1890 MHz; Fortron-550W 80+ bronze; Win10 Pro/64
- Location: Bulgaria/Team #224497/artoar11_ALL_....
Re: Could not authenticate As. Server[171.64.65.105]
I confirm this problem is fixed. Thanks to all
Code: Select all
# Windows GPU Console Edition #################################################
###############################################################################
Folding@Home Client Version 6.41r2
http://folding.stanford.edu
###############################################################################
###############################################################################
Launch directory: E:\Sources\FAH files\_GPU_Console v. 6.41
Executable: E:\Sources\FAH files\_GPU_Console v. 6.41\F@H-Win32-GPU.exe
Arguments: -forcegpu nvidia_fermi -verbosity 9
[06:10:51] - Ask before connecting: No
[06:10:51] - User name: artoar_home (Team 224497)
[06:10:51] - User ID: 7892D91A0BA0CA2D
[06:10:51] - Machine ID: 2
[06:10:51]
[06:10:51] Gpu type=3 species=20.
[06:10:51] Loaded queue successfully.
[06:10:51] - Preparing to get new work unit...
[06:10:51] Cleaning up work directory
[06:10:51] - Autosending finished units... [October 3 06:10:51 UTC]
[06:10:51] + Attempting to get work packet
[06:10:51] Trying to send all finished work units
[06:10:51] Passkey found
[06:10:51] + No unsent completed units remaining.
[06:10:51] - Will indicate memory of 8168 MB
[06:10:51] - Autosend completed
[06:10:51] Gpu type=3 species=20.
[06:10:51] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 7
[06:10:51] - Connecting to assignment server
[06:10:51] Connecting to http://assign-GPU.stanford.edu:8080/
[06:10:52] Posted data.
[06:10:52] Initial: 40AB; - Successful: assigned to (171.64.65.105).
[06:10:52] + News From Folding@Home:
[06:10:52] Loaded queue successfully.
[06:10:52] Gpu type=3 species=20.
[06:10:52] Sent data
[06:10:52] Connecting to http://171.64.65.105:8080/
[06:10:53] Posted data.
[06:10:53] Initial: 0000; - Receiving payload (expected size: 127197)
[06:10:54] - Downloaded at ~124 kB/s
[06:10:54] - Averaged speed for that direction ~87 kB/s
[06:10:54] + Received work.
[06:10:54] + Closed connections
[06:10:54]
[06:10:54] + Processing work unit
[06:10:54] Core required: FahCore_15.exe
[06:10:54] Core found.
[06:10:54] Working on queue slot 05 [October 3 06:10:54 UTC]
[06:10:54] + Working ...
[06:10:54] - Calling '.\FahCore_15.exe -dir work/ -suffix 05 -nice 19 -priority 96 -nocpulock -checkpoint 9 -verbose -lifeline 9108 -version 641'
[06:10:55]
[06:10:55] *------------------------------*
[06:10:55] Folding@Home GPU Core
[06:10:55] Version 2.25 (Wed May 9 17:03:01 EDT 2012)
[06:10:55] Build host AmoebaRemote
[06:10:55] Board Type NVIDIA/CUDA
[06:10:55] Core 15
[06:10:55]
[06:10:55] Window's signal control handler registered.
[06:10:55] Preparing to commence simulation
[06:10:55] - Looking at optimizations...
[06:10:55] DeleteFrameFiles: successfully deleted file=work/wudata_05.ckp
[06:10:55] - Created dyn
[06:10:55] - Files status OK
[06:10:55] sizeof(CORE_PACKET_HDR) = 512 file=<>
[06:10:55] - Expanded 126685 -> 507182 (decompressed 400.3 percent)
[06:10:55] Called DecompressByteArray: compressed_data_size=126685 data_size=507182, decompressed_data_size=507182 diff=0
[06:10:55] - Digital signature verified
[06:10:55]
[06:10:55] Project: 7624 (Run 282, Clone 0, Gen 446)
[06:10:55]
[06:10:55] Assembly optimizations on if available.
[06:10:55] Entering M.D.
[06:10:57] Tpr hash work/wudata_05.tpr: 3021345937 1685690718 1633821221 3431530291 3943343404
[06:10:57] GPU device id=0
[06:10:57] Working on Protein
[06:10:57] Client config found, loading data.
[06:10:57] Starting GUI Server
-
- Posts: 79
- Joined: Sun Mar 21, 2010 8:52 pm
- Hardware configuration: Core i7 3930K(C2)@4,2 (1.30v)
Swiftech Apogee Drive II + MCR-H220 Radiator
Asus P9X79
4*4Gb SEC 1600@1866 1.5v
GeForce GTX780ti ref (nztx G10+zalman lq315)
Creative X-Fi Titanium Fatal1ty
Lite-On iHAS124-34
HDD- WD3000GLFS + 2*Hitaсhi HDS723030BLE640 + 2*HDT721010SLA360
case-Corsair Obsidian 700D
PSU - Seasonic Platinum 860W (SS-860XP2)
2) Xeon E5645@4Ghz (1,34v)
ASUS P6T
Thermalright Silver Arrow
Corsair TR3X6G1600C7 (3x2048Mb, 7-7-7-20 1,62v)
GeForce GTX780 ref (nztx G10+corsair H75)
Zotac GTX980 AMP! Edition (ZT-90204-10P)
Hitachi 320Gb HTS543232A7A384
case - Chieftec LBX-03B Dremel edition :-)
PSU - Zalman ZM-850HP+ (Enhance silver)
APC SUA1500RMI2U
APC SUA1500RMI2U
Re: Could not authenticate As. Server[171.64.65.105]
jason403
at one point cut from the work of thousands of cards under 6 versions of the client and not responding to the posts by these people is probably very propel research forward
at one point cut from the work of thousands of cards under 6 versions of the client and not responding to the posts by these people is probably very propel research forward