TCP Address Question

Hi,
I have an ASP.net page that uses a dll to send a request via TCP
channel nnnn (TCPClient / XML Serialiser) to a Windows app.
The Windows app receives (TCPListener / TCPClient / XMLDeserialiser)
processes the request and sends back a response (TCPClient /
XMLSerialiser) via TCP channel yyyy back to the dll
(TCPListener/TCPClient/XMLDeserialiser).


Using the IIS on the development machine and having the windows app
running on the development machine it works fine.

I now want to move the web page across to the production server (Same
LAN)
I am unclear about what IPAddresses to set for the respective TCP
listeners and TCPclients

For the DLL I thought there would be no change because it is still
trying to send and listen to the development machine

For the app I thought I would need to put the local ip of the
webserver upon which the page & dll will be residing.
But when I try to run the app, at the Listener.start command, it
complains that the IP address is not valid in its context.

So I guess it comes down to my understanding (or lack there of) of
what the TCP components expect.

Do the Tx components (TcpClient/XMLSerialiser) expect the destination
address and the Rx components (TCPListener/TcpClient/XMLDeserialiser)
the local address?
or
Do they both expect the local address upon which they reside?
or
is my methodology flawed for what I am trying to achieve.
(Nooo I really don't want a quick to move to WCF if I can avoid it.
I know nothing about it.)
thanks
Bob
.

Relevant Pages

  • RE: Simple TCP Socket Communicator - Please Help
    ... TcpClient to receive data from server, ... Since TcpClient work upon a physical Tcp connection, ... private StreamReader _reader; ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework)
  • Custom classes with web services
    ... I also have a Windows app that will reference a couple of web services. ... Each web service references the .dll to get the user class. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: 4th attempt: UDP Socket Bug
    ... Again, no problems with TCP. ... does function in windows app as the class will show. ... >> By impersonating you can use a TCP socket from a external class and call ... >> ASPNET added the account to the local administrators ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Keeping objects between requests within the same session
    ... I tried using that, but when working with my Windows App accessing the DLL, ... to initialize it, so to speak (I imagine this is explicitly doing what, in a ... > the current page request. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Sharing common code
    ... > I have two apps (one is a service and one is a windows app) that share some ... > common classes. ... > I've thought about making a DLL out the common class but 1) Don't know how ...
    (microsoft.public.dotnet.languages.vb)