search for: failed_connection_cache_timeout

...box to 35 sec (on linux I don't know how must do it) ndd -set /dev/tcp tcp_rexmit_interval_extra 0 ndd -set /dev/tcp tcp_rexmit_interval_initial 500 ndd -set /dev/tcp tcp_ip_abort_interval 20000 ndd -set /dev/tcp tcp_ip_abort_cinterval 20000 2. Setup the FAILED_CONNECTION_CACHE_TIMEOUT constant - #define FAILED_CONNECTION_CACHE_TIMEOUT 30 /* Seconds between attempts */ + #define FAILED_CONNECTION_CACHE_TIMEOUT 3600 /* One hour, it is enough I think */ Problem with the solutions: If the all ADS will be crash, then you must restart the samba after the ADS'...

...two) and for both the ping timed out, and then it put both DCs into negative cache and during DC location process was left with no candidate DCs after negative cache entry elimination from the list. So my questions are: > > 1. What's the default NEG_CONN_CACHE TTL? 60 seconds. #define FAILED_CONNECTION_CACHE_TIMEOUT (LONG_CONNECT_TIMEOUT * 2 / 1000) #define LONG_CONNECT_TIMEOUT 30000 > 2. Is there a way to control NEG_CONN_CACHE, either TTL or contents? Is there a way to force Winbind to try connecting to the DCs it didn't have success with before? 'net cache flush' didn't seem to have much...

I've tried searching manuals and wiki, but I can't seem to find any specifics about NEG_CONN_CACHE entries other than 'idmap negative cache time' option in smb.conf, which refers to SID/UID/GID queries and not unavailable DCs. Specifically the issue I've ran into recently is that with 'winbind max domain connections' set to 10 I saw Winbind had single active connection