Web Service time out??

I've got an ASP.NET web service running on a server at discountasp.net. It works most of the time, but it occasionally times out on random calls. Other calls are very fast. It also doesn?t seem to be the ?first call takes forever recompile? issue. I know the code works ? it works on other servers (that I manage) and it works in Visual Studio. Only when I deploy the client (a Windows C# .NET client) do I get this strange time-out situation. </o>
</o>
Also, I can hit the service directly (as in going to the asmx page and invoking things) and this is always fast. </o>
</o>
Any ideas? </o>

 

Well, here's some (lots of?) details:</o>
</o>
Service connects to a SQL Server (on discount.net) to update some tables.Only one client connects at any one time.
</o>
The very strange thing is that it will work outside of where I work (at a college - I'm a professor there), and at certain stations (the client application only, not with the web service project running). When running from within Visual Studio (at work), it will always work, but when I run the client executable alone, it will not work at some station in the college, mainly the ?student? ports. </o>
</o>
I know our network service people have placed some restrictions on the ports the students plug their notebooks into. For example, multiple MAC addresses (and other restrictions, like particular ports, I'm sure) at the same port aren?t allowed (preventing a hub being plugged in, for example). </o>
</o>
However, this client simply connects through port 80 (http) to the web service, and, again, it works when running in Visual Studio. </o>
</o>
Do you know if Visual Studio broadcasts something different when it runs an application vs. when the executable runs alone? I know that using DCOM, this was the case with Visual Studio 6 - you could determine the application that was attempting to connect and prevent it - if you run within Visual Studio 6 (to debug), you had to be sure to alter your code to allow ?Visual Studio? (or whatever it broadcasted as) to connect. </o>
</o>
Any help (or ammunition to throw at the network services people, who always say the ports on the routers are ?wide open? when they are not) would help. I can't see anything strange that I'm doing at my end. </o>
</o>
I?m running XP Pro, if that helps, but the client works under Windows 2000 Server, Pro, and Windows 2003 Server (again, outside the college). </o>
</o>
I?ve tried with Windows firewall on and off ? no change: Run in visual studio = works; run executable alone = works only on ?instructor? stations. </o>
</o>
</o>
</o>
Thanks.</o>
</o>

 

Yes, you can hit it from Internet Explorer and invoke the methods without any problems.

 

Thanks for your input. It turns out that it was something that the network services people were doing at my end. Initially, nothing had been changed, but when I pushed the point (that it works ?everywhere? else ? including various places on the globe) except in certain rooms here, they said they ?didn?t know? but the problem mysteriously went away a few days later. Interesting?