Please keep me from turning this **** win2k dell 1300 box into a door stop.......

[John Doe]

I am at my wits end with IIS security.

I am trying to run a component from an aspx page which accesses the sockets
namespace. Of course because most administrators cannot keep there servers
secure microsoft now has it so any attempt to access a socket from the
aspnet account results in "An attempt was made to access a socket in a way
forbidden by its access permissions". How in the hell do I get around this.

Whats been tried:

ASPNET added the account to the local administrators
ASPNET act as part of the os inside local policy
<identity impersonate="true" userName="administrator" password="*****" />
inside the web.config file.
System.Security.Principal.WindowsIdentity.GetCurrent.Impersonate in code
I have seen (http://support.microsoft.com/default.aspx?scid=kb;EN-US;195445)

Please if you have any idea then by all means share it. Oh by the way the
same code works flawlessly on the xp.pro development machine.

 

[Ken Cox [Microsoft MVP]]

Just checking that you unchecked Anonymous access in IIS?

It may be that the "user" at that time is IUSR_<machinename>, so make sure
he has enough rights to execute that assembly.

I found the chart here useful in determine who the "user" is at any given
time:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/secnetap05.asp

 

[Bryan Martin]

This was tried without success.

Just checking that you unchecked Anonymous access in IIS?

It may be that the "user" at that time is IUSR_<machinename>, so make sure
he has enough rights to execute that assembly.

I found the chart here useful in determine who the "user" is at any given
time:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/secnetap05.asp