OTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Vista Remoting Problem
On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
>
> Tell me how those differ?
They don't. I don't recall saying otherwise.
> My point was that if a client tries to connect to port X on a se
On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
Tell me how those differ?
They don't. I don't recall saying otherwise.
My point was that if a client tries to connect to port X on a server and
the
server receives the connection but doesn't do anything with it causing the
client to time o
On 6/20/07, Steve Johnson <[EMAIL PROTECTED]> wrote:
The error message being returned by remoting (with which I have very
little experience) in this case is simply MS's (poor, IMO) choice of words
for the socket error.
Assuming, of course, that it is indeed a firewall issue. I'll have to de
orts, even ones that don't currently
have listeners, which they don't).
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Johnson
Sent: Wednesday, June 20, 2007 4:31 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-D
.NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Pardee, Roy
Sent: Wednesday, June 20, 2007 4:23 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Vista Remoting Problem
Is that right? It sounds backwards to me...
-Original Message-
From: Discussion of advanced
On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
If I try to connect to a server which is not listening on a port, my
connection fails immediately with "the target machine actively refused the
connection" (because its remote IP stack received the request but refused
the connection because the p
On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
A time out would indicate that *someone* was listening on that port but
refused to establish the connection and response, which would expose data
to
the bad guys (they'd know something was back there). Actively refused
means
nobody is listening o
Is that right? It sounds backwards to me...
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Sills
Sent: Wednesday, June 20, 2007 2:19 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Vista Remoting Problem
ssage-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Johnson
Sent: Wednesday, June 20, 2007 3:15 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Vista Remoting Problem
On 6/20/07, Gregory Miley <[EMAIL PROTECTED]> wrote:
>
&g
I get the same message if a firewall blocks one of my apps, I would
agree that it is quite likely to be a firewall in this case.
Greg
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Johnson
Sent: Wednesday, June 20, 2007 15:50
To:
On 6/20/07, Gregory Miley <[EMAIL PROTECTED]> wrote:
I get the same message if a firewall blocks one of my apps, I would
agree that it is quite likely to be a firewall in this case.
Interesting. Thanks for the info, and sorry for the mis-info.
--
Steve Johnson
On 6/20/07, Adam Sills <[EMAIL PROTECTED]> wrote:
Firewall
I would think that if it were being blocked by a firewall, the connection
attempt would time out. "The target machine actively refused it" indicates
that the request made it into the server's network stack and was refused.
--
Steve
Firewall
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Tracy Ding
Sent: Wednesday, June 20, 2007 2:24 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] Vista Remoting Problem
Hi,
I don't have Vista machine, bu
Hi,
I don't have Vista machine, but our customer Vista machines has problem
with remoting, "No connection could be made because the target machine
server actively refused it".
Remoting formatter is binary and channel is tcp.
Has anyone known the reasons?
Tracy Ding
==
14 matches
Mail list logo
