Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Port forwarding to windows rdp Post 302909730 by in2nix4life on Friday 18th of July 2014 04:02:38 PM
Old 07-18-2014
Not enough information to describe what you're trying to do.

If you're trying to go from Windows machine to another, then you'd need an SSH server installed to do the port forwarding.

Are you using a Linux box to perform the forwarding?

Is this going from an external machine to an internal one?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

iptables: forwarding a port

I've been googling for a while now, trying to forward port 3000 to port 80.... In the past I used to DLink router to forward port 3000 to 80. I recently finished (well, is it ever done anyhow?) setting up my linux box and got it acting as a router. I want to continue to run Apache on port 80... (1 Reply)
Discussion started by: meeps
1 Replies

2. UNIX for Advanced & Expert Users

port forwarding

Hi, I have to install an application that has a built in tftp server. Tftp comes in on port 69. As i am not installing this application as a root user i am running into trouble because only the root user can listen to ports < 1024. So changing the port i listen to to one greater than 1023 isn't... (1 Reply)
Discussion started by: imloaded24_7
1 Replies

3. UNIX for Advanced & Expert Users

Port forwarding

Hi I want to set up port forwarding from one network to another network. I already have this configured on the Linux box using iptables. iptables -t nat -A PREROUTING -p tcp -i eth1 --dport 1521 -j DNAT --to 10.218.146.230 iptables -A FORWARD -p tcp -i eth1 -d 10.218.146.230 -j ACCEPT ... (2 Replies)
Discussion started by: slash_blog
2 Replies

4. IP Networking

SSH Port Forwarding - sharing the same port

Hi Linux/Unix Guru, I am setting Linux Hopping Station to another different servers. My current config to connect to another servers is using different port to connect. e.g ssh -D 1080 -p 22 username@server1.com ssh -D 1081 -p 22 username@server2.com Now what I would like to have... (3 Replies)
Discussion started by: regmaster
3 Replies

5. UNIX for Advanced & Expert Users

port forwarding from unix to windows

Hi, can anyone please tell me how can i do port forwarding from unix box to windows box. Which command will be used for this one. thanks in advance. Arpit (1 Reply)
Discussion started by: thearpit
1 Replies

6. Red Hat

Is there a way to use windows RDP with red hat 6

Besides installing VNC on the red hat server which i know i can do, is there any RDP servers (using the windows rdp client) to remote control a red hat 6.2 server? Thanks in advance for this. (1 Reply)
Discussion started by: frankkahle
1 Replies

7. IP Networking

VPN ssh access over RDP port?

Guys, Can I use an open RDP port to gain ssh access to my Linux server running the other side of our firewall? I work from home on the odd occasion, we only have RDP port 3389 available once logged into the VPN. I would rather ssh into my workstation without the need for a desktop display. ... (3 Replies)
Discussion started by: general_lee
3 Replies

8. IP Networking

Port forwarding issue

hi guys i have a simple question ! i have two ips . a valid and internal(172.16.11.2) i want to use port forwarding to forward any request to valid IP port 8001 to internal ip port 80 . i use this rule : sysctl -w net.ipv4.ip_forward=1 iptables -t nat -A PREROUTING -p tcp... (1 Reply)
Discussion started by: mhs
1 Replies

9. UNIX for Advanced & Expert Users

Help on port forwarding please..

Hi experts, We have windows machine ( A ) in one network & 2 Linux Servers ( B & C ) in another network. There is a firewall between these 2 networks and SSH (TCP/22) & HTTPS (TCP/443) are allowed from A to B only (but not to C). There is no personal firewall / iptables running on any machine.... (1 Reply)
Discussion started by: magnus29
1 Replies

10. IP Networking

Port Forwarding not working

Hello Gurus, I have configured port forwarding at router. But after configuration I am not able to connect the computer from outside/Over internet/Remote desktp from other computer. Could you please advice? Thanks- Pokhraj (2 Replies)
Discussion started by: pokhraj_d
2 Replies
dropbear(8)						      System Manager's Manual						       dropbear(8)

NAME
dropbear - lightweight SSH2 server SYNOPSIS
dropbear [-FEmwsgjki] [-b banner] [-d dsskey] [-r rsakey] [-p [address:]port] DESCRIPTION
dropbear is a SSH 2 server designed to be small enough to be used in small memory environments, while still being functional and secure enough for general use. OPTIONS
-b banner bannerfile. Display the contents of the file banner before user login (default: none). -d dsskey dsskeyfile. Use the contents of the file dsskey for the DSS host key (default: /etc/dropbear/dropbear_dss_host_key). Note that some SSH implementations use the term "DSA" rather than "DSS", they mean the same thing. This file is generated with dropbear- key(8). -r rsakey rsakeyfile. Use the contents of the file rsakey for the rsa host key (default: /etc/dropbear/dropbear_rsa_host_key). This file is generated with dropbearkey(8). -F Don't fork into background. -E Log to standard error rather than syslog. -m Don't display the message of the day on login. -w Disallow root logins. -s Disable password logins. -g Disable password logins for root. -j Disable local port forwarding. -k Disable remote port forwarding. -p [address:]port Listen on specified address and TCP port. If just a port is given listen on all addresses. up to 10 can be specified (default 22 if none specified). -i Service program mode. Use this option to run dropbear under TCP/IP servers like inetd, tcpsvd, or tcpserver. In program mode the -F option is implied, and -p options are ignored. -P pidfile Specify a pidfile to create when running as a daemon. If not specified, the default is /var/run/dropbear.pid -a Allow remote hosts to connect to forwarded ports. -W windowsize Specify the per-channel receive window buffer size. Increasing this may improve network performance at the expense of memory use. Use -h to see the default buffer size. -K timeout_seconds Ensure that traffic is transmitted at a certain interval in seconds. This is useful for working around firewalls or routers that drop connections after a certain period of inactivity. The trade-off is that a session may be closed if there is a temporary lapse of network connectivity. A setting if 0 disables keepalives. -I idle_timeout Disconnect the session if no traffic is transmitted or received for idle_timeout seconds. FILES
Authorized Keys ~/.ssh/authorized_keys can be set up to allow remote login with a RSA or DSS key. Each line is of the form [restrictions] ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIgAsp... [comment] and can be extracted from a Dropbear private host key with "dropbearkey -y". This is the same format as used by OpenSSH, though the restrictions are a subset (keys with unknown restrictions are ignored). Restrictions are comma separated, with double quotes around spaces in arguments. Available restrictions are: no-port-forwarding Don't allow port forwarding for this connection no-agent-forwarding Don't allow agent forwarding for this connection no-X11-forwarding Don't allow X11 forwarding for this connection no-pty Disable PTY allocation. Note that a user can still obtain most of the same functionality with other means even if no-pty is set. command="forced_command" Disregard the command provided by the user and always run forced_command. The authorized_keys file and its containing ~/.ssh directory must only be writable by the user, otherwise Dropbear will not allow a login using public key authentication. Host Key Files Host key files are read at startup from a standard location, by default /etc/dropbear/dropbear_dss_host_key and /etc/dropbear/drop- bear_rsa_host_key or specified on the commandline with -d or -r. These are of the form generated by dropbearkey. Message Of The Day By default the file /etc/motd will be printed for any login shell (unless disabled at compile-time). This can also be disabled per- user by creating a file ~/.hushlogin . ENVIRONMENT VARIABLES
Dropbear sets the standard variables USER, LOGNAME, HOME, SHELL, PATH, and TERM. The variables below are set for sessions as appropriate. SSH_TTY This is set to the allocated TTY if a PTY was used. SSH_CONNECTION Contains "<remote_ip> <remote_port> <local_ip> <local_port>". DISPLAY Set X11 forwarding is used. SSH_ORIGINAL_COMMAND If a 'command=' authorized_keys option was used, the original command is specified in this variable. If a shell was requested this is set to an empty value. SSH_AUTH_SOCK Set to a forwarded ssh-agent connection. AUTHOR
Matt Johnston (matt@ucc.asn.au). Gerrit Pape (pape@smarden.org) wrote this manual page. SEE ALSO
dropbearkey(8), dbclient(1) http://matt.ucc.asn.au/dropbear/dropbear.html dropbear(8)
All times are GMT -4. The time now is 05:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy