Displaying 3 results from an estimated 3 matches for "stata16".
2019 Aug 30
3
flood of (auth in progress) connections from unresponsive windows client crashing samba
...ger it was to try and use the network drive as the user library install location in R/Rstudio. After informing all users not to do that, things seemed to stabilize again, but we are still seeing this occur every other day or so at seemingly random times. Most of our users on the clients are using Stata16 to access data on the mapped drive.
The only additional clue is from the log.clienthostname file and is: ""lookup_name_smbconf for clienthostname$ failed". This appears to show the client trying to connect as itself and not a specific user. I cannot confirm if this is actually rel...
2019 Aug 30
0
flood of (auth in progress) connections from unresponsive windows client crashing samba
...ger it was to try and use the network drive as the user library install location in R/Rstudio. After informing all users not to do that, things seemed to stabilize again, but we are still seeing this occur every other day or so at seemingly random times. Most of our users on the clients are using Stata16 to access data on the mapped drive.
>
> The only additional clue is from the log.clienthostname file and is: ""lookup_name_smbconf for clienthostname$ failed". This appears to show the client trying to connect as itself and not a specific user. I cannot confirm if this is act...
2019 Aug 30
1
flood of (auth in progress) connections from unresponsive windows client crashing samba
...ger it was to try and use the network drive as the user library install location in R/Rstudio. After informing all users not to do that, things seemed to stabilize again, but we are still seeing this occur every other day or so at seemingly random times. Most of our users on the clients are using Stata16 to access data on the mapped drive.
>
> The only additional clue is from the log.clienthostname file and is: ""lookup_name_smbconf for clienthostname$ failed". This appears to show the client trying to connect as itself and not a specific user. I cannot confirm if this is act...