Issues with iControl.dll on network?

Ok, this is bizarre as a 403 error indicates the calling application is attempting to access a resource on the server that isn't allowed (ie, trying to browse a directory or hit a resource that doesn't have access on it). I have no clue why running the assembly from one location would effect the URL it's trying to access. Internally the assembly is building a URL like this

 

 

https:///iControl/iControlPortal.cgi

 

 

with the only variable being the bigip_address value.

 

 

You might want to attempt to look in the apache error_log on the LTM to see if you can figure out what's causing the 403 error to be thrown. That's probably the only debugging step you can do here as the .net client doesn't have a useful trace facility.

 

 

The iControl assembly does use an optional proxy server if you passed info in for it in one of the secondary initialize methods and that could theoretically be the one throwing the error, but that's all guessing on my part.

 

 

I'll play around with this a bit and see if I can reproduce it on my end. If so, I'll let you know. Please let me know if you figure things out on your side and I can try to document this for others that might have the same problem.

 

 

-Joe