I know that DCOM does not work with NAT. Does W2K/Soap/COM offer any solutions to make an application work with NAT? The biggest problem with DCOM is that it stores the IP address in the data portion of the packet and NAT will not change that portion of the packet. This makes the application inoperable using NAT. In addition, NAT is very useful today due to the likelihood that you and your business partners will have duplicate IP addresses.
The good news is that SOAP does not hard code the IP address at all. Basically, if you set up your server, to handle HTTP POSTs, you can SOAP all you want. The trick is that most servers aren't set up to hand the HTTP POSTs by default so once you get it going, you're set.

This was first published in May 2001

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top