- Joined
- Aug 17, 2008
- Messages
- 2,190 (0.38/day)
- Location
- Minnesota, USA
System Name | TaichiTig |
---|---|
Processor | i7 6800K |
Motherboard | ASRock X99 Taichi |
Memory | 32GB DDR4 3200 |
Video Card(s) | RTX 4070 |
Storage | SSD + Misc. HDDs in DrivePool |
Display(s) | BenQ PD3200U, Samsung C32HG70 |
Case | Antec Twelve Hundred |
Audio Device(s) | Behringer UMC404HD, LSR308, Shure SRH840, AKG K612, Etymotic HF5 |
Power Supply | Corsair 750TX |
Mouse | Logitech G502 |
Keyboard | Deck Legend Ice Tactile |
Software | Win10 |
I just moved and upgraded some computers around here, and looking at FahMon on my main rig (which is set to remotely monitor FAH on all my computers), noticed the WUs on one machine had supposedly been downloaded two weeks ago and missed their deadlines. So I checked the local FahMon installation on that machine (it's just two 9800GX2s and no SMP), and found the values were reported differently [and accurately] there. All other numbers are reported accurately both by local and remote FahMon installations.
FahMon on the clients' local machine:
And FahMon on my main rig, which monitors clients on all my computers remotely:
The FahMon installation in question is reporting accurate values for all other remote machines. What might cause it to report just those values incorrectly when monitored remotely [but not when monitored locally]?
FahMon on the clients' local machine:
And FahMon on my main rig, which monitors clients on all my computers remotely:
The FahMon installation in question is reporting accurate values for all other remote machines. What might cause it to report just those values incorrectly when monitored remotely [but not when monitored locally]?