Skip to main content


Showing posts from September, 2012

problem encountered using ftp-ssl with opalis (and corrected)

for a few days, i have been intermittently pulling my hair out trying to figure out why ftp-ssl with the opalis “upload file” object wasn’t working. after trying many permutations, i finally figured it out. sigh. it required some opening ports and other stuff… but the last thing that got me was this particular setting which i’ll get to in a second. for now, let’s examine the error in the output: Error Summary: Connection to FTP site failed Details: OPR-FTP(9560) v3.6.17.8 SCRIPT LOG FILE   Thu Sep 13 08:46:52 -- Line 6: FTPLOGON "myftpsite" /user=xxxxxxxx /pw=************** /port=xxx /servertype=FTPSDATA /trust=ALL /timeout=30 Thu Sep 13 08:46:52 => *Logging on to <myftpsite> as SSL/FTP with secure control and data channels. Thu Sep 13 08:46:52 => *Logon in progress... Thu Sep 13 08:47:07 => *Change directory (CWD) failed during log on -- may need to use /allowerrors option. Thu Sep 13 08:47:08 => *Conn

retrieving wmi class mof information

this powershell powertip is SO cool i just had to repeat it. using the wmiclass type accelerator , you can use a method called gettext to pull down the mof. so using their example, the following command is issued: ([wmiclass] "win32_pingstatus" ).GetText( "MOF" )   from that, we receive the following information: [dynamic: ToInstance, provider( "WMIPingProvider" ): ToInstance] class Win32_PingStatus { [read: ToSubClass, key] String Address; [read: ToSubClass, key] uint32 TimeToLive = 80; [read: ToSubClass, key] uint32 Timeout = 4000; [read: ToSubClass, key] uint32 BufferSize = 32; [read: ToSubClass, key] boolean NoFragmentation = FALSE; [read: ToSubClass, key] uint32 TypeofService = 0; [read: ToSubClass, key] uint32 RecordRoute = 0; [read: ToSubClass, key] uint32 TimestampRoute = 0; [read: ToSubClass, key, ValueMap{ "0" , "1" , "2" }: ToSubClass] uint32 SourceRouteType = 0; [read

finding the right nic in server core

a recently deployed server, on windows 2008 server core , start kicking out some replication notifications which when checking the configuration did not seem to jive. i started poking around when i realized the horror: i don’t know where to find what i’m looking for! long story short, the server suffered from a biological procedural failure to set the nic properly to the right speed. while the nic was set for auto, it was not set for the critical 1gb full auto. the question now is how was this determined, even though netsh is not helpful for this scenario? the answer is … the registry. <sigh>   finding the right interface guid this is a fairly simple and probably routine thing for you if you’ve done any digging around. the idea is to find the nic with the right ip address associated to it. it’s difficult sometimes to do this when you have a server with four nics but only one enabled. this is a smart way to filter them out. navigate to hklm\system\currentcontrolset\services\