Is there any way around this error occurring without sinking the clocks on
the client and server because this is not an option at all.
Thanks in advance,
Jarad Stahl

Found references to above problem in the discussion group, but details must
have been discussed some time ago.  I am using vs 03 and .net 1.1.4322.  The
web method in question only has 1 parameter, a dataset (which is
serializable) and returns an integer.

Does anyone know if there is a way out of the box to declaratively tie WSE
3.0 authentication and authorization the the ASP.NET 2.0 Membership Provider?
Or do I need to create a custum UsernameTokenManager and code it manually?
Thanks much,

is it possible to perform authentication by X.509 signature at the Router
node (in DMZ), but not at the actual service location?
Regards,
Vasily

We have run into a problem trying to build a client which works with a
web service implemented against the WSDL at [1].  We have successfully
created clients using other tools than the DotNet framework, and in fact
we were able to create a client using an earlier version of the

Although I setting the Connection timeout of IIS 6.0 to 600 sec
I am still seeing the connection closing after 100 sec (via perfmon -
Current Connections of Web service).
The Enable HTTP Keep-Alives in the IIS is on.

Ok, I am hoping someone will be able to answer this very quickly.
I have been writing a bunch of webservices in c#, the one thing I notice is
this.
On about half of them, when I call the .asmx page, and click on a function,

Does anyone have an idea why I keep getting the standard message :
This web service is using http://tempuri.org/ as its default namespace.
Recommendation: Change the default namespace before the XML Web service is
made public.

I am working on a project where i need to trace the flow of operations
through a class i am using for my web services.
This class inherits from SoapService (which inherits from
SoapReceiver).

I've stoumbled over this Exception when I installed WSE 2.0 SP2 on my machine
and called Wse WEB Service.
Non-Wse WEB Service worked fine.
The bug could be reproduced like this:

i tried to access webservice (it's not .net webservice) from javascript using
webservice.htc.
I got the problem in result, the result's always : 'service unavailbale'
so my question, is webservice.htc only compatible with .Net webservice?

Is there any information out there about interoperabilty issues of the new
policy paradigm in WSE 3.0 and WCF?
Does this completely new approach work smoothly with BEA or IBM products?
Does it conform to WS-Policy standards from 2004?

I'm a complete newbie at security in WSE, so I don't know if this is
simple or impossible.  I have written a Windows Service that uses WSE
to expose a web service.  I have written a Windows Forms client
application to consume the web service.  Those parts were trivial and

I am starting to plan a portal site that will eventually (hopefully)
increase exponetianlly in the amount of traffic to the site. I am
planning to do this in a 3-tier/4-tier layout, I'm just wondering of
any design considerations before I embark.

I have some starters questions.
The blank webservice in the 'webservice template' in 'visual web developer'
start with some lines of code. I hope some one can tell me more about it.
[WebService(Namespace = "http://tempuri.org/")]