Peter Bowen wrote:
I assume that remote desktop works within the office... Are you using
the web connection to login or are you going direct?
-Peter
Yes, it works from other machines on the same private network. I am
trying to connect remotely from the Remote Desktop Client on my Windows
XP P
I assume that remote desktop works within the office... Are you using
the web connection to login or are you going direct?
-Peter
Kenneth Burgener wrote:
Grant Robinson wrote:
As Doran pointed out, if you are using these rules, then from an
outside box you would do:
telnet your.firewall.ip 800
Grant Robinson wrote:
As Doran pointed out, if you are using these rules, then from an outside
box you would do:
telnet your.firewall.ip 8001
to get to 192.168.0.117:3389. Do you see? Doing:
telnet your.firewall.ip 3389
does nothing, because you firewall is listening on port 8001 and
forwardin
On Mar 23, 2005, at 7:54 AM, Kenneth Burgener wrote:
David Smith wrote:
[EMAIL PROTECTED]:~$ telnet xxx.xxx.xxx.xxx 3389
Trying xxx.xxx.xxx.xxx...
telnet: Unable to connect to remote host: Connection refused
I hate to ask the obvious, but is anything actually listening on port
3389
on the desinat
David Smith wrote:
[EMAIL PROTECTED]:~$ telnet xxx.xxx.xxx.xxx 3389
Trying xxx.xxx.xxx.xxx...
telnet: Unable to connect to remote host: Connection refused
I hate to ask the obvious, but is anything actually listening on port 3389
on the desination machine? This woulnd't be LDAP would it?
It is f
Doran Barton wrote:
Make sure your iptables rules allow traffic to a port in addition to
forward it.
As you can see in the script all traffic is currently set to ACCEPT. So
unless if there is something I am missing (which I think I am, and is
the reason I posted my question) then I haven't any i
> [EMAIL PROTECTED]:~$ telnet xxx.xxx.xxx.xxx 3389
> Trying xxx.xxx.xxx.xxx...
> telnet: Unable to connect to remote host: Connection refused
I hate to ask the obvious, but is anything actually listening on port 3389
on the desination machine? This woulnd't be LDAP would it?
--Dave
.
Not long ago, Kenneth Burgener proclaimed...
> I am having issues getting port 3389 to forward to a machine behind my
> Linux firewall/routing machine. It is forwarding port 80 and 8080 fine,
> but 3389 does not forward. I have attached the NAT/iptables script below.
Make sure your iptables rule
I am having issues getting port 3389 to forward to a machine behind my
Linux firewall/routing machine. It is forwarding port 80 and 8080 fine,
but 3389 does not forward. I have attached the NAT/iptables script below.
I am able to connect from the firewall/routing machine:
llama:~# telnet 192.168.
