Connection delay after upgrade to .NET 1.1

When making a socket connection to a server from a client
using the new .NET Framework version 1.1 in a Web
Application, we are getting a severe delay in the granting
of the socket connection. We did not get this using the
previous version of .NET (1.0...). The delay is between 1
and several minutes long. Finally, after the delay, the
socket connection is made with no abnormal messages.
Then, as long as that IE remains up, we can dis-connect
and re-connect as many times as we want with no delays at
all.

Any and all comments would be greatly appreciated.

Mario
Mon Aug 11 13:50:21 CDT 2003

Sounds to me that the ASP.NET page is recompiling. There's usually a delay
the first time you access a user accesses a page.

Mario

"Mike O'Brien" <obrien@codem.com> wrote in message
news:098f01c36025$4e8325a0$a501280a@phx.gbl...
> When making a socket connection to a server from a client
> using the new .NET Framework version 1.1 in a Web
> Application, we are getting a severe delay in the granting
> of the socket connection. We did not get this using the
> previous version of .NET (1.0...). The delay is between 1
> and several minutes long. Finally, after the delay, the
> socket connection is made with no abnormal messages.
> Then, as long as that IE remains up, we can dis-connect
> and re-connect as many times as we want with no delays at
> all.
>
> Any and all comments would be greatly appreciated.

Mike
Mon Aug 11 14:28:55 CDT 2003

Mario,

Thanks for the response. The web page is already loaded
and present. It is a user control that is launched (and
visible) and has issued the socket connect. The response
from the connect is delayed a long time the first time
during the IE session. I keep thinking something has
changed in the network security schemes from .NET 1.0 to
1.1. I tried 'caspol -security off' and disabling all
other security settings in IE to no avail.

Still trying...

>-----Original Message-----
>Sounds to me that the ASP.NET page is recompiling.
There's usually a delay
>the first time you access a user accesses a page.
>
>Mario
>
>"Mike O'Brien" <obrien@codem.com> wrote in message
>news:098f01c36025$4e8325a0$a501280a@phx.gbl...
>> When making a socket connection to a server from a
client
>> using the new .NET Framework version 1.1 in a Web
>> Application, we are getting a severe delay in the
granting
>> of the socket connection. We did not get this using the
>> previous version of .NET (1.0...). The delay is
between 1
>> and several minutes long. Finally, after the delay, the
>> socket connection is made with no abnormal messages.
>> Then, as long as that IE remains up, we can dis-connect
>> and re-connect as many times as we want with no delays
at
>> all.
>>
>> Any and all comments would be greatly appreciated.
>
>
>.
>

Mike
Mon Aug 11 14:47:06 CDT 2003

Found another ref to this problem on the web and its
fixed: http://groups.google.com/groups?hl=en&lr=&ie=UTF-
8&threadm=Rr4Sa.82099%24GL4.21173%
40rwcrnsc53&rnum=2&prev=/groups%3Fhl%3Den%26lr%3D%26ie%
3DISO-8859-1%26q%3DSocket%2Bconnect%2Bdelay%26meta%3Dgroup%
253Dmicrosoft.public.dotnet.*

>-----Original Message-----
>Sounds to me that the ASP.NET page is recompiling.
There's usually a delay
>the first time you access a user accesses a page.
>
>Mario
>
>"Mike O'Brien" <obrien@codem.com> wrote in message
>news:098f01c36025$4e8325a0$a501280a@phx.gbl...
>> When making a socket connection to a server from a
client
>> using the new .NET Framework version 1.1 in a Web
>> Application, we are getting a severe delay in the
granting
>> of the socket connection. We did not get this using the
>> previous version of .NET (1.0...). The delay is
between 1
>> and several minutes long. Finally, after the delay, the
>> socket connection is made with no abnormal messages.
>> Then, as long as that IE remains up, we can dis-connect
>> and re-connect as many times as we want with no delays
at
>> all.
>>
>> Any and all comments would be greatly appreciated.
>
>
>.
>