|
|
Question : Problem: Using Cisco 3560\3750 SFP port for Tape Library
|
|
I am going to be setting up a tape library. I am told with the library that I'm getting that there are two ways to set it up,
[svrs to be backed up]----->thru the lan---->[backup svr]--->SCSI--->[tape library]
or
[fiber nic]------>[fiber bridge]------>[tape library]
My question is, can I use a cisco switch (3560\3750) and plug the tape library in one of the spf ports on it?
I want to buy the switch to act as the 'fiber bridge' and since it's a gb switch and all the servers have gb nics, i just want them to have a gb connection to the tape library which itself is connected by fiber.
Also, in buying the switch, it says the SFP ports are empty, do I need to purchase a specific gbic or fiber module to plug into the spf port? And i'm assuming this module will depend what type of fiber connection is coming off the tape library, would that be correct? like SC to LC or someting another
|
Answer : Problem: Using Cisco 3560\3750 SFP port for Tape Library
|
|
>> I also tried... IIS provider ignores alternate credentials in Username and Password property due to the fact that it always runs on behalf of the security context of which your code is running under (in your case is NETWORK SERVICE account).
>> Q1 and Q2 IIS administration involves operations that requires high privileges and it is always good to not give such privileges to NETWORK SERVICE account. This to prevent the so-called elevation of privilege attack where an attacker "lures" a highly privileged component to do something bad on his behalf. If you write a commercial program or an application that you can't exactly know who your users are, I'd suggest to always use least privilege account.
>> Q3 It is well documented here http://msdn.microsoft.com/library/en-us/vsent7/html/vxconImpersonation.asp?frame=true http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q306158
Since you're targetting IIS6 (pls correct me if I'm wrong), you can also create an application pool (non default) to serve your web app. Then assign a custom domain account (or local account, depending whether you want this account to have access to network resources) to the app pool's worker process identity. This custom account will only need necessary rights to perform IIS administration.
>> Q4 It looks good, except I'm not sure why you need to CommitChanges twice. You also should dispose those DirectoryEntry objects.
HTH Henry
|
|
|
|