Problem with TCP in a derived UserControl
-
I'm creating a prototype and have a simple control that I've derived from System.Windows.Forms.UserControl. I intend to be able to use this control in both a windows form client as well as to imbed it in a web page. In order to get data into the control, I'm opening a tcp connection to my app server and requesting data, I am very familiar with tcp and have no problems there. Everything is working perfectly when I put the control into a windows form app. My issue comes up when I plug the control into a web page. Now, I have configured the .NET CAS properly to grant appropriate permissions to the code using strong name evidence so I don't think I have a security problem with CAS. But, I send in the tcp request from the web page, I am able to connect (I see the syn - syn/ack - ack in my sniffer) but then several requests are issued from my host to NETLOGON and some to port 445 (Microsoft directory services). Eventually (over 90 seconds later), my request completes (with my host sending psh-ack and getting fin-psh-ack) as expected. I just can't understand why the control is querying port 445 or what is going on. I don't see why my request is taking 90+ seconds from the time my connection opens until my request goes to the server...?? Any of you run across this before or have any suggestions? thanks Tim