Re: TCP Listener Problem
From: Ken Kolda (ken.kolda_at_elliemae-nospamplease.com)
Date: 01/28/05
- Next message: Dave: "Best book for VB.NET remoting"
- Previous message: Ken Kolda: "Re: Synchronized objects"
- In reply to: Earl: "TCP Listener Problem"
- Next in thread: Earl: "Re: TCP Listener Problem"
- Reply: Earl: "Re: TCP Listener Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 27 Jan 2005 18:50:31 -0800
With your server running, use telnet to try to connect to the port it's
using from the local machine. Then do the same thing from the remote
machine. If the local machine works and the remote doesn't, you've still got
firewall/router issues. If the local machine doesn't work either, try doing
a "netstat -a" and see if the server is listening on the specified port.
This should help you diagnose the source of your problem.
Ken
"Earl" <Earl@discussions.microsoft.com> wrote in message
news:7417176B-EC83-4CA2-AEFE-5A68C58BD198@microsoft.com...
> I have built a TCP client/server application pair that I use to upload
data
> into an SQL Server DB. The client/server pair communicate properly while
> using a local network connection. However, I need to run them over an
> internet connection through a firewall. I have mapped the firewall port I
am
> using to the server computer (windows 2003 machine), but now the TCP
listener
> will not respond when I attempt to connect to it from a remote location.
> Please note that this machine (server) is also running Terminal Server.
> Thoughts or solutions are always greatly appreciated.
>
> This does not use remoting, rather I am working at the socket level.
- Next message: Dave: "Best book for VB.NET remoting"
- Previous message: Ken Kolda: "Re: Synchronized objects"
- In reply to: Earl: "TCP Listener Problem"
- Next in thread: Earl: "Re: TCP Listener Problem"
- Reply: Earl: "Re: TCP Listener Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
