Bye's questions

Recommendations for how I might configure Windows and Macs to perform port address translation locally.

Need to test a web service that sits on port 99. The client application I am testing (think device simulator) will not allow me to hit a port, it automatically assumes port 80. In production, we have a gateway that would perform a translation between incoming port 80 to port 99 on the web server. I'm looking for something no-frills to do the job locally on the client box, without having to installing squid or other firewall/proxy service elsewhere.

I am trying to isolate the cause of a KRB5KDC_ERR_BADOPTION (13) that I am seeing come back in a WireShark trace.

I have set an SPN to associate xxx/server.fqdn:port with the domain account that the xxx service is running under on the target server (lets call it domain\target). The server service that is will be acting as the delegate is running on a different service account (e.g. domain\delegate). Is this allowed? Or do all of the services need to be running under the same service account (i.e. the service account being used by both the target service and the middle-man service are running with the same AD service account, with appropriate SPNs set up for both services associated to that same AD service account)

Running Win 2008, I'd like to extend the volume of a SAN attached drive that is part of a failover cluster. The SAN team has allocated additional drive space which is being seen by Windows Storage Manager. However, the option to "Extend Volume" is disabled, so is the ability to turn it into a dynamic disk.

Is the ability to extend volumes when part of a failover cluster disabled or not available when it's part of SAN attached storage?