search for: moment_

Displaying 10 results from an estimated 10 matches for "moment_".

Did you mean: moment
turned on log level = 10 . . . no logs
2016 Sep 30
2
turned on log level = 10 . . . no logs
...well, then not. Now experiencing dns issues. My syslog on first DC shows "Failed to connect host 192.168.xx.49 (22******c8._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC connection failed.) Now, _please set the dns issue aside for the moment_ as I went to my second DC and set log level to "10" to see what is going on and the second DC is not generating log files. It did not create /var/log/samba/* anything. This after a couple of restarts. I checked the "smbd -b" output of DC2 and Samba is set to "LOGFILEBASE: /...
turned on log level = 10 . . . no logs
2016 Sep 30
2
turned on log level = 10 . . . no logs
...g on first DC >> shows "Failed to connect host 192.168.xx.49 >> (22******c8._msdcs.dtshrm.dt) on port 135 - >> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC >> connection failed.) >> >> Now, _please set the dns issue aside for the moment_ as I went to my >> second DC and set log level to "10" to see what is going on and the >> second DC is not generating log files. It did not create >> /var/log/samba/* anything. This after a couple of restarts. I checked >> the "smbd -b" output of DC2 and...
turned on log level = 10 . . . no logs
2016 Sep 30
2
turned on log level = 10 . . . no logs
...ing dns issues. My syslog on first > DC shows "Failed to connect host 192.168.xx.49 > (22******c8._msdcs.dtshrm.dt) on port 135 - > NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC > connection failed.) > > Now, _please set the dns issue aside for the moment_ as I went to > my second DC and set log level to "10" to see what is going on and > the second DC is not generating log files. It did not create > /var/log/samba/* anything. This after a couple of restarts. I > checked the "smbd -b" output of DC2 and Samba is set to...
turned on log level = 10 . . . no logs
2016 Sep 30
2
turned on log level = 10 . . . no logs
...ows "Failed to connect host 192.168.xx.49 > >> (22******c8._msdcs.dtshrm.dt) on port 135 - > >> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC > >> connection failed.) > >> > >> Now, _please set the dns issue aside for the moment_ as I went to > >> my second DC and set log level to "10" to see what is going on and > >> the second DC is not generating log files. It did not create > >> /var/log/samba/* anything. This after a couple of restarts. I > >> checked the "smbd -b&quot...
turned on log level = 10 . . . no logs
2016 Sep 30
0
turned on log level = 10 . . . no logs
...ing dns issues. My syslog on first DC > shows "Failed to connect host 192.168.xx.49 > (22******c8._msdcs.dtshrm.dt) on port 135 - > NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC > connection failed.) > > Now, _please set the dns issue aside for the moment_ as I went to my > second DC and set log level to "10" to see what is going on and the > second DC is not generating log files. It did not create > /var/log/samba/* anything. This after a couple of restarts. I checked > the "smbd -b" output of DC2 and Samba is set to...
turned on log level = 10 . . . no logs
2016 Sep 30
0
turned on log level = 10 . . . no logs
...ows "Failed to connect host 192.168.xx.49 > >> (22******c8._msdcs.dtshrm.dt) on port 135 - > >> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC > >> connection failed.) > >> > >> Now, _please set the dns issue aside for the moment_ as I went to > >> my second DC and set log level to "10" to see what is going on and > >> the second DC is not generating log files. It did not create > >> /var/log/samba/* anything. This after a couple of restarts. I > >> checked the "smbd -b&quot...
turned on log level = 10 . . . no logs
2016 Sep 30
0
turned on log level = 10 . . . no logs
...g on first >> DC shows "Failed to connect host 192.168.xx.49 >> (22******c8._msdcs.dtshrm.dt) on port 135 - >> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC >> connection failed.) >> >> Now, _please set the dns issue aside for the moment_ as I went to >> my second DC and set log level to "10" to see what is going on and >> the second DC is not generating log files. It did not create >> /var/log/samba/* anything. This after a couple of restarts. I >> checked the "smbd -b" output of DC2 and...
Last R-devel snapshot is an empty tarball
2006 Oct 05
2
Last R-devel snapshot is an empty tarball
Dear list, The last R-devel snapshot (2006-10-03) is an empty tarball: ftp://ftp.stat.math.ethz.ch/Software/R/ Thanks, H.
turned on log level = 10 . . . no logs
2016 Sep 30
0
turned on log level = 10 . . . no logs
...ing dns issues. My syslog on first > DC shows "Failed to connect host 192.168.xx.49 > (22******c8._msdcs.dtshrm.dt) on port 135 - > NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC > connection failed.) > > Now, _please set the dns issue aside for the moment_ as I went to > my second DC and set log level to "10" to see what is going on and > the second DC is not generating log files. It did not create > /var/log/samba/* anything. This after a couple of restarts. I > checked the "smbd -b" output of DC2 and Samba is set to...
turned on log level = 10 . . . no logs
2016 Oct 02
1
turned on log level = 10 . . . no logs
...g on first >> DC shows "Failed to connect host 192.168.xx.49 >> (22******c8._msdcs.dtshrm.dt) on port 135 - >> NT_STATUS_CONNECTION_REFUSED." (Which is referencing the second DC >> connection failed.) >> >> Now, _please set the dns issue aside for the moment_ as I went to >> my second DC and set log level to "10" to see what is going on and >> the second DC is not generating log files. It did not create >> /var/log/samba/* anything. This after a couple of restarts. I >> checked the "smbd -b" output of DC2 and...