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).
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 11 months ago.
Improve this question
I'm having a hard time viewing Wildfly welcome page on port 8080 + tried apache on port 80 too, and they timeout. I can ssh to the server and using (curl localhost:8080) and (curl localhost:80) show Wildfly and apache welcome pages respectively. I have checked the Security List and Security groups and even opened ALL traffic just to see if they are causing this problem, but unfortunately the problem still there.
I'm using ubuntu 20.04 image and the UFW (firewall) is inactive so the problem isn't from there.
By default every oracle instances come with 2 firewall.
Hardware Firewall (Known as VCN)
Software Firewall (They use a very hard iptables rules and regular ufw doesn't work with that.)
The 2nd option is very annoying and also took me about 3 days to solve my problem. You can follow my following instructions and hopefully it will also fix your problem.
1st you have to open the port on the Hardware Firewall (VCN) and when you believe you have opened the port then by login to the server using ssh use this command to clear the default oracle iptables rule.
sudo iptables -F
But remember whenever you will reboot the server you will need to again run the flash command. So if you don't want to run this command every time after server reboot. Then after running the flash command run this command to save your flashed iptables rules.
sudo netfilter-persistent save
So, you will not need to run the iptables falsh command every time on the startup of the server.
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 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.)
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 2 years ago.
Improve this question
Please forgive the embarrassingly dumb newb question.
Here's the scenario:
As part of a task I have to SSH into a server and create some files. I was given the servers name (some.server.com) and an SSH key (id_rsa.username) to use. I am told to use the username and the provided key to login. Since I am relatively new to the workings of SSH this is what I have done:
I have downloaded id_rsa.username to my Downloads directory.
I have tried loggin in with
ssh -i downloads/id_rsa.username username#some.server.com
But I get ssh: connect to host some.server.com port 22: Operation timed out
I have tried using port 2222 and also 11234 ( I used that port once on a different server).
Is there anything I am doing wrong on my end? I don't have access the server admin to ask any questions so I have to try to figure this out myself.
in my case, I change the rule of ufw, and that rule ban the ssh connect
so run sudo ufw allow sshsolve the problem
"Operation timed out" means that you're not making a TCP connection to the remote server. The remote computer may be down, or there may be a firewall blocking access to the the remote server, or your local computer may not have suitable network access. It's not really possible to say what the exact problem is, based on the information here.
If you're in a corporate network, you should contact your local computer support staff for assistance. It's not unheard of for companies to block outgoing SSH from their corporate network.
Otherwise, if you need help troubleshooting network connectivity, you'd probably get better results on Superuser.
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.