Dear List members
I am posting this question again since so far I have not been able to
find any solution. But I do believe there is one -- which I cannot find
and hopefully someone will be able to share her/his effective solution
with me.
Thanks
---BeginMessage---
Hello, is 3389
On Sat, 02 Aug 2008 00:06:46 +
FreeBSD [EMAIL PROTECTED] wrote:
I am posting this question again since so far I have not been able to
find any solution. But I do believe there is one -- which I cannot
find and hopefully someone will be able to share her/his effective
solution with me.
If
Dear Darko
Thanks for your mail.
To answer your question, no, we are on the same network and from my
machine everything is open. Also, I tried it from my home, which has the
basic firewall allowing me to connect to whereever I want (I tried it
with no firewall as well), nothing worked.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of FreeBSD
Sent: July 24, 2008 5:41 PM
To: darko gavrilovic
Cc: User Questions
Subject: Re: connecting to a secured Windows 2003 terminal server
Dear Darko
Thanks for your mail.
To answer
What ver. of rdesktop are you running? Are you running the latest?
sorry, I don't know enough about MS encryption or their TS services to
suggest any advanced rdesktop tweaks. Wonder if you can run rdesktop in
verbose mode and look at any logs it spews out.
On Thu, Jul 24, 2008 at 5:40 PM,
doubt, since even after googling for nearly five days I couldn't find any
solution.
Recently my company has updated their server to Windows 2003. The earlier
2000 server didn't have SSL enabled, so rdp/rdesktop worked for me without
any problem. But now, as I try to connect to the server, it
Wojciech Puchar wrote:
doubt, since even after googling for nearly five days I couldn't find
any solution.
Recently my company has updated their server to Windows 2003. The
earlier 2000 server didn't have SSL enabled, so rdp/rdesktop worked
for me without any problem. But now, as I try to
Recently my company has updated their server to Windows 2003. The earlier
2000 server didn't have SSL enabled, so rdp/rdesktop worked for me without
any problem. But now, as I try to connect to the server, it simply gives me
ERROR: recv: Connection reset by peer
Did you make sure that the
what happens when you type this?
# openssl s_client -connect someipaddress:3389
you should get a response of CONNECTED or something to that effect.
you might have to change the 3389 if you have rdp listening on another port.
On Tue, Jul 22, 2008 at 9:17 PM, Simon Chang [EMAIL PROTECTED]
--On July 22, 2008 9:17:45 PM -0400 Simon Chang [EMAIL PROTECTED]
wrote:
Recently my company has updated their server to Windows 2003. The
earlier 2000 server didn't have SSL enabled, so rdp/rdesktop worked for
me without any problem. But now, as I try to connect to the server, it
simply gives
Paul Schmehl wrote:
--On July 22, 2008 9:17:45 PM -0400 Simon Chang [EMAIL PROTECTED]
wrote:
Recently my company has updated their server to Windows 2003. The
earlier 2000 server didn't have SSL enabled, so rdp/rdesktop worked for
me without any problem. But now, as I try to connect to the
--On July 22, 2008 10:03:36 PM -0400 Steve Bertrand [EMAIL PROTECTED]
wrote:
Umm..it's a terminal server
...ummm, in Windows-land, Terminal Services == rdp (port 3389 TCP).
Umm..no. In Windows-land, Terminal Services == rdp (port 3389 TCP) but a
terminal *server* is used specifically
--On July 22, 2008 9:26:27 PM -0500 Paul Schmehl
[EMAIL PROTECTED] wrote:
--On July 22, 2008 10:03:36 PM -0400 Steve Bertrand [EMAIL PROTECTED]
wrote:
Umm..it's a terminal server
...ummm, in Windows-land, Terminal Services == rdp (port 3389 TCP).
Umm..no. In Windows-land, Terminal
Paul Schmehl wrote:
Umm..no. In Windows-land, Terminal Services == rdp (port 3389 TCP) but
a terminal *server* is used specifically to allow mutliple (as in more
than the default limit of two) concurrent sessions and requires the
purchase of additional licenses. Now, *maybe* the OP really
Paul Schmehl wrote:
To the OP - here's what I get when testing from a FreeBSD box to one of
our servers:
[EMAIL PROTECTED] telnet hostname.utdallas.edu 3389
Connection closed by foreign host.
Does your server have SSL enabled? The OP stated that prior to upgrade,
the box did NOT have
--On July 22, 2008 11:21:48 PM -0400 Steve Bertrand [EMAIL PROTECTED]
wrote:
Paul Schmehl wrote:
To the OP - here's what I get when testing from a FreeBSD box to one of
our servers:
[EMAIL PROTECTED] telnet hostname.utdallas.edu 3389
Connection closed by foreign host.
Does your server
16 matches
Mail list logo
