Hi Pete! You didn't mentionned it but I guess your client is in Java since you're in this list right? [Client point to http://server:8080/adir/file.asmx?WSDL] -->[MSSoapT Listen to 8080. Redirect call to server on port 80] --> [The server (Listenning to 80) take this and respond (suppose to)] If with this you server doesn't respond, maybe it got a problem. I have a Java client and a .NET service and that's what I do. Steeve... Pete Roth <[EMAIL PROTECTED]> on 31/07/2001 10:13:38 AM Please respond to [EMAIL PROTECTED] To: "Soap-dev List (E-mail)" <[EMAIL PROTECTED]>, "Soap-user list (E-mail)" <[EMAIL PROTECTED]> cc: (bcc: Steeve Gilbert/G_STGEORGES/CANAM_MANAC) Subject: need Using the MSSoapT (and TcpTunnelGui) trace program included with MSSoap toolkit Has anyone gotten the MSSoapT tracing program to work that comes with the MSSoap toolkit? It is a similar program to TcpTunnelGUI. I cannot get it to pass the information to my server correctly. The instructions below however do not say what to do with the wsdl file once it is downloaded and modified. If I do exactly what it says, nothing will happen since my client still points to the asmx file on the server. Also, I am running a .NET server which the endpoint is not .wsdl, but .asmx. To see the WSDL file you do (POST or GET I forget) and add a ?WSDL to the end of the .asmx URL. So, I tried pointing my client to the local wsdl file I downloaded and modified. This however will not work, since I cannot have a local web server on the same port that the MSSoapT program is listening on which would, I think, be required if I point my client to the local wsdl file. Any help would be appreciated. I am trying to get this Microsoft Trace program working since the TcpTunnelGui would never pass the requests it receives to the server. (Basically the same problem I'm having now). If someone could help me with that program that would be just as great. For TcpTunnelGui, I point my client to the local port (with the server path to the .asmx file still appended), run TcpTunnelGui with that local port, put the server IP address as the second argument and port 80 (port server is listening on) as the third argument. Doing this, the client just hangs after sending out the XML, which I see in TcpTunnelGui. It seems to be waiting for the server to respond, which it never does. Any help on either matter would be VERY helpful. I haven't found anything in the archives about TcpTunnelGui not working after it is seemingly setup correctly. Should I specify the path on the host argument to TcpTunnelGui maybe? I have tried that and that never worked either. These are the instructions Microsoft includes for using this program: Copy the WSDL file from the server to the client. Modify location attribute of the <soap:address> element in the local copy of the WSDL document to direct the client to localhost:8080 and make a note of the current host and port. For example, if the WSDL contains <http://MyServer/VDir/Service.wsdl>, change it to <http://localhost:8080/VDir/Service.wsdl> and make note of "MyServer". On the client, run MSSOPT.exe. On the File menu, point to New, and either click Formatted Trace (if you don't want to see HTTP headers) or click Unformatted Trace (if you do want to see HTTP headers). In the Destination host box, enter the host specified in Step 2. In the Destination port box, enter the port specified in Step 2. Click OK. Thanks. Peter Roth Telemetry Technologies Inc. p: 404.231.0021 ext. 1290 e: [EMAIL PROTECTED]
