Re: 4th attempt: UDP Socket Bug - DOTNET

This has all been checked and verified. Again, no problems with TCP. This
does function in windows app as the class will show. Also this same thing
has functioned on IIS prior to SP4 without problems.

I guess I will continue to post every few days until I get some kind of
response from M$ or someone who can point me to supporting documents one way
or the other.

Later


"Chris Botha" <chris_s_botha@AT.h.o.t.m.a.i.l.com> wrote in message
news:e6Zn9Pg1DHA.1508@TK2MSFTNGP12.phx.gbl...
> First make sure that the code works and that it is not some other problem,
> thus run the code in a normal windows app.
> Then make sure your impersonation works. Did you switch anonymous access
off
> to the virtual directory? Add a test call returning the connecting user
> info, thus return
> System.Security.Principal.WindowsIdentity.GetCurrent().Name
> and check that it is the expected user.
> If it still does not work, then I'm stumped too.
>
> "Bryan Martin" <spam@ahwayside.com, uce@ftc.gov> wrote in message
> news:%23kHpEoe1DHA.484@TK2MSFTNGP10.phx.gbl...
> > Using udp sockets inside a class called by ASP.NET
> >
> > By impersonating you can use a TCP socket from a external class and call
> it
> > from a ASP.NET page. However, changing the socket type to UDP and
binding
> > it to a port throws an error "An attempt was made to access a socket in
a
> > way forbidden by its access permissions".
> >
> > I tried all the methods I knew of to get this to work such as...
> > 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 inside
> code
> > I have seen
> (http://support.microsoft.com/default...b;EN-US;195445)
> >
> > Equipment & Software:
> > W2K Advanced Server SP4 IIS 5
> > VS.NET 1.0
> >
> > This leaves me at a loss on how to get my class to run from a ASP.NET
> page.
> > I have searched the web and msdn without success. If anyone knows
> something
> > I dont then please speak up.
> >
> > Bryan
> >
> >
> >
> > See the attached file for example class. Calling this from ASP.NET
gives
> > the same result on win2ksp4 IIS5.
> >
> > "An attempt was made to access a socket in a way forbidden by its access
> > permissions"
> >
> >
> >
>
>

Bryan,

Try posting this question at www.asp.net. Many of the ASP.NET development
team lurk in there and might be able to point you to something. On a
connected note - have you tried this on a different build spec server
(perhaps one not service packed), or a different runtime to try to eliminate
some of the possible causes.

--
Regards

John Timney (Microsoft ASP.NET MVP)
----------------------------------------------
<shameless_author_plug>
Professional .NET for Java Developers with C#
ISBN:1-861007-91-4
Professional Windows Forms
ISBN: 1861005547
Professional JSP 2nd Edition
ISBN: 1861004958
Professional JSP
ISBN: 1861003625
Beginning JSP Web Development
ISBN: 1861002092
</shameless_author_plug>
----------------------------------------------

"Bryan Martin" <spam@ahwayside.com, uce@ftc.gov> wrote in message
news:uk6FB8g1DHA.2328@TK2MSFTNGP10.phx.gbl...
> This has all been checked and verified. Again, no problems with TCP.
This
> does function in windows app as the class will show. Also this same thing
> has functioned on IIS prior to SP4 without problems.
>
> I guess I will continue to post every few days until I get some kind of
> response from M$ or someone who can point me to supporting documents one
way
> or the other.
>
> Later
>
>
> "Chris Botha" <chris_s_botha@AT.h.o.t.m.a.i.l.com> wrote in message
> news:e6Zn9Pg1DHA.1508@TK2MSFTNGP12.phx.gbl...
> > First make sure that the code works and that it is not some other
problem,
> > thus run the code in a normal windows app.
> > Then make sure your impersonation works. Did you switch anonymous access
> off
> > to the virtual directory? Add a test call returning the connecting user
> > info, thus return
> > System.Security.Principal.WindowsIdentity.GetCurrent().Name
> > and check that it is the expected user.
> > If it still does not work, then I'm stumped too.
> >
> > "Bryan Martin" <spam@ahwayside.com, uce@ftc.gov> wrote in message
> > news:%23kHpEoe1DHA.484@TK2MSFTNGP10.phx.gbl...
> > > Using udp sockets inside a class called by ASP.NET
> > >
> > > By impersonating you can use a TCP socket from a external class and
call
> > it
> > > from a ASP.NET page. However, changing the socket type to UDP and
> binding
> > > it to a port throws an error "An attempt was made to access a socket
in
> a
> > > way forbidden by its access permissions".
> > >
> > > I tried all the methods I knew of to get this to work such as...
> > > 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
inside
> > code
> > > I have seen
> > (http://support.microsoft.com/default...b;EN-US;195445)
> > >
> > > Equipment & Software:
> > > W2K Advanced Server SP4 IIS 5
> > > VS.NET 1.0
> > >
> > > This leaves me at a loss on how to get my class to run from a ASP.NET
> > page.
> > > I have searched the web and msdn without success. If anyone knows
> > something
> > > I dont then please speak up.
> > >
> > > Bryan
> > >
> > >
> > >
> > > See the attached file for example class. Calling this from ASP.NET
> gives
> > > the same result on win2ksp4 IIS5.
> > >
> > > "An attempt was made to access a socket in a way forbidden by its
access
> > > permissions"
> > >
> > >
> > >
> >
> >
>
>

Thanks for the info and I will try it.

Yes this was function on this server and one other one prior to SP4.


"John Timney (Microsoft MVP)" <timneyj@despammed.com> wrote in message
news:epi$VBk1DHA.1676@TK2MSFTNGP12.phx.gbl...
> Bryan,
>
> Try posting this question at www.asp.net. Many of the ASP.NET development
> team lurk in there and might be able to point you to something. On a
> connected note - have you tried this on a different build spec server
> (perhaps one not service packed), or a different runtime to try to
eliminate
> some of the possible causes.
>
> --
> Regards
>
> John Timney (Microsoft ASP.NET MVP)
> ----------------------------------------------
> <shameless_author_plug>
> Professional .NET for Java Developers with C#
> ISBN:1-861007-91-4
> Professional Windows Forms
> ISBN: 1861005547
> Professional JSP 2nd Edition
> ISBN: 1861004958
> Professional JSP
> ISBN: 1861003625
> Beginning JSP Web Development
> ISBN: 1861002092
> </shameless_author_plug>
> ----------------------------------------------
>
> "Bryan Martin" <spam@ahwayside.com, uce@ftc.gov> wrote in message
> news:uk6FB8g1DHA.2328@TK2MSFTNGP10.phx.gbl...
> > This has all been checked and verified. Again, no problems with TCP.
> This
> > does function in windows app as the class will show. Also this same
thing
> > has functioned on IIS prior to SP4 without problems.
> >
> > I guess I will continue to post every few days until I get some kind of
> > response from M$ or someone who can point me to supporting documents one
> way
> > or the other.
> >
> > Later
> >
> >
> > "Chris Botha" <chris_s_botha@AT.h.o.t.m.a.i.l.com> wrote in message
> > news:e6Zn9Pg1DHA.1508@TK2MSFTNGP12.phx.gbl...
> > > First make sure that the code works and that it is not some other
> problem,
> > > thus run the code in a normal windows app.
> > > Then make sure your impersonation works. Did you switch anonymous
access
> > off
> > > to the virtual directory? Add a test call returning the connecting
user
> > > info, thus return
> > > System.Security.Principal.WindowsIdentity.GetCurrent().Name
> > > and check that it is the expected user.
> > > If it still does not work, then I'm stumped too.
> > >
> > > "Bryan Martin" <spam@ahwayside.com, uce@ftc.gov> wrote in message
> > > news:%23kHpEoe1DHA.484@TK2MSFTNGP10.phx.gbl...
> > > > Using udp sockets inside a class called by ASP.NET
> > > >
> > > > By impersonating you can use a TCP socket from a external class and
> call
> > > it
> > > > from a ASP.NET page. However, changing the socket type to UDP and
> > binding
> > > > it to a port throws an error "An attempt was made to access a socket
> in
> > a
> > > > way forbidden by its access permissions".
> > > >
> > > > I tried all the methods I knew of to get this to work such as...
> > > > 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
> inside
> > > code
> > > > I have seen
> > > (http://support.microsoft.com/default...b;EN-US;195445)
> > > >
> > > > Equipment & Software:
> > > > W2K Advanced Server SP4 IIS 5
> > > > VS.NET 1.0
> > > >
> > > > This leaves me at a loss on how to get my class to run from a
ASP.NET
> > > page.
> > > > I have searched the web and msdn without success. If anyone knows
> > > something
> > > > I dont then please speak up.
> > > >
> > > > Bryan
> > > >
> > > >
> > > >
> > > > See the attached file for example class. Calling this from ASP.NET
> > gives
> > > > the same result on win2ksp4 IIS5.
> > > >
> > > > "An attempt was made to access a socket in a way forbidden by its
> access
> > > > permissions"
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>