Strange behavior in a .NET web service client when not running as local administrator

We ran into a very strange situation when we deployed an application on a client site. This application is implemented as a service using C # in .NET 3. The application communicates with a web service that is written using gSOAP. In our .NET application, the classes that wrap the web service were created by doing Add Service in Visual Studio and referencing the WSDL. Communication is done using HTTPS, but using port 35000.

What we see is that when our application is running as a "Local Administrator Account" everything works well. However, when our application runs like any other account, including the "Local System Account" and even a user account with network administrator privileges, the web service method sometimes causes a timeout. In other cases, they do well, but for a very long time, for example. 100 seconds, not less than 1 second as expected.

This customer uses Cisco switches on their network.

We have not encountered this behavior on other sites. Any ideas or suggestions would be greatly appreciated.

+1


source to share


2 answers


Any event log messages for timeouts, exceptions, etc.

Is the application a Windows service? Are you using RunAs to run under a different custom context? Does this require desktop interaction or any references to System.Windows.Forms?

@Comment 1: Windows Service, Web Service, WCF Service?

Enable security auditing for local and remote computers for the resources most likely to be used by the service.



Another thing is to add a debug log like this ... (Sorry for the VB pseudo)

Sub OnStart(args())
 LogToFile("Starting Service, processing arguments")
 'process args'
 LogToFile("ArgsProcessed calling main worker method")
 'call main worker method'
End OnStart

Sub LogToFile(message as String)
 If (AppConfigKeys[debugLogging] = True) Then
   'writes "DateTime.Now.ToString() & "-" & message" to a text file log' 
 End If
End Sub

      

Insert this kind of logging into your application before and after any process that is likely to fail.

+1


source


Does the client have BI rules on the firewall hardware? (I'm grabbing at straws, but we got similar behavior from one of our clients who used one of our services a few years ago because they turned on some funky BI rules on the firewall.)



+1


source







All Articles