Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am running Ubuntu 14.04LTS and have FileZilla 3.7.3 installed, I also have a VM running WIN7 with WinSCP 5.5.1.
Under WIN7 when using WinSCP, in the editing dialog under the advanced tab there is a category “Connection” with two options, Proxy and Tunnel . The server I need to FTP or SFTP requires a tunnel, so my setting are Connection through ssh tunnel checked off as yes. The host name Tunnel.rr.net on port 22 and I have to enter in my user name and password, file protcall is set to SFTP, local tunnel port is set to Autoselect and no private key is needed. I know these setting are correct because it works just fine for me I my WIN7 VM, I select the server I need, I see it connect to the tunnel and than my server.
I am new to FileZillaile and the setting options seem to be a bit more extensive, the closest thing I see equivalent is under settings in Generic Proxy. So I set my tunnel host, user name and password which I know are correct because I have no issue with WinSCP.
When I set the Generic proxy to HTTP/1.1 using CONNECT method I get error, Error: Proxy error: HTTP response was absent
& Error: Could not connect to server, when I set it to SOCK 5 I get an error Error: Proxy error: SOCKS proxy returned unexpected version
& Error: Could not connect to server.
Again, I am new to FileZilla so it must be a setting that missing glaring because it is too simple under WinSCP.
So what would the equivalent of “tunnel” be on with WinSCP , in FileZilla?
FileZilla does not support anything equivalent to WinSCP SSH tunneling feature.
You can of course tunnel it through an external SSH tunnel. E.g. via PuTTY or OpenSSH ssh.
See my guide Setting up tunnel using PuTTY for SFTP/SCP session.
(The guide is for WinSCP, but works for any SFTP/SCP client.)
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I cant access a server Windows 2008 via RDP. I had to login to the VCenter where the server is located in order to have access. I verified that the Remote Host service is enabled and that the default port for RDP is 3389, the firewall is disabled(it cannot be blocking the connection), the FIPS cryptography is also disabled. So far the only thing that I have found is that when I telnet this way:
telnet [host_name] 3389 the connection is established.
When I telnet [ip_adress] 3389 the connection is also established, but when I telnet with just the host it doesn't allow me to connect:
telnet [host/ip_adress]
What could be the issue here??
Your last telnet is trying to connect to port 25 which is obviously not your target.
I think you should change the remote setting of your windows server 2008 from properties of PC and remote connection tab. There is 2 different security options for remote desktop which determines possibility of user's connections.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Probably has been asked before.
I've set up an FTP server in IIS on an Windows 8 machine using the following steps:
Installed IIS FTP services
Set a static public IP and a static internal LAN IP, set up Router
Created a new FTP site in IIS manager
created a root ftp folder, gave test_user r/w permissions
Required SSL, selected self-generated certificate
Entered the static LAN ip of my machine, used port 21
Enabled Basic authentication
Allowed authorization for "selected user": test_user
Logged successfully as test_user into the ftp server from within the local network.
Remoted to an outside server, browsed to [publicip]:21 and ftp://[mypublicip]
FAIL
Troubleshooting
Tried to access the FTP server from another PC on the LAN using the [PublicIP]:[PortNumber]
Turned off Windows firewall
No SSL
Basic Authentication, same test_user
Connected my computer directly to WAN, without router (I have an ethernet line to WAN, no modem - so I could just plug in the cable)
tried a different port for the FTP server (1342)
checked my public IP
remoted to the same server, tried browsing for my FTP again
went through several combinations of the above steps. at one point, the combination contained all of the troubleshooting steps.
FAIL
So no matter what I did, I could not access the FTP server remotely. Really mystified.
What could I have done wrong? Can the ISP block FTP even if you use non-standard ports?
Turns out you can access the FTP server when connected directly to the modem. I accidentally forgot to change site bindings (wrong ip) in IIS before changing the network connection. Of course I still can't connect through the router, with the firewall disabled. The issue is the router (or maybe Im an idiot) and I can't find any solution aside from trying another router.
Is your router translating the public IP down to the internal lan IP? This is typically done through a NAT rule in the router to tell it where to send the public traffic to inside your network.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a unix class in school and we need to log into the server which is an address like:
something.something.ac.il
in this connection the other students had to download putty , and they use telnet too...
From what I know I can use mac terminal to connect to the school server with ssh, i'v seen some posts say to do something like: ssh username#something.something.ac.il but this docent work for me...I get an error:
ssh: connect to host something.something.ac.il port 22: Operation timed out
I know my port is 23, and we use telnet..
Please help me to log in through terminal...tnx!
I use an app called DOC that works fine that its configurations looks like this:
but i want to use terminal
According to your figure - you are connecting to a telnet server as tripleee suggested. From your mac terminal you should be able to connect using:
telnet something.something.ac.il 23
and you should get prompted for a username and password. Or you could do:
telnet -l username something.something.ac.il 23
In the odd chance that your university is using ssh from a different port (it's not that uncommon, but it would be uncommon to use a port designated to another service). You can specify the port number with ssh on the command-line:
ssh user#something.something.ac.il -p 23
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm a newbie in working with remote servers and in working with FreeBSD. I want to connect to the FreeBSD running on a virtual machine on my Windows 7 in order to be able to see the files with an explorer interface and be able to copy/paste files to and from it.
I have done this before a while ago using WinSCP but that time it took me 3 days to figure out the configurations I need to make the connection and unfortunately I can't remember them now and do not have another 3 days to waste!!
In my active networks I see to VMware Network adaptors (VMware is the virtual machine I am using) which have the IPv4s: 192.168.134.1 and 192.168.80.1 and when I run "ifconfig" on my virtual FreeBSD there is no IP address (except inet 127.0.0.1). The hostname of FreeBSD is "FreeBSD1" .
WinSCP requires me to fill in a file protocol which I think should be FTP **(correct me if I'm wrong; the other options are SFTP and SCP), a port number (which it sets to 21 by default for FTP) a hostname which I have tried "FreeBSD1", "192.168.134.1" and "192.168.80.1" with my username(root) and password.
When I use the hostname "FreeBSD1" I get the error:
"The requested name is valid, but no data of the requested type was found.
Connection failed."
and for the other two I get:
"No connection could be made because the target machine actively refused it.
Connection failed."
The only thing is, as far as I remember, last time I tried (and succeeded after 3 days) "ifconfig" would show an IP which I think I used as hostname.
** For FTP it also requires an encryption which I set to no encryption. The other options are "SSL/TLS Implicit", "SSL Explicit" and "TLS Explicit".
Any help would be appreciated!
Your Windows machine does not recognize the FreeBSD1 hostname ("The requested name is valid, but no data of the requested type was found" error). So there's no point trying that further.
But it seems that the IPs work, just the FTP port 21 is not open ("No connection could be made because the target machine actively refused it" error).
I would actually not expect that FreeBSD has unencrypted FTP port opened by default. I guess you will have more luck with SFTP (SSH).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am able to ping the IP-address of a machine but I am unable to establish a remote desktop connection . When I try to do so it says:
Remote Desktop can't connect to the remote computer for one of these
reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled."
...any help?
If you can ping it, it means it's turned on. If you can ping it, it means the computer is available on the network... which one of the possibility remains? Only one.
Check your firewall rules. Check that VNC Server (or whatever service are you trying to use is running properly). Without other details, our answer can't be more precise.
However, this question is likely to be migrated to http://serverfault.com.
I am assuming you haven't turned off the remote computer, so let's look on the other parts of the error message, i.e. 1) and 3).
As part 1) of the message suggests: Most likely you haven't enabled remote access on the remote computer yet.
How you can enable it, is described here on the SuperUser forum.
Regarding the other reason mentioned by the error message ("2) The remote computer is not available on the network"):
The link above also describes how you can change the default listening port 3389 for RDP (remote desktop protocol) in case it is blocked by the firewall.
Please check as well, if you need a VPN tunnel to establish a remote connection. This is the case in most corporate networks (especially if you're working from home).
Last, but not least, check that your network is running as it should (VDSL or cable modem/router) - keep in mind your modem/router usually also has a firewall: check it and find out if it is blocking.
Finally, one reason could be that the hostname you entered cannot be resolved by DNS (domain name service). Check if you configured DNS correctly on both PCs - and as workaround you can use the remote PCs IP address to connect.