Web Services Forum - WSE 2.0 SP1 SoapClient/Service and NAT

Articles |
News |
Weblogs |
Books |
Forums

Artima Forums | Articles | Weblogs | Java Answers | News

Sponsored Link •

Web Services Forum
WSE 2.0 SP1 SoapClient/Service and NAT

1 reply on 1 page. Most recent reply: Oct 17, 2004 5:03 PM by Julian Lawrence

Welcome Guest
Sign In

Back to Topic List

Reply to this Topic

Search Forum

Threaded View


Previous Topic		Next Topic

Flat View: This topic has 1 reply on 1 page

Christopher Crooker

Posts: 1
Nickname: can
Registered: Aug, 2004

WSE 2.0 SP1 SoapClient/Service and NAT

Posted: Aug 1, 2004 3:07 PM

I have been working with WSE 2.0 for a few weeks now and it works great when I use endpoints that are completely local (soap.tcp://localhost/...). However, in my network environment I am behind a NAT router and I can't figure out how to get the client and service to communicate because WSE seems to be picky about addressing.

I have a dynamic DNS address that refers to the machine externally, and binding to that address as the SoapService's EndpointReference fails because the transport address cannot be associated with a local interface. I have read alot of documentation, forums and blogs and tried many configurations to get this to work with differing results including a socket exceptiona because the connection is being actively refused and AddressingFaults of Destination Unreachable.

I have attempted to "manually" route the messages using Via, making the client anonymous by having the From field set to http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous, assign the correct adress to the SoapService using the SoapActor attribute, modify my router's port access (to ensure it wasn't an external problem) etc. and all to no avail. It must be a WSE issue because I can connect to the SoapService from an external machine via telnet when I bind it to "localhost", but WSE can't communicate properly.

The bottom line question is: How can you use WSE 2.0 to start a service bound to a local interface address and then connect to that service using a different externally visible address? Any help would be immensely appreciated.

Thanks,
Chris

Julian Lawrence

Posts: 1
Nickname: epicycler
Registered: Oct, 2004

Re: WSE 2.0 SP1 SoapClient/Service and NAT

Posted: Oct 17, 2004 5:03 PM

I've been going through similar problems for the last week or so in VB, there's a lack of practical examples.

Once I got the "connection is being actively refused" or "Method not available" errors I was reasonably happy that the address was correct.

A couple of things I noticed which may help.

I initially got confused as to when I was using my SoapReceiver Class or the Instance of it.

In SoapReceivers.Add(Receiver, aSoapReceiver) the Receiver needs addresses which refer to a SoapReceiver Class and aSoapReceiver is an Instance.

At one point the SoapReceiver Receive procedure was being called but in a new instance.

SoapReceivers.Add can be overloaded so that aSoapReceiver can be either a Class or an instance. Once I had inadvertently used a Class "it seemed to be stuck with it", I got a "connection is being actively refused" response no matter what I did, even when I had it right.

Sounds silly, but eventually I provided SoapReceivers.Add(Receiver, GetType(SoapReceiver)) - when I ran the programme, changed SoapReceivers.Add back to its correct usage the communication magically worked. Its been reliable ever since.

Enabling message tracing helped a bit, at least I could see when something was happening.

My current problem is that I can't see how to get all the "via" entries where both the server and client are behind different NAT firewalls.

hope this helps, if you want more detail let me know,

Epicycler

Flat View: This topic has 1 reply on 1 page

Previous Topic

Next Topic


	Web Artima.com