a:63:{s:15:"comment_post_ID";s:4:"2963";s:14:"comment_author";s:5:"mitch";s:20:"comment_author_email";s:23:"mitch@cuip.uchicago.edu";s:18:"comment_author_url";s:0:"";s:15:"comment_content";s:1214:"Hi, Erwin!

Thanks again for your excellent work and reporting, both. 

On your 10/26 item:  Yes, Reavis had a private domain for a while, called REAVISDOMAIN.  One of the tricks for joining a client computer to another domain is to set its DNS to a manually entered address, for which you use the address of the local Domain Controller (which should be running DNS service for the private domain).  This is almost certainly how/why this client computer got that kind of setting.  

Alnog with fixing the DNS server setting on that computer, it may be worth checking that it is really on INSTR ad not clinging to REAVISDOMAIN in some fashion.  

I thought we had caught all the machnes that were still members of REAVISDOMAIN -- I mean those where the "Log on to" drop down shows that along with the expected INSTR etc.  This one may have been already joined back to INSTR but that DNS setting overlooked.  Anyway, if you do come across others, no reason to hesitate in putting them back to standard.  

It's //possible// the fileserver still thinks of itself as belonging to, nay running, the REAVISDOMAIN domain. We can look at that sometime and try to convince it otherwise.  

Thanks,

   ==Mitch";s:12:"comment_type";s:0:"";s:14:"comment_parent";s:1:"0";s:7:"user_ID";s:1:"2";s:7:"user_ip";s:12:"75.21.85.225";s:10:"user_agent";s:106:"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4";s:8:"referrer";s:51:"http://reporting.cuip3.org/2012/11/weeks-45-reavis/";s:4:"blog";s:26:"http://reporting.cuip3.org";s:9:"blog_lang";s:2:"en";s:12:"blog_charset";s:5:"UTF-8";s:9:"permalink";s:51:"http://reporting.cuip3.org/2012/11/weeks-45-reavis/";s:9:"user_role";s:13:"administrator";s:21:"akismet_comment_nonce";s:6:"passed";s:12:"POST_comment";s:1218:"Hi, Erwin!

Thanks again for your excellent work and reporting, both. 

On your 10/26 item:  Yes, Reavis had a private domain for a while, called REAVISDOMAIN.  One of the tricks for joining a client computer to another domain is to set its DNS to a manually entered address, for which you use the address of the local Domain Controller (which should be running DNS service for the private domain).  This is almost certainly how/why this client computer got that kind of setting.  

Alnog with fixing the DNS server setting on that computer, it may be worth checking that it is really on INSTR ad not clinging to REAVISDOMAIN in some fashion.  

I thought we had caught all the machnes that were still members of REAVISDOMAIN -- I mean those where the "Log on to" drop down shows that along with the expected INSTR etc.  This one may have been already joined back to INSTR but that DNS setting overlooked.  Anyway, if you do come across others, no reason to hesitate in putting them back to standard.  

It's //possible// the fileserver still thinks of itself as belonging to, nay running, the REAVISDOMAIN domain. We can look at that sometime and try to convince it otherwise.  

Thanks,

   ==Mitch
  ";s:11:"POST_submit";s:14:"Submit Comment";s:20:"POST_comment_post_ID";s:4:"2963";s:32:"POST__wp_unfiltered_html_comment";s:10:"b7f5b10252";s:26:"POST_akismet_comment_nonce";s:10:"c1ead5dde4";s:15:"SERVER_SOFTWARE";s:6:"Apache";s:11:"REQUEST_URI";s:21:"/wp-comments-post.php";s:9:"AUTH_TYPE";s:5:"Basic";s:14:"CONTENT_LENGTH";s:4:"1453";s:12:"CONTENT_TYPE";s:33:"application/x-www-form-urlencoded";s:13:"DOCUMENT_ROOT";s:57:"/home/cuipmar4/public_html/blogs/standalone-WPs/reporting";s:17:"GATEWAY_INTERFACE";s:7:"CGI/1.1";s:11:"HTTP_ACCEPT";s:63:"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8";s:19:"HTTP_ACCEPT_CHARSET";s:30:"ISO-8859-1,utf-8;q=0.7,*;q=0.3";s:20:"HTTP_ACCEPT_ENCODING";s:17:"gzip,deflate,sdch";s:20:"HTTP_ACCEPT_LANGUAGE";s:14:"en-US,en;q=0.8";s:18:"HTTP_CACHE_CONTROL";s:9:"max-age=0";s:15:"HTTP_CONNECTION";s:10:"keep-alive";s:11:"HTTP_COOKIE";s:0:"";s:9:"HTTP_HOST";s:19:"reporting.cuip3.org";s:11:"HTTP_ORIGIN";s:26:"http://reporting.cuip3.org";s:12:"HTTP_REFERER";s:51:"http://reporting.cuip3.org/2012/11/weeks-45-reavis/";s:15:"HTTP_USER_AGENT";s:106:"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4";s:4:"PATH";s:13:"/bin:/usr/bin";s:11:"PHP_AUTH_PW";s:0:"";s:13:"PHP_AUTH_USER";s:3:"nsp";s:12:"QUERY_STRING";s:0:"";s:15:"REDIRECT_STATUS";s:3:"200";s:11:"REMOTE_ADDR";s:12:"75.21.85.225";s:11:"REMOTE_PORT";s:5:"53150";s:11:"REMOTE_USER";s:3:"nsp";s:14:"REQUEST_METHOD";s:4:"POST";s:15:"SCRIPT_FILENAME";s:78:"/home/cuipmar4/public_html/blogs/standalone-WPs/reporting/wp-comments-post.php";s:11:"SCRIPT_NAME";s:21:"/wp-comments-post.php";s:11:"SERVER_ADDR";s:14:"174.127.110.33";s:12:"SERVER_ADMIN";s:29:"webmaster@reporting.cuip3.org";s:11:"SERVER_NAME";s:19:"reporting.cuip3.org";s:11:"SERVER_PORT";s:2:"80";s:15:"SERVER_PROTOCOL";s:8:"HTTP/1.1";s:16:"SERVER_SIGNATURE";s:0:"";s:9:"UNIQUE_ID";s:24:"UJkRKdHsR2MABQrPpKYAAAAe";s:8:"PHP_SELF";s:21:"/wp-comments-post.php";s:12:"REQUEST_TIME";s:10:"1352208681";s:4:"argv";s:0:"";s:4:"argc";s:1:"0";s:25:"comment_post_modified_gmt";s:19:"2012-11-04 17:18:14";}