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.
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 2 years ago.
Improve this question
This might be a very basic question but I've been stucked for 2 days
I've bought the domain name AAA.xyz on Namecheap and I have my Golang web server running on my port :8095 (I've redirected my ports on my router so my server is accessible from everywhere with my public IP http://93.6.XXX.YYY:8095/)
How do I make my Namecheap domain name point to my IP adress with the right port so when I enter AAA.xyz on my browser I get response from my API ?
You have to edit your namecheap DNS settings to add an A Record, which will point to your server IP. That's enough to divert all traffic to your domain, to your server.
Although, unless it's not a production setup, it'd be better to let a reverse proxy server like nginx handle the incoming http traffic. Then you won't have to expose your port to the outside world either. (Unless you want to).
Install nginx. Add a proxy pass to your nginx config file which will route all requests coming to port 8095 to your application at 127.0.0.1:8095.
This will also help you when you have multiple go apps running on your server on different ports. You can use different URLs to point to different apps.
e.g. https://yourdomain.com/app1 will go to 127.0.0.1:8095
and https://yourdomain.com/app2 will go to 127.0.0.1:8096
Bonus: You can use Letsencrypt to provide your nginx server with an HTTPS certificate for free and then all communication with your applications will be happening through port 443 on HTTPS, without configuring every app to handle the certificate.
Also, open ports 80 and 443 in your firewall.
If you need any help with a specific step. I'll expand on that.
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.
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 8 years ago.
Improve this question
I have a web side hosted on IIS, windows 8 os. I can access from my browser to this page via these urls:
localhost/mysamplesite
192.168.21.10/mysamplesite
I can ping my ip address like this: ping 192.168.21.10
But I can not ping to 192.168.21.10/mysamplesite this command gives error: ping request could not find host 192.168.21.10/mysamplesite
Actually have another machine (192.168.21.45) that installed apache banchmark on. I want to test request from apache banchmark to my site. So I can not send request.
ab -n 1 -c -1 192.168.21.10/mysamplesite
This does not work.
As arco444 mentioned, you can't ping a website, just a computer itself.
ping is the first thing to try when troubleshooting network connectivity problems
ping 192.168.21.10
from the remove machine.
You can also try PsPing to test for connectivity to a certain port:
psping 192.168.21.10:80
however you can not use this to check for a particular resource on your web site.
Instead you have to use a tool to test for http traffic, Apache Benchmark is one of them, depending on the OS on the remote machine, there are many other tools.
If ping works, check the firewall settings on your Windows 8 machine.
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.